Punch-List / Closeout Field Note: Minimum Facts Before an AI Customer Update

Why a punch-list field note must exist before the AI update

A routine progress email can lean on the work order and the crew schedule. A punch list leans on a named walkthrough, a scope pointer that defines what "done" means, and an item-by-item record of what is still open, who owns it, and what the office is willing to say. Treating a superintendent's hallway recap like a complete closeout file is how offices send a polished AI summary that claims "only two cosmetic items remain and we will finish Friday" when the note only supports one paint touch-up, a missing part that has not been ordered, and no approved date.

Read the job pointer and the walkthrough record before anyone prompts a model. Classify the update purpose: internal pre-walk list, joint owner walkthrough punch list, customer-facing remaining-items letter, substantial-completion notice draft, final-completion / closeout draft, or other office-defined purpose. Many packets mix two purposes. Write both down. The purpose decides which facts must be real and which claims the owner must approve.

Treat the AI as a writer working from a field note, not as a site witness who "was at the walk." It can organize verified items, keep tone steady, and list gaps. It cannot know what was behind a closed door, whether a scuff is in-scope, or whether the owner wants a holding list versus a letter that the job is complete except as written.

Closeout language also creates legal and payment risk when it is sloppy. Phrases like "substantially complete," "ready for final inspection," "warranty starts today," or "retainage can be released" are not decorative. If the owner has not decided those positions, the draft should not invent them. Mark each as DO NOT PROMISE until an approver says otherwise.

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, site address shorthand on file, and customer or property label the office already uses.
• Scope pointer — the contract, proposal, or scope sheet that defines what complete means, plus any approved change-order IDs that changed that baseline.
• Update purpose — internal pre-walk, joint owner punch list, remaining-items letter, substantial-completion draft, final-completion / closeout draft, or other. Quote the office language, not marketing language.
• Walkthrough record — date, type (internal, joint with owner, vendor-only), who attended by role, and whether the walk covered the whole job or only listed areas.
• Open-item list — for each item: a stable item ID, location, verified description, category (incomplete, deficient finish, missing material, customer-request, disputed), owner (crew, vendor, office, customer), next action, and a photo pointer or UNKNOWN.
• Completed-this-visit items — only items the walk or crew record actually closed; do not backfill a "typical closeout checklist."
• Exclusions and not-in-scope mentions — customer asks or site conditions the walk noted that are outside the current scope pointer.
• Access, material, and inspection blockers — parts not ordered, customer-held keys, occupied rooms not walked, pending inspection, or UNKNOWN.
• Related inspection status — permit / inspection ID and last known outcome, or UNKNOWN. Do not guess a pass.
• Office position — internal QC list only; customer punch-list draft; remaining-items letter with no completion claim; substantial-completion draft pending owner review; final-completion / closeout draft pending owner review; or not yet decided.
• Promises and next steps — return-visit window if approved, or DO NOT PROMISE items (fixed completion dates, inspection results, retainage release, warranty start, unpaid extras performed for free).
• Approval owner — who must approve customer language, completion claims, and any fee, concession, or extra-work wording.
• Channel and timing — how the list or update will be sent and when a reply is reasonably expected.
• PII check — confirm the prompt excludes payment card data, full account numbers, government IDs, and anything not needed for this closeout purpose.

Office position is the field that prevents accidental guarantees. If the owner has not decided whether this is an internal punch list or a customer-facing completion letter, a model will often fill the gap with polished certainty. That sentence can imply acceptance, payment timing, or warranty start nobody authorized. An internal list that names verified open items and marks completion as UNKNOWN is safer than a dramatic "the home is ready for you to move back in Friday" line.

Item IDs beat memory. "The bathroom thing" tells the model nothing useful. A one-line item ("PL-03 master bath paint touch-up at shower corner, deficient finish, painter owns next action") is what keeps the draft inside the walkthrough.

An illustrative example

Several gaps still matter even in a "simple" punch-list send: PL-02 has no photo yet, the soap-niche request is not in-scope work, and the final inspection has not happened. The safe AI draft at this stage (1) names the job pointer and the 2026-11-08 joint walk, (2) lists only the three verified open items with owners and next actions, (3) can mention the silicone item as closed on the walk if the approver wants that courtesy line, and (4) avoids completion, inspection, retainage, and warranty promises. The draft should not add the soap niche as "we will handle that too," and it should not say the job passed inspection.

Once the owner keeps the punch-list position and the superintendent confirms the three item descriptions, the field note stays stable for send. If the customer replies asking for a price to add the soap niche, stop using this sheet as a remaining-items template and open the matching change order field note before the next AI draft. If they later report a leak after accepting the job under warranty language, open the warranty service visit field note instead.

A short sequence before anyone prompts the model

