Stakeholder Update Writer

The Prompt

You are a senior communications lead who specializes in translating messy project realities into clear, honest stakeholder updates. Your job is to convert raw bullet points into a polished written update that builds trust — not one that obscures problems or oversells progress.

BULLET POINTS: {{bullet_points}}
PROJECT CONTEXT: {{project_context}}
AUDIENCE LEVEL: {{audience_level}}
TONE: {{tone}}

Produce the following:

1. Subject Line
   One subject line that conveys the status and the ask (if any) without being vague. Avoid "update" or "FYI" as standalone subject lines.

2. Update Body
   A structured written update with three sections:
   - Progress: What was completed or moved forward since the last update, with specifics. No vague "we made good progress" language.
   - Blockers and risks: What is slowing the work, what decisions are needed, and what could derail the timeline. Surface these directly — stakeholders who find out about blockers late trust future updates less.
   - Next steps: What happens next, who owns it, and by when. Specific names or roles, not "the team."

3. Key Metrics Callout
   If any numbers appear in the bullet points, surface the one to three most important ones as a brief callout box or bold line that a time-limited reader scanning the update will catch.

4. The Ask
   If the stakeholder needs to do anything — approve, decide, unblock, attend — state it explicitly in one sentence at the end. If there is no ask, state "No action required."

5. Diplomatic Risk Check
   One to two sentences flagging any content in the original bullet points that may land harder than intended, or that is missing context stakeholders will need to interpret correctly. Suggest a specific framing adjustment if one is needed.

Do not invent information not in the bullet points.
Do not soften blockers to the point of invisibility — stakeholders who trust you will forgive problems; they won't forgive surprises.
Calibrate vocabulary and detail level to the stated audience.
If the bullet points are too thin to write an honest update, say what information is missing rather than padding the output.

When to Use

Use this prompt when you have the raw facts of what happened but need to turn them into a communication that a busy stakeholder can read, understand, and act on in under two minutes. Most useful when the news is mixed — good progress alongside real blockers — because that’s the hardest update to write honestly.

Good for:

• Weekly or sprint-end project status updates
• Executive summaries before a board or leadership review
• Cross-team updates where the audience has limited context
• Client-facing progress reports
• Post-incident summaries to non-technical stakeholders

Variables

Variable	Description	Examples
bullet_points	Raw facts, in whatever order they came to mind	”Launch delayed 2 weeks. Design approved. API still broken on mobile. Need legal sign-off by Friday. Engineering is blocked on infra access.”
project_context	What this project is and where it is in its lifecycle	”Q2 product launch, entering the final 4 weeks before release”
audience_level	Who will read this and their relationship to the work	"Executive team with no day-to-day involvement", "Peer team leads who know the project well", "External client expecting delivery next month"
tone	Register for the communication	"direct and professional", "reassuring but honest", "concise and neutral"

Tips & Variations

• Lead with the most important thing — If you’re behind schedule, that goes in paragraph one, not paragraph three. Ask the model: “Reorder the update so the highest-stakes information appears first.”
• Separate decisions from information — Add a note to the prompt: “Clearly distinguish information-only content from items that require a stakeholder decision or action.” Mixing these is a common reason updates fail to produce the responses they need.
• Version for async vs. live — For a document stakeholders will read alone, the written form here works well. For a summary before a live meeting, follow up with: “Now write a 3-sentence spoken version I can use to open the meeting.”
• Run a retrospective version — After a project ends, paste the full series of updates and ask: “What patterns in these updates predicted the problems we had? What did we consistently underreport?”
• Build a template — After several good outputs, ask the model: “Extract a reusable template structure from these updates that fits our project cadence.”

Example Output

Subject line: Mobile API launch — 2-week delay confirmed, legal approval needed by Friday

Blocker (example): The mobile API remains broken on iOS 16 and below. Engineering has identified the cause (a third-party SDK conflict introduced in build 3.4) and is targeting a fix by Thursday. If this slips past Thursday, the launch date will need to move again. No further delay is expected if Thursday holds.

The ask: Legal sign-off on the updated terms of service is required by end of day Friday to maintain the revised launch timeline. Please confirm with [Name] directly.