# Turn verified site notes into buyer updates people can trust

AI can draft a weekly buyer update from approved field notes, selection records and documented decisions. The draft keeps completed work, current activity, upcoming decisions and known constraints in separate sections. It does not infer progress from photos, promise a completion date or explain a delay without verified context. The project owner reads every sentence before it goes out.

## What belongs in a weekly buyer update?

What was verified, what needs the buyer's attention and what the team expects to address next. Not the whole job log. Field notes, inspection records, selection status and approved schedule commentary are the source. The agent arranges those facts into a consistent reader-facing draft.

The update follows construction sequence without overstating certainty. "Mechanical rough was reported complete in the approved site note" is backed by a source. "The project is back on schedule" is a conclusion that needs explicit approval and context. A photo of installed material proves nothing about the related inspection, payment or milestone.

This workflow sits in the [AI for builders article cluster](/articles/ai-for-builders/), where preparation and checking stay apart from human judgment. Approved notes are the foundation: the companion article on [AI meeting notes for builders](/articles/ai-for-builders/ai-meeting-notes-for-builders/) shows how a working conversation becomes a reviewed project record before it feeds an update.

### Which sections keep the update readable?

| Update section | Source | Review focus |
| --- | --- | --- |
| Completed work | Approved superintendent or project notes | Was the work verified? |
| Current activity | Current field report and trade coordination | Does the wording avoid a completion claim? |
| Buyer decisions | Approved selections record | Are item, status and requested action correct? |
| Constraints | Documented issue and approved explanation | Facts only, no unsupported cause? |
| Next work | Reviewed look-ahead | Framed as planned work, not a guarantee? |
| Attachments | Approved photos or documents | Right project, revision and recipients? |

## How do field notes become a buyer-facing draft?

Field notes are shorthand that makes sense to the superintendent and nobody else. The agent expands defined terms, groups work by phase and strips internal coordination language that does not belong in a buyer message. It does not reinterpret an ambiguous note. "Waiting on cabinet answer" needs a person before it becomes an update.

Keep a source trail. Each working sentence points back to a note, an approved record or a responsible person during review. The buyer never sees the citations. The reviewer needs them.

### Can job-site photos be the source?

Photos support a verified note and help the buyer see progress. They are never the only proof of phase completion. Image dates, project identity and visible conditions get misread. A person picks the images, confirms the project and approves any caption before attachment.

## How do you run the drafting and review cycle?

1. **Close the note window.** Set the point when field, selection and decision notes are ready for drafting.

2. **Confirm the source set.** Use the approved project record. Mark older or superseded notes.

3. **Draft by status.** Completed, current, planned and decision-needed, kept apart.

4. **Flag gaps.** Ask for clarification when a note lacks an owner, a condition or a verified result.

5. **Review project facts.** The accountable project person checks work status, constraints, dates and decision requests.

6. **Review communication.** Recipients, tone, attachments and any contractual sensitivity.

7. **Save the final update.** The sent version goes in the builder-owned project record.

The [AI operations stage](/process/ai-operations/) defines this workflow's permissions, review gate and manual fallback. Our Claude and Codex AI agents draft and check against the supplied records. People decide what the project status means.

The [AI for home builders guide](/guides/ai-for-home-builders/) covers the wider controls for source files, agent access and accountable approval.

## How does the update handle delays and uncertain work?

State the verified condition, the current response and the next review point. Do not fill silence with reassurance. Weather, inspections, material availability, design changes and trade sequencing all move work, and the agent names a cause only when the responsible person has approved that explanation.

Planned work needs careful wording. Describe it as the current look-ahead, subject to field conditions and required approvals, if that matches your process. Never let the agent compute a new completion forecast from task durations. Schedule commitments belong to the people responsible for the job and to the governing documents.

The [weather-delay communication article](/articles/process-and-documents/weather-delay-communication/) covers one narrow case. This weekly workflow carries only the approved version of that message.

### What if nothing visible changed?

The update can still report what happened: plan review, procurement coordination, inspection scheduling, a selection resolved, a known hold. Do not invent activity to fill the page. If no approved information exists, the workflow routes the gap to the project owner instead of producing filler.

## How do updates stay consistent without sounding automated?

Same sections every week, project-specific language every week. Buyers recognize their home, their current decisions and their next step. Repeated headings let them scan. Varied details prove the job is real. The agent uses the phase, selection and responsibility vocabulary from your [operating profile](/glossary/operating-profile/).

The [weekly buyer updates article](/articles/sales-process/weekly-buyer-updates/) covers cadence and buyer expectations. AI's job is narrower: turn current approved inputs into a first draft and check that no required section is missing.

Selections data enters only after review. The companion [AI selections tracker](/articles/ai-for-builders/ai-selections-tracker/) shows how to keep proposed choices apart from approved status. That boundary keeps a buyer update from presenting an open finish, fixture or allowance question as settled.

### What else gets asked about AI buyer updates?

### Can AI read site photos and report progress?

It can organize approved site photos for a buyer update. A qualified person verifies what the images show and what project status can be stated.

### Should every update mention a completion date?

No. Include schedule language only when the responsible person approves it and the message matches your governing process.

### What if superintendent notes are incomplete?

The agent lists the missing facts and pauses the affected section. It does not infer field conditions or trade status to fill the gap.

### Can the update go directly to the buyer?

Not at first. Start with required human review. Change sending authority only after you define, test and approve a specific control.