The Hidden Cost of Missed Variations

The Invisible Margin Leak

Industry estimates suggest 15-25% of legitimate variation entitlement goes unrecovered on typical projects. It isn't disputed or negotiated down. It's simply missed.

On a £20M project with £2M of actual variations, that's £300-500K of margin that evaporated without anyone noticing until it was too late.

This is about recovering the costs you legitimately incurred because the client changed the works, not aggressive commercial management or extracting maximum value from clients. Miss these, and you're subsidising your client's changes from your own margin.

Where Variations Get Lost

Variations don't disappear randomly. They leak through predictable gaps in the identification and recovery process.

The Instruction Gap

Verbal instruction on site. Work gets done. Nobody confirms in writing. Three months later when preparing the account, nobody remembers the instruction clearly enough to claim it. Lost.

The Recognition Gap

Site team sees additional work as "part of the job" rather than a change to scope. Foundation deeper than shown on drawings? Just deal with it. Ground conditions different than described? Crack on. Legitimate variations absorbed as contractor risk because nobody flagged them as changes.

The Notification Gap

Work identified as a variation, but notice not submitted within contract timescales. Under NEC4, the 8-week time bar means late notification results in complete loss of entitlement. The work was done. The cost was incurred. But the right to recover has expired.

The Evidence Gap

Variation identified and notified, but records don't support the claimed value. "We think it took 200 hours" doesn't compete with "allocation sheets show 187 hours deployed over these dates." Weak evidence means weak settlements.

The Submission Gap

Variations sit in "to be claimed" lists that never get actioned. Commercial teams stretched across multiple projects prioritise urgent over important. Months pass. The window for effective recovery narrows.

Quantifying the Cost

Realistic numbers for a £15M infrastructure project:

• Total variations incurred: £1.5M (10% of contract value, typical for infrastructure)
• Identified and notified: £1.2M (80%)
• Missed due to instruction gap: £150K
• Missed due to recognition gap: £100K
• Time-barred: £50K

Of the £1.2M identified:

• Fully evidenced and recovered: £900K (75%)
• Partially recovered due to evidence gaps: £200K at 60% = £120K
• Stuck in submission backlog: £100K (compromised at 40%) = £40K

Total recovered: £1.06M from £1.5M entitlement = 71%

Margin leaked: £440K

On a project with planned margin of £750K (5%), that's 59% of your profit lost to preventable variation leakage.

The Root Causes

Why does this keep happening? The causes are systemic:

Information Flow

QS sits in the office. Events happen on site. By the time information reaches the commercial team, the moment for contemporaneous recording has passed. Variations are identified retrospectively, if at all.

Commercial Awareness

Site supervisors and engineers aren't trained to think commercially. They solve problems, not identify entitlements. A changed instruction is just another day's challenge, not a variation to be captured.

System Design

Record-keeping systems don't prompt for variation identification. Daily diaries capture activities but don't ask "what changed today?" The structure of the records doesn't support the commercial process.

Workload

QS teams managing multiple projects can't review every diary entry, every instruction, every site condition. They rely on others to flag variations. When flagging doesn't happen, variations fall through.

Building Better Systems

Preventing variation leakage requires systematic changes:

Daily Variation Prompt

Every daily diary should include a specific question: "What variations or changes occurred today?" Force the consideration, capture the answer, even if it's "none." This creates the habit of thinking about changes.

Site Team Training

Supervisors need to recognise variations. Not detailed commercial knowledge, but the ability to spot when something differs from the contract, drawings, or programme. "That's different" should trigger "tell the QS."

Rapid Notification Process

Streamlined process for getting potential variations from site to commercial team within 24-48 hours. The QS can decide if it's a valid variation, but they can't make that decision about events they don't know occurred.

Weekly Variation Review

Structured weekly meeting between site and commercial to review potential variations, confirm notifications, and ensure nothing falls through gaps. Ten minutes a week prevents hundreds of thousands in leakage.

Variation Tracking

Every potential variation tracked from identification through notification, substantiation, agreement, and payment. Visibility of the pipeline prevents items stalling in queues.

Make the diary ask the question

A structured diary can prompt for the change that day. Rosie can flag entries that look like an instruction so the QS decides while the notice window is still open. Tools amplify the habit. They do not invent the instruction.

The fundamental requirement is people who recognise variations and a process that captures them the same day.

What This Means for Your Projects

Every missed variation is pure margin loss, gone forever, not just margin at risk or under negotiation.

The construction industry has accepted this leakage as normal for too long, but it's preventable. The contractors who build systems to capture their full entitlement will consistently outperform those who accept 70-80% recovery as inevitable.

Look at your current projects. Check your recovery rate and find out what's falling through the gaps.

Name the instruction that day

A missed variation is usually a verbal instruction that never made the book. Put it on the site diary the same day. Rosie reads those entries against the contract so the instruction is a notice, not a story at final account.