TL;DR: A contract variation changes the value of the job it’s attached to. If your fee is a percentage of the contract sum, or claimed in stages against it, that fee should move too, but on a live project, it often doesn’t. This post covers how percentage fees are meant to track contract variations, why the tracking usually breaks down in practice, and what planning consultants working through framework call-off orders need to watch for instead.
Imagine a job billed as a percentage of the contract sum, claimed in stages as the work progresses. Three months in, a contract variation lands: extra structural work, a revised layout, a planning condition that sends part of the design back to the drawing board. Someone logs it, usually in its own spreadsheet, separate from the last one and the one before that.
Nobody goes back to check whether the fee needs to be recalculated, or whether the next-stage claim is still working off the right number. That is where fee income disappears. It’s not because the client refuses to pay for extra work, but because nobody can clearly say what’s already been claimed against the original contract sum and what’s changed since.
It shows up differently depending on how you’re appointed. Architects and engineers usually feel it through a moving percentage fee. Planning consultants feel it through a variation to a framework or call-off order. Either way, the fix starts with treating a variation as something you track from the day it’s instructed, not something you reconcile at the end.
What Is a Contract Variation, and What Counts as One?
A variation is any instructed change to scope, contract sum or programme that sits outside what you originally agreed: a formal construction variation instructed by the Contract Administrator, or a change to a call-off order under a framework appointment. The label differs. The test doesn’t: is this work outside your original fee?
Under most standard forms, a variation covers three things: an addition, an omission, or a substitution to the agreed works. Designing Buildings Wiki is blunt about the authority question: no power to instruct a variation is ever implied. Someone, usually the Architect or Contract Administrator, has to hold that authority explicitly under the contract.
That matters because disputes tend to start here, not at valuation. Pinsent Masons points out that variation clauses exist precisely because contracts are meant to be certain, and a change made informally, by the wrong person, or without proper record, undermines that certainty for everyone on the job.
How Percentage Fees Are Meant to Track the Contract Sum
A percentage fee is worked out against the construction cost agreed at the outset, then claimed in instalments as the job progresses, often loosely aligned to project stages. Most practices tolerate around 10% movement in that construction cost before the fee itself needs renegotiating. Beyond that, it’s a conversation, not an assumption.
RIBA’s own guidance sets out a typical split: roughly 35% of the fee across the early stages through planning, 35% at technical design, and the remaining 30% from construction to handover. Some practices bill closer to that pattern; others front-load a larger share upfront and claim the balance less whatever’s already been invoiced. Either way, every claim after a variation is only correct if it’s calculated against the current contract sum, not the one from the appointment letter.
The 10% tolerance is the detail worth remembering. It’s not a hard rule, but it’s roughly the point at which “we’ll absorb this” stops being reasonable and “we need to talk about fee” starts. Nobody hits that point on purpose. Most practices cross it by accident, one small variation at a time.
Why Contract Variation Tracking Falls Behind in Practice
We see this most clearly with practices billing a percentage of contract sum in stages, sometimes a chunk upfront, then further claims less whatever’s already been paid. One practice we spoke to recently had a fee structure close to that, plus a handful of jobs blending a fixed element, a flat planning fee, with a percentage on top.
Every time a variation landed, it got logged in its own spreadsheet. Nobody was cutting corners. The work was properly recorded. It just wasn’t recorded anywhere that showed the whole picture: how much had actually been billed against the current contract sum, versus what the original agreement covered.
That’s the pattern behind most of this kind of fee leakage. Not a client dispute, not dishonesty, just no running total. Small variations accumulate quietly, and by the time anyone adds them up, at final account or when a client queries an invoice, the practice has usually crossed its own renegotiation threshold weeks earlier without noticing.
The wider research backs this up. A 2025 review of over 400 construction cost-overrun studies found scope changes and variation management failures among the most consistent drivers of budgets running away, not isolated bad luck. It’s the same failure mode we’ve written about in how scope creep erodes fee income, just sharper here, because the fee itself, not only the hours behind it, is meant to move with the job.
Planning Consultants: Variations to a Call-off or Framework Order
Planning consultants working within public sector frameworks don’t have a construction contract sum to track, but the same issue manifests differently. Scope changes get issued as a variation to the call-off or project order, and unless it’s logged against your original fee, it’s easy to deliver the extra work without ever billing for it separately.
Frameworks like the Planning Consultancy Framework appoint consultants through a call-off process, often on a schedule of rates rather than a single fixed sum. When the scope of a call-off changes, the paperwork varies by framework and by client; one might call it a Project Order Variation, another might just call it a variation to the order. Whatever the label, it sits outside the original agreement, and it needs its own line, not a mental note.
For planning consultancies juggling several live frameworks at once, that’s the real risk: not one missed variation, but a handful of small ones spread across different clients, each easy to justify skipping on its own.
What Properly Tracking a Variation Actually Looks Like
Properly tracking a variation means logging the instruction (date, source and value) against your original fee the moment it’s issued, recalculating the next stage claim off the new total straight away, and checking cumulative changes against your renegotiation threshold as you go, not only at final account.
None of that requires new habits so much as a different starting point. The instruction gets logged where the job’s other numbers already live, not in a new spreadsheet named after the variation. The next invoice pulls from the current total, not the original one. Someone, at a glance, can see where cumulative change sits against the 10% mark before it becomes a problem.
Building This Into Your Systems Instead of a Spreadsheet Per Variation
A better spreadsheet template isn’t the fix. The fix is having variations logged against the job in the same system that calculates the fee and tracks work in progress (WIP), so the running total and the next claim are correct without anyone reconciling sheets by hand.
That’s what real-time WIP reporting against the contract sum is for: not a monthly catch-up exercise, but a live view that already reflects every instructed change. In WorkflowMax, a variation is logged against the job’s budget on the day it’s instructed, the contract sum updates, and the next claim is calculated based on the correct number automatically.
It won’t stop clients issuing variations. It just means you’re not the one who has to remember, six months later, which spreadsheet has the answer.
Don’t Wait Until Final Account to Find Out
The money in a contract variation is earned the moment it’s properly instructed. What’s usually lost isn’t the client’s willingness to pay; it’s the reconciliation: knowing what’s already been claimed, what’s changed since then, and whether your fee has quietly fallen behind the job it’s supposed to track.
If you want to see where your own variation and fee-tracking process actually breaks down, our App Fit Sprint is built for exactly that: a short, structured look at your current systems before we recommend changing anything.
