Risk allowances in BoQs: the UK QS guide

A risk allowance in a Bill of Quantities is a priced provision for a specific, identified risk — a "known unknown" that you can name, quantify with a probability and impact, and trace back to a risk register entry. Before you issue any BoQ, do three things: link every allowance line to a named risk register item, state the valuation method that will govern drawdown, and record the assumptions underpinning the figure. A properly structured allowance, with those three elements in place, makes tender returns directly comparable and gives the contract a clear mechanism for releasing or adjusting the sum — which is the difference between a defensible cost plan and a dispute waiting to happen.

Pro Tip: If you cannot point to a risk register entry for an allowance line, it is not an allowance — it is an unstructured contingency. Treat it as such, or restructure it before the BoQ is issued.

Key takeaways

A risk allowance in a BoQ is only defensible when it is linked to a named risk register entry, carries a stated valuation method, and has a written drawdown procedure — without those three elements, it is an unstructured contingency regardless of what it is labelled.

Table of Contents

• What a risk allowance actually is and why it belongs in your cost plan
• How a risk allowance differs from contingency and risk premiums
• Where and how to show a risk allowance in an NRM2-aligned BoQ
• How to quantify a risk allowance from the project risk register
• What to include and exclude when pricing a risk allowance
• Drafting assumptions, valuation mechanisms and the drawdown process
• How to check and normalise risk allowances during tender analysis
• Common BoQ mistakes with risk allowances and red flags in tender returns
• Worked example: converting a risk register entry into a BoQ allowance
• Practical pre-issue QS checklist for BoQs covering risk allowances
• A practitioner's perspective on managing risk allowances
• Quantiflow makes NRM2-aligned BoQs with traceable risk allowances faster to produce
• Sources

What a risk allowance actually is and why it belongs in your cost plan

A risk allowance is a targeted, named provision for a cost risk that has been identified and assessed but cannot yet be fully measured. It sits between the base measured cost and the contingency reserve, and it is always linked to a specific risk event. The RICS defines the distinction clearly: a risk allowance covers "known unknowns" — risks you can identify and model — while contingency covers "unknown unknowns," the residual uncertainty that remains after all identifiable risks have been assessed.

In NRM2 practice, the cost structure reads as a simple hierarchy:

• Base measured cost: the fully quantified, priced work described in the measured BoQ sections.
• Risk allowance: a named provision for an identified risk event, valued by expected value or a stated method, and linked to the risk register.
• Contingency: an unallocated reserve for residual uncertainty, expressed as a percentage of the base cost or a lump sum, and held by the employer unless the contract states otherwise.

Each layer has a different governance mechanism. Base cost is released through the standard valuation of measured work. A risk allowance is released only when the risk event occurs and the drawdown criteria are met. Contingency is held back until the employer authorises its use, typically at practical completion or at defined project milestones.

In a cost plan, each allowance should carry four pieces of metadata: the risk register ID, the risk owner, the valuation method (expected value, quotation, dayworks rate, or schedule of rates), and the assumptions on which the figure rests. Without those four elements, the allowance is not auditable and cannot be defended at tender or during a post-contract review. Maintaining an internal register that maps every allowance to a single mechanism and owner prevents double counting and keeps drawdown auditable — a practice that experienced QS teams treat as non-negotiable.

How a risk allowance differs from contingency and risk premiums

These three mechanisms are frequently conflated, and conflating them creates governance problems that surface at the worst possible moment: during tender levelling or a post-contract dispute.

The decision rule is straightforward. Use a risk allowance when you can name the risk, assign a probability and an impact range, and define a drawdown mechanism. Use contingency when the risk is real but not yet identifiable enough to model. Use a risk premium label only when you are describing cost that the contractor has absorbed into their own rates and that will not be released or adjusted post-contract.

The stage of the project matters. At RIBA Stage 2 or early Stage 3, information is sparse and contingency percentages are appropriate for much of the residual uncertainty. As design develops toward Stage 4 and the BoQ is prepared, named risks should migrate from contingency into discrete allowance lines, each with its own valuation method. Contingency should shrink as allowances grow more specific.

Pro Tip: Stacking is the most common double-counting error: a risk appears as both a provisional sum and a contingency percentage applied to the same scope. Maintain an internal split and a clear mapping between each risk item and the single mechanism used to carry it. If a risk is in the allowance register, it must be removed from the contingency base.

Good contingency governance also requires clarity on whether the fund is an owner reserve or a contractor contingency, what categories of cost are eligible, and what the approval process for drawdown looks like. Without those rules written down, disputes are almost inevitable.

