Measurement basis
Agree measurement rules, allowances, exclusions and the BOQ structure before anything is counted.
A quantity is only as good as the rule that measured it. Ours state the rule, the source model and its version on every line.
Quantity takeoff, schedules & BOQ
Measured quantities from a model answer "how much is drawn". A bill of quantities answers "how much is to be built, under which measurement rules, with which allowances". Pricing is a third question again. We keep the three separate on paper, because blurring them is how a takeoff ends up treated as a commitment it never was.
Is that pipe length measured centre-line through fittings or net between them? Are hangers counted, or allowed for? A quantity without its rule cannot be checked, compared or defended. Every takeoff we issue states the measurement rules, the exclusions, the allowances and the source model version.
The first takeoff is useful. The comparison between revision C and revision D is what a commercial team actually needs — what moved, by how much, and where. Model-based quantities make that comparison a routine rather than a re-measure.
Deliverables
Any of these can be appointed on their own or combined. Nothing here depends on buying the intelligence layer, which is not for sale in any case.
Catalogue scope
The full list from the BIMRACE service catalogue. Each item can be included or excluded in a proposal; the code is the one used in our scope documents.
How it runs
Sequence is not a formality on this kind of work. Most of the expensive rework we are asked to fix was produced by doing step four before step two.
Agree measurement rules, allowances, exclusions and the BOQ structure before anything is counted.
Test that the elements to be measured exist, are classified and carry the parameters the takeoff depends on.
Quantities extracted from the model by discipline, classified to the agreed structure.
Model quantities reconciled against drawings, with discrepancies listed rather than absorbed.
Consolidated workbook and BOQ issued with the measurement notes.
Each new revision compared with the last and the changes reported.
What we need to start
Missing any of these is survivable. Not knowing which of them are missing is not, so we establish it at enquiry stage rather than at forty per cent.
AI & automation
AI is used throughout our delivery workflow, and an engineer reviews every output. Every line carries its real status.
Scope boundary
Published because a scope boundary discovered at month three is a dispute, and the same boundary stated at enquiry stage is just information.
Request a quote
Tell us the building, the stage and what you need. An engineer replies within two working days with approach, deliverables and a fee basis.
Quote request received
Have drawings ready? Use the full enquiry form to attach them.
What a useful quote needs. Building type and approximate area, the disciplines, the project stage, and which drawings or models exist. If you have them ready, the full enquiry form takes file uploads.
NDAs. We sign before drawings or models are shared, as a matter of course.
FAQ
Not by default. We prepare quantities and BOQ structures; rates and pricing are included only when explicitly agreed.
We can first model the systems from your drawings and then extract quantities, which also gives you a reusable model for later revisions.
The one the project names. We state it, with the allowances and exclusions, on every issue.
Yes — revision comparison and change reports are a standard deliverable, and usually the most useful one to a commercial team.
Related
Engineering enquiry
Send a scope, a drawing set or the workflow you want this applied to. You will get a technical response on approach, disciplines, deliverables and what is realistically automatable — from an engineer, not a sales desk.