Builder Client Communication: Set a Weekly Site Routine

The client chooses a fitting in a message. The buyer orders the old specification and the site supervisor installs it. Builder client communication breaks down when site decisions never reach the job record.

Set the send day. Pull out the decisions, variations, blockers and work planned next. Send them from one person and record every answer against the job.

Agree the builder client communication routine before work starts

Set the routine during the job handover. Do not wait until the client starts asking for progress reports.

Write down who sends the update, who answers for the client, which channel you will use and when site information must reach the sender. Put those details in the job record.

The weekly update says what is finished, what is blocked and what needs a decision. It does not replace the quote, contract, written variation, invoice, inspection record or certificate.

Name one sender and one client decision-maker

Give the update to the owner, project manager or site supervisor who can see the whole job. That person gathers the facts and sends the message.

Do not let separate tradespeople promise different dates, prices or specifications. They can answer site questions. They should pass anything that changes the scope, programme or cost back to the named sender.

Ask the client to name the person who can approve decisions. A homeowner, designer and property manager may all comment, but you still need to know who can approve selections, variations and access arrangements.

Record any limits on that authority. A designer may choose a finish without being able to approve extra cost. A positive comment is not approval.

Set the cutoff from orders and trade bookings

Choose the update time by working backwards from the job. Look at material orders, client-supplied items, inspections and subcontractor bookings.

If the next trade depends on a selection, put the answer date before the point when you must order or release the work. If the answer misses that point, report the affected task as blocked.

Set an internal cutoff for site notes. The sender needs time to check the diary, speak to trade leads and compare the programme with what is actually ready.

Call urgent problems when they happen

Do not hold an urgent problem for the weekly site update. Call when access fails, a concealed condition stops work or a safety issue changes the plan.

Record the call afterwards. State the condition, the instruction and who gave it. Put the result in the next update so the client-facing record stays complete.

Build the weekly site update around work needing action

A useful builder client communication update is not a progress newsletter. It tells the client what needs an answer, what has changed and what can start next.

Use the same order each time. Put actions first. Keep background detail underneath.

Put client decisions at the top

Write each request as a job instruction waiting for an answer. Include:

• the room or work area
• the exact question or specification needed
• the person who must answer
• the answer date
• the task that depends on it
• the current status

Do not write “Please confirm bathroom fittings”. Name the fitting, location and information required. The buyer and installer must be able to use the answer without searching an old message thread.

Separate completed, current and planned work

Completed work has reached a clear stage. Name the area and what was finished.

Work underway is open on site now. State the next action and who owns it.

Planned work has not started. Name the dependency beside it. A subcontractor booking is not proof that the area is ready.

Before promising the next start, compare the preceding work with the incoming trade’s scope. A builder subcontractor quote comparison helps you check where one trade ends and the next begins.

Give every photograph a purpose

Add the location, subject and reason to each photograph. Say whether it records completed work, a concealed condition, a decision request or work before it is covered.

Do not send a photo dump. The client should understand why each image matters without guessing what part of the site it shows.

Keep the original photograph in the job record. The update is only the client-facing view.

Use a fixed blank template

The site decision log controls each client decision. Enter the full instruction there once, then use its reference in the action list, selection section and programme blocker instead of copying the wording.

Copy this structure into the live job. Remove headings that genuinely have no entry rather than filling them with vague progress comments.

Project: [client and address]
Job reference: [reference]
Update date: [written date]
Sent by: [name]
Client decision-maker: [name]
Reply channel: [channel]

Actions required from the client
- [decision reference, answer date and affected task; full entry held in the site decision log]

Work completed
- [work area or stage, completed work]

Work underway
- [work area, current task, next action, responsible person]

Work planned next
- [planned task, dependency reference that must be cleared first]

Selections and site decisions
- [decision reference and current status; specification held in the site decision log]

Access and client-supplied items
- [requirement, date needed, work affected]

Photographs
- [location, subject, purpose]

Sign-offs or checks holding work
- [sign-off reference, work area, responsible person, status and blocked task]

Pending variations
- [variation reference, condition or request, pricing status, work held]

Approved variations
- [variation reference, approved scope, price effect, programme effect]

Programme blockers
- [decision, sign-off or variation reference, consequence, next action and owner]

Quote, variation and invoice references
- Current quote: [reference]
- Approved variations: [references]
- Current stage invoice: [reference]

Pull client facts from the builder daily log

The builder daily log records site activity. The weekly update extracts the facts that the client must know or act on. They are separate documents with separate jobs.

Use the builder site diary process for refurbishment work to collect the underlying record. Do not copy the contractor job diary into an email and call it an update.

Filter every entry through the client test

Read the daily records and ask whether each event affects a decision, cost, date, access requirement, completed stage or sign-off. If it does, move it into the update. If it does not, leave it in the site record.

A damaged substrate matters when it changes preparation. A missing delivery matters when it blocks installation. Routine crew movements and internal reminders stay out.

Convert the site note into an action. A daily entry might say, “Kitchen wall not closed. Client has not confirmed the socket position.” The client entry becomes, “Decision [reference]: kitchen socket position needed; wall closing is blocked; client owns the answer; next action is written confirmation.”

This keeps builder client communication short without hiding the facts that control the job.

Check the next handoff on site

Walk the area before confirming the next trade. Check that preceding work is complete, access is available and the required selection or sign-off has been recorded.

The programme may show a start. The ceiling, floor or service route may show something else.

Ask the incoming trade what must be ready. Put any missing condition in the update with an owner and next action. Do not promise a revised completion date until the sequence is clear.

