Weekly status update for your manager

Turn your week's work into a crisp status update covering progress, blockers and next steps.

Change note: Initial version

Prompt

Write a status update from the raw notes below.

Reader: {{reader}}
Project or team: {{project}}
Reporting period: {{period}}
Format: {{format}}

My raw notes:
{{notes}}

Rules:
- Lead with overall status as one of: On track, At risk, Off track, with a one-line reason.
- Report results and outcomes, not activity. "Shipped X" beats "worked on X".
- Quantify progress where my notes allow. Do not invent numbers or dates.
- Make blockers specific: what is blocked, who can unblock it and by when.
- List next-period priorities in order, three at most.
- Keep it under 180 words and avoid filler like "just wanted to update you".

Output format: use the requested format, with sections Status, Done, Blockers and asks, Next. Omit empty sections.

Variables

• {{reader}}Readertext

  Default: My director, who reads this on her phone

• {{project}}Projecttext

  Default: Mobile app v2.0 rebuild

• {{period}}Periodtext

  Default: Week of 9 June

• {{format}}Formatselect

  Options: Slack message, Email, Bulleted list, Short paragraph

  Default: Slack message

• {{notes}}Raw noteslong

  Default: finished login screens, 12 of 15 screens done. payments API still not ready from vendor, waiting since Tuesday. QA found 4 crash bugs, 3 fixed. thinking release may slip if payments not here by 20 June. next: finish remaining screens, start load test.

  Anything you did, in any order

Example output

**Status: At risk.** Release depends on the vendor's payments API, which has not arrived.

**Done**
- 12 of 15 screens complete, including login.
- QA found 4 crash bugs; 3 are fixed.

**Blockers and asks**
- Payments API from the vendor, outstanding since Tuesday. Release slips if it is not delivered by 20 June. Could you escalate to the vendor contact?

**Next**
1. Finish the remaining 3 screens.
2. Fix the last crash bug.
3. Start load testing.

Notes

Marking an honest At risk with a named ask is what makes a status update useful. Include dates in your notes for sharper deadlines.