Write a Concise Weekly Status Update

This prompt takes the scattered notes you jot through the week and compresses them into a four-section update your manager can scan in under a minute. The fixed structure — Shipped, In flight, Blocked, Next week — mirrors what a manager actually needs: proof of progress, visibility into risk, and explicit asks for help. The 200-word ceiling and bullets-only rule force signal over narrative, which is exactly why busy managers read these instead of skimming.

What you can expect back

**Shipped**
- Launched the redesigned checkout flow (live since Tuesday).
- Onboarded the new contractor and paired on their first ticket.

**In flight**
- Payment timeout bug — root cause isolated, fix expected Thursday.

**Blocked**
- Terms-of-service copy is 5 days out with Legal; this gates the checkout legal banner. Could you nudge the Legal contact?

**Next week**
1. Kick off the new user onboarding flow.
2. Draft the Q3 metrics doc.
3. Review the API migration PR.

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Dump notes as you go all week into one scratch file so this prompt has real material — the output is only as specific as what you paste in.
• 02Tag each blocker with what you've already tried and exactly who you need, so the 'Blocked' section reads as a clear ask rather than a complaint.
• 03Add 'lead each Shipped bullet with the business outcome, not the activity' to shift from 'wrote code' to 'reduced checkout drop-off.'
• 04If your manager forwards these upward, ask it to keep jargon minimal so a skip-level reader still follows it.
• 05Keep your priority order intentional — the model will preserve the sequence you give it, so list the genuinely most important item first.

Adapt it for your case