A portfolio status report is the periodic summary of every project in a portfolio, sent to the people who can act on it. It covers status by project, spend against budget, the milestones that moved, the risks and issues that need a decision, and the decisions being asked for this period. One page for executives, a longer pack behind it for anyone who wants the detail.
It is not the same thing as your dashboard. The portfolio dashboard is always on and answers "where are we right now". The status report is a dated artifact that says what changed since the last one and what you want done about it.
Key takeaways
- Lead with decisions requested, not with project-by-project narrative. If the reader stops after the first screen, they should still have done their job.
- One page for the executive audience. The detail pack lives behind it and is read by maybe four people.
- Report the delta. Status that has not changed since last period needs one word, not a paragraph.
- Show budget as committed plus actual against approved, not just spent to date. Spend alone hides the hole.
- Every red project needs an owner, a date and an ask. Red with no ask trains people to ignore red.
- Monthly at portfolio level, weekly only for a genuine crisis. Weekly portfolio reporting produces weekly copy-paste.
Last updated July 2026.
What should be included in a portfolio status report?
A portfolio status report should include a period header, an overall portfolio position, a status line per project, financials, the movement since last period, escalations, and the decisions being requested. Here is what each section is doing and who actually reads it.
| Section | What goes in it | Read by |
|---|---|---|
| Header | Reporting period, date issued, author, distribution | Everyone, later, when someone asks which version this was |
| Decisions requested | Numbered asks with owner and needed-by date | The sponsor and the steering committee. This is why the report exists. |
| Portfolio position | Count by status, spend against approved, delivery against plan | Executives |
| Project status lines | One row per project: status, phase, next milestone, change since last period | Sponsors and the PMO |
| Financials | Approved, committed, actual, forecast to complete, variance | Finance and the portfolio owner |
| Escalations | Risks and issues that exceed a project manager's authority | The steering committee |
| Changes since last period | Projects started, stopped, paused, rebaselined | Everyone. This is the section people actually scan. |
| Appendix | Per-project detail, full risk register extract, milestone log | Almost nobody, and that is fine. It exists to be referenced, not read. |
Notice the order. Decisions come second, before the status detail. Most templates bury the asks at the end, after twelve project summaries, which is precisely where an executive reader has already stopped.
The one page portfolio status report
The executive version is one page and answers four questions: is the portfolio in trouble, where is the money, what changed, and what do you need from me. Everything else is appendix.
- Top strip. Project counts by status, approved versus forecast spend, milestones due this period and how many landed.
- Decisions requested. Three to five numbered items, each with an owner and a date. If you have more than five, you have a governance problem, not a reporting problem.
- Exceptions. Only the projects that are red or newly amber, one line each, with the ask.
- Movement. What started, stopped, paused or rebaselined since the last report.
The discipline that makes this work is refusing to report on green projects. A green project gets a row in the appendix table and no narrative. The moment green projects get paragraphs, the exceptions stop standing out and the report becomes wallpaper.
Portfolio status report example
The core table, illustrative but structurally what a real one looks like. Approved and forecast figures in thousands.
| Project | Status | Trend | Phase | Next milestone | Approved | Forecast | Ask |
|---|---|---|---|---|---|---|---|
| Payments migration | Red | Down | Build | Pilot cutover, 14 Aug | 820 | 960 | Approve 140k or cut phase 2 scope |
| Warehouse automation | Amber | Flat | Build | UAT start, 02 Sep | 1,450 | 1,480 | Release the second QA lead |
| CRM consolidation | Amber | Up | Design | Design sign-off, 21 Aug | 390 | 390 | None, watching |
| Data platform | Green | Flat | Build | Phase 1 live, 30 Sep | 640 | 625 | None |
| Field app refresh | Green | Flat | Discovery | Business case, 08 Aug | 75 | 75 | None |
| Compliance reporting | Paused | n/a | Hold | Restart decision, 29 Aug | 210 | 210 | Confirm restart or close |
Two columns do most of the work here and most templates omit both. The trend column tells a reader whether amber is amber on the way up or on the way down, which changes the response entirely. The ask column forces the writer to say what they want, and a status report where every ask says "none" is telling you either the portfolio is genuinely calm or that nobody is willing to raise anything, and it is worth knowing which.
How you decide what counts as red is a separate discipline worth getting right first, because inconsistent criteria across project managers make the whole table meaningless. RAG status criteria covers how to define the thresholds so two people report the same situation the same way.
Financials: committed, not just spent
The financial section fails in one predictable way. A project reports 40 percent of budget spent at the halfway point and looks fine, while another 35 percent is already committed on signed purchase orders and contractor engagements that have not been invoiced yet. Reporting spend alone means the overrun appears the month the invoices land, which is far too late to do anything.
Four columns fix it: approved, committed, actual to date, and forecast to complete. Variance is the difference between approved and forecast, not between approved and actual. If your finance system cannot give you the committed figure, get it from the purchase order and commitment data instead, and say in the report which source you used.
Portfolio status report vs project status report
They are different documents for different readers, and merging them produces a report that serves neither.
| Project status report | Portfolio status report | |
|---|---|---|
| Question it answers | Is this project on track? | Are we delivering the right things, and can we afford them? |
| Unit | Tasks, milestones, risks, issues | Projects, spend, benefits, capacity |
| Written by | Project manager | PMO |
| Read by | Sponsor, project board | Steering committee, executive team |
| Cadence | Weekly or biweekly | Monthly |
| Typical failure | Activity narrative with no decision in it | Twelve project reports stapled together |
That last row is the one to watch. A portfolio report is not a compilation. It is a different level of analysis that happens to use project data as its input, in the same way a set of accounts is not a pile of receipts.
How often should a portfolio status report be produced?
Monthly for most portfolios, aligned to the meeting where decisions actually get made. Match the cadence to the decision, not to the calendar, and never produce a report that has no meeting attached to it.
| Cadence | When it fits | Risk |
|---|---|---|
| Weekly | A portfolio in genuine crisis, or a short transformation with daily-moving dependencies | Copy-paste reporting within three weeks |
| Monthly | Almost every steady-state portfolio | Slow reaction to a fast-moving red project, which exception reporting should cover |
| Quarterly | Board-level and investment reporting | Too slow to steer anything on its own |
Run exception reporting alongside whatever cadence you pick: a project going red does not wait for the last Thursday of the month. Publish the report two working days before the portfolio review meeting so people have read it, and make it explicit that the meeting will not walk through the pack. Reading the report aloud is how a ninety minute governance meeting produces two decisions.
Excel, slides, or the tool you already have
Most portfolio status reports are built twice: once in a spreadsheet where the numbers live, and once in slides because that is what goes to the committee. That duplication is where errors get introduced, usually by a manual retype the week someone is on leave.
Pick the spreadsheet as the source of truth and generate the deck from it, even if generating means paste-linking a range. If your PPM tool produces the report natively, use it and stop maintaining the spreadsheet, on the condition that project managers actually keep their data current in the tool. A generated report from stale data is worse than a manual report from a chased spreadsheet, because it looks authoritative.
The decisions section
If you change one thing about your report, make it this. Write each ask in the form: decision needed, by whom, by when, and what happens if it slips. "Approve additional 140k for payments migration, portfolio owner, by 14 August, or phase 2 scope is cut" is a decision. "Budget pressure on payments migration" is a weather report.
Then track the asks. Number them, carry unresolved ones forward with their original date, and show how long each has been open. A portfolio report with three decisions that have been open for four months is telling you something far more important than any RAG column, which is that your governance forum is not deciding things. That belongs in front of the steering committee, and it is usually the most useful thing a PMO can put in front of them.
Common questions about portfolio status reports
What is a portfolio status report?
A portfolio status report is a dated summary of all projects in a portfolio, produced for the governance forum that oversees them. It reports status and trend per project, spend against approved budget, milestone movement, escalated risks and issues, and the specific decisions the portfolio needs from its executives this period.
What should be included in a portfolio status report?
Include the reporting period and distribution, the decisions requested, an overall portfolio position, one status line per project with trend and next milestone, financials showing approved, committed, actual and forecast, escalations above project authority, and what started, stopped or was rebaselined since the last report.
How long should a portfolio status report be?
One page for the executive audience, plus an appendix of any length for reference. If the summary runs past a single screen, you are reporting on green projects. Cut every project that is on track to a single table row and give the space to exceptions and decisions instead.
What is the difference between a portfolio status report and a project status report?
A project status report answers whether one project is on track and is written by its project manager for its sponsor. A portfolio status report answers whether the organization is delivering the right mix affordably, is written by the PMO for the steering committee, and treats projects as its unit of analysis rather than tasks.
Who prepares the portfolio status report?
The PMO prepares it, using data supplied by project managers. The critical part is that the PMO analyzes rather than compiles: chasing missing inputs, challenging optimistic status, spotting patterns across projects, and turning the result into a small number of decisions. A PMO that only collates is an expensive mail merge.
How do you report a project that is red every month?
Change the question the report asks about it. A project that has been red for three consecutive periods no longer needs a status update, it needs a stop-or-fix decision with a date. Put it in the decisions section rather than the status table, with the cumulative slippage and spend since it first went red.
Where this fits in your reporting
The status report is one output of a reporting system, not the whole thing. The metrics that populate it should come from an agreed set, covered in portfolio KPIs and metrics, and the broader principles behind what to report and what to leave out are in PMO reporting and portfolio dashboards. If the decisions in your report keep going unmade, the problem is upstream in portfolio governance rather than in the document.