The five-section Friday update that keeps clients quiet

There's a thing that happens around week three of an engagement that catches almost every solo consultant off guard. The client, who was quiet and confident in week one, starts sending Tuesday-morning check-ins. "Hey, how's it going?" Then a Wednesday Slack: "Any update on the audit?" By week four they're on a video call with their CEO asking what they should expect, and the CEO is asking why they don't already know.

You haven't done anything wrong. The work is on track. What you've done — the only thing you've done — is fail to ship a weekly status email.

The weekly client update is the single highest-leverage low-effort artifact in any consulting engagement. It costs about 12 minutes to write and prevents the entire spiral above. Clients who receive a Friday update stop checking in randomly because they have a scheduled moment of clarity arriving every week. Clients who don't receive one assume nothing is happening and start escalating, because their CFO is asking and they need something to forward.

This article is the structure of the update that works, what to do with AI for the parts that are AI-tractable, and the failure modes that kill the practice in week six.

Why the obvious version fails

The version most consultants write — when they write one at all — is a paragraph-or-two summary, sent late Friday or rolled into a Monday recap, that reads defensively. "This week I continued working on the analysis, completed several key deliverables, and made progress on the deck. Looking forward to next week's deeper dive into…"

Three problems with that version.

It's too vague to be useful. "Continued working on the analysis" tells the client nothing about whether anything actually advanced. If the client forwards the update to their CEO, the CEO has no idea what they paid for this week. Vague status reads as nothing happened.

It's defensive. Words like "continued," "looking forward to," and "deeper dive" are hedge-language that signals you're not sure where you are. Clients pick this up — not consciously, but it lands. A confident update reads differently because confident operators write differently.

It's late. A status update that arrives Sunday night or Monday morning misses the window. The client has already spent the weekend wondering what's happening. The update should arrive on Friday before the client closes their laptop — preferably before noon Eastern, so it lands during the client's working hours regardless of their timezone.

The five-section structure

The version that works is five sections, in this order, in a single email:

1. Headline. One sentence on where things stand. Confident, not equivocal. "On track for Monday delivery." or "Hit a snag with the Mixpanel access — revised plan below." The headline tells the busy client everything they need to know in five seconds; the rest of the email is for the careful reader.

2. Done this week. Two or three bullets. Concrete artifacts, not activities. This is the most-violated rule. "Continued working on the analysis" is an activity. "Completed the funnel-stage breakdown; flagged 3 friction points" is an artifact. Always the second form. If you can't name an artifact, the bullet doesn't belong in the email.

3. Coming next week. Two or three bullets. What you'll deliver, with day-of-week. Tuesday: scope draft. Thursday: case-study interviews complete. Friday: recommendations doc shared. Day-of-week matters. "Next week" alone means nothing; "Thursday" is a commitment the client can hold.

4. Open items. Anything you need from them. Crisp, with the date you need it by. "Need Mixpanel read-access by Tuesday or the Wednesday milestone slips." Not "could you possibly send over the data when you get a chance" — that's vendor energy, and you're not a vendor.

5. Anything else (optional). A short note when there's something real to say — a stakeholder concern that surfaced, a question worth flagging, a small win worth naming. Skip the section entirely when there isn't. Don't pad.

That's the email. It runs five to seven sentences across the five sections. Twelve minutes to draft, two minutes to edit, sent before noon Friday.

The subject-line discipline

The subject line is its own piece of work. Almost everyone writes "Weekly update — [client name]" or "Status — Week 3." That subject line gets the email opened, but it doesn't get it read — and it doesn't get it forwarded to the CFO who's been asking what's going on.

Better: the subject line is the most important thing from the week. If the headline says "Diagnostic complete; recommendations in your inbox Monday," the subject line is "Diagnostic done — recommendations land Monday." If the headline says "Hit a snag with Mixpanel access," the subject line is "Mixpanel access blocked; revised plan." The subject becomes the artifact's identity. It's the line the client uses to find the email three weeks later when they're trying to remember what was decided.

This sounds like a small thing. It isn't. The CFO who gets the forward of "Mixpanel access blocked; revised plan" understands what's happening immediately. The CFO who gets the forward of "Weekly update — Acme" skims it for three seconds and asks the client to summarize.

The two versions of the same week

Concrete example. A solo consultant is in week 3 of a 6-week onboarding-funnel diagnostic for a B2B SaaS. The work this week: stakeholder interviews, a Mixpanel access blocker resolved on Wednesday, a friction-points draft started Thursday.

