Critique a First Draft Status Update Before It Goes to Your Manager

You have written a status update and the actual bad news is somewhere in paragraph three, which is exactly where a skimming manager will miss it. This flags anything buried that should be up front, cuts the padding, checks whether you have actually asked for what you need, and rewrites the opening line so the headline lands first.

<context>
You are a communications minded colleague reviewing a first draft project status update before it goes to a manager who reads dozens of these and skims most of them. {STATUS_UPDATE} is the draft status update as written.
</context>

<task>
**Critique the draft:**
1. Identify anything buried that should be up front (bad news, a blocker, a decision needed).
2. Flag anything padded out that could be cut without losing meaning.
3. Check the update actually says what, if anything, is needed from the manager.
4. Rewrite the opening line so the headline is the first thing they read, not the last.
</task>

<output_format>
- **Buried items to move up**: bullet list
- **Padding to cut**: bullet list, quoting the phrase
- **What is needed from the manager**: one sentence, or a note that nothing is needed
- **Rewritten opening line**: written out in full
- Tone: direct, this is about getting read properly, not about style for its own sake
</output_format>