How often should a builder update a customer?

Agree a cadence that fits the job, then update when something meaningful changes: a stage completes, a decision is needed, timing moves or the customer needs to know what happens next.

What should a construction progress update include?

Include what happened, useful evidence, anything that changed, what you need from the customer and the next expected step. Be clear when timing is provisional.

Are photos enough for a customer update?

Usually not. A photo needs context. Explain what the customer is looking at, why it matters and whether there is a decision or action attached to it.

How to send better construction progress updates to customers

Customers rarely need a minute-by-minute diary. They need confidence that the work is understood, the next step is clear and someone will tell them when a decision is needed.

Why customer communication becomes admin

Updates are often written late in the day, after the useful facts are spread across photos, crew messages and the owner's memory. That makes communication inconsistent: too much detail when the job is calm, too little when something has changed.

The answer is not sending more messages. It is capturing the right facts once and reusing them in a clear customer-facing format.

Communication principle

A good update answers the customer's next question before they have to ask it.

The five-line progress update

Where are we? Name the current stage or milestone.
What happened? Summarise the work completed since the last update.
What proves it? Include the clearest job-linked photo or document.
What changed? Explain any access, scope, timing or variation issue early.
What happens next? Give the next action, owner and expected timing where known.

Use evidence, not performance theatre

Customers do not need a gallery of random site photos. They need evidence that helps them understand progress: a prepared area, a concealed installation before it is covered, a key stage completed or the finished result.

Keep uncertainty visible. “We expect to return on Thursday, subject to the material arriving” builds more trust than an overconfident promise that later changes.

Make decisions easy to answer

If you need a customer decision, ask one clear question and include the consequence of waiting. Put the relevant variation, photo or option beside the question rather than sending the customer searching through a thread.

Keep site capture simple

Installers should not have to write a polished customer email from a phone. A quick photo, voice note or short site note can give the office enough factual material to assemble the update. The office remains responsible for customer communication and judgement.

Practical test

Read the update as a customer who was not on site. If you cannot tell what changed, whether you need to decide anything or what happens next, rewrite it.

Key takeaways

Useful updates are structured, not constant.
Photos need context and a clear reason for being included.
Honest timing and explicit next actions protect customer confidence.

Next step: use the customer communication SOP and the site photo guide to tighten the process.