Keep one site decision log for selections and instructions

The site decision log is the bridge between the client’s answer and the work. It must show the current instruction without deleting the old one.

Give each decision a reference. Record the work area, question, answer owner, answer date, cost effect, programme effect, status and approval record.

Turn conversations into written instructions

A client may choose a fitting during a site walk or send a finish in a message. That choice is not ready for purchasing until you enter the exact specification in the job record.

Write the product or description, finish, location and quantity where those details matter. Attach the written answer. Pass the instruction to the buyer, site supervisor and installer.

Do not treat silence or a friendly reply as approval. Record the decision only when the client has answered the actual question.

Preserve replaced and declined choices

Do not overwrite an old selection. Mark it replaced or declined, then create the current entry.

That trail matters when an old specification remains in a supplier message or printed drawing. The buyer can see which instruction is live. The site supervisor can stop the wrong item being installed.

Set the answer date from the dependent task

Start with the work that needs the decision. Work backwards through ordering, delivery, preparation and installation.

Name the consequence without turning it into a threat. State that the affected task cannot be released until the answer is recorded. Then show the next available sequence when you know it.

Stop and document a variation before extra work starts

When the scope changes, stop the affected work. Compare the condition or request with the quote. Price the extra labour, materials and markup. State any programme effect and get written approval.

Keep pending variations separate from approved variations. Keep both separate from the original quote.

For a trade-specific example of the same control, use the plumber variation process for hidden work.

Show the quoted scope and the changed condition

Start with what the quote includes and excludes. Then state what the crew found or what the client requested.

Describe the extra work and its price effect. If pricing or approval is still open, label the variation pending. Do not add it to the approved total or tell the crew to proceed.

Worked example: the Oak Street variation

This house example is an electrical job. R. Chen’s Quote Q-1847 at 14 Oak Street covered a bathroom exhaust fan, 150mm and ducted through the roof, plus four LED downlights. The quote was 1,105 sample currency units.

The ceiling was lined and the quote excluded chasing. Extra cable and chasing were approved on site as a 160 variation. Invoice INV-1847 was 1,265.

The weekly update should keep the original quote and approved variation separate:

Carry approval into every working record

Move the approved variation into the crew instruction, purchasing record, programme, cost tracking and invoice record. Use the same reference throughout.

The message to the client is not enough. The people ordering and installing the work need the approved instruction. For a practical cost-record example, see electrician job costing for labour, materials and profit.

Put the UK sign-off route beside the blocked task

Do not write “waiting for inspection”. Name the work being held, the question being checked, the responsible person and the next action.

The route depends on the UK nation, location and work. Do not present one process as covering every UK job.

Record building approval against the work area

For building regulations approval in England or Wales, check the route with building control (opens in a new tab). Put the location, status and responsible person beside the task it holds.

For a Scottish project, check the building warrant and approval route through building standards in Scotland (opens in a new tab). Do not copy an English process into the Scottish job record.

For work in Northern Ireland, check the approval route with local council building control (opens in a new tab). Record the council area, responsible person and work held for approval.

The weekly update reports the status. It is not the approval itself.

Record the Part P responsibility where it matters

For relevant notifiable domestic electrical work in England and Wales, record who is handling the notification or self-certification route. Check the correct route with the applicable competent person scheme (opens in a new tab).

This Part P advice covers England and Wales only. It does not describe the electrical approval routes in Scotland or Northern Ireland.

Do not tell the client that the work is signed off until the required record exists. State what is complete, what remains open and which task is held.

Explain a delay by cause and consequence

A useful blocker entry names the blocked task, cause, consequence, owner and next action. Add the revised sequence only when it is known.

Separate client decisions from concealed conditions, subcontractor dependencies and sign-offs. Different causes need different actions.

Do not give a hopeful finish date to make the message sound better. Report the next controllable step.

Match the update to invoices and cost tracking

The amounts in the builder client communication update must come from the current job documents. Do not rebuild them from memory or site conversations.

Show the quote reference, approved variation references and current stage invoice. Leave pending variations out of approved totals.

Post approved variations under the same reference

When the client approves a variation, open the cost entry under that variation reference. Assign the labour entries and material receipts to it instead of burying them in the original quoted work.

Keep pending variations out of cost tracking for approved work and out of the stage invoice. Once the work is billed, compare the approved variation, its recorded labour and materials, and the stage invoice entry. Correct a missing or wrongly assigned cost before closing the stage.

Keep VAT wording consistent

Copy the net, VAT and gross treatment from the controlling quote or invoice. If you need to check the treatment, use HMRC guidance for VAT and businesses (opens in a new tab).

Do not explain tax rules inside the weekly update. Do not use the update to change the invoice. Correct the controlling document first, then report its current reference.

Tie progress statements to real stages

If an invoice depends on a completed stage, check the work before reporting that stage complete. A programme label is not proof.

A stage may look finished while a client decision or required sign-off still blocks the next trade. State what is physically complete and what remains held. Keep the distinction clear.

File the update with its evidence

Attach the sent update to the job record. Keep the client’s answers, variation approvals, photographs and supporting records with it.

Yes Foreman can hold the update and its job references in the same building job record used by the office and site team. The point is not another message channel. It is one current record for the people releasing the work.

Common questions

Should the client reply to the whole update?

For clean builder client communication, ask for replies against the named decision references. That makes each answer easier to place in the site decision log and pass to the crew.

If a reply changes several parts of the job, split it into separate instructions. Do not leave a long message for the buyer and site supervisor to interpret differently.

File the sent update, client replies and controlling records against the job before releasing the next trade.