Client updates that stop becoming phone calls

The phone calls that exhaust a project manager aren't the difficult ones. They're the call that asks, for the third time this week, "where are we on the kitchen?" Each call costs you twenty minutes and gives the client nothing they couldn't have read in a one-line email.

The update pattern that works

A weekly client update that has the same shape every time — what got done, what's next, when the next milestone lands — answers 80% of the questions your client could plausibly ask. You don't need to invent fresh copy. You need the cadence.

• A milestone lands (subfloor finished, kitchen rough-in complete) — that fires an update.
• A photo gets tagged to the job from the foreman's phone — that's the second item.
• The next inspection is on the calendar — that's the third.

The bulk of what reads as "good client communication" isn't wordsmithing. It's the discipline of sending the update the same day the milestone landed, instead of "after I get back from this other site."

Why this works even when the update is short

A client receiving a one-paragraph update every Thursday afternoon isn't going to call on Friday morning to ask whether anything has changed. They're going to wait for the next one. The call doesn't happen because the question was already answered.