Which bill of quantities format should you use?

Start with an NRM2-aligned elemental format if you're building a cost plan or comparing tenders on a traditionally procured project. Switch to work section (trade) format when contractors expect trade-grouped pricing, and use work package format for design-and-build or contract packaging where the works are split by procurement route rather than by element.

Every version follows the same skeleton: item number, description, unit, quantity, rate, total. What changes is how items are grouped above that skeleton.

Elemental — grouped by building element (substructure, frame, roof), ideal for cost planning and elemental cost comparison.
Work section (trade) — grouped by trade package (groundworks, joinery, electrical), familiar to contractors and subcontractors.
Work package — grouped by contract package, suited to design-and-build or management contracts.

For a ready-to-adapt starting point, see the downloadable NRM2 templates and Quantiflow's overview of how automation handles NRM2-aligned takeoffs.

Key Takeaways

The right bill of quantities format depends on project stage and procurement route, but every version must follow NRM2's column order and item sequencing to stay tender-ready.

Point	Details
Default to elemental early	Use NRM2-aligned elemental format during cost planning, then regroup for trade tender if needed.
Follow the six-column layout	Item number, description, unit, quantity, rate, and total, with preambles kept outside the table.
Ring-fence provisional sums	Keep provisional and PC sums in their own bill with a single summary reference line.
Run the four core QA checks	Codification, unit sanity, rounding policy, and cross-total verification before every issue.
Automate takeoff, review judgement	Quantiflow produces NRM2-aligned takeoffs from drawings while keeping override points for QS sign-off.

BoQ formats explained: elemental, work section and work package
What is the standard BoQ layout and column order?
How do you choose the right BoQ format for your project?
Templates, file formats and Excel layout best practice
Common BoQ errors and the quality checks that prevent disputes
How QuantiFlow supports NRM2-aligned BoQs while preserving quantity surveyor judgement
Faster NRM2-aligned BoQs without losing your sign-off
Sources

BoQ formats explained: elemental, work section and work package

NRM2 sets out three principal structures for organising a bill of quantities, and each has its own ordering rules and typical use case. Picking the wrong one for the project stage is one of the most common reasons BoQs get reworked mid-tender.

Elemental format groups items by building element rather than trade. It's the natural choice during early cost planning because it lets a quantity surveyor benchmark against historical elemental cost data and spot outliers before the design is finished.
Work section (trade) format groups items by trade, which contractors generally find quicker to price because it mirrors how they organise their own subcontractor enquiries. NRM2 notes that trade groupings often speed up tender returns on trade-split procurements.
Work package format splits the works by contract package rather than element or trade, which fits design-and-build and management contracting where different parties price different scopes.

On multi-building schemes, decide early whether you need separate bills per building or one summary bill drawing figures from each. Separate building bills make post-contract variance tracking far cleaner; a summary bill is faster to produce but blurs which building is driving cost.

Pro Tip: If the design is still moving, start elemental. You can always regroup into trade sections later for tender, but reworking an elemental cost plan from a trade bill is a much bigger job.

For a deeper comparison with worked examples, Quantiflow's guide to the types of bills of quantities walks through each format against real project scenarios.

What is the standard BoQ layout and column order?

Every compliant bill uses the same six columns in the same order: item number, description, unit, quantity, rate, and total. Preambles, method statements, and pricing assumptions sit outside the table entirely, typically on a separate preamble page ahead of the measured items, as shown in standard BoQ format examples.

Within each element or work section, NRM2 also sets a strict ordering rule for the items themselves:

Cubic items first, then square, then linear, then enumerated, then itemised.
Labour-only items before labour-and-materials items.
Where items are of equal type, order by value, highest first.

This isn't just tidiness. NRM2's own figures (A.1 to A.6) codify this sequence so that any two surveyors measuring the same drawings produce bills that read the same way, which matters enormously when a QS is checking a subcontractor's return against the main bill.

NRM2 also recommends starting each bill on a new sheet, with consistent codification so every line traces back to its cost plan entry. That single habit, numbering an item so it can be found again six months later during a variation dispute, does more to prevent argument than almost anything else in the document. Templates that follow this NRM2-style structure exist and have been shown to save significant time over building a bill from scratch, provided the template itself hasn't drifted from current NRM2 rules.

How do you choose the right BoQ format for your project?

The format decision comes down to five variables, and running through them in order avoids the mid-project rework that eats far more time than the format choice itself:

Project type — new build, refurbishment, or civils each lean differently; refurbishment often needs more itemised, descriptive entries because quantities are harder to measure precisely from drawings alone.
Design completeness — early-stage designs favour elemental; a fully detailed design ready for competitive tender favours trade sections.
Procurement route — traditional contracts usually work best with elemental or trade bills; design-and-build or management contracts often need work package format.
Subcontract scope — if you know trades will be let separately, trade format saves a re-sort later.
Client reporting needs — clients wanting element-by-element cost tracking need elemental bills regardless of procurement route.

