How to Write Weekly Client Update Emails Using AI

What Every Client Update Email Needs

A good client update email answers three questions and stops: what moved, what is at risk, and what happens next. Everything else — the pleasantries, the context-setting, the list of tasks nobody asked about — is padding that buries the two lines your client is actually scanning for.

We call this the Friday Three, and it is the structure the rest of this system is built on. The Friday Three is a three-slot template for any recurring client update: one slot for progress, one for risk, one for the next step. If a sentence does not belong in one of those three slots, it does not go in the email.

The Friday Three approach we teach at PromptPeakAI works because it fixes the decision that actually slows you down. You are not stuck on phrasing. You are stuck on whether the copy delay counts as a risk worth mentioning. Once the slot exists, the answer is obvious: it goes in the risk slot, in one sentence, this week.

Run every sentence you were about to write through the slot test:

• Does it name something that finished? Progress slot.
• Does it name something that could slip, and by when? Risk slot.
• Does it say what you or they do next? Next slot.
• None of the above? Cut it.

Length matters more than people expect. A client update email past about 200 words stops being read and starts being filed. Three slots at one or two sentences each covers almost every week of almost every project. The weeks that need more need a call instead.

Most client-facing writing that goes badly fails the same way. A sales proposal that talks about you instead of the client and an update that hides the one slipping deadline share a mistake: writing to feel productive rather than to be useful. Set the expectation early, ideally when you built the onboarding packet, that updates land on a fixed day and stay short.

Build One Prompt You Reuse Weekly

The system only works if you build it once. You are not writing a new prompt for every client update email — you write one, save it somewhere you can reach in two clicks, and feed it different notes each week.

Open one note per active client and add a line whenever something happens. Not at the end of the week — as it happens. Three seconds each time.

• “Homepage copy sent to Sarah for review, Tuesday”
• “Still waiting on brand assets, asked twice”
• “Analytics access granted, setup can start Monday”

These are fragments, not sentences. That is the point. The note is raw material for the client update email, and raw material is the one thing AI cannot generate for you.

This is the prompt that turns those fragments into a draft. Paste it into a saved workspace so it is waiting for you next Friday.

You are drafting a weekly client update email on my behalf.

My role: [your title] at [your company].
Client: [client name], my main contact is [contact name, their role].
Relationship context: [how formal, how long we have worked together, anything sensitive].

Below are my rough notes from this week. Use only what is in these notes. Do not invent progress, dates, or outcomes that I have not written down. If something is unclear, leave it out and list it at the end as a question for me.

NOTES:
[paste your running note here]

Write the email in exactly three parts, with no headings:
1. What moved this week — specific and concrete, named deliverables only.
2. What is at risk — one item maximum, stated plainly, with the consequence and the date.
3. What happens next — my next move, plus anything I need from the client, with a deadline.

Rules:
- Under 200 words total.
- Plain professional English. No filler openers, no "hope you're well", no exclamation marks.
- Write a subject line in the format: [Project name] — week of [date].
- If nothing is genuinely at risk, say so in one sentence rather than manufacturing a concern.

Paste your notes, run the prompt, then read the draft with one question in mind: would my client be surprised by anything here, or by anything missing? That read takes ninety seconds and catches almost everything.

Six client accounts now cost you half an hour rather than half a day. That scaling is most of the value, and it is the logic behind handling several client accounts at once or building a reusable email template library: write the system once, run it many times.

Which AI Tool Fits Your Inbox

Any of the four mainstream assistants can write this email. What separates them is what you pay and where the prompt lives. Here is the honest position as of September 2026.

The free-versus-paid line is the part most guides get wrong. Plenty of them report that Google made its Gmail writing features free for everyone in January 2026. Google’s own Gmail feature availability documentation says something narrower: “Help me write” is free on personal Gmail accounts in the US only, and everywhere else it needs a Google AI Plus, Pro or Ultra plan, or an eligible Workspace plan.

In practice, start with whichever one you already have open. The prompt is the asset, not the tool — it moves between all four without a single edit.

If you are choosing deliberately, the question is where your notes live. Notes in a document or notes app pair with ChatGPT or Claude, which hold the prompt and client context together between sessions. Notes that live in your inbox pair better with Gemini or Copilot, where the client update email is drafted in the window it will be sent from.

Drafting Inside Gmail or Outlook Directly

