Aligning Delivery Practices for Major Transport Projects

Experienced project directors were achieving local results through different methods, but inconsistent definitions, controls and reporting limited dependable portfolio decisions. Clarus Caelum created a minimum common delivery framework that improved visibility and discipline without replacing project accountability.

The buyer situation

Each project had capable leadership and an established way of working. The problem was not an absence of management activity. It was that definitions, controls, reporting cycles and escalation thresholds varied enough to obscure the portfolio position. Comparison required manual interpretation, shared-resource choices were difficult, and executives could not reliably distinguish a local reporting difference from a material delivery risk.

A heavy central standard would have created resistance and risked weakening the accountability of experienced project directors. The organisation needed enough consistency for sound portfolio decisions while preserving the flexibility required by different delivery environments.

The mandate

Clarus Caelum was asked to establish a minimum common delivery framework: the smallest set of definitions, controls, information and decision points required for dependable portfolio governance. The framework had to reduce administrative effort, support adoption and remain useful to the directors responsible for delivery.

The approach

1. Understand what already worked

Existing practices were mapped with project and technical leaders. The design separated useful local variation from differences that prevented portfolio comparison or obscured risk.

2. Define the minimum control set

Common milestone, KPI, risk, change, dependency and escalation definitions were established. The focus remained on information needed for decisions rather than the production of uniform documents for their own sake.

3. Co-design for adoption

Project, portfolio and partner stakeholders shaped the working framework. This allowed practical constraints and director accountability to be addressed before the model became a mandated process.

4. Apply it to live delivery

The controls were tested against current project conditions. Redundant reporting was removed, unclear definitions were refined and decision packs were adjusted around the questions executives actually needed to answer.

5. Transfer ownership

Guidance, templates, decision routes and adoption expectations were structured so the organisation could maintain and improve the framework without relying on a permanent consultancy layer.

What was delivered

• A minimum common delivery standard.

• Common milestone and KPI definitions.

• Portfolio decision and escalation thresholds.

• A streamlined reporting and decision pack.

• Decision, action, dependency and risk controls.

• Practical adoption guidance for project directors.

The value Clarus Caelum brought

Clarus Caelum balanced disciplined portfolio control with respect for project-specific delivery conditions. This combination made it possible to remove low-value variation without forcing capable directors into an identical operating model. The framework was useful because it improved decisions, not because it created more compliance activity.

Delivery focus

The framework described in this case connected common definitions, reporting and escalation to portfolio decisions. Its focus was a workable level of consistency while preserving the accountability of individual project directors.

When this experience is relevant

• Every project report requires a different interpretation.

• Project leaders see portfolio governance as additional administration.

• Shared-resource and investment decisions lack a comparable evidence base.

• Escalation thresholds vary by project or individual.

• The organisation wants common control without removing delegated accountability.

Relevant service streams