Portfolio Health Dashboard: Every Project's RAG, Schedule, Budget, and Risks in One View

The problem this kills

Every Monday the same scramble happens. The PMO emails twenty project managers asking for status, and twenty different answers trickle back — a slide here, a spreadsheet tab there, a Slack message, a "we're basically green." Someone then spends hours copy-pasting it all into one master deck for the steering committee, hand-coloring red-amber-green cells, and praying the numbers are current. By the time leadership sees it, half of it is a week stale and nobody is quite sure which projects are actually in trouble.

The deeper problem is that "green" means something different on every project. One PM calls it green because the team is happy; another calls it green because the budget is fine but the schedule is slipping. There's no consistent rule, so the portfolio view is really twenty opinions stapled together. Projects that quietly stopped reporting just vanish from attention. And because the master deck lives on one laptop, when that person is out, leadership flies blind.

A portfolio health dashboard should be a single, governed, always-current view — one consistent definition of health applied to every project, with the messy roll-up done by software and signed off by a human before it goes up the chain. Not a hand-built deck held together by Sunday-night heroics.

What you'll build

A simple internal web app for your PMO and leadership. You import each project's status data — schedule (planned vs. actual or % complete), budget (approved vs. spent vs. forecast), and its top risks and issues — from CSV or a Google Sheet, one row per project per reporting period.

The tool applies one consistent set of health rules across the whole portfolio: it computes a schedule RAG, a budget RAG, and a risk RAG from your thresholds, then rolls them into an overall RAG (red / amber / green) health rating for each project. It shows a filterable portfolio dashboard — by program, sponsor, status, business unit, or RAG — where leadership sees the whole landscape at a glance and can drill down into any single project to see its schedule, budget detail, and top risks. It automatically flags projects with stale or missing data so nothing quietly drops off the radar. The PMO reviews the consolidated snapshot, overrides any rating that needs human judgment (with a logged reason), and approves it before it's published to leadership and exported.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your portfolio — how status is collected today, what systems and spreadsheets your project data lives in, the real column names and project-code conventions in your exports, your reporting cadence, your exact RAG thresholds, and the messy exceptions (projects on hold, programs vs. projects, a PM who didn't report this week). It reflects a short tailored spec back to you and gets your thumbs-up before it builds anything, so the dashboard matches how your PMO actually defines health — not a generic template.

From there it walks the agent through the data model, the portfolio import, the health-rule engine that turns your thresholds into consistent RAG ratings, the stale-and-missing-data flagging, the filterable dashboard and per-project drill-down, the PMO approval gate, the published leadership view, and the clean CSV export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that uses Google Sheet / CSV imports as the data source and produces a clean CSV snapshot — so you can build and run the whole thing this weekend regardless of whether your data lives in Jira, Smartsheet, Planview, MS Project, or a pile of spreadsheets.

The governance it includes (this is the point)

This view goes to your steering committee, so the controls aren't optional. The plan builds in login so only your team can use it, row-level security so each organization only ever sees its own portfolio, a complete audit trail of who changed which rating and who approved which snapshot, a hard human-approval gate so no portfolio snapshot is published to leadership until the PMO signs off on it, and duplicate guards — deduping on (project + reporting period) — so the same project can't be counted twice when reports are re-imported.

Who it's for

PMO directors and analysts, program managers, delivery leaders, and the executives and sponsors who consume portfolio status. Especially anyone who rebuilds a master status deck by hand every week, struggles to compare projects rated by twenty different yardsticks, or has been surprised by a project that was "green" right up until it wasn't. If you can describe your RAG rules and what a project status report looks like, you can build this.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your whole portfolio on one screen before the weekend's out.