How do I give executives a one-page status view across all projects?

Build a portfolio one-pager that answers three executive questions: Are we on track? What changed? Where do you need a decision or help? Keep project detail in linked drill-downs; the one-pager should support decisions, not retell every project plan. (pmi.org)

A practical one-page layout

1. Headline — top row

• Reporting date and portfolio owner
• Overall portfolio health
• 3–5 headline metrics, such as projects on track, forecast spend vs. budget, milestones at risk, and decisions overdue

2. Portfolio table — the main area

Use consistent status definitions. For example, red means a committed outcome, date, or budget is at risk and needs intervention—not simply that a project has issues. Show trend (improving, stable, worsening) so a snapshot doesn’t hide movement.

3. Exceptions and asks — bottom row

• Top 3 risks/issues: impact, mitigation, owner, and next checkpoint
• Decisions needed: the specific decision, decision-maker, and deadline
• Recent material changes: only changes that affect outcomes, dates, cost, or capacity

Make it useful and trustworthy

• Standardize the reporting rules. Set the same definitions, measures, and update cadence for every project; otherwise roll-ups aren’t comparable.
• Show exceptions, not paragraphs. Give each project one concise row; reserve commentary for amber/red items and meaningful changes.
• Include dates and owners. “Delayed” is less actionable than “pilot forecast moves from Nov 15 to Dec 6; sponsor decision needed by Nov 3.”
• Track strategic alignment and outcomes, not just schedule and budget, so executives can see whether the work still merits investment. PMI emphasizes accurate portfolio context and status to support timely executive decisions. (pmi.org)
• Automate the roll-up where possible, but assign someone to validate it. A dashboard is only as good as the underlying project updates. (smartsheet.com)

A useful test: an executive should be able to scan the page in under a minute and know what’s healthy, what needs attention, and what they’re being asked to do.

A useful one-pager is a single table with one row per project, plus a short header and a decisions section. Here's how to build it.

1. Set the boundaries first
Name the portfolio, the reporting period, a data cutoff date, the audience, and who prepares and reviews the report. Decide whether proposed, paused, and business-as-usual work is included, or totals and trends won't be comparable from one period to the next. 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.

2. Pick the columns
Keep the table to what an executive needs to act. A common set is project name, sponsor, phase, overall health (RAG), budget signal, percent complete, next milestone, and top risk. One template lists sponsor, phase, health and budget RAG, percent complete, and the next milestone per project. Add a trend arrow or a note showing whether health changed since last period, since carrying last period's status next to this period's lets a reader spot a slow slide early.

3. Define what each color means
Agree on written criteria for green, amber, and red before the first report goes out. Otherwise the colors reflect each project manager's optimism. Consider rating several dimensions separately (schedule, budget, scope, resources) so a project can be green on budget and red on timeline. One guide suggests color-coded indicators (Green, Yellow, Red) for budget, timeline, resources, and scope. Also allow an "unknown" status with an owner and due date, rather than a guessed color. "Unknown" should be an allowed status with an evidence owner and due date.

4. Put the decisions at the top
Lead with an executive summary of two or three sentences, then list the decisions or help you need. If you need a decision, more budget, or an unblocked dependency, put it in the first line, phrased so the reader can say yes in one sentence. If nothing is needed, say so explicitly.

5. Limit the detail
Include only the risks that change a decision or the confidence in a date. Prioritize top-level insights and KPIs while avoiding operational details — executives need overall project health, not task-level minutiae. Keep task lists in the project-level reports and link to them if needed.

6. Standardize and automate the data pull
Use the same template every period so readers learn where to look. If you pull data from a PM tool, Excel, or a PPM system, have each project owner confirm their line before publishing. Name who supplied each status and when, so disagreements can be traced. Where a project owner and the portfolio office disagree and can't resolve it, show both positions rather than hiding the disagreement. Where the parties do not resolve a material difference by publication, show both positions, the evidence gap and the accountable resolver.

7. Choose a cadence and distribution
Weekly works for fast-moving programs, while monthly is more common for leadership portfolio reviews. Keep the same one-pager for both if possible, and send it before the meeting so the meeting can focus on decisions instead of status recitation.

A starter layout

• Header: portfolio, period, data cutoff, owner
• Summary: overall portfolio health, what changed, 2–3 sentences
• Decisions needed: the asks, with owner and deadline
• Table: one row per project with the columns above, plus trend
• Top 3–5 risks: impact, mitigation, and owner
• Footnote: definitions of RAG and any "unknown" statuses

