A one-page PMO weekly status report is a roll-up with one row per active project and the same columns each week: project, overall rating, last week's rating, next milestone, top risk, blocked decision with its decider and needed-by date, and next week's first step. A sponsor reads the whole portfolio from that page and sees which projects need a decision before the next sponsor meeting. The filled example below uses bracketed placeholders, and the rules explain how to keep each row to a single line.
How is a PMO roll-up different from a project weekly report?
A project weekly report covers one project and comes from its lead to the sponsor. A PMO roll-up puts every active project on one page, gathered by the PMO before a shared cut-off, so the sponsor reads the whole portfolio in one place. The roll-up is the summary, and each project report holds the detail behind it.
The two differ in who writes them and what they must answer:
- Project weekly report: the project lead writes it. It carries the detail behind the work, such as activities, evidence, and the full plan.
- PMO roll-up: the PMO collects each lead's reply, checks the ratings against the written tests, and builds the page. It carries only what a sponsor across projects needs to decide or act on.
Set the cut-off before the first roll-up goes out. Tell each lead the day, the time, and where to send the reply. Replies that arrive after the cut-off go on the following week's page, and the header states the time the page is complete as of.
Link each row to its project. The Project column names the project and its next milestone, so a sponsor who needs the evidence can open that project's own report.
Which columns belong on a one-page PMO weekly roll-up?
A one-page PMO weekly roll-up keeps the same columns in the same order every week: project, overall rating, last week's rating, next milestone, top risk, blocked decision, who decides and by when, and next week's first step. Each column answers one question the sponsor asks. Drop any column that does not change a decision the sponsor makes.
Start the page with a header you can copy:
PMO roll-up for week of [date]. Prepared by [name, role]. Updates due [time] on [day]. Complete as of [time].
Read the columns left to right. Each one tells the sponsor something specific:
- Project: the project's name, which links the row to its own report.
- Overall: the worst rating across the areas the project tracks.
- Last week: the rating copied from the saved page, so movement stays visible.
- Next milestone: the milestone, its date, and whether it has moved.
- Top risk: the one risk most likely to move that milestone, with its owner and fix date. Blocked items do not go here.
- Blocked: decision needed: the choice the sponsor must make, written in the sponsor's words.
- Decides, by: the decider's name and role, and the date the decision is needed.
- Next week: the first step the team takes, and who owns it.
Apply one rule to every project. A project with a change this week or an open decision gets a full row. A project with no change and no decision gets a single line below the table.
What does a filled one-page roll-up look like?
A filled roll-up gives each project that changed or needs a decision its own row, and gives a quiet project one line below the table. The example below is illustrative: every project name, milestone, date, and person is a [placeholder] to replace with your own, and each cell holds plain wording a sponsor can read at a glance.
Illustrative roll-up. Bracketed items are placeholders for your own projects, owners, and dates.
| Project | Overall | Last week | Next milestone | Top risk | Blocked: decision needed | Decides, by | Next week |
|---|---|---|---|---|---|---|---|
| [Project A: customer onboarding] | Amber | Green | [milestone], [date] | [Supplier] may miss the [date] signing. Owner: [name] | None | None | Call [supplier] to confirm the signing date. Owner: [name] |
| [Project B: system migration] | Red | Amber | [milestone], [date] | Decision overdue since [date], so [milestone] may move. Owner: [name] | Decision needed: [option A] or [option B] for the [area] scope. | [sponsor name, role], by [date] | Hold new build work until the decision is made. Owner: [name] |
| [Project C: training rollout] | Green | Red | [milestone], [date] | None open this week. | None | None | Decision closed: [option] chosen by [name, role] on [date]. Next: confirm training dates. Owner: [name] |
| [Project D: data reporting] | Amber | Amber | [milestone], [date] | [Data access] may slip the [test] date. Owner: [name] | Decision needed: [choice] for the [area] scope. | [name, role], by [date] | Send the decision request with both options. Owner: [name] |
Keep each cell to a single line, and move extra detail to the project's own report, which the Project column names.
A quiet project gets one line below the table:
[Project name]: Green. No change and no decision. Next milestone: [milestone], [date].
Two readings are easy to get wrong:
- Overall shows the worst area. GenPPT's guide sets overall status from the worst area, so Project B shows Red because its decision is overdue, whatever its other areas show.
- Last week comes from the saved page. Project C moved from Red to Green when its decision closed. Its Last week cell still says Red, and its Next week cell records the decision and who made it.
How do I rate overall health and risk?
Rate each area a project tracks as green, amber, or red against a written test, and let the worst area set the overall rating. Write each test as a sentence a sponsor can check against the plan, and agree the tests with the PMO before the first roll-up goes out.
Zeno's guide recommends tying each RAG colour to a written test, so a red on one project means what it means on another.
- Write the red test for each tracked area:
Red: [milestone] will move past [date] unless [decision] is made by [date].
- Write amber the same way:
Amber: [milestone] is at risk because [reason]. Fix: [action] by [date].
- Write green as plainly:
Green: [milestone] is on [date] and no decision is open.
- Set the overall rating to the worst area. If a project does not track budget, drop budget from its test rather than marking it green.
- Beside every amber or red, write the reason, the owner, and the date of the fix, as GenPPT's guide also suggests.
- This guide's own recommendation, not a published standard: count a decision that passes its needed-by date with no answer toward the red test, and say so in the Top risk cell.
How do I write a blocked item the sponsor can decide?
Write a blocked item as the decision you need, not as a status update. Name the choice, the person who makes it, and the date it must be made to protect the milestone. A sponsor can answer a sentence written that way in one reply, without scheduling a meeting.
Zeno's guide lists decisions needed as one of the blocks of a status report, and the Blocked column plays that role on a roll-up. A blocked item such as 'waiting on feedback' names no choice, so the sponsor has nothing to answer.
- Start the cell with 'Decision needed:' and one sentence naming the choice.
- Say what waits if the decision is not made, in plain words.
- Name the person who decides, by name and role.
- Give the date the decision is needed and the milestone it protects.
- Add a recommendation in one clause, if you have one.
Decision needed: [option A or option B] for the [area] scope. Waiting on: [sponsor name, role]. Needed by: [date], to keep [milestone] on [date]. Recommendation: [option], because [reason].
Copy this reply line under the blocked item, so the sponsor can answer in one line:
Reply: Decision: [option A or option B]. Decided by: [name, role]. Date: [date]. Reason, if any: [reason].
What does a project lead send each week?
A project lead replies to the weekly request before the cut-off with the overall rating and its reason, the next milestone and whether it moved, the top risk with its owner, any decision needed with its decider and date, and the first step for next week.
- Reply in this order:
Subject: [Project name] update for [date]
Overall: [green, amber, or red]. Reason: [reason].
Next milestone: [milestone], [date]. Moved: [yes or no, and the new date].
Top risk: [risk]. Owner: [name]. Fix by: [date].
Decision needed: [choice]. Decider: [name, role]. Needed by: [date].
First step next week: [action]. Owner: [name].
- Check your rating against the written test before you send it. Ask which line of the test your project's facts match.
- If a decision is needed, write it as the blocked item above, so it can go to the sponsor unchanged.
- When the saved page comes back, check your row. If it differs from your reply, tell the PMO before the sponsor meeting.
- When the sponsor answers, write the answer into your next update and take the first step you agreed.
For the person who builds the page
- Check each reply's dates against the project plan. If they differ, ask the lead which one is right before the page goes out.
- Copy each decision into the Blocked column in the sponsor's words. Do not leave a decision only in a project's notes.
- Copy last week's ratings from the saved page, not from memory. SlideTeam's PMO templates include current and previous RAG fields, so the page keeps a last-week column.
What mistakes make the roll-up hard to use?
The most common mistakes are putting blockers in the risk column, marking every row green, rating with no written test, and writing dates without a day or year. Each one hides a decision or lets readers see different things. Check for each before the page goes out.
- Blockers in the risk column. ONES's reporting example folds blockers into its Risks/Issues section. Give blocked items their own column, so each decision has an owner and a date.
- Every row green. The sponsor cannot tell which project needs them. A project on track needs only its quiet line.
- Colours with no test. Leads can rate the same problem differently, and both can feel they followed their judgment.
- Dates with no day or year. Readers guess which date is meant. Write the day and the date.
- Long cells. Keep each cell to a single line, and keep the detail in the project plan.
- Changed columns. Readers then have to find their place again each week.
Can a document or a tool carry the roll-up?
A document, spreadsheet, or slide deck can carry the PMO roll-up, as long as its columns and cut-off stay the same from week to week. Pick the place the team already updates, and use it for every roll-up so the sponsor knows where to look. The tool matters less than the columns.
Keep each open decision on the page until the sponsor answers it, so the next roll-up shows the result. Start with your next weekly update: fill the header, fill in the rows that changed, and send the page to your sponsor before the next sponsor meeting.