Model

Project Controls Maturity Model

A practical model for assessing where a programme’s controls capability actually sits — and what changes to move it up a level.

Five levels, from reporting the past to informing the decision in front of leadership. It is a practitioner’s model — a way to have an honest conversation about capability — not an externally certified industry standard.

05

Decision Intelligence

Executive decision support.

Typical capability

Controls output drives the decision leadership must make.

Typical weakness

A demanding standard to sustain, cycle after cycle.

Sustained by

The top of the model — held by consistent discipline.

04

Predictive

Early warning.

Typical capability

Emerging exposure is seen before it hits completion.

Typical weakness

Insight may still not reach or change executive decisions.

Enables progression

Framing exposure and options around the decision itself.

03

Integrated

Connected controls.

Typical capability

Time, risk, change and reporting are read together.

Typical weakness

Still explains the present more than the emerging future.

Enables progression

Trend analysis, early warning and forecast confidence.

02

Controlled

Structured baseline & reporting.

Typical capability

The programme is measured reliably every cycle.

Typical weakness

Dimensions aren’t joined up; risk and change sit apart.

Enables progression

Integrating time, risk, change and governance.

01

Reactive

Historical reporting.

Typical capability

Status is assembled after the fact.

Typical weakness

No forward visibility; decisions lag events.

Enables progression

An accepted baseline and structured progress measurement.

Reactive → Controlled → Integrated → Predictive → Decision Intelligence

Using the model

Most programmes are more than one level at once.

A programme can have a strong baseline (Controlled) while its risk and change sit in a spreadsheet nobody reads (still Reactive on that dimension). The point of the model is not a single score — it is to see where the gaps are, and to move the weakest dimension up. Each level is built on Integrity-Led Project Controls: you cannot be Predictive on a baseline you cannot trust.

Indicative self-assessment

Where is your project-controls capability today?

Ten questions for an indicative read on where a programme sits against the model. It runs in your browser and is a discussion and diagnostic tool — not an independently certified assessment.

01There is a controlled, accepted baseline.
02Progress is independently verifiable.
03Critical-path changes are actively monitored.
04Risk and change are connected to programme impacts.
05Forecasting is evidence-based.
06Recovery strategies are tested, not assumed.
07Management receives decision-ready information.
08Project controls are integrated across the programme.
09Emerging issues are identified before they become major delays.
10Project-controls information influences executive decisions.