Large infrastructure programmes — motorways, railways, energy infrastructure, major construction — face a project controls challenge fundamentally different from standard project management. The scale, duration, and complexity create visibility problems that standard controls approaches cannot adequately address.
The organisations that deliver these programmes most effectively share a common characteristic: they establish rigorous controls infrastructure before significant spend begins, not in response to problems that emerge later.
Why Infrastructure Controls Are Different
Scale of the WBS — A major infrastructure programme may have thousands of work packages across hundreds of contractors and subcontractors. The Work Breakdown Structure must be designed carefully to enable meaningful aggregation at programme level without losing the operational detail that project managers need day to day.
Extended timescales — Multi-year programmes require controls that remain reliable across changing teams, technology platforms, and reporting requirements. The system established in year one must still produce trustworthy data in year four, often with significant personnel turnover in between.
Multi-contractor environments — When cost and schedule data arrives from dozens of contractors using different systems, formats, and conventions, consolidation is a significant undertaking. Without standardised data templates and clear submission requirements, the controls function spends most of its time chasing and reconciling rather than analysing.
Governance and regulatory reporting — Major infrastructure programmes in the UK typically involve government clients, funding bodies, or regulatory oversight. Controls must produce the information these stakeholders require, in the formats they expect, without creating parallel reporting processes that consume additional capacity.
The Controls Infrastructure That Works
Invest in the baseline — Meaningful earned value analysis requires a realistic, well-structured baseline that represents how the work will actually be executed. Programmes that rush the baseline to meet governance deadlines end up measuring performance against a plan that no longer reflects operational reality.
Standardise contractor reporting — Require all contractors and major subcontractors to submit progress and cost data in a standardised format, at a consistent frequency. The additional burden this places on contractors is significantly less than the reconciliation effort it saves the controls function.
Move to weekly cadence — Monthly reporting is insufficient for infrastructure programmes where a week's delay on a critical path activity can cascade into months of programme impact. Weekly cost and schedule updates, even if approximate, enable faster intervention than monthly precision.
Risk-based focus — With thousands of work packages in a major programme, the controls function cannot give equal attention to everything. Focus analytical resource on packages that are on the critical path, carry the highest cost exposure, or are showing early warning signals of schedule pressure.
Earned Value in Infrastructure Contexts
Earned value management is particularly powerful in infrastructure programmes because the sheer scale makes intuitive assessment unreliable. When a project manager says "we're roughly on track," EVM provides the quantitative basis to confirm or challenge that assessment.
The challenge is implementing EVM in a way that programme teams find credible and useful rather than bureaucratic and abstract. This requires investing in WBS structure, training project managers to understand what CPI and SPI mean in operational terms, and ensuring EVM reports always include narrative context alongside the numbers.
The Cost of Getting Controls Wrong
The cost of inadequate project controls on a large infrastructure programme is not just a few missed reporting deadlines. It is cost overruns that compound undetected, schedule delays that are not surfaced until they are unavoidable, and contract disputes that emerge because neither party has reliable data about what was actually delivered and when.
Establishing strong controls at programme inception is not overhead — it is risk management. The relatively modest investment in controls infrastructure at the outset is consistently returned many times over through earlier problem identification and more confident delivery decisions.