1. Name the job, the scope pointer, and the update purpose — one sentence the approver can hear without opening the photo album.
2. Confirm the walkthrough record — date, type, attendees by role, and areas not walked.
3. Write the open-item list with stable IDs — location, verified description, category, owner, next action, photo pointer or UNKNOWN.
4. Separate extras from punch items — customer requests outside the scope pointer go to a change-order discussion, not onto the remaining-items list as if they were defects.
5. Fill office position and DO NOT PROMISE — if position is undecided, draft only an internal checklist, not a customer completion letter.
6. Prompt with the field note only — attach curated item photos if the note includes them; do not paste the entire phone dump.
7. Review by role — field lead checks item accuracy; PM or office checks job and change-order IDs; owner checks position and promises; sender checks recipients and attachments.
8. Save the packet — field note, item list, draft, edits, and sent message with the job file.

This sequence is short on purpose. Most punch-list failures are not writing failures; they are walkthrough, scope, and position failures. A beautiful draft from an undocumented hallway recap is still a liability.

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 and any curated item photos named in it. If a fact is UNKNOWN, say the office is checking it; do not fill the gap.
• List only verified open items; do not invent deficiencies, completions, measurements, code violations, or causes the note does not state.
• Do not invent walkthrough dates, inspection outcomes, remaining-work percentages, or "standard industry" punch-list findings.
• If promises are DO NOT PROMISE, omit them entirely—even in a P.S.
• If office position is "not yet decided," draft only an internal holding summary or a non-sent checklist, not a customer completion email.
• Do not recategorize a customer extra as an in-scope punch item "to be helpful."
• If a change-order, warranty, or inspection sheet is the real next step, say so and stop expanding this punch list into pricing, blame, or legal conclusions.
• Keep length limited; one clear purpose; one named contact; one reply path.
• After the draft, list every sentence that depends on a field a human must verify against the walk record and job file.

That final checklist turns review into matching claims to the walkthrough and the field note, instead of rereading a smooth closeout letter for vibes.

Common failure patterns

The first failure is the invented item: the model adds "caulk all wet areas and adjust all doors" because closeout letters often sound that way. If the note only supports three verified items, the draft may only list those three.

The second failure is the invented completion claim: asserting the job is substantially complete, ready for occupancy, or ready for final payment when the office position is only "here is the remaining-items list." Completion words are a position, not a tone choice.

The third failure is date fiction: promising Friday, "end of next week," or a warranty start the approver never set. If no return-visit window is approved, say the office will follow up when parts or access are confirmed.

The fourth failure is mixing extras into punch items. A soap niche, an added shelf, or a finish upgrade the contract never included is not a deficiency. Pricing language belongs on a change-order sheet.

The fifth failure is inspection fiction. A scheduled final is not a passed final. Use the permit / inspection status field note when the customer is asking about the inspector, and mark outcome UNKNOWN until the card or portal says otherwise.

The sixth failure is prompt oversharing. Dumping every jobsite photo into a chat so the model can "build the punch list from pictures" parks faces, plates, and household details in a log the office may not control. Curate first, and keep item photos on the matching photo note. The FTC's protecting personal information guide and Start with Security are practical baselines: keep only what the task needs, limit access, and avoid parking sensitive customer data in chat logs.

Finally, keep the record. Save the field note, item list, withhold decisions for any photos, draft, reviewer edits, and sent message with the job file. If the account later becomes a warranty visit, a payment dispute, or a complaint, that packet shows what the business knew when it described remaining work.

How this note connects to related field guides

Use this sheet when the immediate job is to document remaining work or draft a closeout update before an AI writes. Use the jobsite photo field note when an item depends on what the camera shows. Use the scope of work field note when the baseline itself is unclear. Use a change order field note before extra-work pricing language. After acceptance, later callbacks belong on the warranty sheet, not on a recycled punch list that pretends the original job never closed.

The habit across Contractor AI Hub field notes is the same: collect minimum facts, mark UNKNOWN, name the approver, then draft. Closeout language does not relax that habit; it makes it more important, because a confident "job complete" sentence travels farther than a wrong paragraph about a single scuff.

A copyable one-page template

Keep the filled sheet with the job file beside the item list. 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 closeout."

Assumptions and limits

All examples are hypothetical. Contract language about substantial completion, final completion, retainage, warranties, consumer protection, licensing, and inspections varies by jurisdiction and by your agreements; this page does not interpret those rules and is not legal, insurance, engineering, or financial advice. Do not use AI drafts to invent punch items, completion claims, inspection outcomes, or fixed calendar results. If a customer mentions a lawyer, a regulator, a formal payment dispute, or a formal complaint, stop casual AI drafting and follow your advisor's guidance. AI vendors differ in data retention; review their terms before pasting customer names, photos, and contact data. This guide claims no measured closeout-speed, collection, or satisfaction improvement.

Sources and method

• FTC: protecting personal information — retrieved 2026-11-08
• FTC: start with security — retrieved 2026-11-08

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.