If your notes are short and the week was uneventful, you can skip the chat window entirely and write the client update email inside your mail client. It is faster, and the draft lands where you need it.

In Gmail, open a new message and look for the “Help me write” control in the compose toolbar. The full prompt is too long for a compose box, so keep a shortened version for this route.

Write a client progress email under 200 words from these notes. Three parts, no headings: what moved, what is at risk with its date and consequence, what happens next. Use only what is in the notes — invent nothing. Plain professional tone, no filler opener.

NOTES: [paste your notes]

Outlook works the same way but gates it differently. Microsoft’s Draft with Copilot documentation puts the control behind the Copilot icon in the compose toolbar, and notes two restrictions worth knowing before you go looking for it: it needs a work, school, or Microsoft-family account, and it will not appear at all on a message composed in plain text.

When the Draft Button Is Missing

Four things account for nearly every “I cannot find it” moment.

How to Flag Risk Without Losing Trust

The risk slot is where a client update email earns its keep, and it is the slot people quietly delete when the news is bad. That instinct is backwards. Clients do not lose confidence because something slipped; they lose confidence because they found out late.

AI drafts risk badly by default. Ask for an update and it produces something diplomatic to the point of meaninglessness. The fix is to write the consequence and the date yourself, then let AI handle the wording around them.

Notice what the second version does not do: it does not apologise, assign blame, or ask for reassurance. It states a fact, a consequence, and a date. That is the whole job.

The opposite problem is just as common. On an uneventful week, people invent a risk because an empty slot feels lazy. Do not. “Nothing at risk this week, the 14th still holds” is complete and useful, and a client who gets a few of those learns that your flags are real.

Rewrite the sentence below for a client email.

Keep every fact exactly as written. Do not soften the consequence or remove the date.

Make it calm and factual, not apologetic. No blame, no hedging words like "slightly" or "a bit". Maximum two sentences.

SENTENCE:
[paste your blunt version here]

This is the same discipline that makes a good client delay notice work, and the same reason a clear no by email lands better than a vague maybe. If the tone still reads wrong after the rewrite, a separate tone pass on the draft is more reliable than asking for both at once. For projects where status needs to be visible at a glance, borrowing the red, amber and green indicator convention gives the risk slot a shorthand your client learns in a week.

Weekly Update, Status Report, or QBR

Three documents get confused constantly, and sending the wrong one is why some clients complain about being flooded while others complain about silence. They differ on audience and cadence, not on quality.

The internal version is a different document with a different job — it carries blockers, owners, and detail your client neither needs nor wants, which is exactly why the weekly status report for your own team gets written separately. The quarterly review is the one that argues value and outcomes; a weekly client update email never tries to do that.

Remember who your reader forwards this to. Most client contacts are not the final decision-maker, and your client update email often gets pasted straight into a message to their own boss. Write it so that paste works unedited, and you make your contact look organised every week.

Cadence is a decision you make once, at kickoff, and then defend. Weekly for active delivery. Monthly for maintenance retainers. Anything more frequent than weekly and your client starts skimming, which costs you the one week you genuinely need them to read carefully. Incident-driven messages sit outside the cadence entirely — a reply to a complaint goes out the same day, not in Friday’s update.

What AI Cannot Do Here

The honest limits of this workflow are worth stating plainly, because pretending they do not exist is how people end up sending a confident email about a project that is quietly on fire.

The accuracy point has a partial fix. Before you send, run the draft back through the tool with the notes attached and ask it to police itself.

Compare the draft email below against my original notes.

List anything in the draft that is not directly supported by the notes — any date, outcome, name, or commitment I did not actually write down. List it plainly, do not rewrite the email.

If everything in the draft is supported by the notes, reply with the single word: CLEAN.

NOTES:
[paste your notes]

DRAFT:
[paste the drafted email]

It will not catch everything. But it reliably catches the invented date, which is the error that costs you most.

There is also the data question, which matters more here than in most AI writing tasks. A client update email is built entirely from client information, so every run of this workflow puts someone else’s commercial detail into a prompt box.

The practical habit is to write your running notes with initials and project codenames from the start, rather than scrubbing them on Friday afternoon. It costs nothing and removes the decision entirely.

Run this for a month and the Friday feeling disappears — not because AI writes a better client update email than you do, but because you stopped starting from a blank page. The notes carry the week. The prompt carries the structure. You carry the judgment.