The wall-of-text version (~120 words, the version most consultants write):

"Hi Priya — quick update on the week. I continued working on the diagnostic this week and made progress on a number of fronts. Stakeholder interviews went well overall, though we did hit a slight delay early in the week on the Mixpanel access that we discussed last Friday. Happy to report that's now resolved and we're back on track. Started drafting the friction-points analysis Thursday and will continue through next week. Looking forward to a deeper dive into the data once everything is in place. Let me know if you have any questions in the meantime — happy to chat."

The five-section version (~85 words, same week, same work):

Subject: Stakeholder interviews complete; friction-points doc lands Tuesday

Headline. On track for the Tuesday delivery. Done this week. Completed 5 of 5 stakeholder interviews. Resolved the Mixpanel access blocker (Wed). Drafted friction-points doc through page 4. Coming next week. Tuesday: friction-points doc shared. Thursday: priority-ranking session (30 min, calendar invite coming). Open items. Need confirmation on Thursday's session — proposed times in the calendar invite. Reply by Monday EOD. Anything else. Surfaced one cultural-fit concern from the interviews worth a 10-min discussion. Will raise on Thursday.

Same work. Same week. The second one tells the CFO who gets forwarded the email exactly what they paid for, exactly what's coming, and exactly what's being asked of them. The first reads like a vendor; the second reads like a peer.

What Claude does, and what stays human

The five-section structure is AI-tractable in places, and stubbornly human in others.

What Claude can produce well: the first draft of sections 2 and 3 (done this week / coming next week). You paste your task tracker, your meeting notes, and last week's update. Claude returns a structured draft in 60 seconds. You edit the bullets in your voice.

What Claude does badly without help: the headline. The headline requires you to make a confidence call — are we on track, or are we hedging? AI defaults to hedging. You can prompt it toward confidence, but the call itself is yours.

What Claude can't do at all: the open-items section. Claude doesn't know which thing you've been asking the client for. It can write "Need [X] from client" placeholders, but the substance is yours.

The prompt that works has four inputs: last week's update (to maintain continuity), this week's task tracker, any meeting notes from the week, and a one-line gut read on confidence. The prompt returns a five-section structure, and you edit to ship.

The pattern that doesn't work: asking Claude to "write a weekly client update" without those four inputs. It will, but the output is the generic version — "continued working on the analysis" — and you'll spend more time rewriting than you saved.

Pitfalls that show up by week six

Even consultants who adopt the structure tend to drift. The five most common failure modes:

Skipping a week and not catching up. You skip Friday because the work is going well and there's nothing to report. The next week the client check-in arrives because they've gone two weeks without a signal. Lesson: even a one-line "On track for the Monday milestone — nothing to flag this week" counts as a Friday update. Send it.

Padding the sections that don't have content. If "Done this week" is one bullet, ship one bullet. Don't manufacture two more to fill the structure. The client can tell.

Burying bad news. When something slips, the headline names it. "Hit a snag with Mixpanel access; revised plan below." Not "Several items continued progressing this week, with one minor blocker we're working through." Clients respect the operator who flags slippage early. They lose trust in the operator who buries it.

Letting the email get long. A weekly update over 200 words gets skimmed; over 400 words gets ignored. If you can't get the five sections into 150-200 words, the work is unfocused, not the update.

Forgetting to file the update in the client folder. Every weekly update is also a record of what was decided and when. When the engagement wraps and you need to write the case study, the chain of weekly updates is the source material. A consultant who saves them produces a case study in 30 minutes; one who doesn't spends two hours reconstructing the engagement from memory.

Why this is a procedure, not a habit

The weekly client update is the kind of thing that lives or dies on whether you've turned it into a procedure. As a habit — "I should send those updates" — it slips. As a procedure that fires every Friday on a trigger, it doesn't.

The procedural version of this — the trigger that fires the procedure, the four-input Claude prompt that produces the draft, the five-section structure with examples, and the pitfalls list — is SOP 02 in The Solo Operator's SOP Bundle. Each SOP in the bundle has the same shape: when to use, the procedure, the paired Claude prompt, the pitfalls. Drop it into a client folder when an engagement starts; the update flows from the trigger every Friday whether you remembered or not.

If you're running one engagement at a time, you can hold the structure in your head and run it manually. If you're running two or three engagements at once and the Friday update is what's slipping, the procedure is the fix. The cost of the slip — anxious clients, defensive emails, lost trust — adds up faster than the cost of installing the procedure.

Twelve minutes a week per client. The cheapest defense against a relationship spiral you have.