Bill of Quantities Software: A Fair Comparison and What to Test
Bill of quantities software helps estimators turn construction drawings into measured quantities, and it falls into two broad categories: generic measuring software, where a person still traces each element on screen, and AI that reads drawings and extracts the quantities itself. Both should be compared against the baseline of manual takeoff. The right choice depends less on headline speed and more on units, traceability and how the tool behaves when the drawing is unclear.
What are the main types of bill of quantities software?
Bill of quantities software can be grouped into three approaches, ordered by how much of the reading work stays with the estimator. Seeing them side by side makes it easier to understand what each one actually automates.
Manual takeoff is the baseline: printed or on-screen drawings, a scale, a highlighter and a spreadsheet. The estimator reads every sheet, interprets every note and performs every calculation. Nothing is automated, but every assumption is made consciously by a person.
Generic measuring software digitises the act of measuring. The estimator clicks along lines, draws around areas and counts symbols, and the software calculates lengths, areas and counts at the correct scale. It is fast at measuring, but it does not understand what it is measuring: the person still decides which line is a beam, which hatch is a slab and which detail applies where.
AI that reads drawings goes one step further. It interprets the drawing content itself, identifies elements such as beams, columns, slabs, footings and bars, reads dimensions, profiles and notes, and produces quantities for the estimator to review. The estimator's role shifts from measuring to checking.
How do manual takeoff, generic software and AI that reads drawings compare?
Manual takeoff, generic measuring software and AI that reads drawings differ mainly in who does the reading, how results are expressed and how much checking is still required. The table below is a fair, general comparison; individual products within each category vary.
| Criterion | Manual takeoff | Generic measuring software | AI that reads drawings |
|---|---|---|---|
| Time per drawing set | Longest; scales with every sheet | Faster measuring, but every element is still traced by hand | Quantities produced automatically, then reviewed |
| Output units | Whatever the estimator calculates | Mainly lengths, areas and counts; conversion to weight is often a separate step | Depends on the tool; look for trade units such as tonnes and m³ |
| Transparency | High if the workings are kept; often lost in spreadsheets | Good: markups show what was measured | Varies widely; insist on line-by-line traceability |
| Learning curve | Low for experienced estimators | Moderate: tools, layers, scales, templates | Low for operation; review skills remain essential |
| Main thing to verify | Arithmetic and missed sheets | Scale calibration and elements nobody clicked | How unclear or missing information was resolved |
No category removes the need for review. What changes is the type of error you need to look for: arithmetic slips in manual work, missed clicks in generic software, and silent interpretation in AI tools.
Why do trade-specific units matter in a takeoff tool?
Trade-specific units matter because a bill of quantities is priced in the units the contract defines, and a tool that stops at lengths and areas leaves the most error-prone conversion to the estimator. For structural trades, rebar and structural steel are normally billed by weight in tonnes, while concrete is billed by volume in m³.
Illustrative example: a tool reports 100 m of Ø16 bar. To price it, someone still has to multiply by the mass per metre of Ø16, which is 1.578 kg/m, giving 157.8 kg. That step is easy once, but a real rebar schedule has dozens of diameters, shapes and laps, and the conversion is where transcription errors creep in. The same applies to steel profiles, where each section has its own mass per metre. A takeoff tool that delivers results directly in bill of quantities units removes that layer of manual work. The underlying calculation is explained in how to calculate rebar quantities.
What does traceability mean in bill of quantities software?
Traceability in bill of quantities software means that every line in the output can be followed back to the exact place in the drawing it came from. Without traceability, a reviewer can only compare totals against intuition; with traceability, a reviewer can open any line and confirm the element, the dimension and the sheet.
Traceability is what makes a review practical. When a total looks high, the estimator needs to see which elements drive it, whether one element appears twice across a plan and a section, and which revision the figure came from. Ask any vendor to show you, on screen, how a single line in the report links back to the drawing. If the answer is a summary table with no route back to the source, the review burden simply moves from measuring to guessing.
How should software handle unclear or missing information?
Software should flag unclear, missing or contradictory information and ask the user, rather than silently filling the gap with a default. This is the single most important behaviour to test, because the costliest errors in a bill of quantities are usually assumptions nobody saw being made.
Typical gaps include a slab thickness that appears only in a section that was not supplied, a beam profile that differs between the plan and the elevation, or a typical detail that is referenced but never drawn. A tool that guesses will produce a confident number either way. A tool that asks makes the gap visible and lets the responsible person decide. Quantap is built on that principle: Quantap doesn't guess, it asks. When something is unclear, missing or contradictory, it raises the question through Quick Check, and the quantities update once the user answers. The risk behind silent defaults is covered in detail in the hidden assumptions that cause bill of quantities errors.
What should you test in a bill of quantities software demo?
A bill of quantities software demo is only useful when it runs on your drawings, not the vendor's sample set. Prepare a project you know well and use your own quantities as the benchmark.
- Bring your own complex set. Choose a finished project with plans, sections, elevations and typical details, ideally with at least one revision. Clean sample drawings hide the problems you will meet in practice.
- Check the input formats. Confirm the tool reads the formats your consultants issue (DWG, PDF, IFC) and whether a whole set can be uploaded at once. The trade-offs between formats are explained in DWG vs PDF vs IFC for quantities.
- Check the output units. Rebar and steel should arrive by weight, concrete by volume, in the units your contract uses.
- Trace three random lines. Pick lines you did not choose in advance and ask to see where each one comes from in the drawing.
- Watch what happens with a gap. Remove a section or a note and see whether the tool flags the missing information or fills it in silently.
- Compare line by line, not only totals. Matching totals can hide errors that cancel each other out. Compare element groups against your own figures.
- Time the full cycle. Measure from upload to a reviewed result, including the time you spend checking, not just processing time.
For more questions to bring to the demo, see the FAQ.
Summary
Bill of quantities software ranges from generic measuring tools, where people still trace every element, to AI that reads drawings and produces quantities for review. Every category still needs professional checking; what differs is where errors hide. The most reliable way to choose is a demo on your own complex drawings, judged on trade units, line-by-line traceability and how unclear items are handled. A tool that asks instead of guessing makes the review faster and the final figures easier to defend.
Frequently asked questions
Can bill of quantities software replace a quantity surveyor?
No. Software can take over the repetitive measuring and arithmetic, but a qualified estimator or quantity surveyor still has to review the results, apply the contract's method of measurement and take responsibility for the submitted figures.
Is it worth testing software on a simple drawing first?
A simple drawing is a reasonable warm-up, but it proves very little. Most tools perform well on a clean single sheet; the real differences appear on a full set with sections, typical details, revisions and missing information.
Which file formats should a takeoff tool accept?
At a minimum, a takeoff tool should accept the formats your design team actually issues, which usually means DWG and PDF, and increasingly IFC models. Accepting a whole set in one upload, for example as a ZIP file, saves time and keeps related sheets together.
How long does a fair software trial take?
A useful trial can be run in a few working sessions if you prepare in advance: choose one finished project you know well, keep your own manual quantities as the benchmark, and compare line by line rather than only comparing totals.
