# Draft a Utility Outage Notice Without Inventing Details

> A reusable prompt that turns your supplied outage facts into a plain-language resident notice, with an explicit section for unconfirmed details.

## Install

Copy the content below into your project:

# Draft a Utility Outage Notice Without Inventing Details

A reusable prompt that turns your supplied outage facts into a plain-language resident notice, with an explicit section for unconfirmed details.

## Start here

Gather your facts, then paste the prompt below into an ordinary AI chat that accepts text. Type your outage details where the prompt asks for inputs. Nothing else is needed: no terminal, no account setup, no integrations.

What to paste with the prompt: utility and service type; confirmed start and any confirmed end; affected streets or zones exactly as written; repair status; approved safety instructions; the contact method; notice date/time; and the intended channel.

## Introduction

This prompt writes one resident-facing notice from only the details you supply. It never guesses a repair window, adds nearby streets, or invents emergency numbers. Anything missing or contradictory is collected under a clearly labelled unconfirmed section, so a staff member can review before posting or sending.

## Check the output

- Every street and time in the draft matches what you typed.
- The status line repeats your status; it is not upgraded to a restoration time.
- No contact method or health advice appears that you did not supply.
- The unconfirmed list covers every blank or conflicting item you entered.
- If a check fails, the draft stops and names the failing check instead of guessing.

## Limitations and permissions

This prompt only prepares a draft for human review. It does not post, send, call, page, or schedule anything. Do not paste personal resident data, private phone numbers, or internal incident notes you are not cleared to share with an external tool. Follow your organisation's approval rules before publishing anything.

## FAQ

**What if I leave an input blank?**
The prompt marks that item as unconfirmed in a separate section rather than filling it in.

**What if two of my details conflict?**
It keeps both and writes a "Needs confirmation" line instead of choosing one.

## Verification note

Source reviewed; runtime not tested.

## Source and thanks

Original TokRepo prompt, licensed CC BY 4.0. Reference context: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>).

## Complete reusable prompt

You are helping draft a utility service interruption notice for residents. Use only the details I supply. Do not invent, estimate, or round any outage window, street name, repair status, cause, crew activity, restoration time, compensation, contact channel, or health claim. This prompt prepares a draft for human review; it does not post, send, call, page, or schedule anything.

Inputs I will provide:
1. Utility and service type (for example, water, power, gas, sewer, internet).
2. Confirmed outage window: start date/time and, if known, expected end date/time or duration; label which parts are confirmed.
3. Affected areas exactly as supplied: street names, blocks, building numbers, or service zones. Copy them without adding nearby streets.
4. Repair status as supplied: reported, crew dispatched, repair in progress, parts needed, scheduled, restored, or unknown.
5. Safety or service instructions already approved by the utility (for example, boil-water notice, do not use elevators, keep refrigerator closed). If none are supplied, write "No additional safety instructions supplied."
6. Who residents should contact and how, exactly as supplied. If none is supplied, write "Contact method not yet supplied."
7. Notice date and time.
8. Intended channel: SMS, email, website banner, printed door hanger, or social post.
9. Optional: a short reference or incident number.

Task:
Write one notice in plain language, suitable for the chosen channel. If the channel is SMS, keep the main notice to roughly 300 characters and place anything longer under a separate "Full version" heading. Otherwise aim for 120-220 words.

Required structure:
- Headline: [Utility/service] interruption in [affected area].
- What is affected: service type and area, using exactly the supplied names.
- When: confirmed start and any confirmed expected end, with time zone if supplied.
- Current status: one sentence restating the supplied repair status, or "Status not yet confirmed."
- What residents should do: only supplied safety or service instructions. If none, say so plainly.
- Contact: only the supplied method.
- Issued: notice date and time.
- A final section titled "Unconfirmed or missing details" listing every item above that was not supplied or was marked unconfirmed. If everything is confirmed, write "None."

