The exact process and prompt I use to turn a week of scattered updates into a report your sponsor actually reads.
It’s 4:45 on a Friday. You have a week of scattered updates, a status report due, and the quiet certainty that whoever receives it will skim it for fifteen seconds and miss the one thing that mattered.
Writing it faster isn’t the fix. Writing it so the verdict comes first is. Here’s the exact five-minute process I use to turn a messy week into a clean status report, plus the prompt, so you can take it.
What most status reports get wrong
A status report has exactly one job: tell a busy person whether they need to worry. That’s the whole thing. Most reports bury that answer under a week of activity, so the reader either skims past the risk that mattered or reads it all and resents the time it cost. Both are losses. Lead with the verdict, make the rest skimmable, and the report does its job in a single glance.
Step 1: Open with the verdict
One line, before anything else: ON TRACK, AT RISK, or OFF TRACK. Your reader’s first question is “do I need to do something about this,” so answer it in the first line instead of making them hunt for it in paragraph four.
Step 2: Three wins, two risks, every risk with a next step
Keep it tight. Three wins so they know it’s moving, two risks so they know what’s coming. And never list a risk without a next step beside it. A risk with no plan is just anxiety on company letterhead.
Step 3: Bold the ask
Near the top, one bolded line: what you need from them. “What I need from you: a decision on the contractor by Wednesday.” This is the line that turns a report into action instead of a thing people nod at and forget.
Step 4: Cut everything else
If a sentence doesn’t change what the reader thinks or does, it’s noise. The activity log, the play-by-play, the paragraph proving you were busy, cut it. A short report that leads with the verdict beats a thorough one nobody finishes.
The exact prompt
Paste your week’s updates, messy and unsorted, and let this do the shaping:
Prompt
You are my project chief of staff. Turn the updates below into a weekly status
report for [STAKEHOLDER]. Start with one line: ON TRACK / AT RISK / OFF TRACK.
Then: 3 wins, 2 risks (each with a next step), and a bolded "What I need from
you." Under 200 words. Plain English, no corporate filler. Updates: [PASTE]
Why each line earns its place:
- “Project chief of staff” sets the altitude. It writes tighter and more decisive than a generic “assistant.”
- The status line first forces the verdict to the top, where it belongs.
- “Each with a next step” stops it from listing problems with no plan, which is the exact thing that makes a sponsor nervous.
- “Under 200 words” is the ruthlessness setting. Length is where status reports go to die..
Before and after
Here’s a real-feeling week of updates, the kind you’d actually have open in a notes tab:
Before
…vendor finally delivered the API but it’s failing about 1 in 5 calls… Maria out next week so the design review slips… finance still hasn’t approved the extra contractor, third week now… demo went well, sponsor seemed happy… staging keeps falling over…
And the same week, run through the prompt:
After
- Wins: Sponsor demo landed well and feedback was positive. Vendor API is delivered. Core build remains on schedule.
- Risks: API is failing roughly 1 in 5 calls (next step: vendor call Monday, fix expected by Wednesday). Design review slips a week with Maria out (next step: rescheduled, no downstream impact yet).
- What I need from you: approval on the extra contractor, now three weeks pending and starting to put the timeline at risk.
Five minutes. The reader knows the verdict in one word, sees the two things that could bite, and knows exactly what you need. The “staging keeps falling over” line didn’t make it, because it didn’t change what they think or do. That’s the point.
What to watch
A few honest guardrails so this helps instead of hurts:
- You decide the color, not the AI. “ON TRACK” or “AT RISK” is a judgment call you own. Let the tool format the report; never let it set the verdict.
- Check every number. AI will state a confident figure it invented. That “1 in 5” only belongs in the report if it’s actually true.
- Keep your voice on the ask. The body can be AI-clean. The line where you ask for something should still sound like you.
The version before the version
The fastest status report is the one you barely had to assemble, because you kept a running note all week instead of reconstructing it from memory on Friday. I send one small workflow like that every week in The Status Update, my newsletter for PMs.
My status reports are honest now. They used to say “on track” the way you say “I’m five minutes away” from your car, still in the driveway.