Where and how to show a risk allowance in an NRM2-aligned BoQ

Placement and labelling are where many BoQs fall short. A risk allowance that is buried in a measured section, or labelled ambiguously, will be priced differently by every tenderer — destroying comparability before the returns even arrive.

NRM2 gives you three legitimate options for presenting an allowance:

• Separate allowance line in the BoQ summary: the clearest approach. A dedicated line item in the summary bill, labelled with the risk description, the risk register ID, and the valuation method. Tenderers price it as a lump sum or leave it as a QS-inserted figure, depending on the instruction.
• Provisional sum (defined or undefined): used when the scope is partially known. A defined provisional sum carries enough information for the contractor to price preliminaries; an undefined sum does not. NRM2 requires you to state which type applies. Use a provisional sum when the risk event will generate measurable work; use an allowance line when the risk is a cost provision rather than a scope of work.
• BoQ preface note with cross-reference: when the allowance is held by the employer and not offered to tenderers for pricing, a clear preface note explaining the allowance, its basis, and the drawdown mechanism is the minimum requirement. This approach is common for employer-held risk reserves on NRM2-aligned cost plans.

For each allowance line, the metadata to include in the BoQ or its accompanying notes is:

• Risk register ID (e.g. R-014)
• Risk owner (employer, contractor, or named party)
• Valuation method (expected value, quotation, dayworks, schedule of rates)
• Drawdown route (instruction required, evidence required, approvals required)
• Inclusions and exclusions (supply only, supply and delivery, or supply, delivery and installation)

Suggested heading wording for a BoQ allowance line: "Allowance for [risk description] — Risk ID R-014 — valued by [method] — refer to Risk Register and Drawdown Protocol dated [date]." Avoid vague labels such as "risk allowance" or "contingency sum" with no further description. Those labels guarantee tender variance because each contractor will interpret the scope differently.

For guidance on how construction contracts treat provisional sums and allowances in UK contracting practice, the placement rules above align with standard JCT and NEC3/4 mechanisms.

How to quantify a risk allowance from the project risk register

The expected value method is the professional standard for sizing a risk allowance, and it is far superior to a percentage guess — even a light-touch model creates a paper trail for negotiation and helps governance burn down as design matures. A traceable expected-value approach linked to the risk register is what separates a defensible allowance from a number pulled from experience.

Step-by-step expected value method

1. Identify the risk event from the risk register. Give it a unique ID and a plain-language description (e.g. "Latent ground contamination requiring additional remediation").
2. Assign a probability. Use the risk register's agreed probability scale (e.g. 10%, 30%, 50%, 70%, 90%) or a three-point estimate (low/most likely/high). Be explicit about the basis — site investigation data, historical precedent, or professional judgement.
3. Estimate the impact range. Produce a low, most likely, and high cost impact. For construction risks, the most likely figure is often used as the base; the high figure informs the contingency buffer above the allowance.
4. Calculate expected value: Probability × Most Likely Impact = Expected Value. Where a three-point estimate is used: EV = (Low + 4 × Most Likely + High) ÷ 6 × Probability.
5. Apply a judgement adjustment. If the risk is correlated with other risks (e.g. ground conditions affect both substructure and drainage), uplift the expected value to reflect correlation. Document the adjustment and its rationale.
6. Record all inputs and assumptions in the risk register and the cost plan narrative. The figure in the BoQ should be traceable back to those inputs without any additional explanation.

Alternative methods when data is sparse

At early project stages, or for risks where probability and impact data are genuinely unavailable, two pragmatic alternatives are acceptable — but both should be replaced by an expected value calculation as soon as better information exists.

