Writing a Fire Protection Scope of Works Properly (UK Guide)

Fire protection operates within the framework of the Regulatory Reform (Fire Safety) Order 2005 and, where applicable, the Building Safety Act 2022.

In higher-risk residential buildings, documentation and traceability expectations are significantly more demanding. Procurement documentation may contribute to the "golden thread" information required under the Building Safety Act 2022.

Unclear scope creates:

• Inconsistent pricing
• Inflated risk allowances
• Post-award variation claims
• Programme disruption
• Weak audit defensibility

Across UK housing remediation programmes, a large proportion of commercial dispute arises not from workmanship, but from undefined survey limitations and ambiguous responsibility allocation.

Where scope is issued informally — often via email requests with loosely defined narrative descriptions — pricing inconsistencies and hidden exclusions become more likely. The commercial and compliance risks of that approach are explored in Structured vs Email-Based Fire Tendering.

Scope clarity reduces risk at every stage.

A professional fire protection scope of works should:

• Define what is included.
• Define what is excluded.
• State data limitations.
• Clarify compliance standards.
• Define documentation outputs.
• Allocate responsibility clearly.

If a contractor cannot determine assumptions from your scope, they will price for uncertainty. Uncertainty increases cost.

Within a structured procurement process, scope definition sits at the beginning of the tender sequence. It informs the tender pack, submission format, and evaluation criteria. For a breakdown of how scope integrates into the wider procurement stages, see How Commercial Fire Protection Tendering Works.

1. Building and Asset Context

Define:

• Building type and occupancy
• Height and storey count
• Construction type (where relevant)
• Occupancy constraints (residential, healthcare, education, commercial)
• Access restrictions (permits, security, phased occupation)

Fire protection methodology differs significantly between an occupied residential tower and a vacant commercial unit. Scope must reflect operational reality.

2. Measured Quantities and Survey Data

If issuing survey findings (e.g. fire door inspections or compartmentation surveys), clearly state:

• Survey methodology used
• Sampling limitations
• Access constraints during survey
• Areas excluded
• Date of inspection

Many disputes originate from contractors pricing based on incomplete survey access that was never declared in procurement documents.

Where quantities are estimated, state clearly:

Quantities are indicative only and must be validated prior to installation.

Transparency reduces commercial ambiguity.

3. Defined Standards and Compliance Requirements

Reference relevant compliance frameworks clearly. This may include:

• Alignment with Approved Document B where applicable
• Applicable British Standards (e.g. BS 9999 where relevant)
• Third-party certification expectations
• Manufacturer installation guidance

Avoid generic statements such as "works to be compliant." Define what compliance means in measurable terms.

4. Design Responsibility Allocation

Clarify:

• Is the contractor responsible for design?
• Is design client-provided?
• Are installation details prescriptive?
• Is performance-based compliance required?

Unclear design responsibility is one of the most frequent causes of dispute in active fire system tenders. Responsibility must be defined before pricing.

5. Documentation and Reporting Deliverables

Define evidence requirements at tender stage, not post-award. Specify:

• Photographic capture standards
• Asset tagging requirements
• Digital reporting format
• O&M manual structure
• Certification format and issue timing
• Retention period for records

Under both the Fire Safety Order and Building Safety Act framework, evidence retention may be as critical as physical installation. If reporting standards are not defined, submissions will vary widely in quality.

6. Programme and Access Constraints

State:

• Required completion date
• Phasing requirements
• Working hour restrictions
• Resident communication expectations (if applicable)
• Permit or access control requirements

Programme assumptions significantly affect pricing. If access constraints are unclear, contractors will price for risk.

7. Interface and Coordination Requirements

Fire protection frequently interfaces with:

• Mechanical and electrical penetrations
• Ceiling voids
• Structural elements
• Builders' works
• Ongoing refurbishment packages

Clarify:

• Who is responsible for making good?
• Who coordinates penetrations?
• Who provides builders' openings?
• Who is responsible for reinstatement?

Interface ambiguity compounds during delivery.

Vague narrative descriptions

"Upgrade fire stopping where required" is not measurable scope.

Failure to declare survey limitations

Incomplete access during inspection must be stated clearly.

Undefined documentation expectations

If reporting standards are unclear, evidence quality will vary.

No declared exclusions

Ambiguity around exclusions creates variation exposure.

Copying legacy scopes

Regulatory expectations evolve. Recycled documentation often misses current compliance requirements.

A strong fire protection scope:

• Uses measured schedules
• Declares data limitations transparently
• States compliance frameworks clearly
• Defines evidence output in detail
• Allocates responsibility explicitly
• Aligns with structured procurement sequencing

When structured properly, contractors price based on defined assumptions rather than speculation. This improves pricing accuracy and reduces dispute.

Scope clarity directly influences:

• Pricing consistency
• Variation risk
• Programme reliability
• Reporting quality
• Contractor confidence
• Audit defensibility

Across regulated estate portfolios, procurement decisions increasingly require justification beyond headline cost.

If procuring fire protection works:

• Invest time in scope definition before issue.
• Validate survey completeness.
• Define evidence expectations clearly.
• Allocate design responsibility explicitly.
• Standardise documentation requirements.

Clear scope reduces commercial friction and strengthens regulatory defensibility. Procurement structure begins with scope clarity.

Should we rely solely on a fire risk assessment to define scope?

No. A fire risk assessment identifies hazards and recommendations but rarely provides measured quantities, access limitations, or defined evidence outputs. A scope must convert recommendations into commercially allocable works.

Do passive and active works require separate scopes?

Often yes. Certification standards, design responsibility, testing regimes, and reporting outputs differ significantly between disciplines. Combining them frequently reduces pricing clarity.

Should survey limitations be declared?

Always. Restricted access, sampling, or excluded areas must be stated clearly. Many variation claims arise from assumed data that was never formally allocated during procurement.

How detailed should reporting requirements be?

Define them in measurable terms. Specify photographic standards, tagging protocols, certification format, digital reporting structure, and retention periods. Undefined evidence expectations create inconsistent compliance records.

Can poor scope increase project cost?

Yes. Ambiguity introduces contractor risk allowances and increases the likelihood of post-award variation claims.

How does scope clarity affect regulatory defensibility?

Clear scope documentation strengthens audit resilience. Under the Regulatory Reform (Fire Safety) Order 2005 and the Building Safety Act 2022, procurement documentation may form part of the compliance narrative.