Case Studies in Project Controls

Why Case Studies Matter

Theory tells you what should work. Case studies tell you what actually worked — and what didn't.

The materials in this companion article draw from four real-world contexts: a mega-construction success story (Heathrow Terminal 5), a mega-construction challenge (the 2012 London Olympics), the upstream oil and gas sector, and the discipline of front-end project controls in capital improvement programs. Together, they illustrate how the lifecycle, process groups, and knowledge areas play out when billions of dollars and immovable deadlines are on the line.

---

Case Study 1: Heathrow Terminal 5 — Rewriting the Rules of Risk

The Challenge

Major construction projects have a dismal track record. Cost overruns, schedule delays, and adversarial litigation between clients and contractors are the norm, not the exception. The Wembley Stadium project — which used a traditional fixed-price contract — ended in litigation precisely because the contract structure encouraged blame rather than collaboration.

BAA Ltd., the operator of Heathrow Airport, faced this reality when planning Terminal 5 — one of the largest construction projects in Europe. Traditional contract approaches would, by BAA's own estimates, have delivered the project two years late and 40% over budget.

The Framework Applied

BAA took a radically different approach, built on two foundational government reports from the 1990s: Constructing the Team (Latham, 1994) and Rethinking Construction (Egan, 1998). These reports identified two systemic problems undermining the construction industry: cultural confusion and the reluctance to acknowledge risk.

The result was the Terminal 5 Agreement, a legally binding contract built on three principles:

1. Client Accepts All Risk

Rather than trying to transfer risk to contractors — which, as one industry expert noted, simply drives disputes into court — BAA accepted that it carried all construction risk. This was backed by a project-wide insurance policy.

Trying to transfer risk is fraught with difficulties. Designing a contract that allows one party to win over another just gets you into court.

2. Partnering Over Adversarial Contracting

The agreement moved away from traditional client-contractor adversarial relationships toward a collaborative model. All parties worked as a unified delivery team rather than as opposing interests protecting their own positions.

3. Incentive-Based Performance

A project incentive fund balanced successes and failures across individual contractors. Contractors were rewarded for completing work on time and within budget, creating alignment between individual contractor performance and overall project success.

The Result

Terminal 5 was delivered without the catastrophic overruns that plagued comparable projects. The key success factors, according to industry analysis:

BAA appears to invest strongly in a lot of expertise in order to manage and be heavily involved in each of the individual subprojects. They constructed a good partnership model, but this is underpinned by their great involvement and continuing ownership of the project.

Knowledge Check 1

Consider the Terminal 5 approach through the lens of PMBOK Knowledge Areas:

• Which knowledge area is most relevant to the decision to accept all risk rather than transfer it? (Risk Management)
• Which knowledge area governs the decision to use a partnering model rather than a fixed-price contract? (Procurement Management)
• Which knowledge area is served by BAA's investment in in-house PM expertise? (Human Resource Management)
• How does the project incentive fund relate to Stakeholder Management?

---

Case Study 2: The 2012 London Olympics — When Time is Absolutely Fixed

The Challenge

The 2012 Olympics presented a project management challenge that most projects never face: an immovable deadline. The opening ceremony date was non-negotiable. There was no possibility of delay, no schedule compression option, no "we'll finish next quarter."

The scale was staggering. Since London won the bid, the estimated cost had escalated from an initial £2.4 billion (~$4.9B) to £9.35 billion (~$19.09B). The construction budget alone stood at £5.3 billion, backed by a £2.7 billion contingency fund.

The Framework Applied

In most projects, a project manager can trade off between the three constraints — budget, time, and specification. If budget is tight, you can extend the timeline. If the timeline is compressed, you can reduce scope.

For the Olympics, time was absolutely fixed. This meant the Olympic Delivery Authority (ODA) needed maximum flexibility on the other two constraints and had to scrutinise the project far more rigorously than a typical construction program.

Triple Constraint

⏰ TIME — FIXED — Drop-dead date

💰 BUDGET — FLEXIBLE — £5.3B + £2.7B contingency

📐 SPECIFICATION — FLEXIBLE — Scope can be adjusted

Relationship details

From	Relationship	To
Triple Constraint	leads to	⏰ TIME — FIXED — Drop-dead date
Triple Constraint	leads to	💰 BUDGET — FLEXIBLE — £5.3B + £2.7B contingency
Triple Constraint	leads to	📐 SPECIFICATION — FLEXIBLE — Scope can be adjusted

The ODA's procurement strategy drew directly from the Terminal 5 lessons:

• Partnering contracts were favoured over adversarial fixed-price agreements
• Defined levels of retained risk with triggers for reward at defined performance levels
• The 2012 Construction Commitments charter (drafted by the Strategic Forum for Construction) provided a framework for good practice

The Lessons

Knowledge Check 2

Consider the Olympics through the lens of PRINCE2 governance:

• How would a Project Board handle the fixed-deadline constraint? Which PRINCE2 concept would be most useful for maintaining control? (Tolerances — with time tolerance set to zero, all flexibility must be allocated to cost and scope tolerances)
• Why would management stages be particularly valuable for a project of this scale and risk?
• How would the Business Case be updated at each stage boundary given the escalating costs?

---

Case Study 3: Upstream Oil & Gas — When Data is Scattered and Risk is Underground

The Challenge

A 2004–2005 study by Welcom (a project management software company) and Profit Solutions (a consulting firm) examined project control practices in the upstream oil and gas sector. The findings revealed systemic weaknesses in how the industry managed schedule, cost, and risk.

The fundamental problem: risks are thousands of feet below the surface, and project data is scattered across multiple systems, sometimes in multiple geographic locations.

