Variation Recovery: Why Most Contractors Leave Money on the Table

The Money Is There. The Process Is Not.

Let me be clear about what I mean by "leaving money on the table." I am not talking about speculative claims or inflated variations. I am talking about legitimate extra work that the contractor is contractually entitled to recover but does not, because the process of notifying, substantiating, and following through is too difficult to sustain alongside the operational demands of construction.

On a typical $50M project under NZS 3910, there might be 40 to 80 variations over the life of the contract. Each one requires a notice, a pricing submission, an assessment by the Engineer, and inclusion in a payment claim. Each one has contractual timeframes. Each one generates correspondence. Each one needs to be tracked from the moment the event occurs until the money is in the bank.

The problem is not that contractors do not deserve the money. The problem is that the administrative machinery required to recover it properly is in direct competition with the work of actually building the project.

The Three Ways Contractors Lose Variation Entitlements

1. Missing the notice window

Under NZS 3910, Clause 13.3.1 requires the contractor to give notice of a potential claim "as soon as practicable." In the standard form, this is a soft obligation. But Special Conditions frequently amend it to a hard time bar of 10 working days. Miss that window and the entitlement is extinguished. It does not matter that the work was done. It does not matter that the cost was incurred. If the notice was not given within the contractual timeframe, the right to claim is gone.

On a busy site, 10 working days passes quickly. The site manager is dealing with three subcontractors, a concrete pour, and a safety audit. The variation event happens on a Monday. By the time someone gets around to writing the notice, it is day 12. The entitlement is lost. Not because the contractor was negligent, but because nobody had a system that flagged the clock was running.

2. Failing to substantiate

Even when the notice is given on time, the variation claim often fails at the substantiation stage. The Engineer's assessment under Clause 9.8.3 depends on the contractor providing sufficient detail to support both the entitlement (why the work is a variation) and the quantum (what it costs). Contractors routinely submit thin claims. A one-paragraph description and a lump sum figure. The Engineer assesses it conservatively. The contractor accepts the reduced amount because fighting it requires more paperwork, more time, and more energy than they have available.

The irony is that the contractor usually has the information needed to substantiate properly. The daily site records, the subcontractor invoices, the programme impact analysis. It exists in various places across the project. But compiling it into a coherent claim package takes hours that the project team does not have.

3. Letting items lapse

This is the quiet killer. A variation is identified. A notice is issued. A preliminary pricing is submitted. Then it sits. Nobody follows up. The Engineer does not respond within 10 working days as required under Clause 9.8.3. The contractor does not chase it because they have 15 other items that need attention. Months later, when someone reviews the variation register, there are a dozen items that were notified but never assessed. They are technically still alive but practically dead because the contemporaneous records are no longer fresh, the subcontractor who did the work has moved to another project, and the commercial context has shifted.

Most variation under-recovery is not caused by a single failure. It is caused by dozens of small administrative lapses that individually seem minor but collectively represent hundreds of thousands of dollars in legitimate entitlements that are never claimed.

Why the Current Approach Fails

The standard approach to variation management on most construction projects looks like this: a spreadsheet maintained by the QS or commercial manager, updated when they get around to it, reviewed at the monthly commercial meeting. The site team knows about variation events but does not always communicate them to the commercial team in time. The commercial team tracks variations they know about but does not have visibility of events happening on site in real time.

The gap between the site and the commercial function is where money disappears. A site instruction that triggers a variation is issued verbally on site. The site manager notes it in the daily diary. But nobody tells the commercial manager that a clock is now running on a notice period. By the time it surfaces, the window has closed.

This is not a people problem. It is a systems problem. The people on site are busy building. The people in the commercial team are busy managing claims, subcontract administration, and cash flow. Nobody has bandwidth to run a real-time variation surveillance system using spreadsheets and email.

What Good Variation Recovery Looks Like

Contractors who recover well on variations share common characteristics. They are not more aggressive in their claims. They are more disciplined in their processes.

• Variation events are captured at the point they occur. When a site instruction is issued, when an unforeseen condition is encountered, when a design change is received, the event is logged immediately with a date stamp. The notice clock starts visibly.
• Notices are automated. The system generates draft notices with the relevant contractual references and sends them for review. The commercial manager approves and issues. No notice is missed because nobody forgot.
• Substantiation packages are built continuously. Daily records, photographs, subcontractor time sheets, and programme impact analyses are linked to each variation event as they are created. When the pricing submission is due, the supporting evidence is already compiled.
• Follow-up is systematic. Every variation has a status. Notified, priced, assessed, approved, claimed, paid. If the Engineer does not respond within Clause 9.8.3 timeframes, the system flags it. Nothing lapses because nobody was watching.

The contractors who recover best are not the ones who fight hardest. They are the ones who build systems that ensure every legitimate entitlement is noticed on time, substantiated properly, and pursued to conclusion.

Both Sides Benefit from Better Administration

Good variation administration is not adversarial. When the contractor substantiates properly and the Engineer assesses fairly, variations are resolved quickly. The project stays on track commercially. The relationship between the parties remains intact. Nobody is surprised at final account.

The problems start when variations are poorly documented, assessed under time pressure with insufficient information, and then disputed months later when the money matters more. That is how construction claims escalate into disputes. Not because anyone acted in bad faith, but because the administration was not good enough to resolve the issue when it was small.

Principals and PMCs benefit from contractors who claim properly, too. A well-substantiated variation claim is easier to assess. It reduces the risk of large retrospective claims at final account. It means the principal's financial reporting is accurate because the cost of variations is captured in real time rather than discovered later.