Record a two-minute voice note and take photos before leaving site each day, then give the transcript to a chat assistant with a fixed template: done this week, next week, decisions needed, cost changes. For snag lists, walk room by room dictating each defect, and ask the AI for a numbered table with location, trade, priority and photo reference.
The catch is that AI only organises what you tell it. It cannot see that the second-fix electrics are finished, and when it works from photos it describes damage with more certainty than it has, turning a hairline line in new plaster into a "structural crack". So status, responsibility and anything that sounds like a diagnosis stay in your words. Updates and snag lists become evidence if a job goes sour, and the wording matters.
What a client update needs so homeowners stop phoning
Most "how's it going?" calls come from clients who have had no news, or news they could not follow. A weekly update that answers the same five questions every Friday cuts those calls because the client learns where to look. The format:
- Done this week. Three to six plain bullet points, in the client's words ("the kitchen walls are plastered"), not the trade's ("skim coat to kitchen elevations").
- Coming next week. What will happen and roughly when, including anything that affects them: noise, water off, access needed.
- Decisions we need from you. Each with a date. "Tile choice for the splashback by Wednesday, or the tiler moves to the following week."
- Cost changes. Any agreed variation and its price, and any pending ones awaiting approval. If nothing changed, say so.
- Anything to watch. One line on risks: weather, a late delivery, a hidden problem found.
Keep it under 250 words. Add two or three photos with one-line captions. Clients forward these to partners and parents, so a short, clear update does your marketing too.
Capturing the site day in under five minutes
The update is only as good as what goes in. Before leaving site, the site lead records a voice note covering a fixed checklist, in any order:
- Who was on site and what each trade did.
- What is finished, and what is started but not finished.
- Anything that went wrong or was found (rot, a pipe where the drawings showed none).
- Deliveries in and deliveries still waited for.
- Anything the client asked for or changed their mind about.
Photos go in a folder per job, named room and number: "K-01", "K-02", "BATH-01". That naming is what lets the snag list reference photos later without anyone scrolling through 200 pictures. One voice note a day, five a week, gives the assistant everything it needs on Friday.
From voice notes to the Friday update: a worked run
Take an illustrative six-person building firm running a single-storey rear extension with a new kitchen. Here is part of Thursday's voice note, transcribed by the phone:
"Thursday. Plasterers finished the kitchen walls and ceiling, extension side's still drying. Sparks did second fix in the utility, kitchen second fix waiting on the plaster. Bifolds are delayed, supplier says week after next now not next Tuesday. Found the old soil pipe's cracked where it goes through the wall, need to replace about a metre, told the client, she's fine with it but wants the price. Client asked if we can move the island pendant 30 mil to the left. Skip swap tomorrow."
The prompt, saved in a Project so it is the same every week:
You write weekly client updates for a small building firm.
Use the voice notes below (Monday to Friday) to write this week's update.
Format exactly:
1. Done this week (3-6 bullets, plain words a homeowner understands)
2. Coming next week (with anything that affects the client)
3. Decisions we need from you (each with a deadline)
4. Cost changes (agreed / awaiting approval; write [PRICE] where no
price is given in the notes - never estimate one)
5. Anything to watch (one or two lines)
Rules: under 250 words. Friendly, calm, factual. Never say work is
complete unless the notes say "finished" or "done". Never blame a
subcontractor or supplier by name. No promises of dates the notes
don't contain. List anything unclear at the end under CHECK.
Voice notes: [paste all five days]An illustrative draft, from the whole week's notes:
Done this week: the kitchen walls and ceiling are plastered; the electrics in the utility room are fitted; the extension walls are plastered and drying out.
Coming next week: kitchen electrics once the plaster has dried; replacing a damaged section of the old waste pipe (the water will be off for about two hours, we'll confirm the day).
Decisions we need from you: please confirm the new pendant position for the island by Tuesday so the electrician can fit it on the first visit.
Cost changes: awaiting approval: replacing about a metre of cracked waste pipe, [PRICE].
Anything to watch: the bifold doors are now due the week after next; we're arranging the work so this doesn't hold up the kitchen.
CHECK: is the utility room fully finished, or only the electrics?
Three fixes before sending. The site lead fills in the pipe price. He adds that the pendant move is 30 mm to the left, because the draft dropped the number. And he rewrites the bifold line, which is a small promise ("this doesn't hold up the kitchen") he can only keep if the fitter is available. The whole update took eight minutes including photos, against the forty-odd minutes the owner used to spend writing from memory on a Sunday.
Writing bad news without blame or grovelling
Delays and extra costs are where updates go wrong, because tired builders either bury the news or write it defensively. Here is an illustrative before:
"Bifolds late again, not our fault, supplier messed up. Also found your soil pipe was knackered so that's extra."
And after, with the assistant asked to "rewrite this calmly, with the effect on the client and what we're doing about it":
"The bifold doors have been delayed by the manufacturer and are now due the week after next. We've reordered the work so the kitchen carries on in the meantime, and we'll confirm the fitting date as soon as it's booked. We also found that a section of the old waste pipe is cracked where it passes through the wall. It needs replacing before the kitchen goes in; the price is below for your approval."
The rewrite states the fact, the effect, the plan and the next step. It does not blame, and it does not apologise for something that was not the firm's doing. If the delay changes the price or the contract, handle that through your variation process rather than an update; pricing variations and change orders with AI covers that paperwork.
Snag walks: dictating room by room
A snag walk works best as a slow walk with the phone recording, one room at a time, saying the room name first and taking a numbered photo of each item as you describe it. For each defect, say where it is, what is wrong, and roughly how big. Don't try to assign trades or priorities out loud; the assistant does that from your description and you correct it.
The prompt:
Turn this snag walk transcript into a numbered snag list table.
Columns: No. | Room / exact location | Defect (factual, what is seen) |
Trade to fix | Priority | Photo ref
Priority rules: HIGH = water, safety, security, or stops a room being used.
MEDIUM = something doesn't work properly. LOW = cosmetic.
MONITOR = needs watching, not fixing yet.
Describe only what was said. Don't guess causes. Don't use the words
"structural", "defective workmanship", "negligent" or "failed".
If the trade isn't obvious, write "?" rather than guessing.
Transcript: [paste]An illustrative output from a kitchen-extension handover walk:
| No. | Location | Defect | Trade | Priority | Photo |
|---|---|---|---|---|---|
| 1 | Kitchen, left window reveal | Strip of reveal unpainted, about 30 cm | Decorator | Low | K-03 |
| 2 | Kitchen island, end panel | Double socket faceplate not level | Electrician | Low | K-05 |
| 3 | Utility, sink | Drips at waste trap joint when tap runs | Plumber | High | U-01 |
| 4 | Hall, door to kitchen | Door catches frame at top, won't latch | Carpenter | Medium | H-02 |
| 5 | Bathroom, bath corner | Gap in silicone, about 5 cm | ? | Medium | B-04 |
| 6 | Bedroom 2, above door | Hairline line in new plaster, about 40 cm | Plasterer | Monitor | B2-01 |
| 7 | Rear bifolds, threshold | Drip bar not fitted | Window fitter | High | G-01 |
What the site lead fixed: item 5 went to the plumber, who fitted the bath; item 7 stayed high because water gets in under a threshold without its drip bar. Item 6 is the kind of thing clients worry about. "Monitor" with a note ("hairline lines are common as new plaster dries; we'll check again at the six-week visit") reassures the client without dismissing them, but only the qualified person decides whether that is what it is.
One snag list, two versions
The same list goes to two audiences with different needs. Ask the assistant for both in one go.
For the client: grouped by room, no trade names, a target date for each group, and a line inviting additions. Illustrative extract: "Kitchen: two small finishing items (paint touch-up on the window reveal, levelling a socket cover), both by Friday 12th. Utility: a small leak under the sink, fixed on Monday. Please tell us within seven days if you spot anything we've missed."
For each trade: only their items, with location, photo reference and the date you need it done. Illustrative text to the plumber: "Two items at the extension, please: 1) utility sink, drip at the waste trap joint when the tap runs (photo U-01), 2) bathroom, 5 cm gap in the silicone at the bath corner (photo B-04). Client moves back in on the 15th, so by the 13th if you can."
Splitting it stops a client reading "plumber: leak" and ringing the plumber directly, and it stops each trade scrolling past other people's items.
What AI gets wrong when it reads snag photos
All the main assistants can describe a photo, and it is tempting to skip dictation and just upload the pictures. It works for obvious items and goes wrong in predictable ways:
- Overclaiming. Shown a hairline line in a ceiling, an assistant may call it "a crack indicating possible movement". That phrase in a client document is an invitation to a dispute. Your dictated description is factual; its guess is not.
- Missing context. A photo of a gap by a skirting board cannot tell the AI that the gap is where a radiator pipe will be boxed in next week. It lists it as a defect.
- Scale. Without something in the frame for size, "a small chip" and "a large chip" are guesses. Put a tape or a pen in the shot for anything you might argue about.
- Location. The photo shows a socket, not which wall of which room. Your file name carries the location, so keep naming photos.
The practical rule: dictation is the record, photos are the evidence, and AI photo descriptions are a prompt for you to check, not a line to copy. For more on what these tools can and can't read from images, see what ChatGPT can read from PDFs, spreadsheets and photos.
Wording that holds up if there's a dispute
If a job ends badly, your updates and snag lists get read by someone looking for admissions. A few rules keep them clean, and they are easy to put into the prompt:
- Describe, don't diagnose. "Hairline line in plaster, about 40 cm" rather than "settlement crack".
- Date everything. Each update carries the week's dates; each snag list says when it was walked and by whom.
- "Complete" means complete. If a room has snags outstanding, it is "finished except items 1 and 2", not "complete".
- No fault words. Avoid "defective", "failed", "our mistake" or "negligent" unless you have decided, with advice if needed, that you want to say that.
- Record agreements. "Client confirmed pendant moves 30 mm left (message, 14th)" is worth ten verbal agreements.
- Close the list in writing. When the last item is done, send a short note saying so and asking the client to confirm.
This is not legal advice, and if a dispute is already brewing, talk to a solicitor before sending anything. But builders who write this way rarely end up in the argument in the first place. Surveyors face a similar problem with site notes becoming reports, and how surveyors turn site notes into reports with AI shows a parallel careful-wording approach.
The Friday update that sent a client home for nothing
An illustrative one. A site lead pasted Monday to Thursday's notes on Friday and forgot Friday's own note. Thursday said "tiler starts shower wall tomorrow". The update told the client the shower was being tiled. On Friday the tiler had actually been called to another job, which was in the missing note. The client took a half-day off to see it, found nobody there, and rang the owner.
Two fixes came out of it. The prompt now starts with "Voice notes for [dates]. If any day is missing, say which at the top." And the site lead reads the "Coming next week" section aloud to himself before sending, because that is the section clients act on.
Job software that already drafts some of this
If you use construction management software, check what it does before building your own routine. Buildertrend added an AI Client Updates feature in 2025 that drafts a homeowner summary from the job's daily logs, schedule, change orders and invoices, covering the week just gone and the week ahead, which you edit before sharing through its client portal. Fieldwire lets you pin punch items on the plans, attach photos, assign them to subcontractors and produce a punch list report per subcontractor, with automatic time stamps on photos and messages.
Built-in tools have one big advantage: the data is already there, so nobody pastes anything. Their limit is the same as the chat approach: the update is only as good as the daily logs, so the five-minute capture habit still matters. For smaller firms without that software, the voice-note-and-template method above costs a chat assistant subscription and a bit of discipline. If deliveries and trades keep slipping in your updates, the fix is upstream, and AI scheduling for subcontractors and deliveries is the place to look.
Checking it worked after a month
Measure three things before and after a month of AI-drafted updates and snag lists:
- Client "how's it going" calls and messages per job per week. This is the number that should fall first.
- Time spent writing updates and snag lists. Note it for two weeks before and two weeks after.
- Snags open at handover and days to close the list. A clearer list, sent to each trade on the day of the walk, usually closes faster.
If calls have not fallen, read the last four updates as if you were the client. The usual culprit is the "Coming next week" section being vague ("carry on with kitchen"), which leaves the client guessing and phoning. Tighten the prompt to ask for days and effects, and check again after another month.
Questions builders ask about AI updates and snag lists
Can I let clients see the AI snag list directly?
Yes, once you have checked it. Send the client-facing version, which shows what will be fixed and by when, not who caused it. Keep the trade-facing version internal. Ask the client to add anything they think is missing within a set period, so the list becomes the agreed record rather than one of several competing lists.
Does AI work on site with poor phone signal?
Record voice notes and photos on the phone as normal; they save without signal. Transcribe and draft once you are back in coverage, in the van or at the office. Most chat assistant apps need a connection to process anything, so plan the drafting step for when you have one rather than trying to do it in a basement.
Should the update mention problems with subcontractors?
Tell the client about the effect, not the blame. Write that the plastering finish has moved from Tuesday to Thursday and what that does to the programme. Naming a subcontractor's failings in a client update invites the client to take sides and can cause trouble if the relationship with that trade needs to continue.
Further reads
- AI Estimating Software for Small Builders: Six Options Compared — Six estimating tools compared, if pricing is your next bottleneck.
- Can AI Produce Accurate Estimates for a Small Building Firm? — How far to trust AI on the numbers side of a building job.
- How to Set Up Human Review for AI Work Without Slowing Down — Set up a quick review step so nothing unchecked reaches a client.
- How to Turn Handwritten Forms Into Spreadsheet Data With AI — Turn paper site forms and diaries into data you can search.
- How to Turn Meeting Notes Into Tasks Automatically With AI — Convert site meeting notes into tasks with owners and dates.
- What to Do When AI Gets Something Wrong With a Customer — What to do if an AI-drafted message upsets a client.
- AI for Interior Design Studio Admin: Sourcing, Quotes, Updates — Where AI saves a design studio real admin hours: supplier PDFs into schedule rows, quote wording, chasers and Friday client updates.
- Photo Checklists and Quality Control for Cleaning Teams Using AI — Set checkpoints a camera can prove, a fixed photo set per clean, an AI pass that flags which jobs need a supervisor, and clear privacy rules for clients' homes.
- How Garages Use AI to Send Repair Updates Customers Appreciate — How a small garage can turn technician shorthand into clear, timely repair updates with AI, and where those messages go wrong.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Buildertrend announcement of its AI Client Updates feature; Fieldwire punch management feature page.