Element-specific percentage bands: apply a percentage to the relevant measured element (e.g. Use published benchmarks or your firm's historical data to calibrate the band. This approach is appropriate at RIBA Stage 2 but should be replaced by a named allowance by Stage 4.

Historical benchmark approach: compare the risk profile of the current project against completed projects with similar characteristics and use the outturn allowance as a starting point. This works well for programme risk and inflation risk where historical data is plentiful. For benchmarking allowances against historical projects, calibrated percentage bands from comparable schemes provide a defensible starting point.

Pro Tip: Record the method used for each allowance in the cost plan narrative. When the allowance is challenged at tender — and it will be — you need to show not just the number but the reasoning. A one-paragraph note per allowance line takes five minutes to write and saves hours in tender queries.

What to include and exclude when pricing a risk allowance

This is where BoQ drafting errors cluster. The pricing boundary of an allowance line must be explicit, because under standard UK contract practice and NRM2, allowances typically cover net supply cost only. Contractor labour, handling, overhead and profit are frequently excluded unless the BoQ wording states otherwise.

The default position under common NRM2 practice is:

• Included: net supply cost of materials or goods; delivery to site where stated.
• Excluded (unless explicitly stated): contractor labour for installation, handling and fixing; site management and supervision; contractor's preliminaries attributable to the risk work; overhead and profit on the allowance sum.

That default creates a problem if the risk event involves installation work, because the contractor will need to add labour and prelims on top of the allowance figure. If those additions are not anticipated in the cost plan, the outturn cost will exceed the allowance. The solution is to state the pricing basis explicitly in the BoQ wording.

A short example clause you can adapt:

Additional points to address in the BoQ wording:

• Whether VAT is included or excluded (typically excluded in UK construction contracts, but confirm for the specific procurement route).
• Whether the allowance is fixed or subject to fluctuation (particularly relevant for multi-year projects under NRM2 cost plans that carry inflation risk).
• Whether the contractor is required to submit a quotation before the allowance is released, or whether dayworks or a schedule of rates applies.

Pro Tip: If the risk event involves specialist subcontract work, consider whether a Prime Cost Sum is more appropriate than a risk allowance. A PC Sum gives the contractor a defined mechanism for adding their attendance and profit, which avoids the pricing ambiguity that an allowance line can create.

Drafting assumptions, valuation mechanisms and the drawdown process

The most common dispute trigger in allowance management is the "allowance gap": the point at which the employer believes the allowance covers one thing and the contractor believes it covers another. Unclear drafting is the root cause in the majority of cases, and it is entirely preventable.

A defensible drawdown procedure rests on four drafting elements:

• Valuation mechanism: state whether the allowance will be valued by quotation, dayworks, a schedule of rates, or a combination. The mechanism should match the nature of the risk work.
• Approvals required: name the parties who must authorise drawdown (employer, contract administrator, QS) and the sequence of approvals.
• Documentary evidence: specify what the contractor must submit to trigger drawdown — quotations, dayworks sheets, material invoices, or a combination.
• Timing: state when the allowance can be drawn (before, during, or after the risk event) and any notification requirements.

The audit checklist for approving drawdown should include:

• Written instruction from the contract administrator confirming the risk event has occurred.
• At least two competitive quotations for supply items above a stated threshold (typically £5,000 on commercial projects).
• Comparison of quotations against the original allowance figure, with a written explanation of any variance.
• Risk owner sign-off confirming the drawdown is within the scope of the original risk register entry.
• Updated cost plan showing the allowance balance after drawdown.

For document control and audit trail management on NRM2-aligned BoQs, maintaining a version-controlled allowance register alongside the cost plan is the most reliable way to keep drawdown auditable.

How to check and normalise risk allowances during tender analysis

Tender returns rarely treat allowances consistently. One contractor prices the allowance as supply only; another includes installation; a third absorbs the risk into their preliminaries and returns a nil rate against the allowance line. Without a structured normalisation process, you cannot compare tenders on a like-for-like basis.

The normalisation workflow starts before the returns arrive. The BoQ preface should require tenderers to confirm:

• How they have priced each allowance line (supply only, supply and install, or included elsewhere).
• Whether their preliminaries include any risk provision not shown in the allowance lines.
• The programme duration on which their preliminaries are based.
• Whether overhead and profit is applied within rates, within preliminaries, or as a separate addition.

When returns arrive, work through the following normalisation checklist:

• Align preliminaries: convert all preliminary costs to a common programme-weeks basis. A contractor pricing on 52 weeks versus one pricing on 44 weeks will show a significant prelims difference that has nothing to do with efficiency.
• Align OH&P application: establish whether each tenderer has applied overhead and profit within trade rates, within preliminaries, or as a separate percentage. Adjust to a common basis before comparing totals.
• Reconcile allowance lines: for each allowance line, confirm whether the tenderer has priced it, left it as a QS-inserted figure, or absorbed it elsewhere. Any "included elsewhere" statement requires a clarification query.
• Expose hidden allowances in prelims: preliminaries can carry hidden risk allowances for temporary works, enabling works, and stakeholder management. If a contractor's prelims look unusually high relative to their trade rates, investigate whether risk has been migrated into that section.

Query templates to issue to tenderers:

1. "Please confirm whether your rate against Allowance Line [X] (Risk ID R-014) includes supply only, or supply, delivery and installation. If included elsewhere, please identify the bill page and item reference."
2. "Please confirm the contract programme duration on which your preliminaries are based and identify any risk provision included within your preliminary costs that is not shown against a named allowance line."
3. "Your rate against Item [Y] appears to be nil. Please confirm whether this item is included within another rate or section, and provide the reference."

Nil rates and "included elsewhere" statements should never be accepted without a traceable cross-reference. A priced BoQ read-through requires reconciling totals back to bill pages and confirming that every cross-reference is genuine. Treat any unresolved nil rate as a levelling adjustment item, not a saving.

Common BoQ mistakes with risk allowances and red flags in tender returns

Experienced QSs develop a pattern-recognition instinct for allowance problems. These are the errors that appear most frequently, and the action each one requires.

Frequent drafting errors:

• Stacking allowances and contingency for the same scope: a provisional sum for ground investigation plus a contingency percentage applied to the same element. Remove the overlap before issuing the BoQ.
• Undefined provisional sums with no stated valuation method: each contractor will price the underlying uncertainty differently, destroying comparability. Require tenderers to state their intended pricing methodology for undefined sums.
• Vague allowance labels: "risk allowance — £50,000" with no risk description, no register ID, and no drawdown rule. Rewrite before issue.
• Allowance inclusions/exclusions not stated: the default (supply only) is not universally understood. State it explicitly every time.
• No version control on allowance changes: when the risk register is updated during design development, the BoQ allowances must be updated to match. An allowance register that is out of sync with the risk register is a governance failure.

Red flags in tender returns:

• Unusually low rates on high-uncertainty items: the contractor may have priced the risk elsewhere (in prelims or in a qualification) or may be planning to claim the difference as a variation. Issue a clarification query before accepting the rate.
• High prelims with low trade rates: a classic sign that risk has been migrated into preliminaries. Investigate before normalising.
• Vague qualifications: statements such as "rates are subject to site conditions" or "allowances are indicative only" are red flags. Require the contractor to either price the risk explicitly or confirm that their rate is unconditional.
• Nil rates against allowance lines without explanation: treat as a levelling item. Do not assume the contractor has included the cost elsewhere.
• Allowance lines priced above the QS estimate with no explanation: the contractor may have a better understanding of the risk than the cost plan reflects. Ask for their basis before adjusting downward.

For each red flag, the action is the same: issue a written clarification query, require a written response, and document the outcome in the tender report. Never normalise silently — every adjustment must be recorded and explained.

Worked example: converting a risk register entry into a BoQ allowance

Risk event: Latent ground contamination requiring additional remediation beyond the scope of the Phase 2 Environmental Site Assessment.

Risk register entry: Risk ID R-022, Owner: Employer, Stage: RIBA Stage 4, Status: Open.

Calculation:

The judgement uplift from £15,750 to £18,000 reflects the correlation between ground contamination and the drainage diversion allowance (Risk ID R-023), which would be triggered by the same ground event. That correlation is noted in the cost plan narrative.

NRM2-style BoQ snippet:

The metadata to include alongside this line in the BoQ or its accompanying schedule:

• Risk register ID: R-022
• Risk owner: Employer
• Valuation method: competitive quotation
• Drawdown trigger: written instruction from contract administrator confirming contamination identified during excavation
• Inclusions: specialist remediation supply, disposal, and attendance
• Exclusions: main contractor labour, plant, prelims, OH&P

This level of documentation means that when the risk event occurs on site, there is no ambiguity about what the allowance covers, who authorises drawdown, and what evidence is required. For residential projects where latent condition allowances are particularly common, setting out quantities correctly from the outset makes this kind of traceability much easier to maintain.

Practical pre-issue QS checklist for BoQs covering risk allowances

Run through this checklist before issuing any BoQ or tender document that contains risk allowances or provisional sums.

1. Link every allowance to a risk register ID. No allowance line should appear in the BoQ without a corresponding entry in the project risk register. If the register does not have an entry, create one before issuing.
2. State the valuation method for each allowance. Quotation, dayworks, schedule of rates, or expected value — whichever applies. The method must appear in the BoQ wording, not just the cost plan narrative.
3. Confirm inclusions and exclusions explicitly. Do not rely on the NRM2 default. State whether the allowance covers supply only, supply and delivery, or supply, delivery and installation. State whether OH&P is included or excluded.
4. Provide drawdown rules. Who authorises drawdown? What evidence is required? What is the notification period? These rules must appear in the BoQ preface or the contract particulars.
5. Check for stacking. Cross-reference every allowance line against the contingency base. If a risk appears in both, remove it from one. Maintain the internal mapping register.
6. Confirm normalisation rules for tender. The BoQ preface should state how tenderers are required to price allowance lines (supply only, or inclusive of all costs) and what information they must provide about any risk provision in their preliminaries.
7. Version-control the allowance register. Every change to an allowance — whether triggered by a design update, a risk register revision, or a client instruction — must be logged with a date, a reason, and the name of the person who authorised the change.
8. Ask the project team: Has the risk register been reviewed since the last cost plan revision? Are there new risks that should generate new allowance lines? Have any risks closed that should be removed from the BoQ?
9. Ask tenderers (at pre-tender meeting or in the BoQ preface): Will you price allowance lines as supply only or inclusive of all costs? Are there any risk provisions in your preliminaries that are not shown against a named allowance line? What programme duration have you used for your preliminary costs?
10. Log and version allowance changes during cost plan revisions. When the cost plan is revised — at each RIBA stage gate or following a value engineering exercise — update the allowance register, update the risk register, and record the delta between versions. The transition from cost plan to BoQ is where allowances most often get lost or duplicated; a version-controlled register prevents that.

A practitioner's perspective on managing risk allowances

The most revealing moment in any tender reconciliation is not the bottom-line comparison — it is what happens when you ask each tenderer to explain their allowance lines. A contractor who has genuinely priced the risk will give you a coherent answer: a probability, an impact estimate, a method. A contractor who has buried the risk in their prelims or absorbed it into a rate will give you a vague qualification and a request to discuss.

That asymmetry is why the expected-value approach matters so much in practice. When your allowance is built from a probability and an impact range, you have a framework for the conversation. You can ask the contractor whether they agree with your probability assessment, whether their site experience suggests a different impact range, and whether their prelims include any provision for the same risk. That conversation is productive. The alternative — two parties arguing about whether a lump sum is "reasonable" — rarely is.

The governance point that clients most often resist is the drawdown approval process. Clients want flexibility; they do not want to sign off every small release. The practical answer is a tiered approval threshold: releases below a stated value (say, £5,000) can be approved by the QS alone; releases above that threshold require the contract administrator and the employer's representative. That structure gives the client control over significant expenditure without creating a bureaucratic bottleneck for minor risk events.

When presenting allowances to clients, avoid the temptation to aggregate them into a single "risk pot." Clients who see a single risk line in a cost report have no way to understand what it covers or how it is being managed. A short allowance schedule — risk ID, description, original allowance, amount drawn, balance remaining — takes minutes to produce and transforms the client's understanding of where their contingency is going.

Quantiflow makes NRM2-aligned BoQs with traceable risk allowances faster to produce

Producing a BoQ where every allowance line is linked to a risk register entry, carries a stated valuation method, and is version-controlled through design development is exactly the kind of structured, auditable output that takes disproportionate time to produce manually. Quantiflow automates the NRM2-aligned quantity takeoff and BoQ generation from PDF architectural drawings, so your measured sections are produced accurately and quickly — freeing the time you need to focus on the risk allowance governance that actually requires professional judgement.

The platform's audit log and revision tracking mean that every change to a BoQ line — including allowance updates triggered by risk register revisions — is recorded with a timestamp and a user reference. That traceability is built in, not bolted on. For QS teams who spend hours reconciling tender returns, Quantiflow's structured BoQ output means allowance lines are consistently labelled and positioned, so levelling starts from a clean baseline rather than a patchwork of inconsistent formats.

Quantiflow runs from £39/month on the Solo plan, with Business and Enterprise tiers for larger teams. Quantiflow and see how much faster a traceable, NRM2-aligned BoQ can be produced.

Sources

These are the core references to consult when preparing, reviewing, or defending risk allowances in a UK BoQ context.

• RICS
• Contingency and Risk Allowances in Cost Plans | Rate QS Insights

When preparing a BoQ in the UK, NRM2 is the governing measurement standard. Any allowance presentation that departs from NRM2 conventions should be flagged in the BoQ preface with an explanation of the departure and the alternative approach adopted. Tenderers and contract administrators will expect NRM2 alignment as the default; deviations create ambiguity that costs time and money to resolve.

Recommended

• How construction contracts use BoQ: a UK professional's guide
• Types of bills of quantities: a UK professional's guide
• How cost plans evolve to BoQ: a UK QS guide
• KSQtechnology.com alternatives for UK quantity surveyors