Split buildings into separate bills once you have more than two or three distinct structures on a site. Use a summary bill only when the client genuinely needs one consolidated figure and doesn't require per-building variance data.

Provisional sums, PC sums, and dayworks belong in their own dedicated bill rather than scattered through the measured work, with a single line in the summary referencing the total. NRM2's Appendices D and E set out condensed and expanded pricing summary templates specifically for this purpose, and Quantiflow's guide to presenting provisional sums covers the wording that avoids ambiguity at tender evaluation.

Templates, file formats and Excel layout best practice

Excel remains the standard for tender pricing because contractors can enter rates directly into formula-linked cells rather than retyping figures from a PDF. Template guidance from procurement specialists confirms PDFs are fine for distribution but force manual re-entry, which is where transcription errors creep in.

A clean BoQ workbook typically follows this layout:

One sheet per bill, plus a master summary sheet that pulls totals automatically.
Rate and total columns locked or protected so contractors can't accidentally overwrite formulae.
Assumptions, exclusions, and the pricing validity period placed immediately after the BoQ table, never buried in a separate document.
Consistent units throughout (m, m², m³, nos, item) with no mixing of imperial and metric.

The most frequent template errors are mixed units within the same column, excessive decimal precision on quantities that don't warrant it, and vague descriptions that leave contractors guessing at scope.

Pro Tip: Generic downloadable templates save real time, but treat them as a starting skeleton rather than a finished document. Adapt preambles and PC sum entries to the specific project before issue, since templates built for one sector can quietly reference superseded rules.

Quantiflow's annotated bill of quantities example shows this layout applied to a real project, with the assumptions section and summary sheet both visible.

Common BoQ errors and the quality checks that prevent disputes

Most tender disputes trace back to a small handful of avoidable errors: mixed units within a section, descriptions too vague to price confidently, preliminaries left out of the summary, or provisional sums mixed in with measured work rather than ring-fenced separately.

Run these checks before issuing any bill:

Codification check — does every item number trace back to a cost plan or drawing reference?
Unit and quantity sanity check — do quantities look plausible against the drawn area or length?
Rounding policy — is the same rounding convention applied throughout, not just where it's convenient?
Cross-total verification — do bill totals sum correctly into the summary page?

Dayworks and contractor-designed work entries should sit in their own clearly labelled section rather than embedded within measured items, since tender evaluation processes treat these differently when checking for unbalanced bids.

How QuantiFlow supports NRM2-aligned BoQs while preserving quantity surveyor judgement

Automation handles the repetitive part of takeoff, not the professional judgement that sits around it. Quantiflow extracts measured quantities directly from PDF architectural drawings and structures the output into an NRM2-aligned BoQ ready for export to Excel or PDF, with an audit log tracking every revision.

Automated takeoffs from PDF drawings, cross-referenced against the drawing set for consistency.
Structured exports that follow NRM2 ordering rules, so the output matches what a QS would produce manually.
Editable outputs at every stage, with override points where professional judgement should take precedence.

Automation speeds up the bulk of measured work substantially on repeatable, medium-sized projects. It's less suited to complex provisional sums or contractor-designed packages, where a surveyor's interpretation of scope still matters more than pattern-matching against drawings.

Pro Tip: Run the automated takeoff first, then spend your review time on provisional sums and anything contractor-designed, since that's where judgement adds the most value and automation adds the least.

A practical habit worth stealing

Codify every provisional sum against a single summary line, and cross-check it before issue. It sounds trivial, but it's the single habit that cuts tender queries more than any formatting fix, because bidders stop guessing where an allowance sits in the overall figure. For more on getting this right, see the guide on presenting provisional sums and Quantiflow's wider view on choosing takeoff software.

Faster NRM2-aligned BoQs without losing your sign-off

Building a compliant bill by hand, sheet by sheet, is where most tender programmes lose their slack. Quantiflow reads your PDF drawings, produces NRM2-aligned quantities automatically, and hands you a structured BoQ you can still edit, override, and sign off exactly as you would one measured entirely by hand.

Quantiflow

It suits SME quantity surveying practices, small builders, and architectural teams who need tender-ready output without spending days on repetitive measurement. Pricing runs from Solo at £39 a month for individual practitioners through to Business at £149 a month for teams, with custom Enterprise terms for larger firms. Every output stays editable, with an audit trail showing exactly what changed and why, so professional judgement remains the final word on the bill.

If you've got a stack of drawings waiting to be measured, start with Quantiflow's overview and see how quickly a compliant bill comes together.