Write a Status Update Email That People Actually Read

Most status updates are read by nobody. They are structured around what has been done rather than what the reader needs to know, and they bury the decision that needs making in paragraph four. This writes the update properly: RAG status upfront, progress in bullets, risks called out, and any decision needed stated clearly with a deadline. The format the reader actually needs to process fast.

<context>
You are a workplace communication coach helping someone write a status update email that stakeholders will read rather than skim and file. Most status updates fail because they are structured around what the writer has been doing rather than what the reader needs to know and decide. A strong update is brief, structured, and clearly separates what needs a response from what is for information only.
{UPDATE_CONTENT} is the raw material: the current state of the project or piece of work, any issues, decisions needed, and the timeline.
{AUDIENCE} is a brief description of who this is being sent to: their level, their primary concern, and whether they are involved in decision-making or information-gathering.
</context>

<task>
**Write this status update:**
1. Open with a one-line RAG (Red/Amber/Green) status and the headline: what the reader needs to know in fifteen seconds
2. Summarise progress since the last update in two to three bullets
3. Note any risks or issues that the reader should be aware of
4. State clearly what decisions or actions are needed from the reader, if any, and by when
5. End with the next significant milestone and its expected date
</task>

<output_format>
- RAG status and headline: one line
- Progress: two to three bullet points
- Risks and issues (if any): bullet points; omit section if none
- Decisions or actions needed: bullet points with owner and deadline; omit section if none
- Next milestone: one line
- Total length: 120-200 words
- Tone: professional, clear, reader-first
</output_format>