Optimism Bias

Section 1

Purpose

Optimism bias (OB) is the systematic and documented tendency of project teams to underestimate costs and programme durations, and to overestimate benefits and the achievability of project objectives. It is not a project-specific risk — it is a human behavioural pattern that affects all projects regardless of how carefully individual risks are identified. Both RICS and HM Treasury require it to be addressed explicitly and separately from the risk contingency in any cost estimate.

The primary reference is HM Treasury Supplementary Green Book Guidance on Optimism Bias (Mott MacDonald, 2002), which established the empirical basis for OB uplifts through analysis of hundreds of large public sector projects. The RICS Optimism Bias guidance note (2015) adapts this framework for the QS profession. For public sector clients, applying an OB uplift is a requirement of the Green Book appraisal process. For private sector clients, it represents best practice that protects the QS’s professional position and the client’s budget integrity.

The critical distinction that QS practitioners must understand: optimism bias is applied to the base cost estimate BEFORE the risk allowance is added — not on top of it. OB and risk contingency are complementary, not interchangeable. A cost plan that carries a risk contingency but no OB allowance is still systematically understated.

Section 2

Key Principles

Optimism bias is not the same as risk contingency. Risk contingency covers identified individual risks (quantified via EMV, three-point estimating, or Monte Carlo — see GN-FE-04). OB covers the general, systematic underestimation embedded in the base cost estimate before any individual risks are considered. Both must be present as separate, named lines in a compliant public sector cost plan.
OB uplifts are defined by project type. HM Treasury identifies six categories, each with empirically derived upper and lower percentage bounds for capital cost and works duration. The QS must identify the correct project type at the outset. If a project contains both standard and non-standard elements that cannot be physically separated (and the non-standard element exceeds 35% of capital value), a blended OB figure must be calculated.
Always start with the upper bound and earn the right to reduce it. The upper bound represents the average historical overrun for a project of that type with no active management. The lower bound is achievable by contract award for a well-managed project with robust scope definition, experienced team, and independent verification. Starting with the lower bound is a common mistake and a breach of Green Book methodology.
OB reduces as the project matures. At Strategic Outline Business Case (SOBC) stage: apply upper bound. At Outline Business Case (OBC): apply mitigation factors based on evidence of active management. At Full Business Case (FBC) / contract award: aim for lower bound, supported by Gateway Review verification.
OB applies to programme duration as well as capital cost. Each project type has separate upper and lower bounds for works duration. A QS advising on programme risk must apply the works duration OB and present it alongside the cost OB in the feasibility report.
The 21 contributory factors identify the root causes of optimism bias. They fall into four groups: Procurement (contract complexity, late contractor involvement, poor contractor capability, disputes, information management); Project-specific (design complexity, degree of innovation, environmental impact); Client-specific (inadequacy of the business case, large number of stakeholders, funding availability, PM team capability, poor project intelligence); and External (PR/community opposition, site characteristics, permits and consents, political, economic, legislation, technology). The single largest contributor historically is inadequacy of the business case — accounting for 22–52% of recorded optimism bias.
Mitigation factors reduce the OB uplift. For each contributory factor, a mitigation value of 0.0 to 1.0 is assigned (0.0 = not managed at all; 1.0 = fully managed and mitigated). The mitigation evidence must be clear, tangible, and independently verifiable. Mitigation claimed without evidence will not survive a Gateway Review.

HM Treasury Optimism Bias Uplifts by Project Type:

*For outsourcing, OB is measured against operating expenditure, not capital cost.

Section 3

Practical Application

Follow these five steps to apply optimism bias to a project cost estimate:

Step 1

Determine the project type. Assess whether the project is Standard or Non-Standard. A project is Non-Standard if it is innovative, predominantly unique, or involves high construction complexity (e.g. a specialist hospital with complex M&E, a major refurbishment, or a project over a live railway). If the project has both standard and non-standard elements that cannot be physically separated and the non-standard element exceeds 35% of capital value, calculate a blended OB: multiply each element’s upper bound OB by its proportion of the total capital value and sum.

Step 2

Start with the upper bound OB percentage for the identified project type. Apply this to the base cost estimate (the estimated present value of capital costs before risk allowance is added). This is the unmanaged estimated final cost. Example: Standard Building base cost £100m, upper bound 24% → unmanaged estimated final cost £124m.

Step 3

Assess each of the 21 contributory factors and apply a mitigation value (0.0–1.0) to each. For each factor: 0.0 = no management in place; 0.5 = partial management with some evidence; 1.0 = fully managed with independent verification. Calculate the weighted contribution of each factor to the total OB uplift and reduce it by the mitigation factor. Sum the residual contributions to produce the managed OB percentage. Record the evidence for each mitigation claim — it will be required at Gateway Review.

