Cost Limit & Budget Setting

Section 1

Purpose

Establishing the cost limit and setting the project budget are among the most consequential tasks the QS performs at feasibility stage. The cost limit is the maximum sum the client is prepared to commit to the project at the point of sanction. The project budget is the QS’s structured allocation of that sum across all cost components — construction works, contingency, fees, statutory costs, inflation, and other development expenditure. Both must be set with rigour, documented in writing, and formally agreed with the client before design proceeds.

NRM 1 (2nd edition, reissued October 2022) defines the cost limit as the authorised budget for the project and prescribes how it must be structured. A cost limit that has been derived from the Order of Cost Estimate, reviewed against benchmark data, and agreed in writing provides the baseline against which all subsequent cost plans are measured. When a cost limit is set informally, or simply taken from the client's hoped-for figure without QS input, it often leads to cost overruns and disputes.

The RICS Cost Prediction Professional Statement (reissued June 2024) requires that any cost prediction communicated to a client — including the recommended budget — is accompanied by a statement of its basis, assumptions, exclusions, and accuracy range. This obligation applies equally to the initial budget recommendation and to any subsequent revision.

Section 2

Key Principles

The cost limit is the client’s authorised maximum expenditure. It is set following QS review of the Order of Cost Estimate and must reflect a realistic, evidence-based assessment of the total project cost — not the client’s preferred or aspirational figure. If the client’s stated budget is below the QS’s estimate, this must be reported to the client in writing immediately, with options to resolve the gap (scope reduction, specification change, phasing, or budget increase).
The NRM 1 cost limit structure separates the project cost into defined components: (1) Construction Works Estimate (measured works + preliminaries + contractor OHP); (2) Project/Design Team Fees; (3) Other Development/Project Costs (statutory, planning, surveys, decant, furniture and equipment); (4) Risk Allowances (design contingency + construction risk); (5) Inflation Allowance; (6) VAT (if applicable and not recoverable). Each component must be separately estimated and documented.
Contingency and risk allowances are not the same thing and must not be conflated. The design contingency covers the cost of design development and scope growth as the project advances — it reduces as design is resolved. The construction risk allowance covers identified project risks that may or may not crystallise. A general contingency without a defined risk basis is not an acceptable approach under NRM 1.
The budget must be actively managed, not merely set and filed. The QS’s role is to track actual and committed expenditure against each budget component throughout the project and to report variances promptly. A budget that is set at feasibility and not revisited until practical completion is not cost management — it is cost recording.
Inflation is a discrete budget component and must not be buried in the construction works estimate. At feasibility stage, the inflation allowance should cover the period from the cost plan base date to the mid-point of the construction programme. The basis for the inflation rate (BCIS TPI forecast, fixed assumption, or other) must be stated.
Where the client has a fixed or capped funding envelope (e.g. a grant, a board-approved capital allocation, or a development appraisal constraint), the QS must advise explicitly whether the proposed scope is achievable within that envelope. If it is not, the QS must not simply compress the estimate to fit — this creates a false budget and exposes both the client and the firm to significant risk.

Section 3

Practical Application

Follow these steps to establish a compliant cost limit and structured project budget at feasibility stage:

Step 1

Obtain and review the client’s stated budget or funding envelope. Record the figure, its source (e.g. board approval, development appraisal, grant award), and any conditions attached to it. Do not assume the client’s stated figure is a reliable cost limit — it may be an aspirational target, an inherited estimate, or a figure derived without QS input.

Step 2

Complete the Order of Cost Estimate (per GN-FE-01). This is the evidence base for the budget recommendation. The OCE central estimate becomes the starting point for the cost limit. Present it as a range with the accuracy bounds required by the Cost Prediction PS.

Step 3

Build up the full NRM 1 project budget. To the Construction Works Estimate, add each component separately: Project/Design Team Fees (confirm percentage or lump sum with PM; typically 8–15% of construction cost depending on project type and complexity); Other Development Costs (surveys, statutory fees, planning, decant, furniture and equipment — obtain client confirmation of scope); Risk Allowances (design contingency 10–15% at Stage 1; construction risk from the risk register); Inflation Allowance (state rate and basis); VAT (confirm recoverability with client’s finance adviser). Present the full budget summary in a structured table.

Step 4

Test the budget against the client’s funding envelope. Compare the recommended budget total with the client’s stated figure. If a gap exists, quantify it and present options: (a) increase the budget; (b) reduce the scope; (c) reduce the specification; (d) phase the project; (e) review the programme to reduce inflation exposure. Do not recommend proceeding if the gap cannot be bridged without a credible plan.

Step 5

Advise on value management opportunities. At this stage, identify areas where cost can be reduced without material impact on the brief. Consider: structural system options, envelope specification, M&E strategy, phasing, procurement route, and sustainability targets vs cost. Refer to RICS Value Management and Value Engineering (1st edition) for the structured VM/VE framework.

Step 6

