Stalled / At-Risk Project Watchlist: Start Every Review With the Right Short List

The problem this kills

Every portfolio review starts the same way: someone spends the night before squinting at twelve status reports, a milestone tracker, a budget sheet, and a risk log, trying to remember which projects are actually in trouble. By the time the leadership meeting starts, half the room is debating a green project that's fine while the one quietly bleeding budget never makes the agenda.

The trouble isn't a lack of data — it's that the signals live in four different places and nobody has time to cross-reference them every week. A project can be marked green by an optimistic owner while its milestone slipped a month ago, its spend blew past plan, and a high risk has sat "open" with no mitigation for six weeks. No single sheet shows you that. So the review runs on whoever shouted loudest, not on where the real risk is.

A watchlist should be built the same way every time, from the same rules, with a clear reason on every entry — and it should land on the PMO's desk before the meeting, not get assembled live in the room.

What you'll build

A simple internal web app for your PMO. You import your portfolio status, milestone, budget, and risk data — from CSV or a Google Sheet — and you tell the tool, once, what "at risk" means in your shop: red RAG status, a milestone overdue by more than X days, actual spend over budget by more than Y percent, a status that hasn't been updated in Z days, or an unresolved high/critical risk.

The tool runs those rules across the whole portfolio and drafts a watchlist — every flagged project with the specific reason(s) it made the list. The PMO reviews the draft, confirms the ones that belong, removes the false positives with a reason, or snoozes an item with a note ("known, mitigation in flight — revisit next period"). When the PMO approves, the tool produces the final watchlist plus a short recommended-focus summary and a clean CSV, ready to circulate for the leadership review. It dedupes on project + reporting period, so re-importing the same week's data never creates phantom duplicates.

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 business — how your portfolio is reported today, what systems and sheets the status / milestone / budget / risk data lives in, the exact column names and how you name projects and code your RAG status, your real thresholds for overdue / over-budget / stale, your reporting cadence, and the messy exceptions (projects on hold, programs vs. projects, baseline changes). It reads a short tailored spec back to you and waits for your thumbs-up before it builds anything, so the watchlist matches your governance — not a generic template.

From there it walks the agent through the data model, the multi-source import with dedupe, the rules engine that flags projects and records why, the watchlist draft, the PMO review-and-approve gate with confirm / remove / snooze, the recommended-focus summary, the Resend circulation email, and the 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 export — so you can build and run the whole thing this afternoon, no matter what PPM or spreadsheet stack you're on.

The governance it includes (this is the point)

This is leadership-facing, so the controls aren't optional. The plan builds in login so only your PMO and delivery leaders can use it, row-level security so you only ever see your own organization's portfolio, a complete audit trail of who flagged, removed, snoozed, and approved each item and when, a hard human-approval gate so no watchlist gets circulated until the PMO has reviewed the draft and signed off, and duplicate guards (dedupe on project + period) so the same project can't appear twice when you re-import a reporting period.

Who it's for

PMO directors, program managers, portfolio leads, delivery managers, and executives who run a regular portfolio review and are tired of reassembling "what's actually in trouble" from scratch every cycle. If you can explain what makes a project red, overdue, over budget, or stale in your world, you can build this.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your first auto-built watchlist on screen this afternoon.