Client Status Update Template (Copy and Adapt)

A status update is four fields, not an essay: where it is, what changed, what happens next, what you need. Fill those in and the message writes itself in under a minute — which is the only reason it will still be happening in three months.

The reason status updates stop happening is never that they are hard to write. It is that each one feels like a small composition task, and small composition tasks are exactly what a busy week eliminates. The fix is to stop writing and start filling in.

The master template

Use this for roughly 80% of updatesCopy and adapt · {{fields}} are yours to replace

Subject {{project}} — {{stage}}

Hi {{first_name}},

Where it is: {{stage}}
What changed: {{what_changed}}
Next: {{next_step}}, expected {{date}}
From you: {{what_you_need_or_nothing}}

{{your_name}}

Labelled fields look blunt the first time and then become the reason clients read the whole thing. Scanning four labels takes three seconds; parsing a paragraph takes thirty.

If the labelled format feels too clipped for your relationships, the same four fields work as prose. What matters is that all four are present and in that order — the client's questions arrive in that order, so answering them in a different one makes them re-read.

The same four fields, as proseCopy and adapt · {{fields}} are yours to replace

Subject {{project}} — {{stage}}

Hi {{first_name}},

{{project}} is now at {{stage}} — {{what_changed}}.

Next up is {{next_step}}, which I expect to have done by {{date}}.

{{what_you_need_or_nothing}}

{{your_name}}

What goes in each field

Filling the four fields well
Field	Good	Avoid
Where it is	"Waiting on your documents"	"In progress" for everything
What changed	"Submitted to the lender Tuesday"	"Working on it"
Next	"Their review, usually 5–7 days"	"Will keep you posted"
From you	"Nothing needed" or one specific item	A list of four things

Four variations that cover the rest

No change since last timeCopy and adapt · {{fields}} are yours to replace

Subject {{project}} — no change, next update {{day}}

Hi {{first_name}},

No movement on {{project}} this week — still at {{stage}}. This stage usually runs {{duration}}, so we are on track rather than stuck.

Nothing needed from you. Next update {{day}}.

{{your_name}}

Blocked on the clientCopy and adapt · {{fields}} are yours to replace

Subject One thing needed to move {{project}}

Hi {{first_name}},

{{project}} is paused at {{stage}} until I have one thing:

  • {{specific_item}}

Once it arrives, {{next_step}} — usually within {{duration}}. A photo or partial version is fine to start with.

{{your_name}}

Offering to start with a partial version removes the most common reason people do not reply — they are waiting until they can send the complete thing.

Blocked on a third partyCopy and adapt · {{fields}} are yours to replace

Subject {{project}} — waiting on {{third_party}}

Hi {{first_name}},

{{project}} is with {{third_party}}. Submitted {{date_submitted}}; typical turnaround is {{duration}}.

I have {{what_you_did_to_chase}}. Nothing further we can do to speed it up — I will let you know the moment it moves.

{{your_name}}

DeliveredCopy and adapt · {{fields}} are yours to replace

Subject {{project}} is complete

Hi {{first_name}},

{{project}} is complete as of {{date}}.

What you have: {{deliverables}}
Where it is: {{location}}
{{outstanding_payment_line}}

If anything needs adjusting, reply here.

{{your_name}}

When to send them

Two triggers, both automatic in your head or in your tool: whenever the stage changes, and whenever a fixed interval passes with no change. The second is the one that prevents chasing, and the one people skip.

Weekly suits most service work. Fortnightly is enough for long compliance or legal matters.
Say the cadence out loud at kickoff — "you will hear from me every Friday" — so the client stops wondering.
Send the boring no-change ones. They are the reason the promise means anything.
Keep the day consistent. A predictable rhythm is what stops the client from setting their own reminder to chase you.

When the template is not the right tool

A template is for routine state. Three situations are not routine, and sending one of these as a filled-in form reads as indifference at exactly the moment the client is paying most attention.

Situations that need a written message, not a template
Situation	Why the template fails	Do instead
A significant delay with cost to them	Fields flatten something that needs acknowledgement	Write it, lead with the fact and the new date
You made a mistake	A form reads as avoiding responsibility	Say what happened, what you are doing, what it changes
The client is already unhappy	They will read structure as stonewalling	Call, then confirm in writing

The distinction is whether the client needs information or needs to feel heard. Templates are excellent at the first and actively harmful at the second. Everything else — which is most weeks — is the template.

Making it stick

A status update habit that survives a bad week

Templates live where you send from, not in a document you have to find
Every file has a named stage, so the first field is never a decision
The client-facing stage labels are written once, not improvised per message
A recurring slot in the week for sending the no-change updates
Something that tells you which files have gone quiet, so nothing is missed