Client Update Email Template (Project Status Update That Clients Trust)

A client update email needs four things: what's done, what's in progress, what's next, and anything you need from them — in that order, under 150 words, sent on a predictable schedule. That structure is what keeps a client calm without a call. Silence is what makes clients anxious, not slow progress — a client who hears nothing for two weeks assumes the worst, even when the project is actually fine. Below is the template, when to send it, and a prompt that writes it from your own project notes.

The four-part structure

1. Done — what's been completed since the last update, stated plainly, not buried in process detail.
2. In progress — what's actively being worked on right now.
3. Next — what happens next, with a date if you have one.
4. Needed from you — anything you're waiting on from the client, named specifically, not left implicit.

That fourth section is the one people skip, and it's often the most useful line in the email — a client who doesn't know they're the reason something is stalled can't fix it.

The template

Copy this straight into your email client and fill in the brackets:

Subject: [PROJECT NAME] — update, [DATE]

Hi [CLIENT NAME],

Quick update on where things stand:

Done: [What's been completed since the last update.]

In progress: [What's actively being worked on.]

Next: [What happens next, with a date if you have one.]

Needed from you: [Anything you're waiting on — or "Nothing right now."]

Let me know if anything's unclear.

[YOUR NAME]

Why short updates work better than status calls

A thirty-minute status call costs both people thirty minutes and usually covers information that fits in six lines. Most clients don't want a meeting — they want reassurance that things are moving and clarity on whether they owe you anything. A predictable written update, sent on the same day each week, delivers both without either person's calendar getting involved.

The predictability matters as much as the content. A client who knows an update lands every Friday stops emailing "just checking in" mid-week, because they trust it's coming.

Updates like this are easiest to write straight after your own weekly planning — a weekly review is a natural place to pull the "done, in progress, next" list from before turning it into a client-facing message. And if raw call notes are where the "next" and "needed from you" items actually come from, turning meeting notes into action items is the step that happens just before this one.

What to leave out

Internal process detail. Clients don't need to know you're between two draft versions or debating a tool — they need to know the deliverable is on track.

Hedging language. "Hopefully," "should be," and "fingers crossed" read as uncertainty about your own work. If a date genuinely isn't confirmed, say so plainly — "date to be confirmed by [DAY]" — rather than hedging around it.

A wall of detail to prove you've been busy. A long update reads as anxious, not thorough. If it's over 150 words, cut it down before sending.

The copy-paste prompt

Paste in whatever notes you have — a to-do list, a scribbled progress note, anything — and this turns it into the four-part update above.

You are a plainspoken assistant writing a client project-update email for a freelancer or
solo business owner. The goal is a short, calm update that reassures without over-explaining.

Context:
- Project name: [PROJECT NAME]
- Client name: [CLIENT NAME]
- What's been completed since the last update: [NOTES]
- What's actively in progress right now: [NOTES]
- What happens next, and by when if known: [NOTES]
- Anything you're waiting on from the client: [NOTES, OR "NOTHING RIGHT NOW"]

Task: write a client update email with exactly four sections — Done, In progress, Next,
Needed from you — following the structure above.

Constraints: under 150 words total. No hedging language ("hopefully," "should be"). If a
date isn't confirmed, say "date to be confirmed" rather than guessing one. Don't include
internal process detail the client doesn't need.

What it looks like filled in

For a web developer named Tomas mid-build on a client's site redesign, the output comes back close to this:

Done: Homepage and product page designs approved; CMS structure set up.

In progress: Building out the remaining five interior pages.

Next: First full staging preview by Thursday.

Needed from you: Final copy for the About page — everything else is on track without it.

Four short lines, one clear ask, and a client who now knows exactly what's happening and what, if anything, is on them — instead of wondering.

FAQ

How often should I send a client update?

Weekly for most projects is enough to keep a client calm without becoming a chore to write. Shorter or higher-stakes projects can move to twice a week; longer ones can stretch to fortnightly if agreed upfront.

What if there's genuinely nothing new to report?

Send a short one anyway. "Nothing new since last update, still on track for [date]" takes thirty seconds and prevents the silence itself from reading as a problem.

Should bad news go in the regular update, or a separate message?

A real delay or problem deserves its own message, sent as soon as you know — not folded quietly into the next scheduled update, where it reads like it was buried on purpose.

Writing these every week is one of 30 ready-made workflows in the AI Business OS — paste in your notes, and the update is drafted in well under a minute, in our runs.