Key Takeaways
- McKinsey's analysis of more than 300 billion-dollar-plus megaprojects found average cost overruns of approximately 80% and schedule delays of around 50%. A 2014 EY review of 365 oil and gas megaprojects found 64% exceeded budget and 73% missed schedule.
- Project management is the execution function: it plans, organises, and controls delivery. Project assurance is the governance function: it independently verifies that controls are sound, data is reliable, and the business case remains valid.
- HM Treasury's Orange Book, the OGC Gateway Review process, and PRINCE2 7 all codify assurance independence as a structural requirement, not a preference.
- IPA research across more than 25,000 capital projects shows front-end loading completeness is the single best predictor of cost, schedule, and operability outcomes. Projects that achieve Good or Best Practical FEL are on average 15% more cost-effective than those with Poor FEL - only approximately 13% of projects in recent years have reached execution at that standard.
- Owner teams not sufficiently staffed with experienced personnel are on average 25% more expensive than comparator projects, with 20% more cost growth and 5% worse schedule performance (Independent Project Analysis).
Major capital programmes in Energy, Minerals and Resources (EMR) are among the most complex, capital-intensive undertakings in industry. They involve billions of dollars of committed capital, multi-year delivery timelines, and governance structures spanning boards, executive teams, project organisations, and contractor networks. Within those structures, two distinct functions govern how programmes are executed and independently verified: project management and project assurance.
The two are frequently conflated. Assurance is sometimes treated as a subset of project management, or assigned to members of the delivery team itself. In either case, the governing body loses its independent line of sight to the project and must rely on self-reported status data from the team responsible for delivery.
This article sets out how the two functions differ, why the distinction matters for EMR capital programmes, and what the evidence shows about the consequences of blurring the boundary between them.
How Do Project Management and Project Assurance Differ?
Project management is the execution function. It is responsible for defining, planning, coordinating, and controlling the work required to deliver a project's outputs, within the agreed scope, schedule, and budget. The project manager is accountable to the project sponsor for delivery performance.
Core activities include scope baseline management, schedule development and critical path analysis, cost control and earned value management, risk identification and issue resolution, resource coordination across internal teams and contractors, and stakeholder management within the delivery environment.
Project assurance is the governance function. It provides independent, objective scrutiny of a project's health, assessing whether controls are operating as intended, whether reported data is reliable, and whether the programme remains aligned with the business case and strategic objectives that justified the original investment. The assurance function is accountable to the governing body - the board, executive committee, or steering group - rather than to the delivery team.
Core activities include verifying the integrity of cost, schedule, and risk data; assessing the fitness-for-purpose of internal project controls; validating business case assumptions against current realities; providing an independent view of project status to the governing body; and recommending corrective action where process, data, or governance weaknesses are identified.
The PMI Governance Practice Guide captures the structural distinction clearly: governance determines and approves, while management recommends and implements. Governance reviews and authorises stage gates; management executes and manages the reviews. Governance is strictly accountable for outcomes; management is responsible for executing the work.
Why Does Internal Reporting Diverge from Reality?
The case for independent assurance rests on what the evidence shows about project reporting under organisational pressure.
Research by Bent Flyvbjerg across thousands of major infrastructure and industrial projects identifies two systematic mechanisms. Optimism bias describes the tendency to underestimate costs and overestimate benefits, the natural inclination to weight how things could go right over how they could go wrong. Strategic misrepresentation describes the deliberate lowballing of costs and overstating of benefits to secure approval or continued funding. Both operate within normal project governance environments, and neither is reliably corrected by the project team itself.
The UK National Audit Office has documented the same pattern in major government programmes, noting that projects are routinely initiated on the basis of unrealistic assumptions - time and cost underestimated, benefits overstated - and that independent challenge is the primary available corrective.
The sector-specific data are consistent with this pattern. McKinsey's analysis of more than 300 billion-dollar-plus megaprojects found average cost overruns of approximately 80% and schedule delays of around 50%. A 2014 EY review of 365 oil and gas megaprojects found that 64% exceeded budget and 73% missed schedule, with average completion costs 59% above initial estimates. McKinsey also identifies part of the cause in the reporting mechanisms themselves: project progress data typically relies on contractor payment milestones rather than actual work performed, creating a structural gap between reported completion and physical reality.
This is a governance gap. It reflects the absence of an independent function capable of surfacing the divergence between what is reported and what is occurring on the ground - the gap that internal assurance processes operating within the delivery team are structurally unable to close.
Why Must Assurance Be Independent of the Project Team?
When the team responsible for delivery also holds the mandate to assess its own performance, the structural conditions for objective reporting are absent. Incentives align toward presenting progress favourably, and the governing body receives data filtered through the same function whose work is under review.
HM Treasury's Orange Book - the definitive UK framework for risk management - codifies the independence requirement through its three-lines model. The third line provides an objective evaluation of how effectively an organisation assesses and manages its risks, and explicitly names independent expert assurance reviews of major projects as a distinct and necessary source of assurance, separate from any function within the delivery organisation.
The OGC Gateway Review process, developed for major UK government programmes and applied across multiple jurisdictions, operationalises the same principle: gateway reviews are conducted by a team of reviewers not associated with the project, providing an arm's-length assessment at each decision point. PRINCE2 7 states the requirement directly - project assurance must be independent of the project manager, team managers, and project support staff.
An assurance function that sits within the delivery team, or that is staffed by personnel with direct interests in the project's outcome, cannot fulfil this mandate. The governing body's independent line of sight to the project depends on structural separation - not personal undertakings or informal arrangements.
How Do the Two Functions Converge at the Stage Gate?
The stage gate is the point at which project management and project assurance provide the governing body with two distinct inputs for its capital decision.
The project management team presents the case for proceeding: updated cost and schedule forecasts, the revised business case, execution plans for the next phase, and the current risk register. This reflects the delivery team's view of where the project stands.
The assurance function presents its independent review: an assessment of the quality and reliability of the data underlying that submission. Specifically - are the estimates well-founded? Is the schedule achievable given current performance? Are internal controls operating correctly? Does the project still represent the investment the governing body originally authorised?
Independent Project Analysis (IPA) draws this distinction explicitly: assurance at the gate is an independent review of the underlying work, provided as input to the gate decision. A gate decision made without this independent input is a decision made on the basis of unverified data.
The evidence supports investing in this rigour. IPA research across more than 25,000 capital projects shows that front-end loading completeness is the single best predictor of safety, cost, schedule, and operability outcomes. The correlation is strong: projects that achieve Good or Best Practical FEL are on average 15% more cost-effective than those with Poor FEL - though IPA's research identifies this as a relationship between preparation quality and outcomes, not a direct test of assurance independence as the sole driver. IPA also reports that only approximately 13% of projects in recent years have reached execution with that standard of preparation. Evidence from the gateway review process in Australia, documented by the Global Infrastructure Hub, showed the proportion of projects identified as having significant issues requiring resolution before development could proceed fell from roughly one in five to near-zero in the five years following implementation - the Hub's own characterisation of the result.
What Does Effective Assurance Depend On?
Structural independence is one requirement; capable owner-side personnel are another. IPA research quantifies the latter directly: project teams not sufficiently staffed with experienced owner personnel are on average 25% more expensive than comparator projects, with 20% more cost growth and 5% worse schedule performance.
Project assurance verifies that controls are operating correctly. Capable owner personnel design and operate those controls in the first place. The most effective ownership model pairs a sufficiently resourced, experienced project team with independent assurance carrying a clear mandate to the governing body - and maintains the separation between the two explicitly.
Both requirements are genuine. Owner teams that carry sufficient delivery expertise but operate without independent assurance leave the governing body reliant on self-reported data. Independent assurance applied to an under-resourced owner team surfaces avoidable problems rather than confirming effective controls. For boards and executive teams in the Energy, Minerals and Resources sector, the relationship between the two functions is a governance design question - and one that determines what information reaches the decision-making table, and whether it can be relied upon.
Independent assurance for Energy, Minerals and Resources capital programmes requires practitioners with direct delivery experience and a mandate that sits structurally outside the project team. PDAS provides independent project assurance and governance advisory across the full capital lifecycle - from front-end definition and stage-gate reviews through to programme close-out.
Book a discovery call with our team.
