The client chooses a fixture by text, but the site supervisor and purchasing contact miss it. Renovation contractor client updates fail when the decision lives in a message thread instead of the job record.
Set one weekly update. Put every decision back into the job record. Keep it short. Keep it attached to the job.
Set the renovation contractor client updates routine before work starts
Do not wait for the client to ask what is happening. Agree on the update routine during the project handover.
Name the sender. Name the client contact. Pick the delivery channel and delivery day. Write those details in the job record so nobody has to guess.
Name one sender and one client contact
Give the update to the project manager, site supervisor or owner responsible for the whole job. One person gathers the facts and sends the message.
Do not let every crew member give separate promises about dates, selections or price. Site conversations still happen. The named sender confirms anything that changes the job.
Ask the client to name one contact who can make decisions. If an owner, designer and property manager are involved, record who can approve scope, selections, price and schedule changes.
Copy other contacts when needed. Keep one decision owner.
Pick a delivery day that protects next week’s work
Send the weekly site update early enough to get answers before the next dependent task starts. Work backwards from the crew schedule, material orders and subcontractor bookings.
If cabinets cannot be ordered without hardware selections, the answer date must come before purchasing needs to place the order. If a wall cannot close before an inspection, the update must show that hold point before boarding starts.
Use the same delivery day each week. The client learns when to expect questions. Your team learns when site notes need to be ready.
Separate weekly updates from urgent calls
Tell the client what can wait for the weekly message and what needs an immediate call.
A routine selection, progress photo or next-week plan can wait. A safety issue, blocked access, hidden damage or decision that stops today’s work cannot.
Call about the urgent issue. Then record the answer in writing. The weekly update should carry the result, not become the first notice of a problem that stopped the crew days earlier.
Use the same weekly site update structure
A client should be able to scan the message and find the work completed, open decisions, approved changes, blockers and next stage.
Do not write a diary. Use the same headings every week.
Put decisions at the top
Start with questions that need a client answer. Give each question an answer date and name the work it affects.
A useful decision request says:
- what needs a decision
- the room or work area
- the available option or required specification
- who must answer
- when the answer is needed
- what work waits if the answer is late
Do not bury a selection request under photos and general progress notes. If the crew needs the answer, put it first.
Describe completed work by area and stage
Name the room, system or stage. State what reached a clear stopping point.
Write that the bathroom substrate was prepared and is ready for the required inspection. Do not write that the bathroom is mostly moving along.
Visible results help the client understand progress. They also support billing when the payment schedule is based on completed stages.
Show work underway and work planned next
Work underway is open work on site now. Name the person or trade responsible for the next action.
Work planned next is different. State what the crew expects to start and what must happen first. That condition might be a client selection, material delivery, completed preceding trade, permit-related step or inspection.
This distinction catches bad handoffs. A subcontractor cannot start just because the schedule says so. The preceding work must be complete and the area must be ready.
Record each fact once under the most specific heading. Use the action index only to point to the detailed entry below. If a decision or inspection blocks the schedule, refer to that entry instead of writing it again.
Use this blank template for every project:
Project: [client, address and job reference] Update date: [date] Sent by: [name] Client reply contact: [name and channel] Action index - [short action and pointer to the detailed entry below] Work completed - [room or area, completed stage] Work underway - [room or area, current work, responsible person] Photos - [location, subject, reason for inclusion] Decisions needed - [decision reference, question, owner, answer date, affected work, status] Access - [area, access arrangement, date needed, work affected] Inspections - [inspection reference, work area, inspection or check, status, work held until complete] Pending changes - [change reference, condition or request, pricing status, affected work, work held] Approved change orders - [approval or change-order reference when one exists, scope, price effect, schedule effect] Contract amounts - Original contract amount: [amount] - Approved change total: [amount] - Revised contract amount: [amount] Schedule blockers - [reference to the detailed decision, inspection or change entry, consequence, next task] Work planned next - [planned work and what must happen first]
Save the template against the job before the first update is due.
Collect site facts without rewriting the daily report
The daily site report records what happened. The weekly update tells the client what changed, what needs approval and what comes next.
Keep both records. Give them different jobs.
Pull facts from the site record
Use the daily record to collect progress, crew activity, deliveries, site conditions and blockers. The person sending the update should review those records before writing.
For the field-record process, use a daily site report that captures each renovation job. Pull only the client-facing facts into the weekly message.
A missed delivery matters if it moves installation. A crew note about reorganizing the van does not. A damaged substrate matters if it changes scope. Routine internal instructions do not.
The test is blunt: does the fact affect a client decision, cost, date, access requirement or completed stage? If not, leave it in the daily record.
Add photos with a job to do
Every photo needs a location, subject and reason for inclusion.
A useful caption might identify an open wall in the upstairs bathroom and show the hidden condition that affects the quoted work. Another might show completed waterproofing before it is covered.
Do not send an unexplained photo dump. The client should know whether each image records progress, asks a question, supports a change order or shows a blocker.
Keep the original image with the job record. Use the weekly message as the client-facing view.
Check subcontractor handoffs
Ask each subcontractor what they finished, what remains open and what they need before returning. Compare that answer with the next trade’s start condition.
Set a collection cutoff on the delivery day. Require the site supervisor and each trade lead to submit exceptions by that cutoff. Before issuing the update, the sender checks those exceptions against the daily record, current schedule and open decision log.
Keep one site decision log
A text thread is not a decision system. The client may choose a fixture by text, but the site supervisor and purchasing contact can still miss the answer.
Use a site decision log. Keep selections, approvals, declined options and unanswered questions together.
Record each decision as soon as it appears
Give every decision its own row or entry. Record:
- date raised
- room or work area
- decision required
- options or exact specification
- cost effect
- schedule effect
- decision owner
- answer needed by
- status
- approval record
Use plain status labels such as open, approved, declined or replaced. Do not mark an item approved because the client sounded positive on a call.
Open the site decision log before the next project meeting and enter every unresolved selection, approval and blocker.
Record selections precisely
A selection needs enough detail for purchasing and installation. Record the product, finish, location and quantity when those details matter.
Attach the client’s written approval. Then tell the site supervisor and purchasing contact. A choice is not closed until the people doing the work have the same instruction.
If the client replaces an earlier selection, keep the old entry and mark it replaced. Add the new decision separately. Do not erase the trail.
Set the answer date from the work
Do not pick an arbitrary deadline. Start with the dependent task and work backwards through ordering, delivery, inspection and installation.
The crew may be ready to close a wall, but an inspection or client selection remains unresolved. Mark the wall as blocked. Name the missing step and the person responsible for clearing it.
Stop extra work until the change order is approved
A hidden condition is not automatic permission to spend the client’s money. Stop the affected work. Record what differs from the quote. Price the extra labour and materials. State any schedule effect. Get written approval.
Keep the change separate from the original scope.
Show the original scope and changed condition
Start with the quoted work and its exclusions. Then describe what the crew found or what the client requested.
State the extra work needed. Include the price effect and schedule effect. If either is still being worked out, say that it is pending. Do not present a pending amount as an approved charge.
Use the contractor change order process for Canadian electrical work as a practical stop, write, approve and proceed example. The control method also applies to other renovation trades.
Worked example: Oak Street change control
The house example is an electrical job. R. Chen’s Quote Q-1847 covered a bathroom exhaust fan, 150 mm and ducted through the roof, plus four LED downlights. The quoted total was 1,105 sample currency units.
The ceiling was lined. The quote excluded chasing. Extra cable and chasing were approved on site as a 160 change order before the electrician continued.
Invoice INV-1847 was 1,265. The update should show the approved change order separately from the original quote and state whether it affects the next stage.
Show it in the weekly update like this:
Approved change orders - Extra cable and chasing: 160 sample currency units Reason: ceiling lined; Quote Q-1847 excluded chasing Status: approved on site before work continued Invoice effect: INV-1847 total 1,265 Work status: extra work started after approval
Carry the approval through the job
Once approved, update the site decision log, crew instruction, schedule, cost tracking and invoice record. Use the real approval or change-order reference across those records when one exists.
Do not leave the approval trapped in the client’s text thread. The person ordering materials and the person doing the work both need it.
Report delays by cause and consequence
Do not write that the project is delayed. That tells the client nothing useful.
Name the blocked task. Name the cause. State the consequence and the next action.
Separate the causes
Keep client decisions, site conditions, contractor work, subcontractor dependencies, material issues and inspections separate.
If the electrician cannot start because framing remains open, say which framing item needs completion and who owns it. If material has not arrived, name the affected installation and the action being taken. If access was unavailable, record the area and the work that could not proceed.
Do not use delay language to assign blame. Use it to assign the next action.
Show what moves next
A blocker should point to a task. State whether the crew can move to another area, whether a subcontractor booking needs to change or whether the whole stage must wait.
Update the planned-work section after making that decision. Do not leave blocked work listed as next week’s firm commitment.
Check permit, licensing and safety questions with the right body
Check building permit and inspection questions with the official local authority having jurisdiction over the project address.
For trade licensing, check the relevant official provincial or territorial trade licensing regulator. For safety requirements, check the relevant official provincial or territorial safety regulator. Do not assume the same body handles both questions.
Record who will ask, what question they will ask and which work waits for the answer. Then put the result in the job record.
Connect the update to cost tracking and billing
The client update is not an invoice. It should still agree with the financial record.
Show approved changes separately. Match completed-stage notes to the agreed billing schedule. Flag pending costs without calling them charges.
Keep original and changed scope apart
Do not quietly fold an approved extra into the original contract amount. The client should be able to see the original work, approved change orders and revised amount.
That separation also protects cost tracking. Labour, materials and subcontractor costs should carry the correct job and change reference. Otherwise the original scope can look unprofitable while the approved extra looks free.
Match billing to completed work
If the contract uses progress billing, describe the completed stage in the same terms used by the payment schedule. Avoid broad claims that the renovation is partly complete.
Use a renovation progress payment schedule tied to completed stages to set those billing points before work begins.
A progress invoice should follow the agreed stage and approved changes. The weekly update supports that record. It does not create a new payment term.
Keep pending costs pending
A possible extra is not an approved extra. Mark it pending while you inspect, price and request approval.
Tell the client which work remains stopped while the cost is pending. Once approved, carry the change into renovation contractor client updates, move it to approved change orders and update the cost record. Then tell the crew which task can start.