An exec update that reads like a status report wastes the executive’s attention and your political capital — they don’t need “great progress on initiative Q” three weeks in a row, they need the call where progress is now at risk and the decision only they can make. A good update prompts decisions in line 1, names risks honestly with a colour code that means something, lists the asks the exec must respond to, and skips pleasantries entirely. These prompts work for weekly skip-levels, monthly board updates, and investor reports. Pair with the executive summary prompts when the update needs to compress a 10-page memo into a top-of-email TL;DR.
Who this is for
Functional leads writing weekly updates, founders writing investor / board updates, anyone reporting up to a busy executive.
When not to use these prompts
Don’t use these to hide bad news — execs find out anyway. Don’t use them as a comprehensive log of what your team did.
Prompt anatomy / structure formula
Every prompt should carry six elements:
- Role: who AI plays — chief of staff / manager / analyst.
- Context: team / org / scope / data.
- Goal: one deliverable — plan, memo, talking points, doc.
- Constraints: word count, must-include fields, audience seniority.
- Tone: confident, neutral, factual.
- Examples: 1-2 prior samples to anchor format.
Best for
- Weekly CEO update
- Monthly investor update
- Skip-level update
- Board prep memo
- Project status escalation
12 copy-ready prompt templates
1. Weekly CEO update
Weekly update to CEO. Format: (1) Top 3 wins (with metric), (2) Top 2 misses (honest), (3) 1 decision I need from you, (4) 1 risk you should know. ≤ 200 words.2. Monthly investor update
Monthly investor update: (1) Hero metric, (2) 3 key KPIs vs target, (3) Wins (1-2 concrete examples), (4) Asks (intros, advice), (5) Risks. ≤ 400 words. Skip "we're grinding".3. Board-prep memo
Board meeting next week. Memo: (1) Quarter scorecard, (2) Strategic shifts, (3) Open questions for the board, (4) Pre-read links. 1 page max. Skip cheerleading.4. Skip-level update
Skip-level update to `{name}`. Cover: (1) What's going well in my team, (2) Where I need air cover, (3) One concern about cross-team friction, (4) A question for them. ≤ 200 words.Variables to swap: name
5. Status → action conversion
My draft update has 6 status bullets but no asks. Rewrite to surface decisions: convert at least 2 status items into "Decision needed from you on X by date Y".6. Pulling the alarm responsibly
Something is going wrong. Write a Sev-2 update: (1) What's happening, (2) Impact, (3) What we're doing, (4) What I need from you, (5) Next update timing. Calm tone — don't catastrophise.7. Wins that aren’t bragging
Frame these wins so they read as factual signals: {wins}. Skip "team is amazing", focus on what changed for the business. Each win ≤ 25 words.Variables to swap: wins
8. Misses without spin
I have 2 misses this period. Frame each: (1) What missed, (2) Why (honest, no scapegoats), (3) What I've changed, (4) Next signal to watch. Don't hedge.9. Hero-metric callout
My update should have 1 hero metric. Pick from: revenue, growth rate, conversion, NPS, headcount. Lead with it in the subject line. Body explains.10. Frequency calibration
I send weekly. Audit: (a) Am I sending too often (no real news), (b) Too rarely (surprise), (c) Right cadence. If too often, propose dropping to biweekly with a daily-by-exception rule.11. Update template per audience
I have 3 audiences (board, investors, internal exec). Build 3 templates with different sections / depth / tone. Don't use one template for all.12. Update hygiene audit
Audit my last 4 updates: (1) Average length, (2) Decisions actually asked for, (3) Wins-to-misses ratio (suspicious if all wins), (4) Same risk recurring without movement. Fix list.Common mistakes
- No specific context — output is generic.
- Skipping fact-check — AI invents numbers.
- Vague audience — over/undershoots seniority.
- No word limit — readers won’t finish.
- Same template every situation — readers tune out.
- No “decision needed” framing.
- Forgetting to attach source data.
How to push results further
- Specify audience level.
- Cap length: 1-page tactical, 3-bullet executive.
- Lead with the ask / decision needed.
- Attach source data link.
- Read aloud before sending.
- AI drafts; humans review.
- Save best examples; reuse format, refresh content.
FAQ
- How long should this doc be?: Tactical: 1 page. Executive: 3 bullets + link.
- Can AI replace the analyst / manager?: Drafts and templates yes; judgment no.
- How often refresh?: Cadence-driven; adjust when audience signals fatigue.
- Should risks be included?: Always. Pretending no risk exists erodes trust.
- How to fact-check?: Attach sources; peer review numbers.
- Can AI generate data?: No — AI invents plausible numbers. Connect real data.