Rules:
- Never turn "repair in progress" into a restoration time, and never turn "crew dispatched" into "almost fixed."
- Do not use phrases such as "we expect," "should be back by," "most customers," or "brief" unless those exact words and figures are supplied.
- Do not add emergency numbers, websites, or health advice from general knowledge.
- Do not blame weather, equipment, or anyone unless the cause is supplied.
- If two supplied details conflict, do not choose one. Put both in the unconfirmed section and write "Needs confirmation: [detail A] vs [detail B]."
- Keep sentences short. Avoid jargon. Expand an abbreviation only if I supplied its expansion.
- Put the notice text in a block I can copy, followed by the unconfirmed list. Do not add a preamble or commentary.
- After the notice, add "Review checks" confirming: every street and time appears in my input; the status matches the supplied status; no restoration estimate was added; the contact method matches exactly; and unconfirmed items are listed. If any check fails, say which one and stop rather than guessing.

Fictional mini example:
Input: Utility: water. Confirmed window: Tuesday 7:00 a.m. to no confirmed end. Affected: Oak Street between 2nd and 5th, and Pine Court. Status: crew dispatched, valve repair not started. Safety instructions: none supplied. Contact: city water line, supplied number. Notice time: Tuesday 6:40 a.m. Channel: SMS plus website.
Expected output shape: Headline; what is affected; when; status as "crew dispatched, valve repair not started"; "No additional safety instructions supplied"; contact; issued time; "Unconfirmed or missing details: expected end time, cause, whether other streets are affected." Then review checks.

Failure test for this example: if the draft says water will return by noon, or adds a nearby street, or omits the unconfirmed end time, the notice fails and must be corrected before sending.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 不编造细节，起草公用事业停供通知

一个可复用的提示词，把你提供的停供事实整理成通俗易懂的居民通知，并明确列出尚未确认的细节。

## 开始使用

先把手头的事实整理好，然后把下面的提示词粘贴到能接受文字的普通 AI 对话中。在提示词要求输入的位置填写你的停供信息。不需要终端、账号配置或任何集成。

需要连提示词一起提供的内容：公用事业与服务类型；已确认的开始时间以及已确认的结束时间（如有）；受影响的街道或区域（按原文照抄）；维修状态；已批准的安全提示；联系方式；通知日期与时间；以及发布渠道。

## 简介

这个提示词只根据你提供的细节，撰写一份面向居民的通知。它不会猜测维修时间、不会添加附近街道，也不会编造紧急电话。任何缺失或相互矛盾的信息都会集中放在标注清楚的“未确认”部分，方便工作人员在发布或发送前复核。

## 检查输出

- 草稿中的每一条街道和时间都与你输入的一致。
- 状态一行重复你提供的状态，没有被升级成恢复时间。
- 没有出现你未提供的联系方式或健康建议。
- 未确认列表涵盖你留下的每一项空白或冲突信息。
- 如果某项检查不通过，草稿会停止并指出是哪一项，而不是猜测。

## 限制与权限

该提示词只用于生成供人工审阅的草稿，不会发布、发送、拨打电话、呼叫或安排任何事情。请勿粘贴居民个人数据、私人电话号码，或你不被允许与外部工具共享的内部事件记录。发布前请遵守你所在机构的审批规定。

## 常见问题

**如果某项输入留空会怎样？**
提示词会把它列入单独的未确认部分，而不是替你想一个答案。

**如果两项信息互相冲突怎么办？**
它会同时保留两项，并写出“需要确认”的提示，而不是二选一。

## 核实说明

来源已审阅；运行时未测试。

## 来源与致谢

TokRepo 原创提示词，采用 CC BY 4.0 许可。参考背景：[ChatGPT 发行说明](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)。

## 完整可复制提示词

你正在帮助起草一份面向居民的公用事业服务中断通知。只使用我提供的细节。不要编造、估计或四舍五入任何停供时间窗、街道名称、维修状态、原因、施工人员活动、恢复时间、补偿、联系渠道或健康声明。此提示词生成一份供人工审阅的草稿；它不会发布、发送、拨打电话、呼叫或安排任何事情。

