Write a Clear Stakeholder Update
Craft a project status update that tells stakeholders exactly what they need to know — progress, risks, and what you need from them.
What it does
Stakeholder updates fail in two ways: too much detail (buried signal) or too little (no one trusts it). This prompt produces an update that leads with what changed, highlights what’s at risk, and ends with what you need. It respects your reader’s time while giving them enough to make decisions.
The Prompt
Help me write a stakeholder update.
Project: [PROJECT NAME]
Reporting period: [e.g., "this week", "March 1-15", "Sprint 4"]
Audience: [WHO READS THIS — their role and what they care about most]
What got done:
- [ACCOMPLISHMENT 1]
- [ACCOMPLISHMENT 2]
- [ACCOMPLISHMENT 3]
What's at risk or blocked:
- [RISK/BLOCKER 1 — and what's being done about it]
- [RISK/BLOCKER 2]
What I need from the reader:
- [DECISION, RESOURCE, APPROVAL, OR ACTION NEEDED]
Upcoming:
- [WHAT'S PLANNED NEXT]
Please write the update following these rules:
1. LEAD WITH THE HEADLINE: One sentence that answers "is this project on track?" — yes, mostly, or no. Don't bury the lead.
2. PROGRESS: Turn my accomplishments into impact statements. "Deployed new auth system" → "New auth system live — eliminates the 3-step login flow that caused 40% of support tickets." Show why it matters, not just what shipped.
3. RISKS: For each risk, state: what might happen, how likely (LOW/MEDIUM/HIGH), what's being done, and whether you need help. Never list a risk without a mitigation plan or explicit ask.
4. ASK: Make any request to the reader impossible to miss. Bold it. State the deadline. Make the action concrete — "approve X" not "review X."
5. TONE: Confident but honest. Don't hedge with "we hope to" or "we're trying to." Say what you will do and flag what might prevent it.
Keep it under 300 words. If the reader needs more detail, they'll ask.
Usage Notes
- The single most impactful change you can make to status updates is leading with the headline verdict. Most updates bury “we’re behind schedule” in paragraph 3. Put it in sentence 1.
- “Turn accomplishments into impact statements” prevents the trap of listing tasks instead of outcomes. Your stakeholders don’t care that you merged 14 PRs. They care that the checkout flow is 2 seconds faster.
- For executive audiences, add to the prompt: “Assume the reader will spend 30 seconds on this. The first three lines must contain everything critical.”
- For board-level updates, add: “Include one metric that quantifies progress — preferably the same metric each reporting period so they can see the trend.”
- If everything is genuinely on track and you have no asks, it’s OK for the update to be five sentences. Don’t pad it.