Weather Delay Field Note: Minimum Facts Before an AI Customer Update
A weather stop is easy for a model to turn into a promise. The technician messages "rain, not setting the unit," and the office asks for a customer email. The draft says the crew will return tomorrow morning, the price is unchanged, and nobody needs to be home. It may also explain the sky in language nobody on site used, or fold in an apology that sounds like the company missed the appointment. None of those sentences require a careless writer. They require a gap. The office asked for an update, and the note never said which facts were real. The difference between a careful weather notice and a confident fiction is the field note written before the model drafts.
This guide is that note: the facts to collect, or mark UNKNOWN, before any AI drafts a customer update about work stopped or moved because of conditions at the site. It is not a supplier backorder. If the part has not arrived, use the material delay field note instead of describing a missing shipment as weather. It is not the appointment reminder guide, which is about messages sent before a visit to confirm it. It is not a no-show note: if the customer was not home and the crew could have worked, do not blend "you were out" into a weather story. It is not an equipment-breakdown note: a failed company truck or a dead tool is a different cause and needs its own facts. The dispatch workflow guide is about how the office moves the board. This page is about the minimum record one job needs before a model is allowed to speak to the customer about the stop.
Why a weather note has to exist before the AI update
Weather language creates schedule risk when it is casual. "We'll slide you to tomorrow" feels helpful in a truck and becomes a new arrival promise in an inbox. "No charge for the return" feels polite and becomes a money position the owner has not made. "The storm is over, so we're fine to finish today" feels current and may contradict the person who is actually looking at a flooded pad. A model is good at smoothing those impulses into a paragraph. It is not on the roof, at the pad, or in the owner's pricing conversation.
Read the job pointer and the appointment already given to the customer before anyone prompts a model. Classify the update in office language: internal hold only, customer notice that today's window is stopped with no new date, or customer notice that includes a window the approver has already set. If the owner has not chosen, the honest draft is an internal summary, not a customer email.
Treat the AI as a writer working from the field note, not as a forecaster, a dispatcher, or a person who renegotiated the visit. It can arrange sentences the office already decided. It cannot decide that lightning "usually passes in an hour," that a wet pad is safe, or that the customer will not mind a Saturday. Those decisions stay with named people.
A weather email also sits next to private details the model does not need. Gate codes, alarm words, card numbers, and supplier or dispatch logins are not what makes the notice clear. The NIST small-business privacy page, retrieved 2026-11-14, is aimed at small businesses that want to protect customer privacy and points them toward the NIST Privacy Framework as a place to start. The NIST cybersecurity basics page, also retrieved 2026-11-14, says cybersecurity is a continuous process and lists everyday steps that include knowing which assets matter, training people, and keeping sensitive accounts behind strong authentication and unique passphrases. A customer-update draft is one of those everyday assets. The prompt should carry the job label and the condition, not the secrets that protect the business.
The minimum facts to collect first
Before prompt time, fill each field or write UNKNOWN and the name of the person who can resolve it:
- Job pointer — job or work-order ID, and the customer or property label the office already uses. A street nickname is not a pointer. Do not add a new phone number or email that is not already on the job file.
- Update purpose — internal hold only; customer notice that the current window is stopped and no new date exists; customer notice with an approved new window; or not yet decided. A second purpose, such as a change in scope, is a different note.
- Observer — who saw the condition, at what time, and whether they were on site. A remembered comment from someone who was not there is not an observation.
- Condition, in the observer's words — what they saw or refused to do, quoted or closely paraphrased. Do not upgrade that into a storm name, a rainfall total, or a safety conclusion the observer did not state. If the office is also relying on a forecast, name the source, the time it was read, and the words the approver is willing to repeat. Otherwise the forecast is UNKNOWN and stays out.
- Site decision — work stopped, work continued, or UNKNOWN, and who made that call. The model does not get to reverse it.
- Dates already promised — the arrival or work window already told to the customer, and where that promise lives: confirmation text, proposal, or dispatch board. If none was made, write NONE.
- What was already done — one or two lines: not started, partial, or finished enough that the customer could misunderstand. Do not invent a percent complete.
- What was said on site — if anyone spoke to the customer, write the substance. The email must not contradict a sentence the technician already used. If nobody spoke to them, write that.
- Customer presence — home, not home, or UNKNOWN. If the real problem is a no-show rather than conditions, stop and use a no-show note. Do not tuck absence into a weather paragraph to soften it.
- New window — only a date and window the approver has set. Otherwise UNKNOWN. "When it dries," "tomorrow," and "first available" are not windows.
- Crew and other-trade impact — what was held on the internal calendar, and whether that hold has been released. Other trades waiting on this visit get an internal note, not a guessed ETA.
- Materials pointer — one line: on the truck, on site, or not relevant. This keeps the draft from turning into a backorder story. If the material itself is late, switch to the material-delay note.
- Price and contract position — no money language on this send; a possible change the owner has not decided; or UNKNOWN. Do not invent a credit, a waived fee, or a statement that the contract price is unchanged unless the approver wrote that position. This note is not legal, tax, or contract advice.
- Office position — the send/no-send choice: internal hold, customer notice without a new date, or customer notice with the approved window. If position is blank, do not prompt a customer email.
- Do-not-promise list — the sentences that must not appear: a specific return day, a "no charge" line, a claim the customer caused the delay, a storm category nobody recorded, or the original window restated as if the crew were still coming.
- Approval owner — who must approve customer language, any date the customer will hear, and any money sentence.
- Channel and timing — how the update will be sent, to which contact already on file, and when a reply is reasonably expected. Do not harvest a new address from an old thread "for context."
- Photo pointer — if pictures exist, point to them by job and time. Do not paste them into the prompt. What a photo is allowed to support belongs on the jobsite photo field note.
- PII and secret check — confirm the prompt excludes payment card data, government IDs, gate or alarm codes, full account numbers, and portal or mailbox passwords.
Office position is the field that keeps a stopped visit from becoming a new appointment. If the owner has not decided whether this send is an internal hold or a customer notice, the model will decide by sounding helpful. Helpful, in this setting, usually means a date. Write the position before the prompt exists.
Observer words beat atmosphere. "Lightning nearby and standing water at the pad, Riley will not set the unit" can be checked against the person who was there. "Severe weather made the site unsafe under industry practice" cannot. The second sentence imports a standard and a conclusion the note never earned.
An illustrative example
Several gaps still govern the draft even though the story is simple. Riley stopped the work and said so at the door, without naming a return day. Camille has not created a new window. The condenser is on the truck, so a sentence about a factory backorder would be a different job's story. The original 8:00–12:00 window is a promise that already failed for today. It belongs in the note so the email can acknowledge it. It does not belong in the email as a fresh arrival time. The forecast was never recorded, so the draft does not get to sound like a meteorologist.
A draft that stays inside this note can say, in substance: we were scheduled for Thursday 2026-11-19 between 8:00 and 12:00 on job 5521; our technician stopped the work because of lightning in the area and standing water at the pad; we do not have a new arrival window yet; the office will send one after it is set; this matches what the technician said at the door. It cannot say the crew will be back Friday, that the return is free, that the customer should have expected this, or that the unit is delayed from the supplier.
Once Camille keeps the "no new date" position and Riley confirms the door sentence is complete, the field note is stable enough to prompt. If Camille later sets a window, that is an edit to the new-window field and a second approval, not a silent improvement by the model. If the pad photo is needed to explain the stop, open the photo field note first and decide what the picture is allowed to support. The picture itself stays out of the chat.
The earlier promise is on the note on purpose. Deleting Thursday's window from the prompt would make the new email look cleaner and would hide the sentence the customer is most likely to answer: "You told me this morning." A good weather notice accounts for the promise it is breaking. It does not pretend the morning text never existed.
A short sequence before anyone prompts the model
- Name the job and the update purpose — one sentence: "Job 5521, customer notice, today stopped, no new date." If purpose is not yet decided, stop.
- Read the observer line — who, when, on site or not, and the words actually used. A forecast without a named source is UNKNOWN.
- Separate the old window from the new window — write both. NONE and UNKNOWN are allowed. A hoped-for day is not a new window.
- Write what was already said — door conversation, or none. The draft has to live with that sentence.
- Check the lookalikes — if the part is not here, switch to the material-delay note. If the customer was absent and work could have proceeded, do not call it weather. If a company tool failed, say that cause plainly or leave it UNKNOWN. Do not rename that cause as weather.
- Set price position and the do-not-promise list — no money language, a written position, or UNKNOWN. Blank means the model will invent a courtesy.
- Prompt with the field note only — no forecast screenshots, no photo files, no full proposal if it contains payment data, no extra threads "for tone."
- Review by role — the observer checks the condition wording; the approver checks dates and money; the sender checks the address and that secrets stayed out.
- Save the packet — field note, old promise pointer, draft, edits, and the sent message, stored with the job file.
The sequence is short because most bad weather emails are position failures, not writing failures. A graceful paragraph drafted from an unresolved new window will still name a day. Fix the note, then draft.
Prompt rules that keep the model inside the note
When the note is complete enough to draft, give the model rules as strict as the facts:
- Use only the field note. If a fact is UNKNOWN, say the office is checking it or that no new window is set. Do not fill the gap from a typical weather day.
- Do not invent return dates, storm names, rainfall amounts, safety certifications, "all clear" claims, credits, waived fees, or percent-complete figures.
- Do not restate the old arrival window as if the crew were still on the way. Acknowledge it only if the note says the approver wants that promise mentioned as the one that stopped.
- If price position is "no money language," do not add a P.S. about cost, goodwill, or "no charge for the inconvenience."
- If office position is internal hold only, draft an internal summary, not a customer email.
- Do not assign fault to the customer, the sky, or another trade beyond what the observer and the presence field actually say.
- Do not describe materials as backordered unless the materials pointer says the problem is supply. On-the-truck is not a delay from a vendor.
- If a permit, photo, warranty, or punch-list sheet is the real next step, name that handoff and stop expanding this note into inspection results or closeout.
- Keep one purpose, one named office contact, and one reply path. After the draft, list every sentence that depends on a date or a money claim a human must match to the note.
That last list is the review. The approver should be able to point at each date and each money sentence and find it on the field note. Sentences with no field behind them come out before the message is sent.
Common failure patterns
The first failure is the invented return. The model sees a stopped morning and offers Friday, "tomorrow after it dries," or "first thing." Unless the new-window field contains that day and the approver's name, the sentence goes. A hopeful dispatcher is not an approved window.
The second failure is invented money. A waived trip fee, a courtesy credit, or a promise that the contract price is unchanged may be the right business decision later. It is not a sentence the model may add because the email felt cold. If the price field says no money language, the draft has no dollar signs and no fee words at all.
The third failure is blame, in either direction. "We would have finished if someone had been home" mixes a no-show into a weather stop. "You should have known the forecast" lectures a customer with a source the note may not even contain. Presence is its own field. If it says the homeowner was home, the draft does not imply otherwise.
The fourth failure is the borrowed backorder. A condenser on the truck is not a factory delay. Offices reach for supply language because it sounds more official than "standing water at the pad." Official is not the goal. The materials pointer is the goal. When the pointer says the part is on the truck, the material delay field note stays closed.
The fifth failure is forecast theater. Naming a storm, citing inches of rain, or declaring a site "unsafe by standard practice" without an observer sentence imports authority the company did not record. If a named person wants a forecast line included, the note quotes the source and the time. Otherwise the condition stays in the technician's words.
The sixth failure is repeating the original window as a live plan. In the example, 8:00–12:00 on 2026-11-19 is the promise that stopped. An email that says the crew is still arriving inside that window contradicts Riley's door sentence and the site decision. Acknowledgement is not the same as renewal.
The seventh failure is prompt oversharing. Pasting a forecast app screenshot, a dispatch board, or a pad photo can drag account names, other customers' jobs, gate codes, and card notes into a chat log. Point to the photo. Follow the jobsite photo field note before any description of what the picture shows. Leave passwords and payment data out. The cybersecurity basics page treats training and care around sensitive accounts as ordinary business hygiene, not as a special project. The person who pastes the prompt is part of that hygiene.
The eighth failure is using a weather note to close a different job. A stopped condenser set is not a passed inspection, a finished warranty diagnosis, or a punch list. If the customer is waiting on a permit date, use the permit and inspection status field note. If the visit was a warranty call and the finding matters, use the warranty service visit field note for that finding. This note only carries the weather stop. Mixing them produces an email that sounds complete and answers the wrong question.
Finally, keep the record. Save the field note, the pointer to the original confirmation, the do-not-promise list, the draft, the approver's edits, and the sent message. The next person who gets a reply asking "so when are you coming" should not have to reconstruct the stop from a text thread and a memory of the sky.
How this note connects to related field guides
Use this sheet when the immediate task is a customer or internal update about work the crew stopped or will not start because of conditions at the site. Use the material delay field note when the immediate task is a late or missing part. A job can have both problems. It should not have one paragraph that pretends they are the same cause. If the condenser is on the truck and the sky is the reason the crew left, the weather note is the one that may go to the customer. The material note stays unused until a supply fact exists.
Messages that go out before the visit, asking the customer to confirm a window, belong to the appointment reminder guide. Do not reuse a reminder template for a stop that has already happened. The reminder assumes the window is still live. This note exists because it is not. Board moves, technician reassignment, and the question of which jobs shift are the dispatch workflow guide. This page does not tell the office how to rebuild the day. It tells the writer which facts are allowed into one customer's update.
Pictures of the pad, the roof, or the street stay on the jobsite photo field note until someone decides what the image is allowed to prove. A weather email that describes "the attached photo shows standing water" is a documentation claim. Make that claim on the photo note, or do not make it. Permit timing, if an inspection was also rained out, goes on the permit and inspection status field note with the inspection's own status. A warranty finding goes on the warranty service visit field note. Link the notes by job pointer. Do not merge their conclusions into the weather draft to save a second email unless the approver explicitly made that the purpose.
The habit across these notes is the same. Collect the minimum facts, mark UNKNOWN, name the approver, then draft. A weather text feels smaller than a change order. It still sets a date or refuses to, and the customer will treat that date as the plan.
A copyable one-page template
Keep the filled sheet with the job file beside the confirmation that named the original window. A one-line post-send note is enough when the update was clean: who approved it, and that no new date was included. When it was not clean, the note should say which field was still UNKNOWN, not which technician "sounded unsure."
If the office stops work for weather often enough to be tired of the sheet, the cure is a standing do-not-promise list — no unnamed return day, no fee language, no storm theater — pasted once into the job folder. The template above still needs the observer's words and the approver's position for this visit. The standing list only stops the same three inventions from coming back.
Assumptions and limits
All examples are hypothetical. Contract language about delays, weather days, trip fees, credits, warranties, and consumer notices varies by agreement and by jurisdiction. This page does not interpret a contract, does not give legal or tax advice, and does not offer industry-average costs or durations. No dollar amount appears because a sample price would only look like guidance. The office's own price position, including a decision to say nothing about price, has to be written by the approver.
NIST pages cited below were requested on 2026-11-14 and loaded. The privacy page, updated on the NIST site 2 September 2025, points small businesses toward Privacy Framework resources. The cybersecurity basics page, updated on the NIST site 6 November 2026, describes cybersecurity as a continuous process and lists starter steps such as inventorying important assets, training employees, and protecting sensitive accounts. They are starting points for privacy and everyday security hygiene. They are not a quote of the full frameworks, not a certification, and not a rule that forbids or endorses any particular AI product. Identification of a NIST page is not a claim that NIST reviewed this article.
No visit was observed and no customer message was sent for this article. The worked example uses invented people, an invented company, and a synthetic job so the fields can be read without a real file. If a later company policy is stricter than this note, the policy wins for that office.
Sources and method
- NIST: Small Business Cybersecurity Corner — Privacy — retrieved 2026-11-14
- NIST: Small Business Cybersecurity Corner — Cybersecurity Basics — retrieved 2026-11-14
AI-assisted writing with automated source, calculation and editorial checks. No hands-on testing or professional certification is claimed. Check the stated assumptions before applying this guide.