What a great project status report includes
A status report has one reader-job: let a stakeholder absorb the state of the project in two minutes and know whether anything needs them. That starts with the RAG status (red, amber, green) at the very top, with one honest line on why, and continues through distinct blocks a reader can jump between:
| Block | What it answers | Keep in mind |
|---|---|---|
| Overall status (RAG) | Do I need to act? | First thing on the page, one line of why |
| Summary | What happened, what it means, what’s next | Three or four lines, written last |
| Milestones | Are the dates holding? | Each with target date and state, including “moved” |
| Budget & resources | Is the money and capacity holding? | Spent vs budget with %, plus capacity notes |
| Risks & issues | What could change the RAG? | Impact + action + owner per line |
| Decisions needed | What is waiting on someone? | Named person, named deadline; buried asks die |
The same skeleton serves the weekly cadence (shorter, blockers-focused) and the monthly one (fuller budget and milestone view); only the depth changes, so one template covers both.
How to set a red, amber or green status
The RAG call is the report. Everything else is supporting evidence, so the thresholds deserve precision:
- Green: on track. Milestones holding, budget within plan, no risk that needs a stakeholder. Green does not mean perfect; it means nothing needs the reader.
- Amber: at risk. A named risk threatens a date, the budget or the scope, and it needs a decision or close watching. Amber must always come with the name of the thing. “Amber, generally” is a hedge, not a status.
- Red: off track. A milestone, the budget or the scope is already breached and needs intervention now. Calling red early is a professional act; the report that stays green until the week everything fails is how trust dies.
One useful discipline: when the status is amber or red because of something outside the team (a client sign-off, a supplier), say so plainly and put the decision in the decisions-needed block. The report is a mirror, not an apology.
Project status report example (filled in)
The template at work for a six-week website build, week 6:
PROJECT STATUS REPORT · Portside website build Period: Week 6 · Prepared by: Lena · Date: Fri 17 Jul OVERALL STATUS: AMBER Content sign-off is 9 days overdue on the client side; launch date holds only if approved by Tue 21 Jul. SUMMARY Build is on schedule: all template pages complete, checkout integration passed testing Wednesday. The open risk is content sign-off, now blocking final page population. Launch on 1 Aug holds if sign-off lands by Tuesday; otherwise it moves a week. MILESTONES Design approved → 12 Jun → done Build complete → 18 Jul → on track Content loaded → 24 Jul → at risk (sign-off overdue) Launch → 1 Aug → at risk BUDGET & RESOURCES Spent to date: £14,200 of £18,000 (79%) Resource notes: dev capacity drops to half from 28 Jul (booked on next project). RISKS & ISSUES - Content sign-off overdue 9 days → launch slips a week → escalated to client sponsor, decision by Tue (Lena) DECISIONS NEEDED - Content approval: client sponsor, by Tue 21 Jul NEXT PERIOD - Content loaded, launch checklist run, go/no-go on 29 Jul
Free project status report template (plain text, Google Docs, Notion)
Three ways to Friday’s report. The plain text pastes cleanly into Google Docs or Notion, wherever your stakeholders read.
The plain-text template
RAG up top, every block in its place. Works for weekly and monthly cadences.
PROJECT STATUS REPORT · [Project name] Period: [week/month] · Prepared by: [name] · Date: [date] OVERALL STATUS: [GREEN / AMBER / RED] One line on why. (Green = on track. Amber = at risk, needs a decision or watch. Red = off track, intervene now.) SUMMARY (3-4 lines) What happened this period, what it means, what happens next. MILESTONES [Milestone] → [target date] → [on track / at risk / done / moved] … BUDGET & RESOURCES Spent to date: [amount] of [budget] ([%]) Resource notes: [capacity, availability, anything tightening] RISKS & ISSUES - [Risk or issue] → [impact if unaddressed] → [action + owner] … DECISIONS NEEDED - [The decision, who needs to make it, by when] NEXT PERIOD - [The 3-5 things that will be true by the next report]
The AI prompt
Prefer to use your own AI? Copy this into Claude or ChatGPT with your project notes, and it writes the report with the RAG call justified.
--- title: Project Status Report Generator description: A prompt that writes a stakeholder-ready RAG status report from your project notes, tasks and threads. author: readywhen source: https://readywhen.ai/project-status-report-template homepage: https://readywhen.ai license: CC BY 4.0 (free to use and share with attribution to readywhen) version: 1.0 updated: 2026-07-17 keywords: [project status report template, RAG status report, project health report, status update] --- # Project Status Report Generator _By readywhen. Full guide + free template: https://readywhen.ai/project-status-report-template_ You are writing a project status report a stakeholder can absorb in two minutes. ## Principles - Open with the RAG call (green/amber/red) and one honest line on why. The reader decides in the first ten seconds whether to keep reading. - Amber is a signal, not a hedge: it means a named risk needs a decision or close watching. If you cannot name it, the status is green. - Milestones, budget/resources, and risks are separate blocks. Mixing them buries the news. - Surface decisions needed explicitly, with who and by when. Buried asks do not get answered. - No spin. A red called early is a professional act; a green that turns red overnight is a credibility problem. ## Structure Overall RAG + why · summary (3-4 lines) · milestones with dates and states · budget and resources · risks and issues with actions · decisions needed · next period. ## What I need from you The project and who the report is for · this period’s progress (paste notes, task lists or thread excerpts) · milestone dates · budget position if tracked · anything worrying you. Ask me for what’s missing, then write the report with the RAG call justified. --- _Made by readywhen. readywhen assembles the status from your project tools and sets the RAG from the evidence, ready for you to overrule. https://readywhen.ai/project-status-report-template_
Let readywhen do itRecommended
The template assumes the collating is done. readywhen walks your board and threads itself, matches progress to the milestone dates, and sets the RAG from evidence, so Friday’s job is a two-minute review, not a scramble.
The status already lives in your board, threads and timeline. readywhen assembles it, RAG call included, in ~45 seconds, instead of the Friday-afternoon scramble before the client update.
Watch readywhen draft your status report from your project tools
Every status template assumes the collating is done: that someone has walked the board, re-read the week’s threads, checked the milestone dates and worked out what is actually amber. That collating is the report’s real cost, and it lands on a Friday.
readywhen walks your Notion board and Slack channels itself, matches progress against the milestone dates, sets the RAG from the evidence with the reason attached, and puts the decisions-needed block in front of the right names. You adjust the call if you disagree; disagreeing with a drafted report is a five-minute job.
Works with your existing tools
Project status report FAQs
What does RAG status mean?
Red, amber, green: the traffic-light summary of project health. Green means on track and nothing needs the reader. Amber means a named risk threatens a date, budget or scope and needs a decision or close watching. Red means something is already breached and needs intervention now.
When should a project status be amber instead of green?
The moment you can name a specific risk to a date, the budget or the scope that needs a stakeholder’s attention. Amber without a named cause is a hedge; green with a known threat is a time bomb. If you can finish the sentence “amber because…”, it’s amber.
How often should I send a project status report?
Weekly for active projects with external stakeholders; monthly for slow-moving or internal ones. The skeleton stays the same, the depth changes: weekly reports lean on blockers and decisions, monthly ones give budget and milestones fuller treatment.
How long should a status report be?
One page. A stakeholder should absorb it in two minutes and know if anything needs them. Detail beyond that belongs in the project board the report links to, not in the report itself.
Is there a project status report template for Google Docs or Word?
Yes. Copy the plain-text template on this page into Google Docs, Word or Notion, or download it as a file. All formats are free.
Can’t I just use ChatGPT or Claude to write my status report?
Yes. Paste your notes and the prompt above, and you get a well-structured report. readywhen is the version that does the collating too: it walks your board and threads, matches progress against milestone dates, and sets the RAG from the evidence, which is the hour the template never saves you.
More templates for reporting and follow-through
Board report
The monthly pack: numbers, narrative and asks, drafted from your tools.
Risk register
Scored risks with owners and mitigations, surfaced from your own tools.
Meeting notes
The everyday record: takeaways, decisions and actions from your transcript.
Stop scrambling on Friday. Review a drafted report instead.
Draft your report free with readywhen
About the author and editorial standards
About the author. Sançar Şahin is co-founder and CMO of readywhen. readywhen catches everything you say you’ll do and helps you move it forward: drafted, chased or flagged, ready when you are. He builds readywhen in public on LinkedIn.
Editorial standards. No paid placements. The RAG convention and report structure reflect common project-management practice (PRINCE2-style reporting among others) rather than a single authority. How this page was made: Sançar built the multi-agent research and drafting system behind it, checks its work at several phases, and approves the final page himself. To flag an error, email hello@readywhen.ai.
Last updated: 19 July 2026.