A custom rate library is a structured dataset of unit rates and metadata, aligned to NRM2, that lets a quantity surveyor price bills of quantities consistently and adjust for location, date and project complexity. It draws on benchmarks like BCIS and government indices, then layers in your own project history. Framed correctly, it becomes the backbone of feasibility studies, cost plans and tender pricing alike.
TL;DR:
- A custom rate library should include detailed metadata such as source, date, location, confidence level, and NRM2 reference for each rate to ensure traceability and accuracy.
- Rates must be regularly normalized using material indices and location factors, with updates triggered quarterly, after tender returns, or when market indices show significant movement.
- Validation checks should confirm unit consistency, detect duplicates, and compare rates against benchmarks like BCIS to prevent pricing errors and implausible entries.
- Maintaining a history of superseded rates and linking each to specific projects allows for better trend analysis and more accurate adjustments over time.
- Integration with drafting tools like QuantiFlow can accelerate measurement and seeding processes, but final rate selection and judgment remain the surveyor's responsibility.
Table of Contents
- Core components and metadata every UK custom rate library should capture
- Step-by-step process to build and seed a rate library using UK datasets and your own history
- Governance: roles, versioning and an update cadence that keeps rates current
- Integrating with takeoff and cost-planning tools: formats, validation and practical checks
- Starter templates and a short checklist to seed your first library entries
- How a rate library supports stages from feasibility to tender and final account
- Techniques for validating and testing rate entries to ensure accuracy and reliability
- Best practices for maintaining historical data and trend analysis within the rate library
- Handling variations and contingencies within rate libraries for dynamic project environments
- Option: using QuantiFlow to accelerate seeding and maintaining a UK-aligned rate library
- Sources
- FAQ
Core components and metadata every UK custom rate library should capture
A rate library is only as useful as the information sitting behind each unit rate. Before entering a single figure, decide what fields every record must carry, because retrofitting metadata later across hundreds of entries is a slow job.
At minimum, each rate record should capture:
- Description and unit: a clear item description with the measured unit (m², m³, nr, tonne) matching NRM2 conventions.
- NRM2 reference: the work section and element code so the rate slots directly into a schedule of rates or bill of quantities.
- Rate build-up: labour, plant, material and, where relevant, specialist subcontractor components shown separately rather than as one bundled figure.
- Source and date: whether the rate came from BCIS, a supplier quotation, or an in-house tender return, and when it was recorded.
- Location basis: the region or postcode area the rate was derived for, so location adjustment factors can be applied consistently.
- Confidence rating: a simple high, medium or low flag showing how much professional judgement should be applied before relying on the figure.
Non-measurable items, such as preliminaries or contingency sums, need their own treatment. Rather than forcing them into a per-unit structure, record them as percentage or lump-sum allowances tied to project value, with the same source and date fields as measured rates.
The reason this metadata matters differs by stage. At feasibility, you need enough traceability to justify an order-of-cost estimate without over-engineering the detail. At tender stage, the same record needs a defensible audit trail, because a rate challenged during negotiation must be traceable back to its source and the date it was struck.
Step-by-step process to build and seed a rate library using UK datasets and your own history
Building a library from scratch is less about software and more about sequencing. Rushing the data-gathering stage produces a library that looks complete but collapses under scrutiny at tender.
- Define scope and structure. Set the breakdown by NRM2 work section and element, deciding upfront whether the library will serve one project type or span multiple sectors.
- Gather base data. Pull benchmark rates from BCIS, collect current supplier quotations and extract unit rates from your firm's completed tender returns.
- Cleanse and standardise. Strip out duplicate entries, align units of measurement and confirm every rate carries a source and date before it enters the library.
- Normalise for date and location. Apply tender price index movement to bring older rates to current pricing, and use location factors to adjust national averages for regional variation.
- Seed the library. Load the cleansed, normalised rates into your chosen spreadsheet or database structure, tagging each with its NRM2 reference and confidence rating.
- Test on a sample cost plan. Run the library against a recent project's cost plan and compare the output rates to what was actually tendered.
- Reconcile and adjust. Where seeded rates diverge materially from tender returns, investigate whether the gap is a data error, a genuine market shift, or a project-specific factor, and adjust the library accordingly.
Material and cost index movement should feed directly into this process. Gov publishes monthly and quarterly indices that show how material costs are shifting, and these should inform the normalisation step rather than being checked only at renewal time.
Pro Tip: Test your library on a project you already know the outcome of before trusting it on a live tender: reconciling against a known result exposes weak rates faster than any amount of manual checking.
Governance: roles, versioning and an update cadence that keeps rates current
A rate library without governance drifts. Rates go stale, nobody owns corrections and the version in use during a tender becomes impossible to pin down after the fact.
Set up governance around three roles and a simple update trigger list:
- Author: the person entering or amending a rate, recorded against every change.
- Approver: a senior QS who signs off material changes before they go live in the working library.
- Auditor: someone independent of day-to-day entry who periodically samples records for accuracy and completeness.
- Version identifier: a simple scheme such as year and quarter (2026-Q3) attached to every export, so a rate used on a tender can always be traced to the exact library state.
- Audit fields: date changed, changed by, reason for change and previous value, kept on every record rather than overwritten.
- Update triggers: a quarterly review as standard, plus ad hoc updates when GOV.UK material indices show a material movement, and a review after every tender return to feed lessons back into the library.
This structure does not need to be elaborate. A shared spreadsheet with a change log tab satisfies most of it for a small team, provided the discipline of recording who changed what, and why, is maintained consistently.
Integrating with takeoff and cost-planning tools: formats, validation and practical checks
However well the library is structured, it needs to move cleanly between takeoff, cost-planning and estimating tools without breaking on the way.
Common exchange formats each suit a different purpose:
- Excel or CSV: the most portable option for smaller teams, easy to filter and easy to share with subcontractors for pricing.
- BCIS Elemental Abstract template and XML: designed specifically for exchanging elemental cost analyses between systems, useful when benchmarking against BCIS's own template.
- Database export (SQL or API): appropriate once a firm's rate library grows large enough that spreadsheet performance becomes a constraint.
Whichever format you use, run the same validation checks before rates go live:
- Unit consistency: confirm every rate's unit matches the NRM2 convention for that work section, not a legacy or supplier-specific unit.
- Duplicate detection: check for near-identical descriptions entered twice with slightly different rates, a common source of pricing errors.
- Sanity against indices: compare seeded rates to recent movement in material and cost indices to catch entries that look implausibly high or low.
Takeoff tools that read drawings can produce a draft bill of quantities for a QS to review, which speeds up the mechanical part of measurement, but the rates applied to that draft, and the judgement over what is measurable, remain the surveyor's responsibility.
Starter templates and a short checklist to seed your first library entries
A minimal template needs only a handful of fields to get a first working version off the ground: description, unit, NRM2 reference, rate build-up (labour, plant, material), source, date, location basis and confidence rating. An example entry might read: "Excavate to reduce level, not exceeding 2m depth, m³, NRM2 5.1, source BCIS, dated Q2 2024, London region, confidence high."
Once the first batch of entries is seeded, run through this checklist:
- Unit check: every rate's unit matches its NRM2 element.
- Historical reconciliation: sample entries against a completed project's actual tender return.
- Stage labelling: mark each entry as suitable for feasibility, cost plan or tender use, since a feasibility-stage allowance is rarely precise enough for tender pricing.
- Location tagging: confirm the region each rate was derived for is recorded, not assumed.
| Field | Purpose | Example value |
|---|---|---|
| NRM2 reference | Links rate to measurement rule | 5.1 Excavation |
| Unit | Matches measured quantity | m³ |
| Source | Traceability | BCIS |
| Stage label | Controls where rate is used | Cost plan |
| Confidence rating | Signals need for judgement | High |
Labelling by stage matters because a rate suitable for an early order-of-cost estimate is not automatically fit for a firm tender price, and mixing the two without a label invites errors.
How a rate library supports stages from feasibility to tender and final account
A well-built rate library earns its keep by moving with the project rather than sitting fixed at one stage. At feasibility, it feeds an order-of-cost estimate quickly, using broad, benchmarked rates where precise measurement is not yet possible. As the design develops into an approximate quantities cost plan, the same library supplies more granular, element-level rates, with confidence ratings guiding where a surveyor should refine a figure rather than accept it outright.
By tender stage, the library should be supplying rates specific enough to defend against contractor challenge, each traceable to a source and date. Practitioner guidance on approximate quantities cost plans sets out this progression clearly: cost plans evolve through stages, and a rate library built to support that evolution needs fields for stage applicability built in from the start, not added retrospectively.
At final account, the library's role shifts again. Rather than pricing forward, it becomes a reference for reconciling variations and agreeing final costs, which is where feeding tender returns back into the library pays off. A rate that performed well against three tenders in a row earns a higher confidence rating; one that consistently undershot actual cost gets flagged for review. Treating the library as a living record across the whole project lifecycle, rather than a one-off tender tool, is what keeps it useful project after project.
Techniques for validating and testing rate entries to ensure accuracy and reliability
Validation works best as a layered process rather than a single check at the end. The first layer is structural: does every entry have a unit, an NRM2 reference and a source, with no blank fields masquerading as complete records.
The second layer is comparative. Set seeded rates against a recognised benchmark such as BCIS, which offers labour, plant, material and specialist rates with adjustments for location, date and contract value. A rate that sits far outside the benchmark range is not automatically wrong, but it warrants a second look before it goes live.
The third layer is empirical: test the library against known outcomes. Run a sample cost plan using library rates, then compare the total to what a similar project actually tendered at. Discrepancies at the total level often trace back to two or three individual rates rather than a systemic problem, and finding those outliers is more useful than accepting or rejecting the whole library on one comparison.
Internal historic cost analysis tends to give better adjustments for a firm's own procurement and risk profile than national averages alone, according to guidance on using BCIS data, which is worth remembering when a seeded rate diverges from a benchmark but matches your own project history closely. In that case, the in-house figure often deserves more weight, not less.
Best practices for maintaining historical data and trend analysis within the rate library
Historical data is what turns a rate library from a static price list into a source of insight about how costs move. Keeping every superseded rate, rather than overwriting it, is the single most valuable habit here: a rate replaced in 2025 is still useful evidence of how far costs have shifted by 2026.
Structure the historical record so each rate carries its own timestamp and, where possible, a link to the project it came from. This lets you track a specific work section, such as groundworks or external walls, across several projects and see whether costs are climbing steadily or reacting to a specific market shock. Cross-referencing that internal trend against published movement, such as the series in GOV.UK's construction building materials commentary, helps distinguish a firm-specific pricing issue from a market-wide one.
Avoid the temptation to purge old data to keep the library tidy. A cluttered spreadsheet is a minor inconvenience; losing five years of rate history because it seemed outdated is a real loss, particularly when a client or auditor asks how a rate was arrived at retrospectively. Archive superseded entries in a separate tab or table rather than deleting them, and keep the audit trail linking old to new.
Handling variations and contingencies within rate libraries for dynamic project environments
Variations are where a rigid rate library breaks down fastest, because a variation often falls outside the neat NRM2 categories the library was built around. The fix is not to force every variation into an existing rate, but to build a mechanism for pricing outside the library when the work genuinely does not match.
For contingencies, resist the urge to bury a single blanket percentage across the whole project. A more defensible approach ties contingency allowances to specific risk items, each with its own rate basis and confidence rating, so that when a risk materialises the actual cost impact can be checked against what was allowed. This also makes final account reconciliation faster, since you are comparing like against like rather than unpicking a lump sum.
Where a variation does use an existing library rate as its starting point, record the adjustment separately from the base rate rather than editing the original entry. This keeps the library's core data clean while still capturing how the rate was modified for that specific instance, which matters if the same variation type recurs on a future project and you want to see how it was priced last time.
Option: using QuantiFlow to accelerate seeding and maintaining a UK-aligned rate library
Building a rate library by hand is a legitimate route, and many firms run one successfully in a shared spreadsheet with disciplined governance. For firms working through a high volume of drawings, though, the manual measurement step behind each rate entry is often the slowest part.
QuantiFlow reads construction drawings and produces a draft bill of quantities for a quantity surveyor to review and sign off, currently in development.
- It aims to reduce the manual data entry involved in producing a first-pass BoQ from drawings, leaving the surveyor to review and confirm.
- A rate library can be used alongside the draft takeoff so rates may be applied to measured items without re-entering data by hand.
- Professional judgement remains with the surveyor at every stage, as the platform produces a draft for review rather than a final output.
Firms weighing up whether a contractor's preliminaries or VAT treatment affects how a rate is entered may also want to speak to a specialist such as Contractor Accountants about the invoicing implications before finalising a schedule. For more on QuantiFlow's approach and current plans and pricing, visit the QuantiFlow site.
Sources
Use NRM2 for measurement rules and schedule structure, BCIS for benchmark rates and its elemental abstract templates, and GOV.UK's material indices for current price movement. Designing Buildings offers practical guidance on cost plan evolution worth reading alongside the others.
- Gov
- Approximate quantities cost plan - Designing Buildings
- BCIS Elemental Abstract Excel Template - BCIS
FAQ
What is a custom rate library used for in construction?
A custom rate library is a structured set of unit rates and metadata that a quantity surveyor uses to price cost plans and bills of quantities consistently. It supports work from early feasibility estimates through to tender pricing and final account reconciliation.
How does NRM2 relate to a rate library?
NRM2 provides the measurement rules and work section structure that a rate library's entries should be mapped to, as set out in RICS's NRM2 guidance. Aligning your library's fields to NRM2 element and work section codes keeps rates directly usable in a schedule of rates or bill of quantities.
How often should a rate library be updated?
A quarterly review is a reasonable baseline, supplemented by updates whenever GOV.UK's material indices show material movement or a tender return reveals a gap against a seeded rate. Some firms also trigger a review after every major tender to feed fresh data back into the library.
Can software help build or maintain a rate library?
Software can speed up the mechanical parts of the process, such as generating a draft bill of quantities from drawings, which QuantiFlow is designed to do for a quantity surveyor to review and sign off. The rates applied, and the judgement over what each entry should be, remain the surveyor's responsibility throughout.
Recommended
- NRM2 explained: the RICS standard for measuring building works
- Keep Tender Quantities Within ±5%: NRM2 Workflow for UK QS
- Bill of quantities example for UK QS: download & guide
- Best quantity takeoff software for UK QS firms: 2026 guide
This article is for general information only and is not professional, legal or commercial advice. Quantity surveying decisions should be taken by a qualified professional with reference to the specific project, drawings and contract in question. Content is produced with AI assistance and reviewed before publication. QuantiFlow Ltd accepts no liability for reliance on it.