我将提供的输入：
1. 公用事业与服务类型（例如，水、电、燃气、下水道、互联网）。
2. 已确认的停供时间窗：开始日期/时间，以及如果已知，预计结束日期/时间或持续时间；标明哪些部分是已确认的。
3. 受影响区域（按提供的原文照抄）：街道名称、街区、楼号或服务区域。照抄，不要添加附近街道。
4. 维修状态（按提供的内容）：已报告、已派施工人员、维修进行中、需要零件、已安排、已恢复或未知。
5. 已由公用事业单位批准的安全或服务提示（例如，烧水通知、不要使用电梯、保持冰箱关闭）。如果没有提供，写“未提供额外安全提示。”
6. 居民应联系谁以及如何联系（按提供的原文照抄）。如果没有提供，写“尚未提供联系方式。”
7. 通知日期与时间。
8. 发布渠道：短信、电子邮件、网站横幅、印刷门挂卡或社交帖子。
9. 可选：简短参考号或事件编号。

任务：
用平实语言撰写一份通知，适合所选渠道。如果渠道是短信，将主通知控制在约 300 个字符以内，并将任何较长的内容放在单独的“完整版”标题下。否则以 120-220 个词为目标。

必需结构：
- 标题：[公用事业/服务] 在 [受影响区域] 的中断。
- 受影响内容：服务类型和区域，使用提供的名称原文照抄。
- 时间：已确认的开始时间以及任何已确认的预计结束时间，如果提供了时区则包含时区。
- 当前状态：一句话重述所提供的维修状态，或“状态尚未确认。”
- 居民应做什么：仅提供所提供的安全或服务提示。如果没有，直接说明。
- 联系方式：仅提供所提供的方式。
- 发布：通知日期与时间。
- 最后一个部分标题为“未确认或缺失细节”，列出上述每一项未提供或标记为未确认的内容。如果一切都已确认，写“无。”

规则：
- 绝不把“维修进行中”变成恢复时间，也绝不把“已派施工人员”变成“快修好了”。
- 不要使用诸如“我们预计”、“应该会在此之前恢复”、“大多数客户”或“短暂”之类的措辞，除非这些确切的词和数字已提供。
- 不要从一般知识中添加紧急电话、网站或健康建议。
- 不要归咎于天气、设备或任何人，除非原因已提供。
- 如果两项提供的细节相互冲突，不要选择其中一个。把两者都放在未确认部分，并写“需要确认：[细节 A] 与 [细节 B]。”
- 保持句子简短。避免术语。只有当提供了缩写扩展时才展开缩写。
- 将通知文本放在我可以复制的块中，后面跟上未确认列表。不要添加前言或评论。
- 通知之后，添加“审阅检查”，确认：每一条街道和时间都出现在我的输入中；状态与所提供的状态一致；没有添加恢复估计；联系方式完全一致；未确认项目已列出。如果任何检查不通过，指出是哪一项并停止，而不是猜测。

虚构小示例：
输入：公用事业：水。已确认时间窗：周二上午 7:00 至无确认结束时间。受影响：2nd 与 5th 之间的 Oak Street，以及 Pine Court。状态：已派施工人员，阀门维修尚未开始。安全提示：未提供。联系方式：城市供水热线，已提供号码。通知时间：周二上午 6:40。渠道：短信加网站。
预期输出形态：标题；受影响内容；时间；状态为“已派施工人员，阀门维修尚未开始”；“未提供额外安全提示”；联系方式；发布时间；“未确认或缺失细节：预计结束时间、原因、其他街道是否受影响。”然后是审阅检查。

本例的失败测试：如果草稿写到中午会恢复供水，或添加了一条附近街道，或漏掉未确认的结束时间，该通知即不通过，必须在发送前更正。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/draft-utility-outage-notice-without-inventing-details-ac1fc216
Author: Prompt Lab