The client update email template (steal this one)

Most "client update email template" searches end at a page with eleven templates, each a wall of corporate filler — "I hope this email finds you well! I wanted to provide a brief update on our progress…" — that no working consultant would send and no client wants to receive.

Here is one template. It's the one we use, the one we've argued for, and the one that survives contact with an actual Friday. Copy it, fill it, send it before EOD. Then read the second half of this article, because the template is the easy part — the two disciplines around it are what make clients stop scheduling check-in calls.

The template

Subject: [The single most important thing from the week — never "Weekly update"]

[Name] —

Where things stand: [One sentence. Confident, not equivocal. "On track for Monday delivery." or "Hit a snag with X; revised plan below."]

Done this week:

• [Concrete artifact, not activity — a thing that now exists]
• [Second artifact. Two or three bullets, never padded to three]

Coming next week: [Each item with a day of the week attached]

Open items: [What you need from them, with the date you need it by]

Anything else: [Only when there's a real one. Delete the section otherwise.]

[— Your sign-off]

Rules that bind: under 200 words (300 is the outer limit; shorter is safer), the subject line names the week's one important thing, every "next week" item carries a day, every open item carries a date, and a thin week stays thin — one honest bullet beats three that overstate.

The template, filled in

Abstract templates are how we got the eleven-template listicle. Here's the same skeleton carrying a real week — a funnel-diagnostics consultant, week five of an engagement, writing to a Head of Product who reads on her phone and forwards everything to her CEO:

Subject: Report lands Tuesday — the recordings found the stall point

Priya —

Where things stand: report on track for Tuesday 6/16, 48 hours ahead of Thursday's session, as agreed.

Done this week:

• All 25 session recordings reviewed. 14 of 25 trials stall at the bank-connection step; 9 of those tried at least twice before giving up.
• Timing cross-check complete: the slide starts the week of 3/24, before both the tooltip (4/2) and the copy change (4/7) shipped — so neither is the culprit.
• Mixpanel data reconciled against the raw event export; May trial-to-paid confirms at 9.1% after cleanup.

Coming next week: full report in your inbox Tuesday, ranked fixes with impact math; strategy session Thursday 6/18.

One open item: the January baseline export — I need it Monday morning (6/15) to include the cohort comparison in the report. Without it, the table ships with May data only.

— Sam

Under 160 words. The client learns everything in 30 seconds. The CEO who gets the forward understands what was paid for this week without asking. And notice it leads with a number in the subject line — because this client reads on her phone and forwards up, and the template flexes to how each client actually reads.

Discipline one: extraction, not summary

The reason update emails go bad isn't the structure — it's that consultants write them as summaries of their week instead of extractions from their week. Your week contained fifteen things. The update contains the four that move the client's picture of the engagement.

The raw material for the example above was a messy scratchpad — reconciliation percentages, a note about chasing an export, an invoice confirmation, a stray request to "take a quick look at the pricing page too," a ping from their engineering lead that the engagement rules say stays verbal. From fifteen lines of notes, four made the email.

That's the actual skill, and it has two halves:

Artifacts, not activities. "Continued reviewing session recordings" is an activity; it tells the client nothing advanced. "All 25 recordings reviewed; 14 stall at the bank-connection step" is an artifact with a finding attached. If a bullet can't name a thing that now exists, it isn't done — and it doesn't go in the "done" section.

Only what the notes support. Nothing ships in the update that your week's record doesn't show. The moment an update inflates — a "nearly complete" that's 60% done, a finding stated more confidently than the data — you've converted your cheapest trust-building artifact into a liability with a paper trail.

Discipline two: what stays out

Look back at the raw-material list. Two items never reached the email: the pricing-page request (a scope conversation to have properly, not an update line to concede in passing) and the engineering lead's ping (barred from writing by the engagement's own rules). A weekly update is a client-facing document with a paper trail — scope watch-items, internal politics, and anything you'd only say out loud don't belong, and no template enforces that for you.

This is the part that stays yours even when AI drafts the email. Claude, handed your notes and this template, will produce the five sections reliably. What it can't reliably do is recognize that the pricing-page aside is a scope boundary being tested — that's pattern-matching against your engagement's history and your judgment about the relationship. The extraction runs on rules; the omissions run on judgment. Budget three minutes of review for exactly this, every week, before it sends.

Making it a 10-minute Friday instead of a 40-minute one

Run manually, this template takes about 12 minutes from decent notes. The AI-assisted version takes closer to five plus a three-minute review — if the handoff is set up properly, which means: the template's rules, your client's reading habits, and the week's raw notes, all in front of Claude at once. Ask Claude to "write a client update" without those and you get the eleven-template listicle back, in prose form.

We ship that handoff, set up properly, as a free download: the Friday Update Brief. It's this article's template rebuilt as a fill-in brief — your client's four facts at the top (name, how they read updates, word cap, sign-off), the extraction rules inlined, the never-invent-facts guardrail, and a three-minute review pass. It comes with a sample week of raw notes and the reference output, so you watch it work on a fictional client before you point it at a real one. The price is your email address.

And if the update is one of five deliverable types you'd rather have on rails — proposals, case studies, pipeline memos, offboarding — the standing version of this pattern is the Claude Workspace Kit: a folder where your facts live in files Claude reads automatically, with six engagement briefs of exactly this kind wired in. The free brief is one slice of it; the folder pattern it lives in is its own article.

The Friday rule

However you produce it — by hand from this template, through the free brief, or from a standing workspace — the update ships Friday before EOD. A Monday update is stale on arrival; a skipped week is how the Tuesday check-in spiral starts. Even the thin-week version — a subject line, a one-sentence headline, "nothing to flag" — counts.

Twelve minutes, five sections, under 200 words, extraction not summary, omissions on judgment, sent Friday. That's the whole template. The client who receives it every week stops wondering what they're paying for — which is worth more than the twelve minutes costs, every single week.