Overview
Riser cupboards, shafts, and plant areas are a common source of repeat fire stopping defects because:
- multiple services pass through (pipes, cables, containment)
- access is constrained
- follow-on works re-open sealed penetrations
The fix is less about one perfect product and more about scope discipline and close-out evidence.
Why risers are a repeat-defect hotspot
Risers and shafts combine three things that create noncompliance:
- high service density (multiple cables/pipes/containment)
- frequent access (maintenance and upgrades)
- poor traceability (what was sealed, with what system, and when)
If you only “seal what you see today”, defects tend to reappear after the next contractor visit.
A scope structure that works
1) Start with a defect register
For each breach, capture:
- unique ID
- location reference
- photo(s)
- plain-language defect note
Defect register fields
| Field | Example | Why it helps |
|---|---|---|
| Defect ID | RS-01-L2-FB-07 | Stable reference for close-out |
| Location | Block A / Riser 1 / Level 2 / Face B | Findable on site |
| Photos | Wide + close-up | Defensible evidence |
| Service type(s) | Cables + tray | Drives suitable system choice |
| Priority | Urgent / Planned | Programme control |
2) Group by defect type
Typical buckets:
- service penetrations (single/multiple)
- linear gaps and joints
- access panels and hatches
- incomplete/compromised boxing-in
2a) Add the common riser defect patterns (so you don’t miss them)
- unsealed multiple-service penetrations
- penetrations through non-fire rated boxing-in (false sense of compliance)
- missing or damaged fire-resisting access hatches
- gaps at slab edges / around trunking routes
- penetrations reopened and left open during reactive maintenance
3) Define inclusions and exclusions
Examples:
- include: resealing penetrations within the compartment line
- exclude: re-routing services (unless agreed)
- exclude: asbestos/lead paint constraints (until surveyed)
Inclusions/exclusions
| Topic | Include/exclude | Why it matters |
|---|---|---|
| Penetrations in compartment lines | Include | Core of the compliance outcome |
| Service re-routing | Exclude unless agreed | Avoids scope creep and design risk |
| Intrusive opening-up | Defined sampling | Controls disruption and assumptions |
| Hazard constraints (asbestos/lead) | Exclude until surveyed | Safety and programme protection |
4) Decide the close-out evidence
At minimum:
- updated defect register (closed/open)
- photos of remedials where practical
- product/system references where relevant
- exceptions list (items requiring follow-on design/access)
How to plan access and sequencing
Access
For multi-site programmes, access logistics can make or break delivery:
- agree access windows per block/area
- plan for permits and isolations (where required)
- keep a clear list of “could not access” items (with re-visit plan)
Sequencing
Riser works often benefit from doing them in a consistent order:
- record and label defects
- remediate penetrations/joints systematically
- verify and photograph close-out
- hand over a tidy register that survives audits
What to include in a scope (so it can be delivered)
When you’re scoping riser remedials, the practical details matter. Consider including:
- access requirements (keys, permits, working hours)
- temporary works / making good expectations
- how services will be protected while works are underway
- minimum evidence requirements per defect ID
- how “newly found” defects will be added to the register (change control)
Scope pack checklist
| Item | Why it matters |
|---|---|
| Register export + photos | Lets crews find and close out defects consistently |
| Access rules and permits | Prevents aborted visits |
| Making-good responsibilities | Clarifies who reinstates finishes/boxing |
| Evidence standard | Avoids “done” with no proof |
| Change-control rule | Newly found defects don’t get lost |
Quality control and hold points
To avoid repeat defects, define basic hold points:
- pre-start: confirm defect register, access plan, and any isolations
- during works: verification before areas are closed up or boxed in
- close-out: updated register + photos + exceptions list
Hold points
| Stage | What gets checked | Typical output |
|---|---|---|
| Pre-start | Register, access plan, isolations | Agreed scope + site plan |
| During works | Verify before close-up/boxing-in | Photos + supervisor sign-off |
| Close-out | Register updated, exceptions listed | Handover pack you can audit |
This stops defects being hidden behind boxing-in or left undocumented.
Close-out pack: what “good” looks like
At handover, aim for a pack that a facilities team can actually use:
- updated defect register (with statuses)
- photos tied to defect IDs
- notes of any areas not accessed
- follow-on actions (e.g. re-routing services, access panels, design queries)
Where possible, include simple labelling and a note for follow-on trades: if you cut through a sealed compartment line, it must be reinstated and recorded before the area is handed back.
Change control (so newly found defects don’t vanish)
On live sites, you will find additional breaches once works start. The key is to agree a simple rule: new defects get a new ID, a location, and an agreed priority - and they only move to “closed” when there’s evidence.
FAQs
Should we fix defects as we find them?
Sometimes (especially obvious open breaches), but for programmes it’s often better to record first, then remediate in a controlled phase so you don’t miss related issues.
How do we stop defects coming back?
Use consistent labelling/records and coordinate follow-on trades. The process is part of compliance.
Related pages
Note
This article is general information. Always align remedials to competent guidance, manufacturer/system requirements, and the building’s fire strategy.