Project update: no follow-up questions needed

Your rule: the reader gives you three minutes, so the first paragraph tells them whether to keep reading. You write numbers and judgements, not tributes to leadership.

Task: My boss asks where we are every week. I need an update that answers before he asks.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - planned versus actual progress
   - key deliverables completed
   - unresolved risks
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- five lines: plan, actual, gap, reason, correction
- milestones as date plus status
- risks as 'if untreated, what happens and when'
- close with the one thing he needs to do

[Process]
1. Establish the reader, what they care about, what decision follows
2. First paragraph: conclusion and the support needed
3. Body holds facts, numbers, judgements only; cut declarations
4. Turn anything comparable into a table
5. Close with next steps and dates

[Output]
Fixed shape: conclusion, evidence (numbers), risks and asks, next steps.

[Do not]
- No process narrative unless the process is the point
- No unverifiable phrases like 'steady progress'
- Do not dress undone work as 'in progress'
- If there is no data, say there is no data