How Should QS Teams Quality-Check Automated BOQs?

QS teams should quality-check automated BOQs in four layers: source completeness, measurement logic, pricing logic, and issue control. Automation can generate and format information quickly, but a responsible quantity surveyor should verify exceptions, high-value items, unusual quantities, exclusions, totals, and the relationship between the source data and final client deliverable.

Key Takeaways

• Approve the source model, drawing, or workbook before generation.
• Reconcile source objects or dimension groups to BOQ coverage.
• Test measurement rules, descriptions, units, rates, and totals separately.
• Review exceptions and material items more deeply than routine lines.
• Lock the issued version with its inputs, rules, checks, and approvals.

What is an automated BOQ quality check?

It is a documented review that tests whether an automatically produced bill of quantities is complete, correctly measured, consistently priced, properly structured, and ready for its intended issue. The review should challenge both the generated content and the configuration that produced it.

The objective is not to repeat every calculation manually. It is to obtain reasonable assurance through reconciliations, exception reports, targeted sampling, and independent checks proportional to risk.

How should the source information be checked?

Confirm the correct source revision, issue status, scope, locations, and disciplines. For models, review classification coverage, element properties, duplicate objects, temporary objects, design options, and excluded categories. For CostX or spreadsheet sources, confirm workbook version, dimension groups, units, links, filters, and hidden or omitted data.

Create a source register that names the file, version, received date, preparer, approval state, and known limitation. An automated output should never appear more authoritative than its source.

Which BOQ checks should be mandatory?

Every issue should pass a consistent checklist:

• item coverage reconciles to the approved source;
• descriptions are clear, unique, and correctly grouped;
• units match the measurement rule;
• zero, negative, duplicate, and unusually large quantities are explained;
• rates have valid sources, dates, currencies, and location bases;
• arithmetic, subtotals, summaries, and carried totals reconcile;
• provisional items, assumptions, and exclusions are visible;
• the output follows the required standard or client template;
• reviewer, approver, revision, and issue purpose are recorded.

How should teams use sampling?

Sample by risk, not by a fixed percentage alone. Check all high-value items, newly mapped categories, manual overrides, unusual units, provisional rates, and lines produced by changed rules. Add random samples from routine items to test the general population.

For each sampled item, trace from the BOQ back to source geometry or dimension, repeat the measurement independently, verify the classification, and recalculate the rate or total. Record the result and expand the sample if an error indicates a systemic problem.

How do Concolabs workflows support controlled output?

CostX to BOQ reads CostX dimension groups and workbook data, maps items to NRM2 or a client template, carries rates through, and produces structured output. Quanto for CostX adds priced BOQ workflows to CostX data. These capabilities reduce rebuilding, while the QS remains responsible for approving inputs, mappings, rates, and the issued bill.

Pause here: identify the first step your project cannot evidence today, then assign a clear owner and next action.

For model-led projects, Quanto for Revit and Quanto for ACC connect BIM information to priced BOQ workflows. Model readiness and revision control should be part of the quality plan.

What should happen before issue?

Resolve or formally accept all material exceptions. Generate a final reconciliation summary, record reviewer comments, obtain approval, and freeze the exact source, mapping version, rate library, and output. The issue package should state purpose, status, assumptions, exclusions, base date, and revision.

Track defect escape rate, reopened BOQs, mapping exceptions, manual overrides, review time, and error concentration by source category. The aim is to improve configuration and source quality so future reviews become faster without becoming weaker.

Relevant Concolabs products

• CostX to BOQ converts CostX data into structured client-ready BOQs.
• Quanto for CostX supports priced BOQs and rate prediction from CostX workflows.
• Quanto for Revit supports BOQ generation from Revit models.
• Quanto for ACC connects cloud BIM data to repriced BOQ workflows.

Frequently Asked Questions

Who is responsible for an automatically generated BOQ?

Responsibility remains with the organization and professionals who prepare, review, approve, and issue the deliverable. Software performs configured processing; it does not accept professional or contractual accountability. The quality plan should name the preparer, independent reviewer, approver, and person authorized to issue each revision.

Should every automated BOQ item be checked manually?

Not usually. Teams can combine automated validation, full review of material or exceptional items, risk-based sampling, and independent totals. However, the approach must reflect project risk, source maturity, purpose, and professional obligations. New mappings and unreliable source categories require more extensive checking.

What are the most common automated BOQ errors?

Common failures include incomplete source data, duplicate or excluded objects, incorrect classifications, wrong units, outdated mappings, missing descriptions, unmatched rates, silent overrides, and totals that do not reconcile. Many originate upstream, so the review should test source information and configuration as well as final output.

How should manual BOQ edits be controlled?

Manual edits should require a reason, author, timestamp, and approval status. Keep them in a controlled adjustment layer rather than overwriting generated source values. When the BOQ is regenerated, the system should either reapply valid adjustments or flag them for review instead of losing them silently.

What evidence should be retained with an issued BOQ?

Retain the approved source revision, generation settings, classification and mapping versions, rate library, exception report, reconciliations, sample checks, manual adjustments, reviewer comments, approval, and exact issued file. This evidence package lets another QS reproduce the logic and explain later revisions.