Lump Sum Contract vs Unit Rate Contract: What Every Contractor and QS Must Understand

A contractor won a tender for a residential development — 24 units across three blocks, concrete frame, standard finishes. The drawings at tender stage were at RIBA Stage 3, which is developed design but not yet fully detailed. The contractor priced it as a lump sum. The number was competitive and they were awarded the contract.

By the time the project reached the structural frame, the fully detailed Stage 4 drawings had arrived and several coordination issues had been resolved — column positions adjusted, slab depths revised in two zones, staircore walls thickened to meet acoustic requirements. Each change was small on its own. Together they added roughly 340 tonnes of additional reinforcement and 180 cubic metres of additional concrete that the lump sum had not included.

The contractor submitted variation claims for all of it. The client pushed back, arguing the lump sum covered the complete works. The dispute went to adjudication. The contractor recovered some of the additional cost but not all of it — and the six months it took to resolve the dispute delayed the handover and damaged a relationship that had taken years to build.

The contract type did not cause the design changes. But it determined who carried the financial consequences of those changes — and on a project where the design was not yet complete at tender, a lump sum was the wrong vehicle for that risk allocation.

What a Lump Sum Contract Actually Means in Practice

A lump sum contract sets a single fixed price for the entire scope of work. Once the contractor signs and the client accepts, that number becomes the contract sum. It does not move unless the scope changes — and even then, scope changes require formal variation orders, each one negotiated and agreed before additional work proceeds.

The financial logic of a lump sum is straightforward: the contractor has reviewed all the documents, assessed all the risks, and committed to a price. If their assessment was accurate and the project runs to plan, they make their margin. If their assessment was optimistic or conditions change, they absorb the difference. The client's position is protected — they know what the project will cost from the day they sign.

That protection comes at a price. Contractors who carry quantity risk build contingency into their lump sum to cover it. The more uncertain the design, the more contingency gets added. On a project with incomplete drawings or evolving scope, the lump sum a careful contractor submits will be meaningfully higher than the true expected cost — because they are pricing not just the work, but the uncertainty around it.

What the Lump Sum Covers and What It Does Not

A common misunderstanding is that a lump sum contract means the client pays exactly the agreed sum regardless of what happens on site. In practice, most lump sum contracts include provisions for variations — instructed changes to scope that adjust the contract sum. What the lump sum protects against is quantity risk — the risk that the contractor measured something wrong or that site conditions required more work than anticipated within the defined scope.

A lump sum contract is appropriate when the following conditions are met:

•       Design is complete and fully coordinated: All drawings are at construction issue and the contractor can measure the scope with confidence — not at developed design stage where coordination issues are still being resolved

•       Specification is confirmed: Material specifications, finishes, and system performance requirements are locked — changes after contract award become expensive variation claims

•       Site conditions are understood: Ground investigation reports are available and the contractor has been given the information they need to price groundworks and foundations without significant uncertainty

•       Major changes are unlikely: The client's brief is stable and the design team is not anticipating significant scope evolution during construction

When these conditions are not met and a lump sum is used regardless, the contractor faces a choice at tender: price generously to cover the uncertainty, or price competitively and accept the risk. The first approach costs the client more than necessary. The second approach creates the conditions for exactly the kind of dispute that played out on the residential development.

What a Unit Rate Contract Does Differently

A unit rate contract — also called a remeasurement contract — takes a fundamentally different approach to the relationship between price and quantity. Rather than fixing the total cost before work starts, the parties agree on a rate for each item of work. The contractor is paid based on the quantities actually executed, measured against those agreed rates.

The BOQ in a unit rate contract contains the contractor's rates against estimated quantities. Those estimated quantities are used to calculate an approximate contract sum at tender — but the approximate sum is not the price. The price is the product of the final measured quantities and the agreed rates, calculated at completion through a remeasurement process.

For the client, this means the final cost of the project is not known with precision until the work is measured. For the contractor, it means they are paid accurately for what they actually build — they are not exposed to the risk of underestimating quantities, because quantities are measured rather than assumed. What they are still exposed to is rate risk — if their rate for a particular item did not account for the actual difficulty of executing that work, they carry that consequence.

Where Unit Rate Contracts Are Most Effective

Unit rate contracts are the standard procurement model for civil engineering and infrastructure work — road construction, drainage networks, earthworks, piling, and similar activities where the quantities at tender cannot be reliably fixed in advance. A road project that crosses variable ground conditions will produce earthworks quantities on site that differ from the tender estimate. A unit rate contract accommodates this naturally — the contractor is measured on what they excavate, not what the engineer estimated at tender.

Unit rate contracts work best in the following project conditions:

•       Variable ground conditions: Earthworks, piling, and foundation work where actual quantities depend on what is encountered below ground rather than what was assumed at design stage

•       Linear infrastructure projects: Roads, pipelines, drainage networks, and utility installations where total quantities depend on the final alignment and depth actually achieved

•       Phased or evolving scope: Projects where the client anticipates scope additions during construction — the rate structure accommodates additional work without renegotiation

•       Early contractor involvement: Where the contractor is brought in before design is complete — unit rates can be agreed while detailed design continues, avoiding the risk of a premature lump sum

The Full Comparison — How the Two Contracts Differ at Each Stage

The remeasurement row in that table deserves attention. Under a lump sum, the final account process is relatively contained — the contract sum is adjusted for agreed variations and any adjustments to prime cost and provisional sums. Under a unit rate contract, the entire work is remeasured at completion. This is a significant commercial exercise that requires careful quantity surveying — every section of the BOQ measured against what was actually built, with any differences between the tender quantities and the final quantities resolved at the agreed rates.

Understanding how each contract type connects to BOQ preparation is essential before committing to either approach. For a detailed guide on the relationship between cost estimates, BOQs, and the documents that underpin each contract type, see our article on BOQ vs Cost Estimate: When to Use Each and How to Manage Both.

The Decision That Matters Before the Contract Is Signed

The residential contractor's situation at the opening of this article was not inevitable. The project reached adjudication because a lump sum was used on a project where the design was not yet complete and the quantity risk was therefore not yet quantifiable. Had the procurement been structured as a unit rate contract — with agreed rates against approximate quantities at Stage 3 design, remeasured to final quantities as the Stage 4 drawings were issued — the additional reinforcement and concrete would have been measured and paid for as a matter of course. There would have been no variation claim, no dispute, and no adjudication.

The contract type does not change what the project costs. It determines who carries the uncertainty around that cost — and at what stage of the design process that uncertainty is resolved. A lump sum resolves it at tender, transferring the risk to the contractor in exchange for cost certainty for the client. A unit rate defers it to completion, sharing the risk in exchange for accuracy and flexibility during construction.

Neither is inherently better. Both are appropriate in the right conditions. The question every QS, contractor, and project manager needs to ask before signing is not 'which contract type do we prefer?' but 'which contract type fits the actual state of this project's design and risk profile at the time we are going to tender?'

For a broader overview of how lump sum, unit rate, and other contract types sit within the full range of construction procurement options, see our article on Construction Contract Types Explained: A Complete Guide.