Write a Project Status Report with RAG Calls, Risks and Leadership Asks

Turns your raw project notes into an executive-ready status report with justified red/amber/green ratings, done vs. planned work, a risk table and specific decisions needed.

You getHeader, workstream table and done this period

Prompt

Prompt
You are a senior project manager who writes status reports that executives can read in two minutes.

Job: Turn my project notes into a status report. I will paste my notes (updates, metrics, issues, dates) right after this prompt. If the notes do not include the project name, reporting period, target date or budget position, first ask me up to 3 short numbered questions in one message and wait for my answers.

Rules:
1. Give one overall status and one per workstream: Red, Amber or Green. Each gets a one-line reason tied to a date, number or blocker. No hedged ratings like "Green with concerns."
2. Keep "Done this period" and "Planned next period" separate. Every item starts with a verb and names an owner.
3. Each risk lists likelihood (High/Med/Low), impact, owner, and the next mitigation step with a date.
4. End with "Decisions needed": each ask names who decides, the options, my recommendation, and the deadline after which delay costs time or money.
5. Use only facts from my notes. Mark anything missing as "TBC" instead of guessing.

Output format:
- Header: project, period, overall RAG and reason
- Workstream table: Workstream | RAG | Reason | Owner
- Done this period (bullets)
- Planned next period (bullets)
- Risks table: Risk | Likelihood | Impact | Owner | Mitigation and date
- Decisions needed (numbered)

Finish with one line listing assumptions or gaps in my notes.

Example output

At a glanceCRM migration status at a glanceReporting period 2–13 June, go-live target 30 June
Overall status
AMBER
Data migration 6 days behind
Customer records migrated
38%
vs. 70% planned of 1.2M records
Budget spent
£412k
of £520k (79%) at 82% of timeline
Staff trained
140 of 160
9 of 12 sessions delivered

Example for: a mid-size retailer migrating its CRM, two-week reporting period, go-live target 30 June.

Project Status: CRM Migration (Northwind Retail)

Period: 2–13 June
Overall status: AMBER – Data migration is 6 days behind, which leaves 4 days of buffer before the 30 June go-live.

Workstreams

WorkstreamRAGReasonOwner
Data migrationRed38% of 1.2M customer records migrated vs. 70% planned; duplicate-matching rules failingPriya Shah
IntegrationsAmberPayments API done; loyalty API waiting on vendor sandbox access since 5 JuneTom Reyes
User trainingGreen9 of 12 sessions delivered; 140 of 160 staff trainedAlicia Moreno
BudgetGreen£412k spent of £520k (79%) at 82% of timelineDan Okafor

Done This Period

  • Completed payments API integration and passed 214 of 214 test cases (Tom Reyes)
  • Delivered 5 training sessions to store managers in the North and Midlands regions (Alicia Moreno)
  • Migrated 460k customer records to production staging (Priya Shah)
  • Signed off the go-live cutover plan with IT Operations (Dan Okafor)

Planned Next Period

  • Fix duplicate-matching rules and rerun migration on the remaining 740k records by 20 June (Priya Shah)
  • Complete loyalty API integration within 5 days of sandbox access (Tom Reyes)
  • Run the final 3 training sessions for head-office teams by 24 June (Alicia Moreno)
  • Hold the go/no-go review on 26 June (Dan Okafor)

Risks

RiskLikelihoodImpactOwnerMitigation and date
Data migration misses 30 JuneHighGo-live slips; legacy licence renewal of £38k triggeredPriya ShahAdd 2 contract data engineers from 16 June
Loyalty vendor delays sandbox furtherMediumLoyalty points unavailable at launchTom ReyesEscalate to vendor account director by 17 June
Store staff miss training during peak tradingLowHigher support tickets in launch weekAlicia MorenoRecord sessions and share by 21 June

Decisions Needed

  1. Approve £18k for 2 contract data engineers. Decider: COO. Options: approve now, or accept a likely 2-week slip. Recommendation: approve. Deadline: 16 June, or the 30 June date is lost.
  2. Launch without loyalty integration if the vendor is not ready? Decider: Head of Customer. Options: launch on time with loyalty added in July, or delay everything. Recommendation: launch on time. Deadline: 24 June.

Assumptions and gaps: contractor day rate taken from your notes; loyalty vendor timeline is TBC.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Requiring a one-line reason tied to a number or date stops vague Green or Amber ratings that hide real problems.
  • Separating done from planned, with owners and verbs, makes progress easy to check and assign.
  • Each decision request names who decides, the options and a deadline, so leadership can act in the meeting instead of debating.

Use before a weekly or monthly steering meeting. Have your raw notes, dates and budget figures ready to paste into ChatGPT, Claude or Gemini. Messy bullet notes work fine.

Common edits

  • Ask for a 5-line version for an email or Slack update to senior leadership.
  • Add a column for percent complete or a milestones table with baseline and forecast dates.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Productivity