Why this is an operational problem, not a legal one

When businesses lose money on variations, the instinct is often to blame the contract. Tighten the clause, get more signatures, or negotiate harder. Sometimes that is necessary, but more often it misses where the money is actually being lost.

The expensive variations are often not the disputed ones. They are the agreed changes that never make it onto an invoice.

A stronger contract clause does little to solve this because the failure happens much earlier. The client may have agreed to the work and been willing to pay. The breakdown happens between agreeing the variation and properly recording, pricing and invoicing it.

It usually comes down to two things: there is no simple process to capture a variation when it happens, and no single person owns making sure it has been recorded.

What good looks like

• A lightweight variation register that is updated on the day, not at month-end.

• A clear owner responsible for confirming every agreed change has been logged and priced.

• A weekly review of open variations to move them toward invoicing.

The further you get from the event, the more detail is lost and the harder the conversation becomes.

Margin on a project is managed while the work is happening, not reconstructed afterwards. Variations are one of the clearest examples. Protect them at the point they occur and the contract rarely needs to do the heavy lifting.