If you tell me your tool (Excel, PowerPoint, Jira, Smartsheet, or similar) and how many projects you have, I can draft the specific template or formulas for it.

To provide executives with an effective, one-page status view across all projects, focus on high-level visibility, consistency, and decision-ready insights rather than exhaustive detail.

Executives do not need to see the "how" of every project; they need to know the "what" and the "so what" to make informed decisions.

1. The Core Components of Your One-Pager

Organize your view into these standard sections to ensure clarity and professional consistency:

• Executive Summary: A 2–3 sentence high-level narrative on the overall health of the portfolio. Are we hitting our strategic goals?
• Portfolio Dashboard (The "At-a-Glance" View): A table or visual grid listing all projects with key status indicators:
  • Status (RAG): Red (critical/at-risk), Amber (needs attention), Green (on track).
  • Key Metrics: Budget vs. Actual, Schedule (on-time/delayed), and Scope.
• Top Risks & Roadblocks: Highlight only the top 3–5 items across the entire portfolio that require executive intervention or awareness.
• Strategic Alignment: A quick indicator of how projects are contributing to business priorities (e.g., "Supports Q4 Revenue Goal").
• The "Ask": Clearly state what you need from the executives (e.g., approval for budget reallocation, resource sign-off, or risk acceptance). Never end without a call to action.

2. Best Practices for Design & Delivery

• Prioritize Clarity Over Detail: Use visual hierarchies like bold headings, bullet points, and RAG (Red-Amber-Green) indicators. Avoid technical jargon or excessive data.
• Standardize Your Format: Use a consistent template for every reporting cycle. This allows executives to know exactly where to look for the information they need, saving them time and building trust.
• Focus on Trends, Not Just Snapshots: If possible, include a small indicator (like an arrow) showing whether a project’s status is improving, stable, or declining compared to the last report.
• Enable "Drill-Down" Capability: If you are using a digital dashboard (e.g., Power BI, Tableau, or PM software), the one-pager should be the top-level view. Include a link or reference to the more detailed supporting data for those who wish to dig deeper.
• Be Proactive, Not Just Informative: Treat the report as a decision-making tool. If a project is "Red," don't just report it—propose a solution or a mitigation strategy alongside it.

3. Quick Tips for Success

• Keep it A4/Letter Sized: If you cannot print or view the entire summary on one screen without scrolling, it is likely too detailed.
• Limit Your Metrics: Don’t overwhelm the audience with 20+ KPIs. Select 5–7 that matter most to the business strategy (e.g., Budget Variance, Milestone Completion, Resource Utilization).
• Translate Data into Insight: Instead of stating "Project A is 2 weeks late," state "Project A is 2 weeks late, which impacts the Q3 launch; we are reallocating two developers to get back on track."

By providing this "bird's-eye view," you demonstrate that you are managing the portfolio strategically, which in turn builds credibility and helps your organization make smarter, faster decisions.

Build it around decisions and exceptions, not a collection of project reports. An executive should be able to scan it quickly and answer: How healthy is the portfolio? What changed? Where’s help needed? What decision is required? ¹²

A practical one-page layout

Header

• Reporting date and portfolio owner
• Overall portfolio health
• Small summary: # on track / at risk / off track

Portfolio table
Use one row per active project, with a consistent set of fields:

Keep the status and risk notes short; link to a project detail page for context.

Attention and action panel

• Top 3–5 exceptions, with impact and owner
• Decisions needed, the executive or group needed, and the deadline
• Upcoming major milestones or cross-project dependencies

If space allows, add a small capacity or resource-hotspot summary. Portfolio dashboards commonly highlight health, milestones, budget, risks, dependencies, and capacity—but include only what supports a leadership decision. ²³

Make the signals trustworthy

Define green / amber / red once for the whole portfolio, including what triggers each status and when an issue must be escalated. Show whether status is improving, worsening, or unchanged; a color without a trend can hide a deteriorating project. Use the same reporting period and definitions for every project, and show the date of the last update. ²⁵

A useful rule: every red or amber item should state the problem, its likely impact, the recovery action, the accountable owner, and whether leadership action is needed. Keep the one-page view concise, and let readers drill down for details rather than squeezing them all onto the page. ¹²

For the first version, ask executives what decisions they need to make—such as fund, stop, reprioritize, escalate, or reallocate—then keep only the measures that inform those decisions. ²