From BIM Quantity Take-off to a Procurement-Ready BOM

Separate three different questions

A building information modelling (BIM) quantity describes what is represented in the model. A bill of quantities (BOQ) follows an agreed measurement basis. A procurement bill of materials (BOM) lists materials or components in usable specifications and purchasing units. These outputs can share data, but a model total does not by itself state what still needs to be ordered.

Exporting a schedule does not settle whether the model is complete, whether the scope matches the package, or how a geometric quantity translates into an orderable product. Treat the export as an input to a controlled process rather than its conclusion.

This article proposes a practical reconciliation workflow. It does not prescribe a contractual measurement standard, a wastage allowance or a supplier’s ordering rules.

Start with the quantity basis

Agree the purpose before choosing fields: preliminary planning, tender comparison and purchasing may require different scope and information maturity. Record the source model revision, included areas and systems, excluded items, units and treatment of incomplete information.

Schedule configuration matters. Revit allows filters to limit the data displayed in a schedule or material take-off; Autodesk also documents limitations on the fields available for filtering. Consequently, a schedule’s name alone is not evidence that it contains the intended scope. [1]

Review the actual inclusion rules. Ask whether linked or repeated information has been handled consistently, whether the required objects exist, and whether classification and specification fields are populated. The appropriate checks depend on the authoring setup and intended use.

Map quantities to purchasable specifications

A model family or type name is not necessarily a supplier product code. Build an explicit mapping between the model classification, the required technical specification and the purchasing description. Record who owns this mapping and how substitutions are reviewed.

A TRACEABLE PROCUREMENT LINE

Source revision + scope + measured quantity + specification + purchasing unit + review

Keep the measured value separate from any approved ordering adjustment.

For example, a modelled linear quantity and an order expressed in standard stock lengths require a conversion basis. Packaging, fabrication breakdown, accessories and installation requirements can introduce further differences. Those differences need to be explained; they should not be concealed in an unexplained multiplier.

Do not impose a generic allowance on every item. Use project-approved rules, supplier information and the relevant responsible person’s review. Keep assumptions visible when product or fabrication details remain unresolved.

Reconcile changes before releasing the package

Compare the proposed BOM with the previous approved extraction and purchasing records. Separate design changes from data corrections, scope changes and changes in measurement rules. Then calculate what still needs ordering using the project's agreed reconciliation method. Check existing orders, usable stock, deliveries, cancellations and approved substitutions, without counting a delivered item again as both stock and an outstanding order.

Freeze the source: identify the information revision used for this extraction.

Validate the scope: check the package boundary and record exclusions.

Review the mapping: confirm specification and purchasing-unit compatibility.

Explain the adjustment: retain the measured quantity and the basis of any conversion or allowance.

Reconcile the release: explain the remaining order quantity, avoid duplicate commitments and confirm unresolved decisions and approval responsibilities.

A quantity update should not automatically become an instruction to purchase. Procurement release remains a distinct decision with its own authority and checks.

Make the handoff usable by the purchasing team

Provide more than a spreadsheet of totals. Include the source revision, package definition, specification mapping, unit conventions, exclusions, outstanding queries and a review record. Where information is incomplete, label the affected lines instead of implying the entire package is purchase-ready.

Model authors, quantity reviewers and purchasing staff need a shared understanding of what each column represents. A short walkthrough of one complete line often exposes missing assumptions earlier than a discussion about software capabilities.

A buying decision should be traceable to its source information, specification and agreed ordering rules. SmartBuild Tech's quantity and digital delivery support can help structure that information for review. The purchasing team retains authority to release orders; a model export alone is not evidence that a package is ready to buy.