The tiler is ready, but the client’s layout approval is buried in a private text thread. Builder client communication breaks down when the answer never reaches the supervisor, purchasing contact or subbie.
Set a weekly site update. Give it one sender. Put decisions first, then carry every answer back into the job record.
Set the builder client communication routine before work starts
Agree on the routine during the renovation handover. Do not wait until the client starts asking for updates or the crew is held up by a missing selection.
Record who sends the update, who answers for the client, when the message goes out and where replies must be sent. Add an urgent-contact rule for anything that cannot wait.
Name one sender and one client decision-maker
Give the update to the owner, project manager or supervisor who can see the whole job. That person collects facts from the site and sends one clear message.
Tradies can still speak with the client on site. They should not make separate promises about price, scope or start dates. The named sender confirms any conversation that changes the work.
Ask the client to nominate the person who can approve selections, access arrangements and variations. If an owner, designer and property manager are involved, write down who controls each kind of decision.
Copy other people when they need the information. Keep a named decision owner for every open question.
Pick the delivery day from next week’s work
Work backwards from the next task. Look at purchasing, subbie bookings, access needs and inspection hold points. Send the update early enough for the client to answer before those tasks are affected.
If the tiler needs a layout decision before setting out the room, the answer date must fall before the tiler arrives. If a wall cannot be lined before an inspection, show the inspection as a hold point before the lining work.
Use the same delivery day each week. Set a cutoff for site notes before the message is prepared. The sender then has time to check the facts instead of forwarding half-finished comments.
Keep urgent issues outside the weekly cycle
A weekly message is not an emergency channel. Call when unsafe access, hidden damage, a site condition or a missing decision stops work that day.
Record the call and the agreed action in writing. Put the result in the next update so the full project team can see it.
A client update does not replace a site safety record, incident process or required notification. Take WHS questions to the state or territory WHS regulator responsible for the job.
Pull the weekly site update from the job records
The site diary and client update have different jobs. The diary records what happened. The update extracts completed stages, open decisions, blockers and next actions.
Do not copy the diary into an email. Review it, check the facts and pull out only the items that affect the client or upcoming work.
Use the site diary as the factual record
Read the entries covering work completed, people on site, deliveries, site conditions and work left open. The builder site diary process for renovation jobs explains how to capture those daily facts without turning them into a client message.
Include a diary fact when it changes a decision, cost, date, access arrangement or completed stage. Leave routine crew instructions in the site record.
A delayed delivery matters when it moves installation. An unfinished handoff matters when the next subbie cannot start. A note about cleaning the trailer does not belong in renovation client communication.
Collect exceptions from supervisors and subbies
Ask the supervisor and affected subbies what they finished, what remains open and what they need next. Set a fixed cutoff for their answers.
Compare each claim with the site diary. A subbie may say the room is ready, while the diary shows an unfinished penetration, missing substrate repair or untested service.
Clear scope and handoff responsibilities before work starts. The builder subbie quote comparison checklist helps you line up exclusions, responsibilities and scope before those gaps reach the site update.
Add photos only when they prove something
Give every photo a location, subject and purpose. Write what the client should notice.
Use a photo to show a completed stage, record a hidden condition, identify a decision area or explain a blocker. Keep the original image with the job record.
Do not send an unexplained photo dump. A close-up of an open wall means little without the room, wall location and reason for showing it.
Use fixed headings so decisions stay visible
The weekly site update should look familiar every time. The client should be able to find decisions, completed work, blockers and planned work without reading a progress essay.
Put questions and answer dates first. General progress comes later.
Put decisions and answer dates at the top
Write each request as an action. Name the room, the answer required, the decision owner, the answer date and the task affected.
Do not write “Please confirm tiles”. Write which tiles, which room, which surface and what work waits for the answer.
If a choice affects cost or time, say so beside the request. If the effect is not known yet, mark it pending rather than guessing.
Separate finished, current and planned work
Completed work has reached a checkable point. Name the room or stage and state what was finished.
Work underway is open on site now. Name the next action and who owns it.
Planned work is not a promise without conditions. State what must happen first, such as a selection, delivery, inspection, access arrangement or completed trade handoff.
Put blockers beside the affected task
“Job delayed” is useless. Name the blocked task, the cause, the person responsible for the next action and the consequence for following work.
Keep different causes separate. A client selection is not a delivery delay. An unfinished subbie handoff is not an inspection hold point.
If Friday’s message says work is progressing but hides the missing access approval holding Monday’s task, the message has failed. Put the block where the client can act on it.
Copy this blank weekly update template
Use the same builder client communication template on every renovation. Delete headings that do not apply, but do not move decisions below general progress.
Project: [client, site address and job reference] Update date: [date] Sent by: [name] Client decision-maker: [name] Reply channel: [email or agreed job channel] Actions needed - [reference, action, owner, answer date, affected work] Work completed - [room or area, completed stage] Work underway - [room or area, current task, person responsible] Work planned next - [task, intended start point, condition that must be cleared] Decisions needed - [reference, room, exact question, decision owner, answer date] Access - [area, access needed, date, task affected] Inspections and hold points - [area, required check, status, work that cannot start] Pending variations - [reference, changed condition or request, pricing status, work held] Approved variations - [variation reference, approved scope, price effect, schedule effect] Photos - [location, subject, purpose] Blockers and follow-up - [blocked task, cause, next action, owner]
Save the blank record against the job before the first update is due. Assign its sender at the same time.
Keep one site decision log behind the message
The weekly message asks for answers. The site decision log controls what happens after the client replies.
Use it for selections, access instructions, approvals, declined options and unanswered questions. Give each item its own reference so the update, diary and crew instruction point to the same decision.
Record enough detail to buy and install
For each decision, record the date raised, work area, question, decision owner, answer date, status and approval record. Add the cost or schedule effect when there is one.
A selection is not ready because the client named a colour in a text. Record the exact product, finish, location and quantity where those details matter.
Attach the written answer. Tell the purchasing contact, supervisor and affected subbie. The decision closes only when the people doing the work have the same instruction.
Keep replaced decisions visible
Do not delete the first selection when the client changes their mind. Mark it replaced and add the new instruction as a separate entry.
This leaves a usable trail when ordered materials, labour or dates are affected. It also stops an old screenshot from being treated as the current direction.
Turn every answer into work
A client reply is not the end of the process. Convert it into a purchase instruction, site task, updated drawing note, access booking or variation step.
Name the person responsible. Give the action a status. Check it before telling a subbie that the area is ready.
Put Australian variations in the update without replacing the contract record
A weekly update can show the status of a variation. It is not automatically the formal variation document required for the job.
When the work differs from the quoted scope, stop the affected task. Compare the site condition or client request with the quote. Write the extra labour and materials, price effect, schedule effect and work being held.
Follow the contract process. For questions about domestic building contracts or required variation records, ask the licensing regulator for the state or territory where the work is being done. For NSW work, use NSW Fair Trading (opens in a new tab) for that question rather than relying on an old form or another builder’s process.
Separate the original scope from the changed work
Start with the quoted item and any stated exclusion. Then describe what was found or requested.
Do not rewrite the original quote to make the extra work disappear. Give the variation its own reference and approval status.
If pricing or timing is still being worked out, label it pending. Do not show it as approved. Do not let a general “go ahead” message become the only record if the contract process calls for something else.
Worked example: show the Oak Street variation on its own
The house example is an electrical job. R. Chen at 14 Oak Street had Quote Q-1847 for a bathroom exhaust fan, 150mm and ducted through the roof, plus four LED downlights. The quote total 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 site update should not blend the extra work into the original quote:
Approved variations - Extra cable and chasing: 160 sample currency units Reason: the ceiling was lined; Quote Q-1847 excluded chasing Status: approved on site before the affected work continued Invoice effect: INV-1847 total 1,265 Work status: extra work proceeded after approval
The costs of the variation are not supplied, so do not calculate profit from the invoice total. The point here is the document trail, not a rate card.
For the detailed site sequence, use the Australian electrician variation process: stop, write, approve and then proceed.
Carry approval into every affected record
Once approved, update the crew instruction, program of works, site decision log, purchasing note, job costs and invoice record. Use the variation reference across those records when one exists.
Do not leave approval trapped in a text thread. The supervisor and affected subbie need the current scope before work restarts.
Report delays with a cause and a clearing action
Name the task that cannot start. Then state the cause, consequence, owner and next action.
Write “Bathroom tiling cannot start until the layout is approved by the client” rather than “Tiling delayed”. Add the answer date and the task that follows tiling.
For a trade handoff, name the unfinished item and who must complete it. For a delivery, name the material and affected installation. For an inspection, state the work held until the check is complete.
Do not promise a revised date while the cause remains open. State what will clear the block and update the program of works when that action is complete.
Call urgent site issues when they happen. Record the outcome after the call, then include the resolved or open item in the next weekly message.
Store the sent update with the job
Keep the sent message, labelled photos, client replies, site decision log and variation records together. Builder client communication is part of the job record, not a loose collection of inbox searches.
Use the same job reference on the quote, update, variation and invoice. Keep the document names stable so the office, supervisor and subbies know which record is current.
Check that ABN and GST labels stay consistent across the job documents. Take tax questions to the Australian Taxation Office (opens in a new tab) rather than guessing from an old invoice.
Yes Foreman can keep the weekly update beside the job, quote and follow-up actions. Use it after you have set the routine and named the people responsible; the tool does not replace those decisions.
Common questions
Who should send the weekly site update?
Choose the owner, project manager or supervisor who can see the full renovation. One sender prevents different people giving the client conflicting scope, price or date information.
Tradies can supply site facts. The named sender checks those facts and issues the message.
How long should a weekly site update be?
Make it long enough to show decisions, completed stages, blockers and planned work. Cut diary detail that does not affect the client, cost, access or upcoming tasks.
If the client cannot find an answer date quickly, the update needs editing rather than more detail.
Where should client approvals be stored?
Keep the written reply with the decision entry and the job record. Then carry the instruction into purchasing, the program of works and the affected subbie’s task.
Do not rely on the sender’s inbox or a tradie’s private phone as the only copy.
Before leaving the site, create next week’s blank update. Assign the sender and add the open decisions already holding work. That is where builder client communication becomes a routine instead of a Friday scramble.