Prompts for writing status updates
Prompts that produce clean, manager-ready weekly status updates.
A status update has one job: let a busy reader know in thirty seconds what shipped, what's stuck, and what you need. The Write a Concise Weekly Status Update prompt nails the format, turning a week of scattered notes into a tight, manager-ready summary of about 200 words. The hard part is usually editing yourself down, and that's precisely what the model does well when you hand it the raw material.
The rest of this collection scales the same instinct up and down. The Write a Board Update / Investor Memo prompt applies it to higher stakes with metrics, wins, challenges, and explicit asks stated without spin. The Run a Weekly Review and Build a Structured Daily Plan prompts help you gather the inputs in the first place, and the Write a Self-Review prompt repackages a quarter of updates into a performance case. The pitfall AI helps you avoid is the update that's all activity and no outcome, a list of things you did with no signal about what moved or where you're blocked. Ask it to lead with results and surface risks, and your update earns its read.
What makes a good prompt for writing status updates
A strong status-update prompt feeds the model your raw week, the wins, the blockers, the in-progress items, and tells it who's reading. A manager wants outcomes and risks; an executive wants the one number that changed and what you need from them. Naming the audience changes what rises to the top.
The structural ask that makes updates land is leading with the punchline. Tell the model to open with status and impact, then put detail below, and to call out blockers explicitly with what would unblock them. Ask it to cut anything that's pure activity without an outcome. The best updates make it trivially easy for the reader to know whether to worry and whether they need to act.
Get sharper results
- 01Dump your unfiltered notes for the week and let the model prioritize, rather than pre-editing, since its job is to find the signal you're too close to see.
- 02Name your audience (manager, skip-level, board) so the update surfaces the outcomes and asks that particular reader actually cares about.
- 03Tell it to lead with impact and status, then make every blocker explicit with the one thing that would unblock it, so nobody has to chase you for it.
- 04Hold a hard length cap, around 150 to 250 words, because the value of a status update is inversely proportional to how long it takes to read.
Common questions
How do I keep updates honest without sounding like everything's on fire?
Ask the model for a no-spin tone that states problems plainly alongside what you're doing about them. A blocker paired with a plan reads as competence, not panic. The version to avoid is the one that buries a real risk under cheerful activity.
Can I reuse weekly updates to write my performance review later?
Yes, and that's one of the best reasons to keep them. Paste a quarter's worth of updates into the self-review prompt and ask it to pull out the wins and metrics. Consistent weekly notes turn the dreaded review into an editing job instead of a memory test.
My updates always run too long. How do I fix that?
Set an explicit word cap in the prompt and ask the model to move supporting detail into a short appendix or cut it entirely. Then tell it to lead with the one line your manager would forward upward. Brevity is a constraint you have to impose, because the default is to include everything.
Write a Concise Weekly Status Update
Convert messy weekly notes into a manager-ready 200-word status update.
Write a Board Update / Investor Memo
Write a direct, no-spin investor update memo with metrics, wins, challenges, and asks.
Build a Structured Daily Plan From Your To-Do List
Turn a task list into a time-blocked daily schedule with deep work sessions and an MIT.
Set Up Email Triage Rules and Responses
Create email filter rules, template responses, and an inbox-zero processing cadence.
Run a Weekly Review to Reset and Plan Ahead
Run a structured weekly review and generate a stop/start/continue list with next-week priorities.
Write a Self-Review for Your Performance Review
Turn your wins into a polished, metrics-backed self-review with an explicit ask.
Draft OKRs That Cascade From Company Goal to Team
Drafts outcome-based OKRs that ladder up to the company goal and weeds out tasks masquerading as key results.
Board Update Memo With Metrics, Asks, and Honest Lowlights
Produces a candid, scannable board update with a metrics table, honest lowlights, and specific asks.
Summarize a Sprint Retro Into Themes and Owned Actions
Clusters messy retro notes into themes with root causes and a table of owned, dated actions.
Executive Summary of a Long Document for Time-Poor Leaders
Condenses a long document into a layered executive brief tailored to one reader's priorities.
Triage and Prioritize a Backed-Up Inbox
Sorts a messy inbox into reply, delegate, and archive buckets with fast draft replies.
Turn a Raw Task List into a Realistic Weekly Plan
Converts an unordered task list into a day-by-day weekly plan that respects available hours.
Write a Delegation Brief That Prevents Rework
Produces a clear delegation brief covering outcome, autonomy, deadline, and success criteria.
Draft a Step-by-Step SOP from a Rough Process
Converts an informal process description into a structured, new-hire-ready SOP.
Draft a Project Kickoff Doc That Aligns the Team
Creates a one-page project kickoff doc covering goals, scope, stakeholders, risks, and timeline.
Summarize a Daily Standup into a Shareable Update
Condenses raw standup notes into a scannable async update with blockers and at-risk items surfaced.