Skip to content
Projects Advisors

The framework · 02.1 · Delivery & Controls

Baseline integrity

Is the baseline currently being reported against the one that was sanctioned, and if not, is every step between the two documented?

What goes wrong without it

Performance reporting is only meaningful relative to a baseline, so a baseline that has quietly moved makes every subsequent report defensible and useless. A programme need not lose the baseline in one visible event. It can go in a series of small re-baselines, each individually reasonable, none of which is wrong on its own terms. No single report shows the cumulative movement, so it can go unexamined.

What to examine

4 tests

  1. Reconcile the current baseline to the sanctioned baseline in one continuous chain. The inability to do this is the finding.
  2. Count the re-baselines and read the approval for each. Check who approved them and whether that person also owned the performance being re-based.
  3. Compare current forecast against the original sanction figure, not against the most recent baseline. That comparison carries the cumulative movement.
  4. Check whether scope was removed to hold cost. Descoping presented as underspend is a quiet failure: it reads as success.

Required by

  • ISO 21502:2020, Clause 7, management practices covering planning, scope, schedule, cost and change control.
  • PMBOK Guide, Eighth Edition, November 2025, scope, schedule and finance performance domains.

Read the sources

How the method applies it

A tool: Reporting history check.

direct The means produces evidence at least one of the tests above asks for. A reading, and labelled as one.

In the asset lifecycle methodThe steps of the two methods that this domain examines.

Cite this page

Projects Advisors, “02.1 Baseline integrity,” revised 2026-10-08, https://projects-advisors.com/framework/delivery-and-controls/baseline-integrity