Project Portfolio Status Report Template: Health, Capacity, Dependencies and Decisions

A project portfolio status report template should show leaders what changed across a defined portfolio, why it matters and which decisions or interventions are needed. It is not a bundle of project updates. The portfolio view must make cross-project capacity, dependencies, outcomes and tradeoffs visible without hiding uncertainty behind a single color.

Use controlled source records and a consistent reporting date. The report supports governance; it does not replace project plans, approved financial records, risk registers, contracts or specialist review.

Preserve the published snapshot so later readers can reconstruct the decision context.

Define audience, boundary and reporting rules

Name the portfolio, included initiatives, reporting period, data cutoff, audience, preparer and accountable reviewer. Explain whether proposed work, paused work and business-as-usual initiatives are included. Without a stable boundary, totals and trends cannot be compared responsibly.

Agree definitions for milestone health, outcome health, risk exposure, issue severity, confidence and escalation. State how missing or late data appears. “Unknown” should be an allowed status with an evidence owner and due date.

Set a correction process and distribution level. A report for an executive committee should emphasize exceptions and choices; a working portfolio office may need more operational detail. Use the client status report template when reporting one engagement rather than comparing an internal portfolio.

Publish a short reporting calendar with input deadline, challenge window, governance meeting and final distribution date. This helps teams distinguish the data cutoff from the meeting date. Late changes should be marked as such, with their source and review status, rather than silently merged into a supposedly consistent snapshot.

Assign reporting and review ownership

The portfolio manager compiles the report and challenges inconsistent inputs. Project or program owners certify their source update as of the cutoff date. Sponsors validate outcome context and requested decisions. Capacity owners verify shared-resource claims. Relevant finance, risk, security, legal or commercial specialists review statements in their remit.

The portfolio chair owns the final governance message and decides what requires discussion or escalation. The report preparer should not silently reinterpret a project owner’s forecast. Differences should be resolved or shown transparently.

Record who supplied each material claim. A named source and date make later corrections possible. If AI or automation helps consolidate data, keep the responsible human reviewer visible.

Agree a challenge route. Portfolio managers should be able to question an unsupported green status, and project owners should be able to correct a consolidation error. Where the parties do not resolve a material difference by publication, show both positions, the evidence gap and the accountable resolver. Concealing disagreement makes the report look cleaner while weakening the decision.

Copy this project portfolio status report template

PROJECT PORTFOLIO STATUS REPORT

Portfolio / reporting period / cutoff date:
Prepared by / reviewed by:
Scope and status definitions:

1. EXECUTIVE CHANGE SUMMARY
What changed since last report:
Portfolio outcome or commitment affected:
Decisions or attention required:

2. PORTFOLIO HEALTH
Initiative / sponsor / outcome health / delivery health
Evidence / forecast / confidence / next checkpoint

3. CAPACITY
Constraint / available evidence / affected initiatives
Options / tradeoff / owner / required date

4. DEPENDENCIES
Provider / receiver / required input / due date
Current condition / consequence / response / owner

5. RISKS, ISSUES AND ASSUMPTIONS
Type / description / evidence / effect
Response / owner / escalation trigger / review date

6. DECISIONS AND ESCALATIONS
Question / options / recommendation / authority
Decision or route / owner / deadline

7. ACTIONS AND DATA QUALITY
Action / owner / due date / completion evidence
Missing or stale data / correction owner / date

Keep the main report concise and link to controlled details. Do not copy sensitive source material into a wider distribution than necessary.

Lead with movement and decision need

The executive section should answer what materially changed since the previous report. Include new work, completed outcomes, forecast movement, major dependency changes, capacity conflicts, escalated exposure and decisions taken or required. Avoid listing meetings, documents and routine activity unless they changed the portfolio position.

Compare previous and current conditions. A concise table can show area, prior position, current evidence, effect and attention needed. Explain why a change matters to portfolio objectives rather than assuming the reader knows every project.

Put important uncertainty in the summary. A confident conclusion drawn from stale inputs is more dangerous than a clearly labeled gap. The decision log template should preserve decisions that the status cycle reports.

Report outcome and delivery health separately

An initiative can deliver milestones while evidence for the intended outcome weakens. Conversely, an outcome indicator can improve for reasons unrelated to the project. Show outcome health, delivery health and confidence as separate fields.

For each material initiative, include sponsor, current phase, agreed outcome, latest evidence, next decision point, baseline milestone, current forecast and explanatory note. Define complete, accepted and realized rather than treating them as interchangeable.