Obtain written approval of the cost limit from the client. Issue the budget summary in writing — as part of the feasibility report or as a standalone budget sanction document. Request written confirmation that the client has reviewed, understood, and approved the cost limit, including the accuracy range and the stated assumptions and exclusions. File the signed/acknowledged document on the project file.

Step 7

Establish the budget monitoring framework. Set up the cost report structure that will track budget vs estimate vs commitment vs final cost for each budget component throughout the project. Agree the frequency of cost reporting with the client and PM. The first formal cost report should be issued at or shortly after cost plan 1 (RIBA Stage 2).

Section 4

Common Mistakes to Avoid

Accepting the client’s aspirational budget as the cost limit without QS review. If the client’s figure is below the OCE, the shortfall must be reported in writing immediately. Proceeding without doing so is a dereliction of the QS’s advisory duty and a likely source of future dispute.
Conflating design contingency and construction risk allowance. These are separate budget components serving different purposes. Design contingency reduces as design is resolved; construction risk is linked to the risk register. Lumping them together as a single “contingency” line makes the budget opaque and makes monitoring ineffective.
Burying inflation within the construction works estimate rather than treating it as a discrete budget component. This obscures the inflation assumption, makes it impossible to update it when market conditions change, and understates the construction works cost.
Failing to confirm which items are excluded from the budget. FF&E, IT, tenant fit-out, section 106/278 obligations, and VAT are commonly excluded. If excluded items are not explicitly listed, the client may assume they are included — and the QS will be held responsible for the shortfall.
Not obtaining written sign-off on the cost limit. A budget agreed verbally in a meeting is not a budget — it is a conversation. The QS must always issue the budget in writing and obtain written acknowledgement. This is the baseline against which all subsequent cost performance will be measured.
Setting the budget and then failing to manage it. Budget setting without ongoing cost reporting and proactive variance analysis is a fundamental failure of the QS’s cost management role. The budget must be a living document, reviewed at every project milestone.

Section 5

APC Competency & Quick Reference

This guidance note is relevant to the following RICS APC competencies: Cost Management (, Levels 1–3); Client Care (B2, Levels 1–2); Risk Management (, Levels 1–2); Financial Management (, Level 1).

What is the difference between a cost limit and a project budget, and how are they established at feasibility stage?

The cost limit is the maximum authorised expenditure approved by the client — it is the sanction figure against which cost performance is measured. The project budget is the QS’s structured allocation of that sum across all NRM 1 cost components: Construction Works Estimate, Project/Design Team Fees, Other Development Costs, Risk Allowances (design contingency + construction risk), Inflation Allowance, and VAT. At feasibility stage, the cost limit is derived from the Order of Cost Estimate central figure, tested against the client’s funding envelope, and formally agreed in writing before design proceeds.

What should the QS do if the client’s stated budget is below the Order of Cost Estimate?

The QS must report the shortfall to the client in writing immediately and quantify the gap. The options available to bridge the gap are: (1) increase the budget; (2) reduce the scope of the project; (3) reduce the specification or quality level; (4) phase the project to split the capital requirement; (5) review the programme to reduce inflation exposure. The QS must not compress the estimate to fit the client’s figure without a substantive basis for doing so — this creates a false budget and is a direct breach of the QS’s duty of care.

What is the difference between design contingency and construction risk allowance, and how do they change as the project develops?

Design contingency covers the anticipated cost growth arising from design development — as the design advances from sketch to technical drawings, scope and detail increase and costs firm up. It reduces progressively: 10–15% at Stage 1, 7–10% at Stage 2, 3–5% at Stage 3. Construction risk allowance covers identified risks on the project risk register that may or may not crystallise during construction — it is linked to specific, quantified risks (probability × impact) and does not automatically reduce as design develops. Both must be reported as discrete budget lines.

Section 6

Feasibility Stage Checklist

☐

Client’s stated budget / funding envelope reviewed — source and conditions recorded

☐

Order of Cost Estimate completed and used as the basis for the budget recommendation

☐

Full NRM 1 budget built up: Construction Works + Fees + Development Costs + Risk + Inflation + VAT

☐

Design contingency and construction risk allowance treated as separate budget lines

☐

Inflation allowance stated as a discrete component — rate, basis, and period documented

☐

Budget tested against client’s funding envelope — any gap reported in writing with options

☐

Exclusions from budget explicitly listed in the report (FF&E, VAT, S106, IT, etc.)

☐

Cost limit formally issued to client in writing — written acknowledgement obtained and filed

Section 7

CPD Learning Outcomes

Build a structured NRM 1 project budget from an Order of Cost Estimate, allocating all cost components — construction works, fees, development costs, contingency, inflation, and VAT — as discrete and documented budget lines.
Identify and report a gap between the QS’s recommended budget and the client’s funding envelope, presenting costed options to bridge the gap in a format suitable for client decision-making.
Distinguish between design contingency and construction risk allowance, explain how each is quantified and how each changes as the project advances through the RIBA work stages.

Section 8