The BoQ as commercial defence
Most BoQs are written as pricing documents and never re-read until the buyer's negotiator opens row 412 and asks how the rate was built. By then the estimator who priced it is on another tender, the assumption that justified the rate is in someone's head, and the quantity source is two folders deep on SharePoint. The price collapses - not because it was wrong, but because it cannot be defended.
A BoQ structured as a commercial defence document survives that conversation. Same numbers, but every line carries its working - so any reviewer can read the rate, the assumption, the quantity source and the evidence pointer in five seconds.
Four columns every BoQ row should carry
- Item description and unit - the visible, scoreable detail. Lift verbatim from the ITT specification where possible.
- Quantity source - where the take-off came from (drawing reference, schedule line, parametric model, supplier confirmation). 'Engineer's take-off' is not a source; the drawing is.
- Pricing assumption - the labour rate, plant utilisation, overhead percentage and risk premium that compose the unit rate. One short line per assumption, named so it is reusable.
- Evidence pointer - the supplier quote, sub-contractor return, historic project benchmark or published rate the assumption is grounded in. If a buyer challenges it, you can produce the evidence on the call.
What this beats
Two failure modes disappear when the BoQ is structured this way. First, the 'who priced this' problem: any senior reviewer can defend the rate without involving the original estimator. Second, the 'value-engineering wins' problem: when a buyer asks for a 5 percent reduction, you can see exactly which assumptions to relax (and how the risk shifts) instead of cutting evenly across all lines and hoping margin survives.
The structure also pays back at handover. The same BoQ becomes the contract pricing schedule, the variations baseline, and the cost-plan reference. Variations get priced against the original assumption-and-source rather than from scratch.
Discipline that keeps a structured BoQ alive
- Rate-build sheets are linked, not pasted - if the underlying labour rate changes, every BoQ row using it updates with it.
- Assumptions register travels with the BoQ - when the contract is signed, the assumptions become the contractual baseline, not the negotiator's later interpretation.
- Evidence index is read-only after submission - the bid you priced is the bid you defend. If the source document moves, the evidence pointer is updated with a logged change.
- Variations price off the assumption that changed - never freehand. If the assumption did not change, the variation is a quantity adjustment at the agreed rate.
What this looks like in BuiltAI
The Commercial Control Kit and Bidroom-in-a-Box together produce a structured BoQ as a by-product of the bid intake. Each line carries its rate-build, assumption and evidence pointer in the same record. When variations land later, the variation register reads against the original BoQ row - the assumption-and-source pair becomes the contractual baseline rather than a memory.