Step 4

Apply the managed OB factor to the base cost estimate. OB-Adjusted Cost = Base Cost × (1 + Managed OB%) + Cost of Risk Management. Present the OB uplift as a separate, named line in the cost plan summary — not buried in the construction works estimate or combined with the risk contingency.

Step 5

Apply OB to programme duration. Using the works duration bounds for the project type, calculate the OB-adjusted programme and report P50 and P80 completion dates. For time-critical projects, run this alongside a full SQRA (see GN-FE-04). Present the duration OB in the feasibility report alongside the cost OB.

Section 4

Common Mistakes to Avoid

Confusing OB with risk contingency. Both must appear as separate named lines. Combining them into a single “contingency” figure obscures the basis of the allowance and will fail scrutiny at Gateway Review or RICS audit.
Starting with the lower bound OB. The lower bound is the target for a well-managed project at contract award — not the starting point at feasibility stage. Starting low and hoping to justify it later is a methodological error.
Applying OB to the total project cost including risk. OB is applied to the base cost estimate — the present value of capital costs before risk allowance. Applying OB on top of the risk contingency double-counts the adjustment.
Claiming mitigation without evidence. A mitigation factor of 1.0 on every contributory factor — reducing OB to near zero — without supporting evidence will not survive independent review. Mitigation must be specific, documented, and independently verifiable.
Forgetting programme duration OB. Cost OB without a corresponding works duration OB gives the client an incomplete picture of their exposure. Both must be reported.
Treating OB as a public sector only concern. While Green Book compliance is a statutory requirement for public sector clients, the underlying bias affects all projects. Applying OB methodology on private sector schemes demonstrates rigorous cost management and protects the QS’s professional position.

Section 5

APC Competency & Quick Reference

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

What is optimism bias and why must it be treated separately from risk contingency?

Optimism bias is the systematic, documented tendency of project teams to underestimate costs and durations regardless of how carefully they plan. It arises from cognitive bias, incomplete information, and pressure to present an optimistic case. It is separate from risk contingency because risk contingency covers identified individual risks (probability × impact); OB covers the general underestimation embedded in the base cost estimate itself. OB is applied to the base cost BEFORE the risk allowance is added. Both must appear as separate named lines in any compliant public sector cost plan.

What are the six HM Treasury project types and their capital cost OB upper bounds?

Standard Buildings (offices, hospitals, prisons): 24%. Non-Standard Buildings (specialist hospitals, major refurbishment, unique buildings): 51%. Standard Civil Engineering (most new roads): 44%. Non-Standard Civil Engineering (innovative rail/road, upgrades): 66%. Equipment/Development (ICT systems, software, manufactured equipment): 200%. Outsourcing (FM, ICT services): 41% of operating expenditure. Always start with the upper bound and reduce through documented mitigation of the 21 contributory factors.

What is the single largest contributory factor to optimism bias, and what does it mean in practice?

The single largest contributor is inadequacy of the business case, which accounts for 22–52% of recorded optimism bias across the Mott MacDonald 2002 study. In practice this means: scope not clearly defined; not all stakeholder requirements captured; output specifications vague; key services or facilities overlooked. The remedy is rigorous scope definition early, a complete and signed-off project brief, formal stakeholder engagement, and Gateway Review verification before the business case is approved. A QS who identifies an incomplete brief at feasibility stage and documents this in writing is managing this factor proactively.

Section 6

Feasibility Stage Checklist

☐

Project type identified from HM Treasury six categories — Standard or Non-Standard (or blended if applicable)

☐

Upper bound OB percentage applied to base cost estimate as the starting point

☐

All 21 contributory factors reviewed — mitigation values assigned with supporting evidence documented

☐

Managed OB% calculated and OB uplift presented as a separate named line in the cost summary (not combined with risk contingency)

☐

OB applied to base cost BEFORE risk allowance — sequence confirmed

☐

Works duration OB calculated and reported alongside cost OB

☐

Blended OB calculated where project contains both standard and non-standard elements (>35% non-standard)

☐

OB allowance and methodology documented in feasibility report for Gateway Review or client audit purposes

Section 7

CPD Learning Outcomes

Identify the correct HM Treasury project type, apply the five-step optimism bias calculation process, and present a defensible OB-adjusted cost estimate with the uplift as a separate named line, correctly sequenced before the risk allowance.
Review and score all 21 contributory factors to optimism bias, apply documented mitigation values, and produce a managed OB percentage supported by independently verifiable evidence.
Distinguish between optimism bias, risk contingency, and project-specific risk allowances, and explain their correct sequencing in a public sector cost plan to a client, senior colleague, or APC assessor.

Section 8