Client Update Email
Talk through where things stand — get a sendable client update
What it makes
client update email
Communication
Real output
A multi-item update, made client-ready
A spoken status update to a client covering several work streams at once.
What you said
Okay update for Coastal on the spring campaign. Um so the social ads are live as of Monday, they're running on Instagram and Facebook. The landing page is in internal review right now, should have it over to them for approval by uh end of week. And the first performance report, we'll send that next Friday once we've got a week of data. Oh and we're still waiting on the product photos from them, I need those before we can finalize the email designs, so maybe nudge them on that.
What you got
Hi Coastal,
A quick update on the spring campaign.
The social ads went live Monday and are running on Instagram and Facebook. The landing page is currently in internal review — we should have it over to you for approval by end of week.
Once we have a week of data in, we'll send the first performance report next Friday.
One thing we need from you: the product photos are still outstanding on our end. We need those before we can finalize the email designs, so please do send those over when you get a chance.
Thanks,
Why it’s better
Three work streams said in one breath become a clean, skimmable email led by the headline, and the one thing you need back — the product photos — lands as a clear ask. Your "should have it … by end of week" stays a "should", "next Friday" stays the day you named, and nothing is invented.
Bad news, delivered straight
A reply inside an existing client thread: the launch is slipping, with no confirmed new date yet.
What you said
Okay I need to reply to Meridian about the timeline. So unfortunately the launch is gonna slip, we ran into a problem with the payment integration that's taking longer than we expected to sort out. Um I don't have a firm new date yet, probably another week or so but I need to confirm with the dev team first. I want to be upfront about it but obviously keep it professional, and let them know I'll have a concrete date for them by Wednesday.
What you got
I wanted to be upfront with you: the launch is going to slip. We ran into an issue with the payment integration that's taking longer than expected to resolve, and we don't have a firm new date to share just yet.
We're estimating roughly another week, but I want to confirm that with the dev team before committing to anything. I'll have a concrete date for you by Wednesday.
Why it’s better
The delay is named plainly — no spin, no buried lede — and because it's a reply in an existing thread it skips a fresh greeting. Crucially, it does NOT harden "probably another week" into a committed new launch date; it keeps that as an unconfirmed estimate and holds the one real commitment you made: a concrete date by Wednesday.
What comes back
- A one-line update stays a short, sendable note; a multi-item update gets tight paragraphs or bullets the client can skim.
- Bad news is delivered straight — the delay is named, with no spin and no recovery date or cause you didn't give.
- It never over-promises: an approximate "basically done" stays "basically done", and a tentative timeline keeps its caveat.
- A reply inside an existing thread comes back as a low-ceremony reply, not a re-scaffolded standalone email.
What you can count on
- Never over-promises — your hedges survive ("should", "targeting", "roughly a week") and are never hardened into commitments you didn't make
- Never invents — no delivery date, metric, result, or reassurance you didn't actually say reaches the client
- Flags what it assumed — vague timing, a hedge that could read as a promise, or a too-thin update — for you to confirm before sending
Install Client Update Email and try it on your own voice.
Sign in to install Client Update EmailIs this hat for you?
Rough status into a polished, on-brand client update email.
Client Update Email turns a rough spoken status — what's done, what's in progress, what's next, what you need from them — into a polished, on-brand email your client can read in thirty seconds. It does the discipline a good account lead does by hand: it leads with the headline, keeps your exact level of certainty (a "should be ready Friday" stays a "should", a vague "soon" stays vague), and never over-promises — it won't invent a delivery date, a metric, or a "rest assured, we're on track" you didn't say. Bad news is delivered straight, without spin or a fabricated recovery date. And because a client holds you to every word, it surfaces what it had to assume — vague timing, a hedge that could read as a promise, a too-thin update — for you to confirm before it ever reaches them. You talk; it hands you the email, and tells you what to double-check first.
Best for
- Firing off a client status update between meetings — say where things stand and it comes back as a polished, on-brand email
- A multi-stream update — several work items in one breath become a clean, skimmable email led by the headline
- Delivering bad news — a delay or a blocker, communicated honestly and professionally without spin or an invented recovery date
- Anything you know the gist of but want to read as warm, accountable, and client-ready — without accidentally over-promising
Not for
- An internal note, or a recap of a call that already happened — reach for Meeting Notes or Client-Call Recap
- A quick casual message that doesn't need an email frame — reach for Clarity or Casual Convo
- A structured brief, spec, or SOW for your own team — reach for Campaign Brief, Delegate, or Developer Elite
Using it
How it works
- Just talk through the update — what's done, what's in progress, what's next, and anything you need from the client. Ramble; it shapes the email.
- It leads with the headline status, covers the work in skimmable form, and ends with any clear ask — no buried points, no filler openers.
- It writes in a warm, accountable account-management voice, addressed to your client by name when you've given it.
- It keeps your exact level of certainty — a "should be done Friday" stays a "should", and a vague "soon" stays vague rather than hardening into a date you never promised.
Try saying
- update for Coastal on the spring campaign, the social ads went live Monday on Instagram and Facebook, the landing page is in internal review and should be over to them for approval by end of week, and we'll send the first performance report next Friday, oh and we still need the product photos from them before we can finalize the email designs
- need to reply to Meridian about the timeline, unfortunately the launch is gonna slip, we hit a problem with the payment integration, I don't have a firm new date yet probably another week or so but I need to confirm with the dev team, let them know I'll have a concrete date by Wednesday
- quick update for the Brightline team, the homepage designs are basically done and I want to send them over for review today, ask them for feedback by early next week
Tips
- Name the client if you can — "update for the Brightline team…" lets it open with the right greeting and address.
- Say it as tentatively as it really is — "should be ready Friday", "probably another week" — and it keeps your hedge instead of turning it into a promise to the client.
- Replying inside an existing thread? Say so (or paste the thread into Context) and it keeps the reply light instead of starting a fresh email.