Why Unapproved Variations Can Drain Cash Flow Before the Final Account

Unapproved variations are not just a commercial issue.

They are a cash flow issue. The work still happens, the cost still lands, and the money is still sitting in approval limbo. If the change is not captured and agreed quickly, the job carries the cost long before the income is secure.

That matters on every UK construction project, but it becomes especially painful when margin is tight and the final account is still weeks or months away.

Why unapproved variations hurt cash flow

Cash flow takes a hit when there is a gap between work done and money recognised.

That gap usually opens up when:

• the instruction comes by phone, WhatsApp, or site conversation and is never logged
• the commercial team does not see the change until work is already underway
• the cost is committed before the variation value is agreed
• the final account relies on memory instead of a clean approval trail

Once that happens, the business starts carrying the cost. Even if the variation is eventually approved, the delay can create pressure on wages, subcontractor payments, supplier terms, and month-end forecasting.

The tighter the margin, the more expensive that delay becomes.

The warning signs to watch for

You do not need a complicated system to spot a variation problem early. A few repeating signals are enough.

Look out for:

• site teams asking, "Can we sort the paperwork later?"
• repeated comments like "the client knows about it" without a written instruction
• commercial managers seeing variation paperwork for the first time at the end of the month
• work being completed before pricing or approval is agreed
• disputes about whether the instruction was a change or part of the original scope

If the answer to "Is it approved?" is unclear, the job is already carrying risk.

A practical variation control process

The aim is not to slow the job down. It is to make sure changes are captured fast enough to protect cash and margin.

A simple process should do four things:

1. Record the change immediately

As soon as a change is requested or instructed, capture:

• what changed
• who asked for it
• when it was requested
• which job it relates to
• whether it is priced, provisional, or awaiting instruction

This can be done from site, but it needs to land somewhere the commercial team can see.

2. Separate approved from unapproved

Do not let all changes sit in one pile.

Keep a clear split between:

• approved variations
• pending variations
• rejected variations

That helps the business understand what is real income, what is still exposure, and what needs chasing.

3. Link the cost to the change

If the team is already spending money on the variation, link that cost to the variation record early.

That gives accounts and commercial teams a better view of:

• committed cost
• expected recovery
• margin at risk
• items that need approval before payment

4. Review variations every week

A variation review should be part of the normal job rhythm, not a month-end clean-up.

Use the weekly review to ask:

• what changes were raised this week?
• which ones are still waiting on approval?
• what has been spent already?
• what needs to be chased before the month closes?

The goal is to stop variations becoming invisible debt.

How site teams and commercial teams should work together

Variation control fails when site and commercial work in separate worlds.

Site teams need a simple rule: if the scope changes, log it straight away.

Commercial teams need a second rule: if the change is not visible in the system, it does not exist for forecasting purposes.

That does not mean refusing to help the site team. It means making the process easy enough that people actually use it. If logging a variation takes too long, it will happen too late.

The best setup is one where:

• site can raise the change quickly
• commercial can review it without chasing paperwork
• approvals are visible to everyone who needs them
• the job forecast updates as soon as the variation is real

What accounts needs to see before payment

Accounts should not be left guessing whether a cost belongs to the original scope or a later change.

Before payment, they should be able to see:

• whether the variation is approved
• whether the cost sits inside the agreed scope
• whether the supporting instruction is attached
• whether the commercial team has accepted the amount
• whether there is a risk of paying costs that will not be recovered

If that information is missing, the business is paying first and asking questions later. That is how margin leaks.

What good looks like

A healthy variation process does not remove every uncertainty, but it does make the uncertainty visible.

Good looks like:

• changes are logged on the day they are identified
• approvals are tracked separately from pending items
• cost exposure is visible before invoices or subcontractor claims are paid
• site and commercial share one version of the truth
• month-end reports show realistic job margin, not optimistic margin

That is what protects cash flow. Not perfect paperwork, but timely visibility.

A simple rule for every job

If the work has changed, the job has changed.

The sooner that change is recorded, priced, and approved, the less likely it is to distort cash flow or create a fight at final account.

Conclusion

Unapproved variations are dangerous because they look small at the point of change and expensive later on.

For UK contractors, the practical answer is simple: capture variations early, separate approved from pending work, and make sure the commercial picture updates before the cash leaves the business.

If you want fewer surprise costs and less margin leakage, the goal is not more paperwork. It is faster visibility.

Suggested internal links

• Tracking Spend Is Not the Same as Controlling Spend
• How to Run a Weekly Committed Cost Review on Live Jobs
• What a Clean Subcontractor Invoice Workflow Looks Like

Suggested call to action

If you want fewer surprise costs and less cash tied up in disputes, use BuilderDash to log variations early, keep approvals visible, and see the margin impact before the final account turns into a firefight.