Project Status Report Prompt

What it does

Writes a project status report from your raw notes and updates. The output follows the format that busy stakeholders actually read: RAG status (Red/Amber/Green) at the top, followed by what moved this period, what's on track vs. at risk, blockers requiring decisions, and next-period milestones. No project management jargon, no unnecessary tables, no padding.

undefined

How to use it

Fill in the blockers and decisions needed fields honestly — these are where project managers tend to soften the language, and softening is what leads to escalations that could have been prevented. If a stakeholder needs to decide something, name them and state the deadline.

The RAG system works only if you use it honestly. A project that's been Amber for 6 consecutive weeks is Red.

Example output

Project: CRM Migration | Q2 2026 | Week 6 of 10 | Status: AMBER

Why amber: data validation phase is running 5 days behind due to a legacy data quality issue discovered in Phase 2. Still within buffer but may impact the July 1 go-live if not resolved by May 30.

Completed this period:

• Phase 2 data extraction complete (all 47K records)
• Mapping document signed off by sales ops
• UAT environment configured

At risk:

• Legacy duplicate records (estimated 3,200) require manual review before import — no automated solution. Currently unassigned.

Decision needed (by May 28): Will Sales Ops allocate 2 FTE hours/day for the manual review, or do we hire a contractor? Without this decision, June 1 review start date slips, which cascades to July 1 go-live.

Next milestones: Data validation complete (June 7) → UAT begins (June 10) → Go-live (July 1)

Variations

Client-facing status report: Add "This goes to the client, not internal stakeholders. Soften the internal language where appropriate, but don't obscure real issues. Keep it professional and solution-focused."

Executive summary version: Add "This is for a 5-minute executive briefing. Give me the 3-sentence version only: status, one key fact, and one action needed."

Multi-project portfolio update: Add "I'm reporting on 4 projects at once. Give me one paragraph per project with RAG status, lead sentence, and one key update."

Common pitfalls

Green when it's Amber. Project managers who reflexively mark everything Green lose credibility the moment something actually escalates. Use the status system honestly.

No decisions logged. A status report with no "decisions needed" section is documentation, not communication. Something always needs a decision or a response.

Too long. A status report longer than one page will not be fully read by most stakeholders. Cut everything that isn't essential to the decisions you need from them.

Who uses this prompt

Project managers sending weekly or monthly updates to stakeholders. Program managers coordinating multiple workstreams. Consultants sending client status updates. Anyone who writes project updates by copy-pasting last week's report and changing a few words.