Material Delay Field Note: Minimum Facts Before an AI Customer Update

Why a delay note has to exist before the AI update

A routine "we are on schedule" text can lean on the crew calendar when the calendar is actually firm. A delay update leans on an order pointer, the exact status the supplier gave, and the dates the office has already said out loud. Treating a hallway remark — "the vanity is late" — like a complete purchasing file is how offices send a smooth AI email that claims the new unit arrives Thursday and the crew will install Friday, when the supplier message only says the item is on backorder and no ETA was given.

Read the job pointer and the purchase record before anyone prompts a model. Classify the update purpose in office language: internal hold, customer delay notice with no new date, customer notice with an owner-approved window, substitution request, or another purpose the office names. Many packets mix two purposes. Write both down. An internal hold that tells the crew not to roll a truck is a different document from a customer email, even when both start from the same supplier line.

Treat the AI as a writer working from a field note, not as a purchasing agent who called the supplier and not as a project manager who reset the schedule. It can keep the tone steady, acknowledge an earlier promise, and list what is still unknown. It cannot know an ETA that was never stated, whether a different model is acceptable to this customer, or whether the owner is willing to move the price. Those are decisions. If they are blank, the draft should show the blank.

Delay language creates schedule and money risk when it is casual. Phrases such as "we will still finish on the original date," "the substitute is the same quality," "there is no extra charge," and "inspection is still Thursday" are not decoration. If the owner has not decided those positions, mark each one DO NOT PROMISE. A model will often fill a polite email with exactly those sentences because they sound helpful. Helpful, in this packet, means faithful to the note.

The minimum facts to collect first

Before prompt time, fill each field or write UNKNOWN with the person who can resolve it:

• Job pointer — job or work-order ID, the site address shorthand already on file, and the customer or property label the office uses. If a job ID is enough for the draft, do not paste a full street address into the prompt.
• Scope pointer — the proposal or scope line that names the material, plus any approved change-order IDs that changed that line. A verbal upgrade that was never written down is not a scope pointer.
• Material identity — the description as written on the scope or the purchase order. If the office does not have the spec in front of the note, mark it UNKNOWN. Do not let the model invent a brand, a collection name, or a model number to make the email sound specific.
• Who supplies it — contractor-supplied, customer-supplied, or UNKNOWN. A delay on an item the customer was supposed to purchase is a different sentence from a contractor backorder. Guessing which one it is assigns blame the note does not support.
• Order pointer — purchase order, supplier order, or acknowledgment ID on file, or UNKNOWN. Leave supplier account numbers, portal passwords, and payment card data out of the prompt even if they sit on the same PDF.
• Status source — who said what, on what date, and by which channel: email, portal note, or phone. Quote or closely paraphrase only the status the office actually has. If the only source is that someone at the desk thought they heard a date, the date is UNKNOWN.
• Dates already promised — any arrival, delivery, or install window already told to the customer, and where that promise lives. If none was made, write NONE. If the office cannot find the earlier message, write UNKNOWN rather than reconstructing it from memory.
• New date — only a date the supplier message or the owner has actually set. Otherwise UNKNOWN. A week somebody hopes for is not a date. A date on a different job is not this job's date.
• Crew and other-trade impact — what was tentatively held on the internal calendar, and whether that hold has been released. Other trades waiting, or UNKNOWN. An internal hold is not a customer promise unless the office position says to share it.
• Inspection or permit impact — related permit or inspection ID, and whether it was not yet requested, requested, scheduled, or already resulted. Do not guess a pass or invent a new inspection day. If the customer is asking about the inspector rather than the material, switch to the permit / inspection status field note.
• Substitution position — no substitute offered; a named option proposed but not approved; a named option the customer already approved in writing; or DO NOT OFFER. "Named" means the office wrote the option down from a real source. The word "equivalent" without a name is not a position.
• Price impact — no price change on this send; a possible change that is not yet priced; a priced change that already has an approved change-order ID; or UNKNOWN. Do not invent a credit, a discount, or an upcharge to soften the news.
• Office position — internal hold only; customer delay notice with no new date; customer notice with an approved window; substitution ask; or not yet decided.
• Promises and next steps — the sentences that must not appear, especially the old completion date, an unapproved ETA, a quality comparison, a free upgrade, and any inspection result.
• Approval owner — who must approve customer language, any date the customer will hear, and any money language.
• Channel and timing — how the update will be sent, to which contact already on file, and when a reply is reasonably expected. Do not add new recipients the note does not name.
• PII check — confirm the prompt excludes payment card data, full account numbers, government IDs, gate or alarm codes, and supplier portal screenshots that show those values.

