Turn Raw Notes into a One-Minute Weekly Status Update for Leadership

You get a scannable leadership update that opens with a red/amber/green status and clear asks, followed by a workstream table, risks and wins.

Prompt

Prompt
You are a chief of staff who writes weekly status updates that executives read in under one minute.

I will paste my raw notes from this week right after this message. Turn them into a status update for leadership.

Rules:
1. Open with one overall status (Green, Amber or Red) and a one-sentence reason.
2. Put asks and decisions needed second. Each ask names who must act and the date it is needed by. If there are none, write "No asks this week."
3. Give each workstream its own Green, Amber or Red status. Every Amber or Red item states what changed, the impact on date or budget, and the recovery step.
4. Keep the update under 200 words. Every bullet contains a number, date or named owner. Cut activity that does not affect outcomes, timeline or budget.
5. Use only facts from my notes. If a status, date or owner is unclear, mark it "(confirm)" instead of guessing.

Output format:
- Subject line (under 12 words, includes the overall status)
- Overall status and reason
- Asks and decisions needed (numbered)
- Table with columns: Workstream | Status | This week | Next week
- Risks to watch (up to 3 bullets)
- Wins (up to 2 bullets)

After the update, list anything missing from my notes that leadership is likely to ask about.

Example output

At a glanceCheckout Relaunch Week 6 Status at a GlanceOverall AMBER: payment certification slipped, 14 June launch at risk
Payment certification slip
8 days
Moved from 22 May to 30 May
Weekend QA overtime ask
$6,400
Approval needed by Tue 28 May
Fraud false-positive rate
4.1%
vs 2% target
Front-end screens done
18 of 20
Mobile pass rate 96%

Example for: a project lead at a mid-size retailer running a new online checkout launch, notes pasted from week 6 of 10.

Subject: Checkout Relaunch – Week 6 – Overall AMBER

Overall: AMBER. Payment provider certification slipped 8 days, putting the 14 June launch at risk unless we approve weekend testing.

Asks and decisions needed
  1. Approve weekend QA overtime (est. $6,400) – Dana Ruiz, Finance, by Tue 28 May.
  2. Decide: launch without Apple Pay, add it in July? – Marcus Lee, VP Digital, by Fri 31 May.
Workstreams
WorkstreamStatusThis weekNext week
Payments integrationRedCertification moved from 22 May to 30 May (provider backlog). Impact: 6 days of test buffer lost. Recovery: weekend QA if approved.Submit final test cases by 29 May
Front-end checkoutGreen18 of 20 screens done; mobile pass rate 96%Finish address and promo screens
Fraud rulesAmber3 of 5 rules tuned; false-positive rate 4.1% vs 2% targetPriya Shah retunes rules 4 and 5
Customer support readinessGreenFAQ drafted; 12 agents booked for training 10 JuneFinal FAQ review (confirm owner)
Risks to watch
  • Provider could slip again; no second certification slot before 14 June.
  • Fraud false positives above 3% could block roughly 1 in 30 good orders.
  • Two front-end engineers on leave 3–7 June.
Wins
  • Page load time down from 3.8s to 1.9s in staging.
  • Guest checkout cut steps from 6 to 4.

Likely leadership questions not covered in your notes:

  • Total budget spent to date versus plan.
  • Who owns the final FAQ review.
  • Whether a 21 June fallback launch date has been agreed with marketing.
  • Rollback plan if payment errors rise after launch.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Leading with one RAG status and the asks means executives see what needs their action before any detail.
  • Forcing Amber and Red items to state change, impact and recovery stops vague 'slight delay' reporting.
  • The '(confirm)' rule and the missing-info list prevent invented dates or owners and prep you for follow-up questions.

Use this on Thursday or Friday before sending your weekly update. Have your messy notes, ticket summaries or Slack highlights ready to paste into ChatGPT, Claude or Gemini right after the prompt.

Common edits

  • Ask for a three-line Slack version alongside the full email update.
  • Replace the workstream table with milestone dates if leadership tracks by milestone instead of team.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Business