ConsultantStack

Client conversations · 2026-11-13

What Actually Belongs in a Weekly Client Status Update

Nobody asks you to send it. You send it anyway, because you have learned the expensive way what silence costs: a client who fills the space their own way, a stakeholder who assumes the worst, a request for "a quick update" arriving at the worst time of your week. A good status update does not add work. It subtracts the work of being asked.

The test of a good update

An update is not a summary of what you did. It is an answer to the five questions your client is silently asking:

  1. Is the project still on track?
  2. What happened this week?
  3. What happens next?
  4. What do you need from me?
  5. What is at risk, and how real is it?

If your update answers those five, it is done, regardless of length. If it answers number two and nothing else, it is a diary, and it will produce more questions than it prevents.

The six lines that do the work

The whole update fits in six lines. After the greeting, each line earns its place:

Line 1 — Status. On track / at risk / blocked, in one word, up front. No burying the lead.

Line 2 — What happened. Three bullets maximum, each with a number or a deliverable attached. "Finished the data audit — found two sources still missing" beats "made progress on the audit".

Line 3 — What is next. The next milestone and its date. One line.

Line 4 — Decisions needed. Nothing rhetorical. "Need your call by Thursday: keep all six pages in scope, or cut two to hold the date." A decision with an option attached gets answered; an open question gets polite silence.

Line 5 — Money. One line on hours versus estimate for fixed-fee work, or a budget position for time and materials. This line alone stops the "just wondering how we're tracking" emails.

Line 6 — Risk. One honest sentence about anything slipping, with the date it becomes a problem. Bad news is cheaper the earlier it is delivered, and this line is where you deliver it on your terms.

What to cut

Half of what people put in updates makes them worse:

  • "Just a quick update" — an apology for existing. Cut it; you are being paid to communicate.
  • "Everything is going great" — a claim with no evidence, which reads as avoidance.
  • Task lists. Your to-do list is not news. What happened, not what you are about to do.
  • Emotional commentary. "It was a tough week but we pushed through" tells the client nothing they can act on.

When in doubt, apply the test: does this line answer one of the five questions? No — cut it.

Bad news goes first, with a choice

The update where something is wrong is the update where most people hedge, and hedging is the expensive move. The client does not react to the problem; they react to the delay in hearing about it.

Bad news belongs in line 1 — "At risk" — with the cause in line 2, the choice in line 4, and the date in line 6. Slipped a date? Say the new date and the one decision that could recover it. Over budget? Say by how much, and offer the scope cut that brings it back.

Clients tolerate problems. They do not tolerate discovering problems in a meeting you scheduled after the fact.

Same day, every week

Consistency matters more than content. Send it the same day, at the same time, in the same format, every week — including the weeks nothing happened. A "nothing moved; next action is X on Thursday" update takes three lines and is worth sending, because it establishes that you report by schedule rather than by event.

Once the rhythm is set, the update becomes one more deliverable on your list like any other, and you stop negotiating about it with yourself.

A worked example

Here is the whole thing, sent on a Wednesday afternoon, on a project that has just slipped:

Status: at risk.
This week: finished the audit, three of five sources; drafted section two; ran the workshop with your ops lead.
Next: full draft, Friday the 21st.
Need from you: one decision by Thursday — keep all five sources and move delivery to the 28th, or drop sources four and five and hold the 21st.
Hours: 18 of the 24 estimated; the workshop was not in the original scope.
Risk: sources four and five have not granted access. If access lands after Monday, the 21st is not realistic.

Six lines, ninety seconds to read, one decision attached to a date. Note what is absent: no apology, no story about how hard the week was, and no request for reassurance. The client's reply is a decision, not a question — which is the entire point of writing it this way.

When they reply with something the update should have answered

It happens, and the fix is not a longer update. If a client asks "where are we on the budget", your line five was too vague; if they ask "what do you need from me", line four was missing or rhetorical. Add the missing line next week rather than replying with an essay, and keep the format stable — the format is what makes the update skimmable in the first place.

One exception: if the same question arrives twice, the answer belongs in the update permanently. A recurring question is feedback on the template, not on the project.

Where it lives

The update should be written from the same place every week: your current project state. If you keep hours against estimate, decisions, and next actions somewhere you actually look, the six lines take ten minutes. If you reconstruct them from memory, they take an hour and get skipped.

That is why the habit and the record are the same habit. The record is not for the client; it is so that the update stops being a chore and starts being a by-product.

Related notes