Office position is the field that keeps a delay from becoming a new contract. If the owner has not decided whether this send is an internal hold or a customer notice, a model will often choose the customer notice and fill it with certainty. An internal note that says the ETA is UNKNOWN is safer than a warm paragraph that picks a Thursday. Dates already promised matter for a different reason: if the office told the customer a window last week, the new draft should acknowledge that window or the owner should decide not to mention it. Pretending the earlier sentence never happened is how trust erodes even when the new facts are careful.

Order pointers beat nicknames. "The cabinet thing" lets the model attach the delay to the wrong line. A pointer such as "PO-8831, vanity and top as specified on REV-1" keeps the draft on the material that is actually late. If the PO and the proposal disagree, that disagreement is a fact to write down, not a detail for the model to reconcile by inventing a third description.

An illustrative example

Several gaps still govern the draft even though the story is simple. The supplier gave no ETA. The 2026-11-18 crew hold is internal. No substitute is approved. No inspection has been requested. The safe AI draft at this stage (1) names JOB-4417 and the vanity line, (2) acknowledges the earlier week-of-2026-11-16 expectation if Dana wants that sentence included, (3) says the supplier reported a backorder on 2026-11-10 and did not provide an ETA, and (4) says the office will write again when a date exists. The draft does not offer the 18th, a different model, a credit, a matching-finish claim, or an inspection result. It also does not apologize by inventing a cause, such as a shipping backlog or a factory shutdown, that the supplier email did not state.

Once Dana keeps the "no new date" position and the person who read the supplier email confirms the 2026-11-10 wording, the field note is stable enough to prompt. If the customer replies "just pick a different vanity and take the difference off the price," stop using this sheet as the reply template. Open the change order field note and collect the new spec, the price basis, and the approver before the next draft. A delay notice that quietly becomes a repricing email is how offices give away scope.

The earlier promise is part of the note on purpose. Deleting the week of 2026-11-16 from the prompt would make the new email look cleaner and would hide a sentence the customer already received. The approver may still decide the outgoing mail should not restate that week. That is an editing choice made by Dana, recorded on the sheet, not a gap for the model to smooth over.

A short sequence before anyone prompts the model

1. Name the job, the material line, and the update purpose — one sentence the approver can hear without opening the supplier portal.
2. Read the status source — date, channel, and the words actually on file. A remembered phone call without a note is UNKNOWN, not a date.
3. Separate dates already promised from the new date — write both. NONE and UNKNOWN are allowed. A hoped-for week is not a new date.
4. Set substitution and price — named option, do-not-offer, no price change, or UNKNOWN. Do not leave these as blank adjectives such as "similar" or "fair."
5. Fill office position and the do-not-promise list — if position is not yet decided, draft only an internal hold, not a customer email.
6. Prompt with the field note only — no portal screenshots, no full proposal PDF if it contains payment data, no extra emails "for context" unless those facts have been copied into the note.
7. Review by role — purchasing or the project lead checks the supplier wording; the owner checks dates, substitutions, and money; the sender checks the recipient and attachments.
8. Save the packet — field note, status source pointer, draft, edits, and the sent message, stored with the job file.

The sequence is short because most delay-email failures are purchasing and position failures, not writing failures. A graceful paragraph drafted from an unrecorded hallway comment is still an unauthorized schedule.

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. Do not fill the gap from a typical job.
• Do not invent ETAs, brands, model numbers, "equivalent" quality, credits, discounts, percent-complete figures, or inspection results.
• Do not repeat a stale install or completion date unless the note says the approver wants that date restated. Stale is not the same as current.
• If substitution is DO NOT OFFER, do not suggest alternatives, even as a helpful P.S.
• If office position is "not yet decided" or "internal hold only," draft an internal summary, not a customer email.
• Do not assign fault to the customer or the supplier beyond who supplies the item and what the status source says. A backorder is not, by itself, a story about whose mistake it was.
• If a change-order, punch-list, photo, or permit sheet is the real next step, say so and stop expanding this delay note into pricing, closeout, or inspection claims.
• Keep one purpose, one named office contact, and one reply path. After the draft, list every sentence that depends on a field a human must verify against the supplier message and the job file.

That last list is the review. The owner 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 send.

Common failure patterns

The first failure is the invented ETA. The model sees a backorder and offers "next Thursday" or "seven to ten days" because delay emails often sound that way. If the status source has no date, the draft has no date. "We will update you when the supplier gives us one" is a complete sentence.

