7 Real-World Scope Creep Examples (and What They Cost)

Scope creep is easy to define and hard to see coming. These aren't hypothetical scenarios — they're documented cases where scope expansion turned manageable projects into financial disasters.

1. The FBI's Virtual Case File — $170 Million Lost

Between 2001 and 2005, the FBI attempted to build a case management system called the Virtual Case File (VCF). The original scope was a straightforward upgrade to their ageing Automated Case Support (ACS) system.

What happened: Stakeholders continuously added requirements after development started. Agents in the field wanted features the system wasn't designed for. Security requirements escalated after 9/11. The contractor (SAIC) accepted change after change without resetting the timeline or budget.

The result: The project was abandoned in 2005 after spending $170 million with nothing usable to show for it. The Government Accountability Office (GAO) later cited uncontrolled scope expansion as a primary cause of failure.

The lesson: When every stakeholder can add requirements without a change control gate, no amount of budget saves the project. The FBI eventually succeeded with its replacement (Sentinel) by adopting Agile with strict scope governance per sprint.

Source: GAO Report GAO-06-1049T, "FBI Faces Challenges in Developing Sentinel"

2. Denver International Airport Baggage System — $311 Million Over Budget

Denver International Airport's automated baggage handling system was supposed to be a competitive advantage — bags routed automatically between all three terminals. The original contract with BAE Automated Systems was scoped for a single terminal.

What happened: The airport authority expanded the scope to cover all three terminals and all airlines mid-project. The mechanical complexity exploded. United Airlines, the anchor tenant, kept requesting modifications. Integration requirements with legacy airline systems weren't in the original design.

The result: The airport opening was delayed by 16 months. The system cost $311 million over the original budget. It never worked reliably across all terminals and was eventually dismantled in 2005 in favour of a conventional belt system.

The lesson: Scope expansion that changes the fundamental architecture of a system isn't "creep" — it's a different project. The original contract should have been renegotiated, not stretched.

Source: Calleam Consulting case study; GAO Airport Infrastructure reports

3. HealthCare.gov Launch — $1.7 Billion

The initial budget for the Affordable Care Act's federal health insurance marketplace was approximately $93 million. By launch day (October 2013), the cost had ballooned to an estimated $1.7 billion.

What happened: 55 contractors worked on different parts of the system with no single integrator. Requirements changed repeatedly as policy decisions were made. States that originally planned their own exchanges opted into the federal system, expanding load requirements. CMS (Centers for Medicare & Medicaid Services) added features late in the cycle — notably, the requirement for users to create accounts before browsing plans was added 3 months before launch.

The result: The site crashed on day one, handling only 6 of a targeted 50,000 concurrent users. It took 2 months of emergency remediation to reach basic functionality.

The lesson: Scope creep from policy changes is especially dangerous because it feels non-negotiable. The technically correct response — "this change adds 6 weeks and $X" — gets overruled by political timelines.

Source: HHS Office of Inspector General report OEI-06-14-00350; GAO-14-694

4. The Sydney Opera House — 1,357% Over Budget

Designed by Jørn Utzon, the Sydney Opera House was originally estimated at A$7 million with a 4-year construction timeline (1959–1963). It was completed in 1973 at a cost of A$102 million — a 1,357% overrun.

What happened: The iconic shell roof design was approved before engineers confirmed it could be built. Structural requirements forced a complete redesign of the roof geometry mid-construction. Interior specifications changed repeatedly as the performing arts community weighed in. The NSW government changed political hands, bringing new priorities.

The result: Utzon resigned in 1966 after clashing with the new government over scope and budget. The interior was completed by a different architect. The final building is architecturally celebrated but operationally compromised — the main concert hall's acoustics required a $152 million renovation in 2020.

The lesson: Starting construction before the design is complete is the most expensive form of scope creep. In software terms: building features before requirements are final.

Source: NSW Government Parliamentary Archives; Flyvbjerg, B. (2014) "What You Should Know About Megaprojects"

5. NHS National Programme for IT — £12.7 Billion Abandoned

