Back to catalog
Cross-industryModerate riskBlueprint

Project Portfolio Early-Warning Mission

Review project evidence, delivery risks and escalation needs.

For PMO, CIO | Portfolio management

Executive problem

Status reports are optimistic by default and risk surfaces late, when options are narrow.

PMOs and CIOs overseeing many concurrent initiatives with uneven reporting discipline.

Business question

Which projects show evidence of delivery risk now, and what needs escalation?

Required sources

Not connected by default. Each source is scoped and authorized per engagement.

  • Status reports
  • Milestone and budget records
  • Risk and issue logs
  • Cross-project dependencies

What the agent does

  • Compare reported status with milestone and budget evidence
  • Flag inconsistencies and stale updates
  • Highlight cross-project dependency risk
  • Draft escalation proposals

Boundaries

  • Does not change project data
  • Does not contact project teams or sponsors
  • Flags are evidence-based, not judgments of people

Human accountability

The PMO lead decides what to escalate and owns the conversation with sponsors.

Deliverables

  • Early-warning report
  • Evidence per flagged project
  • Dependency risk view
  • Proposed escalations

Acceptance criteria

  • Every flag cites evidence
  • Stale data is labeled
  • Escalation decisions recorded

Illustrative measures

Proposed measures to baseline during a pilot. These are not reported results.

  • Warnings raised before milestone slip

    Assessed retrospectively during pilot.

  • Flags accepted by PMO

    Share of flags the reviewer confirms.

Prerequisites

  • Portfolio data accessible in a structured form
  • Agreed status definitions
  • PMO reviewer