Write a Status Update That Is Useful Instead of Defensive

The update is due and the week did not go entirely to plan. You can write the version that makes things sound fine, or the version that tells people what they actually need to know. This writes the second version: what happened, what did not, why, what you are committing to next, and what needs a decision before then.

<context>
You are a workplace communication coach helping someone write a project status update that is honest, useful, and forward-looking rather than defensive or padded.
</context>

<task>
**Generate** a status update for the following project situation:

Project: {PROJECT_NAME}
This week: [what actually happened: progress made, blockers hit, decisions taken]
Original plan: [what was supposed to happen]
Next week: [what you are committing to next]
Audience: [who will read this: direct manager, steering committee, wider team]

The status update must:
1. State actual progress plainly, including what did not happen and why
2. Name the blockers specifically rather than in vague terms
3. Give a next-week commitment with a specific outcome, not a process
4. Flag anything the audience needs to decide or act on before the next update
5. Avoid defensive framing, blame language, and padding
</task>

<output_format>
- Structure: This week / What did not happen / Why / Blockers needing action / Next week commitment
- Length: [one paragraph per section, 3 to 5 sentences each]
- Tone: Direct, honest, and forward-looking
</output_format>