Programme Governance
Programme Controls vs Project Controls
The terms are used interchangeably, but the step from one to the other is real — and it is where controls stops being a reporting function and starts being a governance one.
Project controls: depth on one contract
Project controls keeps a single project honest — baseline, progress, cost, change and risk on that contract, measured well and reported clearly. The unit of concern is the project.
Programme controls: integration across many
Programme controls sits a level up. Its job is to make many independent contracts — each with its own schedule and contractor — add up to one coherent, trustworthy picture for the Employer. The unit of concern is the portfolio, and the hardest work is integration: common standards, comparable data, and interfaces that no single project owns.
Why the distinction matters
At programme scale, the failure mode is not a bad project schedule; it is fifteen good ones that cannot be compared or combined. Programme controls exists to prevent that — to turn a stack of project reports into portfolio-level intelligence leadership can decide on. On the Riyadh City programme in Abu Dhabi, holding one standard across 16 contracts is exactly what let a single contractor’s claim be tested against a reliable record.
The leadership implication
If you only have project controls on a multi-contract programme, you have depth without integration — and leadership is left doing the integration itself, in its head, in the meeting. Programme controls does that work first, which is what makes it a governance function rather than a reporting one.