A weekly remodel client update needs four elements: what was completed this week, what's scheduled for next week, any decision the client owes the team, and a photo. Sending it on a fixed day regardless of whether anything went wrong is what actually stops reactive "where are we?" calls, because the client already knows before they'd think to ask.
The "where are we?" call is the most predictable event on a remodel, and also the most avoidable. It doesn't happen because the job is behind — plenty of on-track jobs generate it. It happens because the client's last piece of information is a few days old, and silence is easy to read as a problem. The fix isn't more availability on your part. It's a client update, sent on a schedule, whether or not anything happened worth reporting.
The real cost of poor communication isn't just an annoyed client
In 2018, FMI Corporation and PlanGrid surveyed nearly 600 construction leaders for a report called Construction Disconnected. They found that respondents traced 48% of all project rework back to poor communication (26%) and bad or missing project information (22%) — a combined estimated $31.3 billion a year across the U.S. construction industry. That number is about internal team rework, not client relations directly, but it points at the same root cause: when the people who need information don't have current, reliable information, the job pays for it — in redone work on the crew side, and in anxious phone calls on the client side.
What a client actually needs to hear every week
- What got done this week — specific, not a mood. "Rough plumbing passed inspection Tuesday, cabinets arrive Thursday" beats "things are going well."
- What's planned for next week — sets the expectation before it needs correcting.
- Any decision you need from them — a tile choice, a change-order sign-off, a scheduling conflict. Naming it explicitly, with a date it's needed by, is what actually gets a timely answer instead of a stalled decision.
- One photo — it does more reassurance work than a paragraph of description, because it's evidence, not a claim.
Why "only when something's wrong" backfires
It feels efficient to only message when there's news. In practice it trains the client to interpret silence as risk, because the only signal they've ever gotten from you is bad news. A fixed-cadence update — even a two-line "quiet week, on schedule, next inspection Thursday" — does something a reactive message can't: it proves the plan is being watched even when nothing is happening. That's the actual product being sold in a status update — not information, reassurance that someone's still driving.
Terms worth being precise about
A check-in is the site conversation itself — the walkthrough, the phone call, the moment progress and problems actually get discussed. A status report or client update is the written artifact that goes out afterward, translating the check-in into what the client needs to know. A change order is a formal, priced adjustment to the scope — distinct from a decision request, which is smaller and doesn't necessarily change the contract. Conflating these is how a client update turns into either a legal document or a diary entry — neither of which does the reassurance job it's supposed to do.
A quiet week is still worth sending
The instinct on a boring week is to skip the update — nothing happened, why bother the client. That instinct is backwards. A quiet week is exactly when the update does the most work, because it's the one that costs you nothing to send and reassures the client the most: "Quiet week — demo wrapped Monday, rough plumbing starts Wednesday, nothing needed from you." Two lines, thirty seconds to write, and it closes the door on the phone call you'd otherwise get Thursday night. Save the longer version for weeks with an actual decision or milestone in them.
Keeping the tone right
The update fails if it reads like a status report from a system the client didn't ask to use. Write it the way you'd say it standing in their kitchen — short sentences, plain terms, no invented urgency. "Inspector's booked for Thursday, we're on track" does the job; "Phase 2 milestone tracking nominal" does not. The client isn't grading your vocabulary. They're checking whether the person running their job still has a handle on it, and the update is the evidence.
Keeping it consistent across three jobs at once
On one job, remembering to send Friday's update is easy. Running three or four concurrent jobs, it's the first thing that slips — usually the job that's going fine, because the squeaky wheel gets the attention. The fix is a fixed structure you fill in rather than compose from scratch each time: same four fields, same day, every job, every week. Some remodelers keep this in a template doc; in early access, tools like Lilli can draft the update from the check-in notes you log, so the four fields get filled from what actually happened on-site rather than reconstructed from memory on a Friday afternoon. Either way, the discipline that matters is the fixed structure and the fixed cadence — not which tool holds it.
Questions, answered.
How often should a contractor update a remodel client?
Weekly, on a fixed day, regardless of whether anything eventful happened. A quiet week is still worth a two-line update — it's what tells the client nothing needs their attention, which is exactly the reassurance they're looking for.
What should a client update actually include?
Four things: what got done this week, what's planned for next week, any decision or approval you need from them, and one photo. Anything longer turns into a report nobody reads; anything shorter leaves out the thing they actually needed to know.
Why do clients call asking "where are we?" even when the job is on track?
Because silence reads as a problem, not as good news. Without a scheduled update, the client's only information about the job is whatever they can see or infer, and uncertainty defaults to worry. A predictable update replaces that inference with information.
What's the difference between a check-in and a status report?
A check-in is the site conversation or walkthrough where progress and issues get discussed in person or by phone — the source material. A status report is the written artifact that goes to the client afterward. The check-in generates the information; the update is what you do with it.
Should bad news wait for the weekly update or go out immediately?
Immediately, on its own — a slipped inspection or a supply delay shouldn't sit in a queue until Friday. The weekly update is the steady baseline; anything that changes the client's plans gets its own message the day you know about it.
How do you keep updates consistent across multiple jobs at once?
Use the same four-part structure every time, for every job, so writing the update is a fill-in-the-blank exercise instead of a fresh essay. Whatever tool holds your job notes — a template, a shared doc, or something that drafts the update from your check-in notes for you to approve — the discipline is the fixed structure, not the tool.