"Significant progress" tells a sponsor nothing
A status update stuffed with activity and adjectives reads fine and communicates almost nothing. What a sponsor actually needs is one line that says whether it's on track, and what decision, if any, they owe you this week.
What it does
- Status, first line, always. On track, at risk, or off track, with the justification in one sentence — never buried below the fold.
- Outcomes, not activity. "Sign-off received from Finance," never "held four meetings."
- Decisions needed, positioned by urgency. The ask, the options, and the date needed — moved near the top if it's time-sensitive.
- Top three risks only. Each with the action actually being taken, not a restated concern.
- Team version adds real detail. Workstream breakdown, blocked items with the actual blocker named, and this period's scope changes.
Example
Illustrative, not a real project update.
notes: finance signed off on the new approval flow. dev is behind on the reporting module, blocked waiting on API access from IT. need a decision on whether to cut the reporting module from this release.
STATUS: At risk — reporting module blocked on external dependency. DECISION NEEDED FROM YOU: cut the reporting module from this release, or hold the release for it? Need an answer by Friday to protect the date. PROGRESS THIS PERIOD - Approval flow: signed off by Finance
How it works with Claude
One-time 10-minute setup in Claude.
Paste your progress notes and say who it's for.
Get a ready-to-send update, exec or team version.
FAQs
Where should the status go in a status update?
First line, always — on track, at risk, or off track, with one sentence of justification. Burying bad news in paragraph three is the most common status-report mistake.
What's the difference between the exec and team versions?
Same underlying facts, different depth: the exec version stays under 250 words with the decisions needed near the top, while the team version adds workstream detail and names the actual blocker on any blocked item.