How to stop missing variation revenue on construction projects
From site request to progress claim – how to keep variations visible, approved and claimable.
Ask any project manager how a variation slips through and you’ll usually get a response like: “The client agreed to it on site, we just never got around to writing it up.”
That sentence is more expensive than it sounds.
Here’s how it usually plays out. A client asks for something extra. A drawing changes. A subbie is told to press on regardless. Someone makes a mental note to formalise it later and later has a habit of never arriving. Two weeks on, the work is finished, the materials are paid for, the labour hours are logged – and the only record of the whole thing is a text message buried in a group chat.
By that point the cost is already locked into the job, whether anyone claims for it or not. The only open question is whether the revenue follows it in. Too often, it doesn’t.
This is where construction teams quietly give away margin – not through bad pricing or slow labour, but through variations that were real, completed and simply never made it onto an invoice.
The gap between doing the work and getting paid for it
Nobody sets out to lose variations. It happens because the people who see the change first are rarely the ones responsible for getting it paid.
Site crews spot the change in real time, but they’re focused on finishing the job, not on payment schedules. Project managers are stretched across labour, materials, subbies and a client who wants updates yesterday. Accounts only ever see what’s already made it into the system. By the time an invoice needs writing, three people are working from three different memories of what actually happened.
The result is a business doing more work than it’s billing for, and often not realising it until margins come in thinner than expected.
It shows up as a verbal yes that never got written down, a site photo that never made it into the job file, a cost sitting in the budget with no matching line in the claim. None of that looks like much on a single job. However, multiply it across a dozen live projects and you’re looking at a genuine chunk of margin that quietly evaporated somewhere between site and invoice.
Why the old way falls apart
The usual sequence goes something like this: the change happens on site, someone fires off a message, the PM starts a spreadsheet line, the client gives a verbal yes and the job carries on. The variation gets checked later. The budget gets updated later. The claim gets built later – assuming anyone remembers it exists.
The problem here isn’t that the process is manual. It’s that every “later” is another chance for that variation to quietly fall out of the workflow altogether.
If an approved variation never reaches the payment schedule, there’s a strong chance it never reaches the claim either. Nexvia’s budget check process helps prevent this pattern by prompting teams to check whether approved variations have been sent through to the payment schedule, instead of leaving variation approval until the end of the job.
Which gets at the real point here: variation control isn’t paperwork for its own sake. It’s how a business keeps hold of revenue it’s already earned.
The fix: connect the dots from site to claim
1. Capture it at the source
The best moment to record a variation is the moment it happens – not Friday afternoon, not claim week and definitely not when someone’s chasing an overdue invoice and suddenly remembers there was extra work involved.
Site teams just need something simple: what changed, what’s required, the quantity, the price and a photo or two while the details are still fresh.
A photo and an itemised note do more work than they look like they should. They turn a vague “yeah, we did some extra stuff on Tuesday” into something a business can actually review, approve and defend at invoice time.
2. Keep the budget honest
Once the work is captured, the numbers behind it need to keep pace.
This is where a lot of businesses quietly lose out: a project can look perfectly healthy on paper simply because the original estimate hasn’t been touched, while actual costs, committed spend, labour hours and approved variations are all shifting underneath it.
Regular budget checks help keep current figures reflected in the project summary and reports, so the team is working off a current picture rather than an outdated one.
A claim is genuinely only as reliable as the data sitting behind it. Before a claim goes out, someone should be running the numbers on the budget, POs, bills, hours, stock, variations, running sale and margin together, not piecemeal.
3. Get approved variations onto the payment schedule
Getting a nod of approval isn’t the same as being claim-ready.
In Nexvia, a variation becomes claim-ready once it has been sent through to the payment schedule – that’s the bridge between the work getting done and the business getting paid for it.
Sit outside that bridge and there’s a real chance it gets overlooked when the claim is put together.
This is why variation management has to be part of the day-to-day rhythm of a job, not a clean-up task left for the end. The sooner an approved variation reaches the payment schedule, the sooner it can be included in the claim – while the work is still fresh, still visible and still easy to justify if anyone asks questions about it later.
4. Build claims from data that’s actually current
Completion percentage is a starting point, not the full picture.
Materials might already be sitting on site. Labour might have gone in earlier than planned. Approved variations may have shifted the contract value considerably. Deductions and retention still need to be accounted for – and none of that shows up in a tidy “60% complete” figure.
Nexvia’s Client Progress Claims workflow pulls budget data into the claim and checks it against the project’s running sale. If the Total Budget Ex figure doesn’t match the current Running Sale price from the last budget check, Nexvia flags the mismatch so the team can fix it before the claim goes out, rather than after.
That keeps claims grounded in current numbers and gives PMs and accounts a shared view of what’s being claimed, what’s changed and what still needs a second look.
5. Bring the whole commercial picture into the claim
The final stage is making sure the claim reflects the full commercial position, not just the base contract.
Approved variations and deductions need to flow into the progress claim itself. In Nexvia, only variations and deductions already sent to the payment schedule are available for import, and once they’re pulled in, the claim refreshes so the team can claim against them directly.
Retention travels alongside this same workflow. Where retention is being held, Nexvia calculates or manages it depending on the claim mode in use, with those values flowing through to the Retention Claim tab as claims are accepted – helping teams keep track of releases at milestones like practical completion and defect liability.
The outcome is a clean, traceable line running from current project data through to claim, payment schedule and invoice.
What this actually looks like in Nexvia
In Nexvia, the variation journey stays connected from start to finish.
Site teams capture the change as it happens. The project team checks the budget, reviews actuals and makes sure approved variations are moving through the right channel instead of sitting in someone’s inbox.
When claim time rolls around, the team pulls in budget data, adds variations and deductions, handles retention and sends the accepted claim to the payment schedule for invoicing.
Once a claim is accepted in Nexvia, it locks in place, a claim log sits there for reference and an entry is created in the project’s payment schedule so accounts can generate the invoice without chasing anyone down for details.
That’s the real difference: managing revenue while the job is still live, rather than reconstructing it afterwards from memory and guesswork.
Two contractors, the same leak in different places
Barrett Group, an Australia-wide retail and commercial fitout business, had the variation problem in its clearest form. As the company grew into a fast-moving national operator, jobs started outrunning the systems tracking them – critical job information sat buried in an old system nobody wanted to navigate, staff pieced things together in spreadsheets, and variations slipped through constantly. Purchase orders often got raised after the invoice rather than before, which is about as backwards as it sounds.
It wasn’t a competency problem. It was a timing one: by the time anyone had the full picture, the cost had already landed.
With Nexvia, Barrett Group moved from reactive project management to real-time control across office, factory and site – variations captured the moment they happen, matched straight back to the claim.
Director, Justin Barrett put it simply:
The result is 100% variation capture across every project, with real-time visibility across office, factory and site.
Simply Fire, a fire protection contractor in New Zealand, had a different flavour of the same problem. Their old system meant they were often claiming off completion percentage alone – even when material had already landed on site and the job was worth more than what was being invoiced.
General Manager, Lindsay Duffy, commented:
With quoting, budgeting, time tracking and progress claims connected in Nexvia, Simply Fire started using actuals-versus-budget reporting to claim based on the value actually sitting inside the job. They stopped under-claiming progress payments, gained live visibility across costs and labour, and saved around 15% in admin time through mobile time tracking.
Why it matters
None of this feels dramatic while it’s happening. A verbal approval that never gets typed up. A budget that’s a week out of date. A retention release nobody’s actually tracking. On any one job, it barely registers – a few hundred dollars here, a missed line item there.
Run ten jobs at once and it stops being small. It’s the difference between a job that looked fine on paper and one that actually paid what it should have.
The contractors who avoid this aren’t necessarily better at the work. They’re just not leaving any of it to memory – the variation gets written down on site, the budget gets checked before the claim goes out rather than after, and the approved amount actually makes it onto the payment schedule instead of trusting someone to remember it later.
Ready to stop missing variation revenue?
If your team is still tracking variations through spreadsheets, emails or memory, there’s a good chance claim value is slipping through the cracks right now.
Nexvia connects budgets, variations, progress claims, payment schedules and invoicing in one system – built for construction, fitout and specialty contracting teams.
Get in touch with our team to see how Nexvia can help you protect margin from site request to final claim.
get started
Contact us now for more information about our software and to arrange a free demo.
