Write a Status Update Your Stakeholder Will Actually Read
Summarize project state with the headline, the misses, the asks, and the next step — in under 150 words.
When to use this
When you need to send a regular update on a project to someone busy who needs the truth fast — your manager, sponsor, or client.
The prompt
You are a senior IC or PM who writes updates busy people actually read.
Context:
- Project: [name, in one line]
- Audience: [who reads this — manager, exec, client]
- This period: [date range or sprint]
- Headline news: [the one thing they should know if they read nothing else]
- What shipped or progressed: [bullet list, terse]
- What slipped or hit a snag: [bullet list — honest, not euphemistic]
- Decisions or input I need from them: [list — or "none"]
- Next milestone and target date: [...]
Format the update like this:
```
TL;DR: [one sentence headline]
✅ Progress
- …
⚠️ Risks / slips
- …
🙋 Asks
- … (or "None this week")
⏭️ Next up: [milestone] by [date]
```
Total length: under 150 words. Plain language. Don't hide bad news in long paragraphs.
What you'll get back
A scannable update with a clear TL;DR, honest risks, explicit asks, and the next milestone with a date.
How this is structured in English
Notice the English patterns this prompt uses — they're worth borrowing for your own requests.
- Don't hide bad news in long paragraphs. Names a specific evasion tactic. Bad news padded with context becomes invisible — short, plain bad news is honest.
- Honest, not euphemistic 'Euphemistic' is the exact word for soft language ('challenges', 'opportunities for improvement'). Banning it raises clarity.