Why is the lowest bid not the cheapest?
Because the lowest number is an opinion about scope, not a price. Until every bid has been levelled to the same scope — exclusions priced in, blank rates filled, provisional sums aligned, quantity deviations reconciled — you are not comparing prices at all. The bid that looks lowest is very often the one that priced the least.
What levelling actually does
Bidders do not price identical things. One excludes builder’s work in connection. One leaves a rate blank and writes “included elsewhere”, and it turns out not to be included anywhere. One carries a provisional sum that another has priced properly. One has read the quantities differently.
Levelling normalises all of that to a common scope before anyone compares a total. It is unglamorous, it is where the evaluation is genuinely won or lost, and it is the step that gets compressed when the award date is close.
The chain that follows from skipping it
Award to the lowest incomplete bid. The missing scope surfaces the moment work starts, because it was always going to. It becomes a variation, priced without competitive tension, by the one contractor who is now on site.
The “saving” is gone within months, and what remains is a dispute about whether the exclusion was clear. It usually was clear — in the bid nobody read closely enough.
The rule
Compare levelled bids, not submitted bids. The raw lowest total tells you which contractor was most optimistic, or most aggressive, or most careless about reading the specification. It does not tell you which offer costs least.
And it cuts the other way too: the bid that looks expensive is sometimes the only one that priced the whole job.
In the guides
Terms
References
- module: /modules/tender-management/ — BOQ levelling and bid comparison
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
Related questions
See Zepth on your project.
A short, tailored walkthrough on your real workflow — no generic demo.
Book a meeting