The UK's National Health Service launched the National Programme for IT (NPfIT) in 2002 to create a single electronic health record system across England. Budget: £6.2 billion over 10 years.

What happened: Different NHS trusts had different requirements that couldn't be standardised. Clinicians resisted the system because it didn't match their workflows. Contractors (including Accenture, who walked away from a £2 billion contract in 2006) were asked to deliver a system that kept expanding in scope. The programme tried to serve 30,000+ GP practices and 300+ hospitals with a single architecture.

The result: Officially dismantled in 2011 after spending an estimated £12.7 billion. The Major Projects Authority review found that "scope was not adequately controlled" and that "requirements were not stable."

The lesson: In professional services, the equivalent is taking on a "platform" engagement where every department wants different things. Without a scope freeze and modular delivery, the requirement surface area grows faster than the team can build.

Source: House of Commons Public Accounts Committee, "The National Programme for IT in the NHS: an update on the delivery of detailed care records systems," HC 1070, 2011

6. Construction Scope Creep — The Industry Average

Individual examples are dramatic, but the systemic data is just as telling.

Arcadis's 2022 Global Construction Disputes Report found:

Average construction dispute value: $52.6 million (up from $46.8M in 2021)
#2 cause of disputes worldwide: "Failure to properly administer the contract"
#3 cause: "Errors and/or omissions in the contract document"

Both of these are scope creep by another name — work done beyond what the contract specified, or contracts that didn't specify enough.

McKinsey's 2016 analysis of large construction projects found that 98% of megaprojects experience cost overruns of more than 30%, with scope changes cited as a leading contributor. The average large project was delivered 80% over budget.

In professional services, projects are smaller but the pattern is identical. KPMG's 2019 Global Construction Survey concluded that scope creep was present in 69% of projects they reviewed.

The lesson: Scope creep isn't an outlier — it's the default outcome when scope governance is absent.

Sources: Arcadis Global Construction Disputes Report 2022; McKinsey Global Institute, "Reinventing Construction," 2016; KPMG Global Construction Survey 2019

7. Everyday Consulting Scope Creep — The Invisible Kind

The examples above are spectacular failures. But most scope creep is invisible — it's the 3 extra hours per person per week that nobody tracks.

Consider a typical scenario: A 10-person consulting team on a 6-month fixed-price engagement at £150/hr. The SOW covers 8,000 hours of work.

What actually happens:

Week 3: Client asks for "a few extra reports" during a status call. PM says yes — it's 4 hours of work, not worth a change order.
Week 8: Design review surfaces "one more integration" that wasn't in scope. Dev lead absorbs it because pushing back feels awkward.
Week 14: UAT reveals that the client expected a feature that was ambiguously worded in the SOW. Team builds it to maintain the relationship.
Week 20: Client requests "final tweaks" that are actually new requirements. PM is too deep into the project to push back now.

The cumulative impact:

3 additional hours per person per week × 10 people × 26 weeks = 780 extra hours
At £150/hr = £117,000 of delivered work that was never invoiced
On an 8,000-hour engagement, that's 9.75% of total project value — gone

Multiply that across 5 projects a year and you're looking at over half a million pounds in lost revenue annually. For a single 10-person team.

The lesson: You don't need a £12.7 billion programme collapse to have a scope creep problem. The everyday kind — the "quick asks" absorbed to keep the client happy — is where most professional services firms lose money.

What These Examples Have in Common

Every case above shares the same root causes:

Scope was defined too loosely — ambiguous contracts invite expansion
Changes weren't priced — work was absorbed instead of formalised as change orders
Nobody was watching — scope compliance was manual, intermittent, or non-existent
The cost was invisible — by the time anyone noticed, the money was already spent

The fix isn't saying no to change. It's making change visible, priced, and deliberate. Whether that's a change control clause in your SOW, a weekly scope review, or automated comparison of work against contracted scope — the common thread is awareness.

Overscope monitors your delivery data against your SOW in real-time, flagging scope drift before it becomes a budget problem. See how it works →