The second failure is invented equivalence. "We can switch you to a comparable vanity at no loss of quality" is a specification and a price position. Neither exists when the substitution cell says DO NOT OFFER. Comparable is not a fact the model is allowed to create.

The third failure is invented money. A courtesy credit, a promise of "no charge for the wait," or a statement that the contract price is unchanged can each be wrong in a different direction. If the price cell says no price change on this send, the draft should not discuss price at all. If the price is UNKNOWN, say the office has not finished that review.

The fourth failure is repeating the old finish date as if the delay had not happened. The week of 2026-11-16 in the example is a sentence the office already sent. It is not permission to send it again as a current promise. Acknowledge it only if the approver marked that choice, and pair it with the actual status.

The fifth failure is mixing up who supplies the item. A contractor backorder and a customer who has not yet purchased a fixture produce different next steps. If the who-supplies field is UNKNOWN, the draft should not scold either party. Find the proposal line first.

The sixth failure is prompt oversharing. Pasting a supplier portal screenshot can place account numbers, saved cards, and unrelated orders into a chat log. Pasting the whole proposal can do the same with customer contact data the delay email does not need. NIST's small-business privacy page says an owner may want to protect customers' privacy and points to the NIST Privacy Framework learning materials as a place to start; this page does not summarize that framework or treat it as a legal checklist. NIST's cybersecurity basics page says cybersecurity is a continuous process and lists phishing-resistant multi-factor authentication for sensitive accounts, including business-critical cloud services. Whether a given AI vendor login belongs on that list is an office decision. The field habit here is narrower and does not depend on a vendor slogan: keep the prompt to the job ID, the material line, and the status words you are willing to stand behind.

The seventh failure is using a delay note to close the job. A missing vanity at rough-in is not a punch list, and a missing bumper during a final walk is not a new purchase order story unless the note says so. When the purpose is closeout, switch sheets. When the purpose is an inspection date, switch sheets. One update, one purpose.

Finally, keep the record. Save the field note, the pointer to the supplier message, the do-not-promise list, the draft, the reviewer edits, and the sent email with the job file. If the account later becomes a change order, a complaint, or a payment dispute, that packet shows what the business knew when it described the delay. It does not need to include the customer's full account numbers to do that job.

How this note connects to related field guides

Use this sheet when the immediate task is a customer or internal update about material that is late, backordered, or unavailable, and an AI tool will write the words. Use the scope of work field note when the office cannot point at the line that defined the material. Use the change order field note before any substitute price, credit, or added scope goes into a draft. Use the jobsite photo field note when the update depends on what a picture shows, such as damage to a delivered item or a site that cannot proceed. Use the punch-list / closeout field note when the material question is really an open item on a walkthrough. Use the permit / inspection status field note when the customer's question is about the inspector, not about the purchase order.

The habit across these notes is the same. Collect the minimum facts, mark UNKNOWN, name the approver, then draft. A delay email feels smaller than a contract, which is why the model is tempting. The sentences travel just as far: a date, a substitute, and a price, offered in the company's voice, are still offers.

A copyable one-page template

Keep the filled sheet with the job file beside the supplier message. A one-line post-send note is enough when the update was clean. When it was not, the note should say which field was incomplete rather than which employee was "bad at email."

Assumptions and limits

All examples are hypothetical. Contract language about delays, substitutions, credits, warranties, consumer protection, and inspections varies by jurisdiction and by the agreements you already have; this page does not interpret those rules and is not legal, insurance, engineering, or procurement advice. No lead time, backorder rate, or supplier reliability figure is stated, because none was measured for this guide. Do not use AI drafts to invent arrival dates, product equivalence, price changes, or inspection outcomes. If a customer mentions a lawyer, a regulator, a formal claim, or a payment dispute, stop casual AI drafting and follow your advisor's guidance. AI vendors differ in data retention; review their terms before pasting customer names, supplier documents, and contact data. This guide claims no measured improvement in schedule, collections, or customer satisfaction.

NIST pages cited below were requested on 2026-11-11 and loaded. They are starting points for small-business privacy and cybersecurity hygiene. They are not quoted here as a complete control set, and they do not approve or prohibit any particular AI product. Older Contractor AI Hub notes cite FTC business-guidance URLs; those exact URLs were not reused here because this drafting check did not retrieve them successfully on 2026-11-11. Do not treat a missing retrieval as a finding that the FTC pages are gone for every reader. Treat it as a reason this note cites sources that were actually fetched.

Sources and method

• NIST: Small Business Cybersecurity Corner — Privacy — retrieved 2026-11-11
• NIST: Small Business Cybersecurity Corner — Cybersecurity Basics — retrieved 2026-11-11

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.