Resources • Fire stopping • defects • remediation
Fire stopping defects & remediation: from raised to verified
A practical checklist for raising defects against failed or incomplete penetrations and joints, prioritising by risk to escape routes, and keeping verification evidence — including the tested system used — attached to the right item.
- Defects
- Prioritisation
- Verification
- Tested systems
- Evidence
Turn failed seals into deliverable work
then verify the re-seal with proof linked to the right penetration
A practical checklist for raising defects against the penetrations and joints that fail or are incomplete, prioritising by risk to escape routes, and keeping verification evidence attached to the right item from raised to verified.
Goal 01
Prioritise by risk
Make severity explicit so scheduling and reporting are consistent. When severity is hidden in notes, a failed seal on a protected escape route and a minor annular gap in a plant room get treated the same — and the work that matters most slips down the list.
Goal 02
Keep context
Defects point back to the penetration record and the survey evidence that raised them. When a defect is tracked in a spreadsheet, that link is severed — the installer doesn't know which item, which barrier, or what the survey showed about the substrate and services.
Goal 03
Verify
Before/during/after evidence, the tested system referenced, and PDF outputs trace back to the same penetration history. "Resolved" means little without proof of which certified system was used, before the finished face hid the build-up — especially when an auditor or client asks six months later.
Teams moving defects into work
Use this when you need repeatable prioritisation across surveyors — especially before scaling fire stopping remediation across multiple buildings or handing work to a different installer.
Installers
Clear scope and item context — each defect links back to the penetration, the survey finding, and the photo evidence so the installer knows exactly which item needs re-sealing, with what, and why.
Clients & auditors
Verification evidence that traces back to the original penetration record — before/during/after photos, the tested system referenced, and PDF outputs that answer "was this re-sealed, with what, and when?" without email chains.
A failed seal on an escape route isn't the same as one in a plant room.
Sort defects by risk to the compartment line everyone can agree on.
Three rules for keeping severity explicit and risk-led, then a rubric to adapt to your own workflow — so a defect protecting a means of escape is worked before a cosmetic one, regardless of where it sits in the list.
Three rules · define · separate · agree
Rule 01
Define severity
Use a simple Low / Medium / High scheme — or equivalent — so severity is reportable and filterable. "See notes" and "needs sealing" are not severity levels. The value comes from the field existing on every defect, not from it being perfect.
Rule 02
Separate "what failed" vs "how urgent"
Keep failure reasons consistent — what was wrong with the seal or joint — then add severity as its own separate field. Mixing them creates labels like "urgently re-seal gap" where the urgency is buried in the description rather than in a dedicated field you can sort on.
Rule 03
Agree the rules upfront
Decide what counts as "High" for your workflow before the first survey — typically defects on compartment lines protecting escape routes — not mid-project when the installer and office are already sorting differently. Write it down; even a brief note is enough to prevent disagreement.
Severity rubric · adapt to your policy
Example Low / Medium / High definitions — a starting point, not a compliance rule
Requires prompt action
Issues your competent person policy treats as urgent — requiring prompt action and clear evidence of closure. Typically includes open or unsealed penetrations on compartment lines protecting escape routes, missing collars on combustible pipes, or breaches that directly affect the barrier's rated performance.
Plan into a visit window
Issues that need remediation but can be scheduled within a planned project or maintenance visit. Typically includes partial batts, short or incompatible sealant, or annular gaps that don't immediately compromise the barrier but will degrade the rating if left.
Bundle or monitor
Minor issues to address during planned maintenance, bundle with a larger visit, or monitor for change. Typically includes cosmetic finishing, very minor sealant gaps, or single-service defects in lower-risk locations that don't affect performance at current state.
Defects should inherit context
which penetration, what failed, what evidence exists, what needs to happen
Three rules for keeping defect context intact, plus the four most common workflow mistakes that sever the link between a fire stopping defect and the penetration evidence that raised it.
Three rules · group · link · scope
Group by site or building
Keep work deliverable: one installer, one visit plan, one clear list of penetrations per building. Mixing items from different buildings in a single remediation visit makes scheduling ambiguous and site prep harder — the crew can't load the right systems and materials efficiently.
Keep defects tied to penetrations
A defect should always point back to the penetration record that created it. The item ID, survey finding, photos, substrate, and severity should be accessible from the defect — not stored separately where they can diverge or get lost between survey and re-seal.
Keep scope clear
Scope creep happens when defects are vague. Make the recommended action explicit on every defect — "Re-seal annular gap to EI 120 batt system" not "fix penetration". Vague scope leads to installers using the wrong system, then disputes at verification.
Common mistakes
Four patterns that sever the link between defect and penetration evidence
01
Detached defects
Defects tracked in spreadsheets lose the penetration context and evidence trail — when the installer arrives on site, they have a list of work but no access to the photos, substrate, or survey finding that raised it.
→ Keep defects in the platform, tied to penetration records
02
Duplicate work items
The same penetration issue appearing in multiple lists — one in the system, one in the PM's spreadsheet, one in the installer's email — creates conflicting status and missed verifications.
→ One source of truth · remove duplicates early
03
Scope drift
Unclear recommended action leads to installers using a different system than expected — then verification disputes. "Fix penetration" vs "Re-seal to EI 120 batt system" are very different jobs.
→ Explicit action + tested system on every defect
04
No verification proof
"Resolved" means nothing without before/during/after evidence and the tested system referenced. The audit question isn't "was it sealed?" but "what evidence proves it was sealed with the right certified system?"
→ Photos + tested system referenced before verify
Audits don't just ask "was it sealed?"
they ask "with what system, and what evidence proves it?"
Four steps from scheduling by visit through to PDF outputs traceable back to the penetration history — and a minimum verification pack that makes client questions and audits straightforward to answer once the finished face hides the build-up.
Four steps · schedule · capture · reference · export
Step 01
Schedule by visit
Plan remediation visits by building or block so work is deliverable on site — one installer, one day, one building, the right systems loaded. Don't mix buildings across a single visit unless the crew is genuinely visiting multiple sites in one trip.
Step 02
Capture before/during/after
Attach before, during and after photos to the penetration record — the during shot matters because the finished face hides the build-up. The evidence needs to be accessible from the penetration history, not reconstructed later from the installer's phone gallery.
Step 03
Reference the tested system
Record which tested or certified system the re-seal used — manufacturer, product, classification and cert reference. "Sealed" on a status field is not enough. The question in six months is "which certified system was used here?" — the answer needs to be in the record.
Step 04
Export from the source record
PDFs and portal outputs should trace back to penetration history — generated from the live record, not assembled manually in Word from screenshots. The output and the history are the same thing, ready to feed the building's safety record.
Minimum verification pack · per penetration
Four fields that make audits and client questions easy to answer
01
Before/during/after photos
Build-up + finished face
The before state, the during shot of the seal build-up, and the finished face — enough to show the gap, how it was sealed, and the result once the finish hides the work.
02
Tested system used
Product + classification
The certified system referenced — manufacturer, product, EI classification and cert reference — tied to the penetration, not a general site note. "EI 120 batt, FIRAS cert" not "sealed".
03
When it was done
Date + visit reference
The date the re-seal was completed and the visit or job reference — so the verification can be placed in the audit timeline alongside the original survey.
04
Who verified
Name + role
Name and role of whoever confirmed the re-seal — where required by your process. "Sealed by installer" is not a verification. A named, responsible individual is.
Close the loop on one building.
Survey → prioritised defects → verification → client outputs.
Run a full cycle on one site so severity, defects, and evidence stay on the penetration record end to end — including the tested system the re-seal used.