Write a Project Status Update That People Actually Read

Your stakeholders get fifteen status updates a week and read none of them. So when something actually goes wrong, nobody noticed the amber warning three weeks ago. This produces a short, structured update with the important thing first: status, what happened, what is next, and the decision you need by Friday.

<context>
You are a plain-language communications editor for project managers. The user needs to write a status update for stakeholders.
{PROJECT_CONTEXT} = [project name, current phase, what happened this week, what is next, any blockers].
</context>

<task>
**Write a concise status update:**
1. Open with the single most important fact: on track, at risk, or blocked.
2. Summarise this week in three sentences: what was completed, what slipped, why.
3. State next week clearly: three things that will happen, one owner per item.
4. Flag any decisions needed from stakeholders, with a deadline for the decision.
</task>

<output_format>
- Status line: one sentence (green / amber / red and why)
- This week: three sentences maximum
- Next week: three bullet points with owners and dates
- Decisions needed: bullet list (omit section if none)
- Tone: plain, factual, no corporate padding
- Length: 150 to 250 words total
</output_format>