Aligning Delivery Practices for Major Transport Projects
A transport organisation had experienced project directors and established local practices, but different definitions and reporting methods made portfolio decisions difficult. Clarus Caelum developed a minimum common delivery framework with the people responsible for using it, tested the controls against live projects and prepared the guidance needed to maintain them. The result was a comparable portfolio view that preserved each director's delivery accountability.
Keep what works at project level
The projects did not need identical operating models. They needed enough consistency to compare milestones, risk, shared-resource demands and escalation needs without manually interpreting every report.
We mapped existing practices with project and technical leaders, separating useful local variation from differences that obscured the portfolio position. Project, portfolio and partner stakeholders helped shape the framework before it became a mandated process.
Agree common definitions and test them in use
The framework established common milestone, key performance indicator, risk, change, dependency and escalation definitions. Controls focused on the information needed for decisions.
We applied them to current project conditions, removed redundant reporting, clarified definitions and adjusted decision packs around the questions executives needed to answer. This kept the design connected to the work of the project directors who remained responsible for delivery.
A framework the organisation could own
The delivered package included the common delivery standard, milestone and performance definitions, decision and escalation thresholds, a streamlined reporting pack and action, dependency and risk controls.
Templates and adoption guidance supported transfer to the client team. The framework created a workable level of consistency for portfolio decisions while retaining the flexibility needed by individual projects.
When this experience is relevant
This experience is relevant when every project report needs a different interpretation, executives cannot compare delivery risks or project leaders regard portfolio reporting as additional administration. The practical question is which controls need to be common and which decisions should remain with the project director.
Project Delivery assignment
We developed common project and portfolio management practices with the project directors responsible for using them.
A method for a similar decision
Delivery System Architecture
Identify the work, resources, access and authority controlling your next delivery milestone.
Relevant service streams
Project, programme and PMO management
Provide project and programme direction and management across planning, procurement, design and delivery. Coordinate suppliers, maintain cost, programme and quality controls, and progress the decisions needed for the next milestone.
Commercial risk and stakeholder advisory
Review contractual obligations and delivery risks, clarify responsibilities and maintain the actions and decisions that need management or stakeholder attention.
Prefer a practical starting point?
Use the Multi-Supplier Delivery Health Check to identify where inconsistent governance, interfaces and evidence are affecting outcomes.
Create consistency without losing accountability
Clarus Caelum can help define the minimum common delivery model that gives leaders a dependable portfolio view while preserving practical project ownership.