Key Findings

Schedule Management: Producers prioritise maintaining the schedule because the net present value of an upstream project is more sensitive to schedule delays than to cost increases (up to a point). Most respondents believed existing scheduling tools were adequate — the gap was in processes, not software.

Risk Management: While schedule maintenance was well understood, actual risk identification and management (as opposed to simply adding contingency) was underdeveloped. A qualitative risk tool could significantly improve schedule adherence.

Cost Management — The Earned Value Gap: Few organisations were using software to forecast project success during the project. Accounting systems captured expenditures after the fact, but a time-phased approach — what the industry calls Earned Value — was missing.

Earned Value helps you evaluate and control risk by measuring progress in monetary terms, answering questions like: "I'm under budget, but am I on schedule? My schedule is on target, but will I make a profit?"

Change Management: The single biggest problem for engineering firms. Designs are often only 60–70% complete when construction starts. Managing changes across the owner-engineer-fabricator partnership — using tools ranging from paper forms to phone calls to emails — was chaotic and expensive.

Data Collaboration: Most respondents maintained good project data. The problem was that data was stored in disconnected systems across different locations. Additionally, the "graying" of the workforce meant institutional knowledge was leaving with retiring employees — stored in filing cabinets rather than accessible databases.

The Framework Applied

The study's recommendations map directly to PMBOK knowledge areas:

Knowledge Check 3

• Why is schedule delay more damaging than cost increase in upstream oil and gas? (Think about the net present value of the product stream — every day of delay is a day of lost revenue.)
• How does the Pareto Principle apply to the finding that designs are only 60–70% complete when construction starts?
• What Sarbanes-Oxley (SOX) compliance benefit does Earned Value software provide that spreadsheets cannot? (Security logging of scope changes.)

---

Case Study 4: Front-End Project Controls — Where the Money is Really Won or Lost

The Challenge

Projects rarely run exactly according to plan. Changes are inevitable, and they typically translate into more time and more money. The later a change enters the project, the more expensive it becomes.

The construction industry has recognised this problem for decades — and has largely failed to solve it. The root cause is predictable: poor quality bid documents produced during the design phase.

The Framework Applied: The Pareto Window

The ability to influence final project cost decreases over the project life. Applying Pareto's Principle:

Approximately 80% of project costs are established in the first 20% of the project life.

$$\text{Cost Influence} \propto \frac{1}{\text{Project Timeline Progress}}$$

This means that front-end project controls during design offer the greatest leverage for controlling final cost. By the time you reach construction, most costs are locked in.

Qualitative relationship reconstructed as native HTML.

Relationship	Concept	Detailed engineering	Procurement	Construction	Start-up
Ability to influence final cost	100%	80%	45%	15%	5%
Cumulative expenditure	5%	15%	40%	85%	100%

The Mechanism: Document Quality Drives Cost Outcomes

The chain of causation is straightforward:

Low quality bid documents

Large numbers of RFIs

RFIs become change orders

Change orders add cost — at a premium over — original contract pricing

Project overruns and delays

Relationship details

From	Relationship	To
Low quality bid documents	leads to	Large numbers of RFIs
Large numbers of RFIs	leads to	RFIs become change orders
RFIs become change orders	leads to	Change orders add cost — at a premium over — original contract pricing
Change orders add cost — at a premium over — original contract pricing	leads to	Project overruns and delays

Changes after construction contract award can cost 50% or more above the price of the same scope of work if included in the original bid documents.

The Solution: Design Review Milestones

The authors propose establishing deliverable criteria for each design review milestone:

At each review point, the deliverable criteria must be:

• Quantifiable — the reviewer can match what is in the criteria with what is in the document
• Contractual — tied to the design contract language and payment milestones
• Enforceable — with consequences for non-compliance

The Types of Changes That Can Be Controlled

Not all changes are controllable. Scope changes are discretionary decisions by the client. But the following change types can be controlled or mitigated by producing complete bid documents:

• Varying site conditions — differences between actual conditions and what was shown in bid documents
• Errors and omissions — mistakes in design documents discovered after issue-for-bid
• Clarifications — ambiguities that require designer interpretation during construction

Key Distinction: Scope changes are adds or deletions to the original work. They are not clarifications, errors, omissions, or varying site conditions. Confusing these categories obscures the true cost of poor document quality.

Knowledge Check 4

• If a change order costs 50% more than the same work included in the original bid, what is the cost multiplier? (1.5x — or a 50% premium.)
• A project has $10M in change orders that could have been avoided with better design documents. At a 50$10M - $6.67M = $3.33M in avoidable premium, or equivalently, the work would have cost ~$6.67M if included in original documents.)_
• Which PMBOK process group is most relevant to design review milestones? (Planning — and specifically, Monitoring & Controlling as applied during the design phase.)

---

Synthesis: Connecting Theory to Practice

These four cases reinforce the same foundational lessons:

---

Key Takeaways

• Heathrow Terminal 5 demonstrated that accepting risk, partnering with contractors, and investing in client-side expertise can prevent the overruns that plague mega-projects.
• The 2012 Olympics showed that when one constraint is fixed (time), the PM must maximise flexibility on the others (cost and scope) and apply intense scrutiny throughout.
• Upstream oil and gas revealed that schedule sensitivity, inadequate risk tools, missing EV capability, and scattered data are systemic problems requiring process and technology solutions.
• Front-end project controls offer the highest-leverage opportunity to prevent cost overruns — investing in design document quality pays for itself many times over in reduced change orders.
• The Pareto Principle — 80% of costs established in the first 20% of the project — is the single most important insight for any project manager focused on cost control.