Blog › Claude for Work › Part 4
How to Use Claude for Stakeholder Updates
That Actually Get Read
The weekly status update is one of the most time-consuming and least-read documents in project management. Here's how to draft it in 5 minutes and pitch it so it lands with the right audience every time.
Why stakeholder updates fail before anyone reads them
Most project status updates fail at the same point: they're written by someone who knows everything about the project, for an audience that knows very little - and the writer forgets to make that translation.
The result is updates full of acronyms, task-level detail that means nothing to a sponsor, and buried risks that look like minor footnotes when they're actually the most important thing in the document. The executive reads the first two lines, concludes the project is on track, and misses the paragraph in section four that says the vendor hasn't delivered.
Good stakeholder communication isn't about writing more. It's about translating project reality into the language and format your audience actually processes. Claude can do that translation fast - if you give it the right inputs.
The audience problem - one update doesn't fit all
Different stakeholders need different things from the same project information.
Executive sponsor / steering committee
Needs: overall RAG status, budget and timeline health, top risks, decisions required from them. Doesn't need: task-level detail, technical explanations, who did what this week. Format: one page maximum, executive summary up front, action items called out clearly.
Project team
Needs: what's done, what's up next, blockers that need to be raised, decisions that affect their work. Doesn't need: the financial summary, the high-level governance narrative. Format: action-focused, specific owners and dates, blockers called out explicitly.
Client or end customer
Needs: progress against what they care about, any impacts to their operations, what's coming that requires their input. Doesn't need: internal team issues, budget detail, governance structure. Format: plain language, outcome-focused, professional but accessible.
Broader business stakeholders
Needs: timeline impact to their area, any changes to business-as-usual, what's coming up that affects them. Doesn't need: project governance detail. Format: brief, specific to their area, clear on what they need to do (if anything).
The Claude advantage: give it your raw project notes once, then ask it to rewrite for each audience. Same information, different framing. Takes 2 minutes per version instead of writing each from scratch.
The prompts - copy and adapt
Start with the brain dump, then run whichever audience version you need.
Step 1 - The brain dump (do this first)
Write down everything that happened this week in rough notes. Doesn't need to be structured. Then paste this prompt:
"I'm a project manager. Here are my rough notes from this week on [project name]: [paste notes]. Before we write any updates, extract from these notes: (1) what was completed, (2) what's in progress, (3) what's blocked or at risk, (4) what decisions or actions are needed. Present as four bullet lists. Flag anything that sounds like a risk I might have understated."
Executive / steering committee update
"Using the project notes above, draft a steering committee status update. Format: Overall Status (one sentence with RAG rating - Red/Amber/Green), This Week (3 bullet points - outcomes only, no tasks), Risks and Issues (top 2-3, one sentence each with mitigation or status), Decisions Required (what you need from the committee, if anything), Next Week (3 bullet points). Keep total length under 250 words. No jargon. Write for an executive who's across the project at a high level but hasn't read the detail this week."
Team update (Slack, Teams, or email)
"Using the project notes above, write a weekly team update for posting in our project channel. Format: Done this week (3-5 bullets), In progress (3-5 bullets with owner names where I've mentioned them), Blockers (flag anything the team needs to know about or help with), Coming up next week (3-5 bullets). Keep it practical and direct. The audience is the delivery team - they want to know what's happening and what they need to do, not governance narrative."
Client-facing update email
"Using the project notes above, draft a weekly update email to our client. Audience: [client role, e.g. IT Director at client organisation]. Tone: professional and confident. Include: progress against the timeline (are we on track?), anything this week that affects them or their team, what we need from them this week (if anything), what's coming up in the next two weeks. Do not include: internal team issues, budget detail, or anything that would concern them unnecessarily. Keep under 200 words. Sign-off: [your name or role]."
Escalation email (when something's gone wrong)
"I need to escalate an issue to [executive name/role]. The issue is: [describe the issue]. The impact if unresolved is: [describe impact]. The options I see are: [list options]. What I'm asking them to decide or do: [be specific]. Draft a concise escalation email. Tone: factual, not alarming, solution-focused. Lead with the decision needed, not the backstory. Under 150 words."
Three things that make every update better
Regardless of format or audience.
Lead with status, not activity
"The project is on track" is more useful than "this week the team completed tasks A, B, and C." Tell people the headline first. They can ask for detail if they want it.
Name the risk clearly
Don't bury the risk in the fourth paragraph. If something is genuinely amber or red, say so in the status line. Executives who are surprised at the end of a project are always frustrated they weren't told sooner.
Make the ask explicit
If you need a decision, say "Decision required: X by [date]." Don't imply it in the risk section and hope someone notices. Busy stakeholders don't infer - they need to be told what they're being asked to do.
Try it on this week's update
Write your rough notes, paste them into Claude with the brain dump prompt, then run whichever audience version you need. Free, takes 5 minutes.
Open Claude at claude.ai →Claude for Work - series
Part 1 - What Claude Actually Is
Part 2 - How to Write a Prompt That Doesn't Waste Your Time
Part 3 - How to Use Claude to Draft a Project Plan in 10 Minutes
Part 4 - How to Use Claude for Stakeholder Updates (you're here)
Part 5 - Is Claude Safe for Work Documents? (coming soon)