The Ctrl+C Epidemic: Why We Are Building 2026 Megaprojects with 1998 Specifications

If you want to understand why modern infrastructure projects hemorrhage money, don’t look at the steel prices. Don’t look at the concrete batching plants, and definitely don’t look at the politicians in high-vis jackets pointing at holes in the ground for photo ops.

Look at the Specification document. Specifically, look at page 412, sub-clause 6.3.

If you spend enough time as a Site Engineer reading through the dense, phone-book-sized Works Information documents handed down by design consultancies, you will eventually experience a profound sense of temporal displacement. You will be building a state-of-the-art, digitally modelled HS2 viaduct in 2025, but the specification will aggressively demand the use of a proprietary waterproofing membrane that went out of business during the 2008 financial crash.

Welcome to the Ctrl+C / Ctrl+V Epidemic. It is the silent killer of project budgets, and it is entirely self-inflicted.

Let’s be brutally honest: nobody writes a 600-page technical specification from scratch. That would be madness.

When a design consultancy wins a tender to design a new highway intersection, the lead engineer doesn't sit down with a blank Word document. They open the specification from their last highway project, hit "Save As", change "M1 Junction 14" to "A30 Chiverton", and call it a day.

Over a decade, this document gets passed around the office like a digital baton. It is edited, spliced, and patched by twenty different engineers. The result is a Frankenstein’s Monster of a document.

I once worked on a land-locked, midlands-based railway earthworks package where the specification included five highly detailed pages on the ecological mitigation of marine barnacles on steel sheet piles. We were 80 miles from the nearest drop of seawater. I can only assume the marine clause hitched a ride from a 2014 port expansion project and nobody had the courage to delete it.

The Fear of Deletion

Why does this happen? In a word: Liability. In the design world, deleting a clause feels infinitely more dangerous than leaving it in. “What if we need that obscure requirement for low-alkali cement? I’ll just leave it. Better safe than sued.”

This draconian fear of liability creates a blanket of over-specification. Designers routinely demand tolerances that belong in a Swiss watchmaking factory for elements buried under 10 meters of structural backfill. They will specify a 50-year design life for a temporary haul road that will be ripped up in six months.

(And let’s take a moment of silence for the Estimators. Do we really think the commercial team reads all 600 pages during the 4-week tender period? Of course not. They weigh the document, multiply its thickness by £100,000, and submit the bid. It’s a flawless scientific process.)

The Site Reality: Archaeological Procurement

While the designers are playing it safe in the office, the fallout on site is catastrophic.

When a Sub-Agent is handed a copied-and-pasted spec, they aren't reading it for fun; they are trying to procure materials. Suddenly, the site team is forced into an archaeological dig, trying to source a specific grade of timber treatment that was banned by the Environmental Agency in 2019.

When the buyer inevitably can’t find it, the site team has to propose a modern alternative. This triggers the dreaded RFI (Request for Information) Loop of Despair:

1. Contractor: "The material specified in Clause 4.1 no longer exists. Can we use [Modern Equivalent]?"

2. (Two weeks pass. The concrete pour is delayed. The site manager's hair visibly grays.)

3. Designer: "Please provide a 40-page technical submittal, independent laboratory testing, and a blood oath proving the modern equivalent is equal to the non-existent 1998 product."

We are burning hundreds of thousands of pounds in delay damages and administrative overhead, simply arguing over clauses that should never have been in the document in the first place.

Curing the Epidemic

The construction industry loves to boast about "Digital Twins," "BIM Level 3," and "AI-driven logistics." Yet the legal backbone of what we are actually building is still dictated by heavily bloated, un-audited Word documents from a bygone era.

If we want to stop bleeding money, we need to enforce Lean Specification.

1. The "Prove It" Rule: Designers should be required to mathematically or logically justify every non-standard clause they leave in a specification. If you are specifying a 2mm tolerance on a blinding layer, you better be prepared to explain exactly why the structure fails if it’s 4mm.

2. Digital Spec Linking: Specifications shouldn't be static PDFs. They should be dynamically linked to the 3D model. If a steel pile is deleted from the 3D model, the marine barnacle clause should automatically vanish from the spec.

3. Contractor Pushback: Under NEC4, contractors must aggressively interrogate the Works Information on Day One. Find the impossible clauses, raise the Early Warning Notices immediately, and force the design team to clean up their digital mess before the excavators arrive.

Conclusion

The next time you hear a politician complaining that a major infrastructure project is over budget and delayed, remember the marine barnacles.

Civil engineering is a brilliant, highly technical profession. We know how to build the future. We just need to stop copy-pasting our instructions from the past.