Project Status Report: Template, Filled Example and Red-Amber-Green Rules
Guide · · Published November 2026 · 8 min read
By Ashwin Gopinath, CEO
TL;DR
A project status report is a one-page update that tells sponsors whether a project is on track, what changed since the last report, and what they need to decide. Sentra, the managed organization memory for teams and AI agents, drafts it from what was actually said and decided in meetings, Slack, email, Jira, Linear and GitHub, so the status reflects the work and not one person's recollection. A good report has seven parts: overall status, what changed, milestones, risks and blockers, decisions needed, open commitments and next steps. Write the status as red, amber or green against written rules, put the decision you need at the top, and cite where each claim comes from. The template below can be copied as it is. This guide is for project and programme leads, chiefs of staff and operations leaders who report to sponsors.
What does a project status report template look like?
Copy this into a document or your project tool. It fits on one page when each section holds only what changed.
PROJECT STATUS REPORT
Project: Sponsor: Report date: Period covered:
1. OVERALL STATUS: Green / Amber / Red
One sentence: are we on track for the committed date and scope, and why.
2. WHAT CHANGED SINCE THE LAST REPORT
- Decision, date, who made it, where it was made
- Scope, date or budget change, with the reason
3. MILESTONES
Milestone | Committed date | Forecast date | Status | Owner
4. RISKS AND BLOCKERS
Risk or blocker | Impact | Owner | Next step | Date raised
5. DECISIONS NEEDED FROM SPONSORS
Decision | Options | Needed by | What happens if it slips
6. COMMITMENTS OPEN
What was promised | To whom | Owner | Due | Source (meeting, thread, ticket)
7. NEXT PERIOD
The three things that will be true by the next report.What should a project status report include?
| Section | What to write | Where the evidence usually lives |
|---|---|---|
| Overall status | Green, amber or red against written rules, with one sentence of reason | The milestone table and the risk list |
| What changed | Decisions, scope changes and date changes since the last report, each with a date and an owner | Meetings, Slack threads and email |
| Milestones | Committed date beside forecast date for each milestone | Jira, Linear or the project plan |
| Risks and blockers | What could move the date, who owns it and the next step | Tickets, vendor email and stand-up notes |
| Decisions needed | The choice, the options and the date it is needed by | The steering group agenda |
| Open commitments | Promises made to and by the team that are still open | Meeting notes and follow-up threads |
| Next period | Three outcomes for the next report to be checked against | The plan |
The second and sixth rows are the ones most reports leave out, because the evidence sits in conversations. They are also what sponsors ask about first.
How do teams produce a project status report today?
| Approach | What it reads | What you still do by hand | Where it goes stale |
|---|---|---|---|
| Sentra (organization memory) | Meetings, Slack, email, docs, GitHub, Linear, Jira and CRM, as facts with source and time | Review the draft and set the status colour | Workstreams nobody asked it to track |
| Project tool report (Jira, Linear, Asana) | Tickets and fields inside that one tool | Add the decisions, reasons and commitments made outside the tool | When the real change was agreed in a call and the ticket was not updated |
| Manual document or slide | Whatever the author remembers and collects | Everything: chase owners, read threads, reconcile dates | The day after it is written |
| General AI assistant with pasted notes | The notes you paste into it | Gather the inputs and check every claim | When an input was missed |
How do you set red, amber and green status?
Status colours only work when the rules are written before the project is under pressure. Agree them once with the sponsor and print them on the report.
| Status | Rule | What the sponsor should do |
|---|---|---|
| Green | Forecast date and scope match the commitment, and no open risk can move either | Nothing |
| Amber | A risk or slip exists, and the team has a plan that recovers the date without outside help | Stay informed and ask for the recovery date |
| Red | The date, scope or budget cannot be met without a decision or resource from outside the team | Decide, fund or re-plan this week |
Two habits keep the colours honest. Report the forecast date next to the committed date, so a green status with a slipped milestone is visible. And record who changed the colour and why, so a project does not move from green to red in one report.
What does a filled-in project status report look like?
This example is for a fictional company, Harbourline Logistics, moving its dispatch system to a new platform.
- Overall status: Amber. Go-live holds at 14 December if the carrier integration passes testing by 28 November. The integration vendor delivered the test environment six days late.
- What changed. On 12 November the steering group agreed to drop the driver mobile app from phase one (decided in the weekly review, owner: Head of Operations). On 14 November the vendor confirmed by email that the test environment was ready.
- Milestones. Data migration: committed 7 November, done 7 November. Carrier integration test: committed 21 November, forecast 28 November. Dispatcher training: committed 5 December, forecast 5 December.
- Risks and blockers. Two carriers have not confirmed message formats. Owner: Integration Lead. Next step: call both by 20 November.
- Decision needed. Approve weekend testing on 28 and 29 November, at four days of overtime. Needed by 21 November. Without it, go-live moves to 11 January.
- Open commitments. Finance to confirm the overtime budget by 19 November (promised in the steering call on 12 November). Vendor to supply a rollback plan by 25 November (promised by email on 14 November).
- Next period. Carrier test passed, rollback plan reviewed, training rooms booked.
How often should you send a project status report?
- Weekly for projects under a quarter long or any project that is amber or red. Send it the day before the review meeting so the meeting is spent on decisions.
- Every two weeks for steady multi-quarter programmes, aligned to the sprint or planning cycle.
- Monthly for portfolio and board reporting, where each project gets three lines and the full report is linked.
For the leadership summary that sits above several project reports, use the executive briefing template. For the weekly operating meeting that reviews metrics rather than projects, see the weekly business review.
Why are project status reports late, long and wrong?
The work of a status report is collection. The ticket shows a date. The reason the date moved is in a call, the scope change is in a Slack thread and the vendor's promise is in an email. The author spends hours pulling these together, and by the time the report is read some of it has changed.
Three problems follow. Reports grow long because the author includes everything rather than only what changed. Status turns optimistic because bad news needs evidence that takes time to find. And decisions made between reports are lost, so a sponsor reads that a feature is on track a week after the team agreed to cut it. Keeping a decision log fixes the last problem if someone maintains it.
How does Sentra draft a project status report?
Sentra reads the tools where the project already runs. Jira and Linear are connected read-only, alongside Slack, email, meetings, docs, GitHub and CRM. It keeps what was decided as facts with a source, a time and the source tool's permissions, and records what replaced a fact when a decision changes. Commitments from meetings become to-dos with an owner, with reminders while they stay open.
Asked for the status of a workstream, Sentra answers from that record: what changed since a given date, which decisions were made and where, what is still owed and by whom, each with a link back to the call, thread or ticket. On the workstreams you ask it to track, it also raises a slipped commitment or a contradiction between a decision and a ticket to the owner. People ask in Slack or the Sentra app, and Claude, ChatGPT and Cursor can read the same memory over MCP. Anything Sentra's agent would send or post waits for a person's approval.
The project lead still owns the judgment: the status colour, the recovery plan and what to ask the sponsor for. The hours of collection are what goes away. Sentra is SOC 2 Type II and ISO 27001 certified and runs in the cloud, in an isolated VPC or on-premises.
FAQ
What is a project status report?
A project status report is a short, regular update for sponsors and stakeholders that states whether the project is on track, what changed since the last report, the main risks, and the decisions needed. Most fit on one page.
What should a project status report include?
Seven parts: overall status as red, amber or green; what changed since the last report; milestones with committed and forecast dates; risks and blockers with owners; decisions needed and by when; open commitments; and the outcomes planned for the next period.
What do red, amber and green mean in a status report?
Green means the forecast matches the commitment. Amber means there is a risk or slip and the team can recover without outside help. Red means the date, scope or budget cannot be met without a decision or resource from outside the team.
How long should a project status report be?
One page. If it runs longer, move detail into linked documents and keep only what changed, what is at risk and what needs a decision.
Can AI write a project status report?
Yes, if it can read where the work happened. An assistant given only tickets repeats the ticket fields. Sentra drafts the report from meetings, Slack, email, Jira, Linear and GitHub with a source for each line, and a person reviews it and sets the status.
What is the difference between a status report and a progress report?
A progress report lists what was done. A status report judges whether the project will meet its commitment and says what is needed to keep it there. Sponsors need the second.
Where should you start?
If your reports are late because collection takes hours, fix collection first: write the red, amber and green rules, adopt the one-page template, and let a system that reads your meetings, threads and tickets prepare the draft. If your reports are on time and still surprise sponsors, add the two sections most templates miss, what changed and open commitments. To see Sentra draft a status report for one of your own projects, book a demo.