Handling Variations on Lump-Sum and LSTK Contracts Without Eroding Your Margin

A lump-sum contract promises certainty: one price for a defined scope. The problem is that the scope is never as defined as the drawings suggest, and every ambiguity is an argument waiting to happen. On lump-sum turnkey and EPC work the contractor carries design, quantity, and interface risk, so the natural gravity of the job pulls extra work into your account without extra money. Variations are still recoverable - but the margin between recovering them and absorbing them is pure discipline.

Why Lump-Sum and LSTK Shift Scope Risk to You

Under a remeasurement contract, quantities are re-counted against actuals and you are paid for what you build. Under a lump-sum contract you are paid the agreed sum whether the real quantities come in higher or lower, so quantity risk sits with you. Lump-sum turnkey - LSTK - and the FIDIC Silver Book form push this further. The Silver Book is the EPC and turnkey instrument, and it deliberately transfers most risk to the contractor: design responsibility, site conditions, and the accuracy of the employer's requirements largely become your problem in exchange for price and time certainty the employer will pay a premium for.

The consequence is that the boundary of your scope is defined by documents you may not have written and cannot later disown. If the employer's requirements say the plant must achieve a performance outcome, filling the gap between the stated requirement and the detailed engineering is your cost, not a variation. This is the trade every contractor makes on these forms, and it is worth understanding before tender - our guide to fixed-price versus remeasurement versus cost-reimbursable sets out where each model puts the risk and what premium each deserves.

Variations Are Still Recoverable - But the Mechanics Are Tighter

Contractors sometimes assume that lump-sum means no variations. That is wrong. A variation is a change the employer or engineer instructs to the scope, and under FIDIC that power and its valuation live in the variation clause - Clause 13 across the main forms. A genuine instructed change to the works is recoverable on a Silver Book job just as on a red or yellow one. What differs is the evidential burden and the tighter tolerance for what counts as a change at all.

On a remeasure contract, a modest under-estimate corrects itself when quantities are re-counted. On lump-sum there is no such self-correction, so the only route to more money is to prove that what you did was outside the fixed scope and was instructed. That makes two things decisive: first, a precise definition of what the lump sum actually covers, captured at contract stage; second, a rigorous, contemporaneous record of every instruction that moves you beyond it. Lose either and a real variation becomes an absorbed cost.

The valuation mechanics are also tighter. Where the contract contains a schedule of rates or a priced breakdown, those rates govern the value of instructed change, even if they no longer reflect your real costs. Where no rate fits, valuation falls to a fair assessment of the cost plus reasonable overhead and profit - but you must be able to demonstrate the cost. On EPC work, agree the basis for valuing change before you need it, because arguing methodology after the fact almost always favours the party holding the money.

Scope Creep on Energy and EPC Jobs

Scope creep on a large EPC job rarely arrives as a single dramatic instruction. It arrives as a hundred small ones: a clarification here, a preferred vendor there, a tightened specification in a review comment, a site instruction to keep the works moving. Individually each looks too minor to notify. Collectively they rebuild a meaningful part of the plant at your expense. The employer is not usually acting in bad faith - the works simply evolve - but the cost lands on the contractor unless each increment is caught.

The discipline that defeats creep is treating every instruction, comment, and clarification as a potential change and testing it against the fixed scope at the moment it arrives, not at month-end. If it moves you beyond the baseline, it is notified as a variation before the work is done, not after. This is unglamorous, and it is the single practice that most reliably protects margin. The alternative - raising it all in one large claim at completion - hands the employer the argument that you carried on without complaint and therefore accepted the change.

Energy and process plant jobs make this harder because of interfaces. A change on one package cascades into others - a revised process guarantee alters equipment sizing, which alters civil loads, which alters the programme. On a lump-sum EPC contract those knock-on effects are yours to absorb unless you can trace each one back to a discrete instructed change. That traceability only exists if the original instruction was captured cleanly and its downstream effects were flagged as they emerged. Contractors who record the first change but not its consequences recover a fraction of what they are owed.

The Discipline That Protects Margin

Protecting margin on a lump-sum job comes down to a few habits applied without exception. Establish the scope baseline in writing at the outset, so there is a fixed line to measure change against. Log every instruction and clarification as it happens, with the date, the source, and its cost and time effect. Notify variations promptly and within any contractual time bar. Price change against the contract rates where they apply, and build a demonstrable cost record where they do not. Keep the notice about the fact of a change, and the valuation as a separate, evidenced step.

None of this requires a large commercial team - it requires consistency. A single person on the project who owns the change register, tests every incoming instruction against the baseline, and issues notices on time will protect more margin than a room full of quantity surveyors reconstructing events after handover. The cost of the discipline is modest and predictable; the cost of skipping it lands all at once, at final account, when the leverage has moved to the other side and the record you needed was never made.