Avoid unsupported percentage-complete figures. If a percentage has a valid method, document it. Pair status labels with conditions and response. Do not average several green workstreams into a green project when one unresolved approval controls release.

Show capacity as a portfolio constraint

Report shared skills, people, environments, supplier slots or review capacity that affect several initiatives. Identify demand period, validated availability, affected work and the owner who can resolve allocation. Do not count the same capacity twice across project plans.

Show scenarios where useful: preserve current priorities, delay one initiative, reduce scope or obtain additional approved capacity. State assumptions, operational consequences and authority required. A scenario is not an approved plan.

Capacity reporting should avoid personal performance judgments or unnecessary employee data. Escalate systemic constraints through workforce and portfolio governance, while authorized managers handle individual matters in the appropriate channel.

Track the difference between nominal allocation and usable capacity. Time reserved on a plan may be unavailable because of operational duties, leave, onboarding, context switching or missing access. Validate the period and the kind of work the capacity can perform. When additional capacity is proposed, include the lead time and enablement needed before treating it as available.

Map dependencies in both directions

A dependency record should name the providing initiative or owner, receiving initiative, required input, due date, current evidence, consequence of delay, response and escalation trigger. Reporting only “dependency at risk” leaves both action and accountability unclear.

Highlight chains and concentration. One delayed environment, approval or vendor deliverable may affect several projects. Show that relationship so leaders can prioritize the controlling intervention instead of asking each project for an isolated recovery plan.

Confirm dependencies with both sides. A receiving team’s forecast may not match the provider’s commitment. Preserve the difference until responsible owners reconcile it; do not let reporting automation choose the more convenient date.

Separate risks, issues, assumptions and decisions

A risk is uncertain and future-facing. An issue already affects delivery. An assumption is treated as true for planning but still needs validation. A decision is an authorized choice. Put each in the correct record and summarize only material items in the portfolio report.

For every exception, state evidence, potential or actual effect, response, owner, review date and escalation trigger. Avoid unsupported legal, financial or compliance conclusions. Route those judgments to qualified owners and report their approved position accurately.

The corrective action report template is useful when a recurring issue requires containment, cause analysis and verified corrective action beyond routine status reporting.

Present decisions and escalation neutrally

Frame each decision with the question, deadline, options, evidence, recommendation owner, consequences and required authority. Distinguish the recommendation from the final decision. If the forum lacks authority, record the escalation destination and response date.

Do not bury a decision inside a project narrative. A reader should be able to scan one section and know what is required. After the meeting, update decision and action records rather than relying on the report as the only source.

Report conditions and dissent where material. A decision to continue may depend on evidence due at the next checkpoint. Capturing the condition prevents an unconditional interpretation later.

Maintain a small “decisions aging” view: date raised, current owner, required authority, consequence of delay and next escalation. This shows when portfolio drift is caused by governance latency rather than delivery performance. Close the item only when the authorized decision and resulting source-record updates are complete.

Use recording and drafting tools responsibly

Portfolio meetings can contain confidential strategy, commercial forecasts, security concerns and personnel information. Record only when authorized and necessary. Provide notice, obtain required agreement, control access and retention, and exclude restricted discussion where appropriate.

For an authorized portfolio status review with visible, consented capture, Kuno can help draft decisions and actions for responsible human review. It does not determine health, allocate capacity or approve changes. Explore Kuno

AI may consolidate approved inputs, but it can also flatten uncertainty or repeat stale data. Require humans to verify project identifiers, dates, status definitions, forecasts, dependencies, negations and every executive summary claim.

Complete final QA and close the loop

Before distribution, the portfolio manager and chair should confirm that:

• portfolio scope, cutoff date and definitions are explicit;
• all material claims have a source owner and evidence date;
• outcome, delivery and confidence are not collapsed into one label;
• status changes explain cause, effect and response;
• capacity is validated and not counted twice;
• dependencies name providers, receivers and dates;
• risks, issues, assumptions and decisions remain distinct;
• recommendations, decisions and escalations show correct authority;
• sensitive information has proportionate access;
• every action has one owner, due date and completion evidence.

At the next cycle, check whether prior actions changed the portfolio position. Use meeting follow-up to distribute one reviewed record and manage corrections.

Create a portfolio update people can verify and act on. Kuno supports authorized capture and draft follow-up; accountable leaders confirm evidence, status, decisions and final distribution. See Kuno