PMO weekly status report template with a written RAG rule
- Section
- Resources, Templates
- Sources
- 7 linked below
- Words
- 2,231
- Checked
- Nov 16, 2026
Short answer
A PMO weekly status report needs one row per project with an owner, a status date, the next milestone against its baseline, forecast cost against budget, a color set by a written rule, the reason, and the decision needed. Compute the color from the data, show the manager's own color beside it, and never carry an old color forward.
Download the template
pmo-weekly-status-report.csv
It's Thursday afternoon and the weekly status report is due Friday. You have 8 project trackers open. 5 managers typed "Green" into the status cell, 2 typed "Amber" with no reason, and 1 tracker was last touched 2 weeks ago. You already know which color the steering committee will ask about, and you know you can't explain it from the sheet.
The report is not hard to lay out. What's hard is making a color mean the same thing on every row, every week. This guide gives you a 16-column template, an example red, amber, green (RAG) rule to adapt, a way to roll several projects into one portfolio page, and the mistakes that let a red project report green. The template is also a CSV you can download.
What goes in a weekly status report?
A weekly status report answers 3 questions for each project: where is it against the plan, how do you know, and what do you need from the people reading it. Anything that doesn't serve one of those belongs in the project's own file.
That gives you 6 things per project:
- A status date. The day the data was last updated, not the day the report was sent.
- The next milestone against its baseline. The planned date, the forecast date, and the days between them.
- Forecast cost against budget. What the project is now expected to cost when it finishes, next to what was approved.
- A color and the reason for it. One line that names the number behind the color.
- Risks that nobody owns. A count, with the risk named in the reason.
- The decision needed. What the committee must approve, choose, or unblock this week. "None this week" is a valid answer.
The status date matters more than it looks. The US Government Accountability Office's Schedule Assessment Guide says that unless a status date is provided, a schedule cannot reliably convey past and remaining effort, and that neither the date someone views the schedule nor the file's last save date is a substitute. The same guide says a short narrative should accompany each status update, covering at least the status of key milestone dates and explanations for any changes in them. In a weekly report, that narrative is the reason column.
If you also report earned value, risk counts, or resource use, the definitions and formulas are in PMO dashboard: 12 metrics to report. This template keeps to what a weekly page needs.
What is RAG status, and why does it need a written rule?
RAG stands for red, amber, green: a color that sums up a project's health in one cell. The UK government uses it for its largest projects. Its delivery confidence assessment is defined as an assessment of the likelihood of a project delivering its objectives to time and cost, and the 2025-26 annual report on major projects rated 29 projects green, 109 amber, and 34 red at the end of March 2026.
Those colors come with written meanings. In the same report, amber means delivery appears feasible but significant issues exist that need management attention. The Infrastructure and Projects Authority's guide for review teams goes further and describes each color for time and for cost separately. For time, green is a project on or ahead of schedule, amber is behind schedule but with realistic plans to recover, and red is behind schedule and likely to be delivered late.
Two details in that guidance are worth copying. First, the ratings are described as a snapshot in time, so every color needs a date. Second, the review guide says its assessment "is not a calculation." It is a judgment made by an independent review team with evidence in front of it.
A weekly PMO report usually has no independent review team. The person who sets the color is the person being judged by it. That is why a weekly color works better as a calculation: the same inputs give the same color no matter who fills in the row, and judgment gets its own column next to it.
How do you write a RAG rule so colors stop being opinions?
Pick 2 or 3 measures you already collect, set a cutoff for each color, and write down what happens when measures disagree. Say your rule is this one. It is an example to adapt, not an industry standard.
| Color | Next milestone | Forecast cost | High risks, no owner |
|---|---|---|---|
| Green | 0 to 5 days late | Up to 5% over | 0 |
| Amber | 6 to 15 days late | Over 5%, up to 10% | 1 or more |
| Red | More than 15 days late | More than 10% over | Not used |
| No update | Status date over 7 days old | Status date over 7 days old | Status date over 7 days old |
Then add 3 lines under the table:
- The worst color wins. A project that is green on cost and red on schedule is red.
- No update is its own status. If the status date is more than 7 days before the report date, the row shows "No update" and the date of the last one.
- The rule has a start date. For example, "Rule version 1, in use from October 5, 2026."
Your cutoffs should come from your own projects. A 5-day slip means little on an 18-month build and a lot on a 6-week launch. US Department of Energy training material on earned value makes the same point about its own variance reporting: the thresholds that make a variance significant are defined in the contractor's procedures and in the contract, not in one universal table.
Because the rule only uses numbers in the row, a spreadsheet can apply it. Microsoft documents the Excel IFS function as returning the value for the first condition that is true, so you list the checks from worst to best. With days late in column J, percent over budget in M, unowned high risks in N, the status date in C, and the report date in a cell named ReportDate:
=IFS(ReportDate-C2>7, "No update", OR(J2>15, M2>10), "Red", OR(J2>5, M2>5, N2>0), "Amber", TRUE, "Green")
To color the cell, both Excel and Google Sheets have conditional formatting. Google's help page describes it as formatting cells to change text or background color when they meet certain conditions.
What does the weekly status report template look like?
The template has 16 columns, one row per project. Here they are with one example row filled in, a hypothetical data warehouse migration reported on Friday, November 6, 2026.
| Column | What goes in it | Example |
|---|---|---|
| Project | The name used everywhere else | Data warehouse migration |
| Owner | One person or role | Data platform PM |
| Status date | Date the row was last updated | 2026-11-05 |
| Rule color | Color the rule computes | Amber |
| Reported color | Color the manager reports | Green |
| Last week | Rule color in last week's report | Green |
| Next milestone | The next dated deliverable | Historical data loaded |
| Baseline date | Approved date for it | 2026-11-20 |
| Forecast date | Date now expected | 2026-11-30 |
| Days late | Forecast minus baseline | 10 |
| Budget | Approved total | $400,000 |
| Forecast at completion | Expected total cost | $412,000 |
| Over budget % | Forecast over budget, in percent | 3.0 |
| High risks without owner | Count from the risk log | 0 |
| Reason for color | One line naming the number | Milestone forecast 10 days late |
| Decision needed | What the committee must do | None this week |
Three columns do most of the work. Rule color and Reported color sit side by side, so a disagreement is visible instead of argued in the meeting. In the example, the rule says amber because the milestone is forecast 10 days late, and the manager reports green because a recovery plan is coming. Both are on the page. Last week is copied from last week's saved report, not retyped, so a change in color is a fact and not a memory.
The CSV has this row and 7 more made-up projects, so you can see a red, a "No update," and a row where the two colors disagree.
How do you roll several projects into one portfolio page?
Count, don't average. The portfolio page starts with how many projects sit at each color, then lists the rows that need attention.
Say the 8 projects in the CSV are your portfolio on November 6.
| Status by rule | Projects | Last week |
|---|---|---|
| Green | 3 | 5 |
| Amber | 2 | 3 |
| Red | 2 | 0 |
| No update | 1 | 0 |
Under the counts, show 4 short lists: projects that are red, projects that changed color since last week, projects where the reported color differs from the rule color, and decisions needed. Everything else is one line per project.
Be careful with totals. The 8 budgets add up to $1,550,000 and the 8 forecasts to $1,606,500, which is 3.6% over. By the example rule, 3.6% would be green. But one of those projects, a payroll system replacement, is forecast at $358,000 against a $320,000 budget, 11.9% over and red on its own. A portfolio total is useful for finance. It is not a status. Show the total, and next to it the count of projects more than 10% over.
Which mistakes make a status report misleading?
Watermelon status. Green on the outside, red on the inside. A Microsoft engineering blog post from 2010 describes it as reporting the status you think managers want to see instead of the actual status, and says teams do it because they fear red will make them look incompetent. Asking people to be braver does not fix this. The 2 color columns do. A manager can still report green, but the rule color and the number behind it are on the same row.
Stale updates. A row that nobody touched keeps last week's color and looks current. The status date and the 7-day "No update" rule make the gap visible. GAO's guide suggests tracking progress more often than you report it: if status is reported weekly, track progress daily. For a spreadsheet tracker, that means managers update the row as dates move, not on Friday morning from memory.
Changing the rule mid-quarter. If amber meant 6 to 15 days late in October and 11 to 20 days in November, a drop from 3 amber projects to 1 tells you nothing. Keep cutoffs fixed for the quarter. If you must change them, date the change and restate the earlier weeks under the new rule.
Amber with no end. A project that has been amber for 8 weeks is not being recovered. The UK review guide's wording is a good test: amber is behind schedule with realistic plans to recover. If the reason column has no recovery date, the color is hiding something.
Reasons without numbers. "Some concerns with the vendor" is not a reason. "Vendor delivery forecast December 18, baseline December 1" is.
Where Every Number fits
Every Number makes a dashboard from a spreadsheet, and every number on it opens a receipt: the definition, the filters applied, the rows used, the rows left out and why, the source file, and the date the data runs through. If your weekly status sheet is an Excel or CSV file up to 10 MB, you can drop it at everynumber.app/try with no account. The dashboard is ready in seconds and is deleted after 24 hours unless you save it. The PMO portfolio example shows one built from a weekly status sheet. Teams that sign up on their own are free for the first 30 days, with no card.
It is not a project management tool, and it has no live connectors to project tools. You upload an export. Write the color rule in your sheet first, as in the formula above, so the color is a column in the file you upload. If a portfolio tool your committee already trusts produces the weekly page, you don't need this.
Frequently asked questions
What is the difference between RAG and RYG status?
Only the name of the middle color. RAG says amber and RYG says yellow. The UK government guidance cited here uses red, amber, and green, and the Microsoft post uses red, yellow, and green for the same idea.
Should the project manager or the PMO set the color?
Let the rule set it, and let the project manager report a second color beside it. The PMO owns the rule, the cutoffs, and the report date. The project manager owns the data in the row and the reason.
How many colors should a status report use?
3 plus "No update" is enough for a weekly report. The UK review guide allows amber-red and amber-green for a status that lies in between, which suits a judgment made by a review team. For a computed weekly color, more steps mean more cutoffs to argue about.
What should happen when a project turns red?
The row should already say it: the number that made it red, and the decision needed from the committee. The UK major projects report notes that a red rating does not mean a project will fail. It means significant issues need urgent attention, and the report is how that attention gets asked for.
Sources
- Delivery confidence guide for review teams — Infrastructure and Projects Authority, GOV.UK. Checked November 16, 2026.
- NISTA Major Projects Annual Report 2025-26 — GOV.UK. Checked November 16, 2026.
- Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G) — U.S. Government Accountability Office. Checked November 16, 2026.
- EVMS Training Snippet 4.9: High-level EVM expectations — U.S. Department of Energy. Checked November 16, 2026.
- There's No Room For Watermelons — Microsoft Learn (archived MSDN blog, December 6, 2010). Checked November 16, 2026.
- IFS function — Microsoft Support. Checked November 16, 2026.
- Use conditional formatting rules in Google Sheets — Google Docs Editors Help. Checked November 16, 2026.