Below is a rough sense of how the same instructed change is treated across three pricing models. The point is not the exact figures but the recovery mechanism each model gives you.

Pricing model | Who carries quantity risk | Route to recover instructed change Remeasurement | Employer | Quantities re-measured against actuals; rates in the bill apply Lump-sum / LSTK | Contractor | Must prove change is outside fixed scope and was instructed; valued under the variation clause Cost-reimbursable | Employer | Actual cost plus fee; change absorbed into the reimbursed cost

The through-line is that on lump-sum and LSTK forms nothing self-corrects. Every pound of recovery depends on a clear baseline and a clean record, which is why prevention beats cure by a wide margin. For the practical drafting and process controls that stop valuation fights before they start, see preventing disputes over variation valuation before they start, and consider structured advisory support through CALIM's prevention service when the contract value justifies getting the mechanics right from day one.

Price Certainty Cuts Both Ways

It is worth remembering why the employer chose a lump-sum or LSTK form in the first place. They wanted a fixed number to finance and a fixed date to plan around, and they are paying a premium for that certainty. That premium is your reward for carrying the quantity and design risk - which means the model is not inherently unfair to the contractor, only unforgiving of poor administration. A contractor who prices the risk honestly at tender and then administers change rigorously earns the premium. A contractor who underprices the risk to win the job and then administers loosely gives the premium straight back, and often more.

The lesson is that margin on these forms is decided twice: once at tender, when you set a price that reflects the real scope risk, and again during delivery, when you defend the boundary of that scope against the steady pressure of change. Get either wrong and the fixed price becomes a fixed loss. Get both right and the certainty the employer paid for becomes the certainty of your return.

Frequently Asked Questions

Can I claim variations on a lump-sum or LSTK contract at all?

Yes. A lump-sum price fixes the sum for a defined scope; it does not remove the employer's power to instruct changes or your right to be paid for them. Under FIDIC that power and its valuation sit in the variation clause, Clause 13. The difference from a remeasurement contract is the burden of proof. You must show the instructed work fell outside the fixed scope and was genuinely instructed, then value it under the contract mechanism. A real variation is recoverable on a Silver Book EPC job just as on any other form, provided you can evidence both the instruction and the fact that it went beyond your baseline.

Why does an LSTK or EPC contract put more risk on the contractor?

Because the employer is buying certainty of price and time and paying a premium for it. The FIDIC Silver Book, the standard EPC and turnkey form, deliberately transfers most risk to the contractor - including design responsibility, the accuracy of the employer's requirements, and often site conditions. In exchange the contractor sets a fixed price and completion date the employer can finance and plan around. The effect is that gaps between the stated requirements and the detailed engineering fall to the contractor to fill at its own cost, unless the employer instructs a genuine change to the requirements themselves.

How do I stop scope creep from eating my margin?

Test every instruction, clarification, and review comment against your fixed scope at the moment it arrives, not at month-end. Scope creep on EPC work rarely comes as one big instruction - it accumulates through many small ones that each look too minor to notify. Establish a written scope baseline at the outset so there is a fixed line to measure against, log every instruction as it happens, and notify anything that moves you beyond the baseline as a variation before you do the work. Catching increments early is the single most reliable way to protect margin.

How are variations valued on a lump-sum contract?

Where the contract includes a schedule of rates or a priced breakdown, those rates govern the value of instructed change, even if they no longer match your actual costs. Where no rate reasonably applies, valuation falls to a fair assessment of cost plus reasonable overhead and profit - but you must be able to demonstrate that cost with records. The practical lesson is to agree the valuation basis before you need it, because settling methodology after the work is done tends to favour whoever is holding the money. A clean, contemporaneous cost record is what makes fair valuation achievable.

What records do I need to protect a variation claim on LSTK work?

A precise definition of what the lump sum covers, fixed at contract stage, plus a contemporaneous log of every instruction that moves you beyond it - each with its date, source, and cost and time effect. On a lump-sum form nothing self-corrects the way remeasured quantities do, so recovery depends entirely on proving the change was outside scope and was instructed. Notify promptly and within any contractual time bar, keep the notice separate from the valuation, and build a demonstrable cost trail. Weak records turn genuine variations into absorbed costs, which is exactly how margin disappears without anyone noticing.

On a fixed price the scope is the only thing you can defend - so define it tightly, record every change to it, and notify before you build.

Note: This article is general commentary on variation and pricing mechanics, not legal advice; clause numbering and valuation rules vary between FIDIC editions and bespoke amendments, so check your own contract and take advice on significant claims.