Resources • Fire stopping • evidence • audit trail
How to build a defensible fire stopping evidence trail
The finished seal hides the build-up, so the evidence is captured at the point of work. A practical playbook for item identity, before/during/after photos, tested-system references, and a golden-thread handover that traces back to the same penetration record — not a folder of finished-face photos and PDFs.
- Evidence trail
- During-photos
- Tested systems
- Golden thread
- Handover PDF
A seal-by-seal story —
not a folder of finished-face photos and PDFs
On new work the finished face hides the build-up, so the evidence is captured at the point of work; on a survey you record each seal as found. Lock each penetration's item ID, reference the tested system it was sealed to, and keep its evidence photos attached to the same record.
Goal 01
Outcome
Every penetration keeps one history: capture → system reference → evidence photos → handover. The PDF and export trace back to the same record. Anyone picking up the file can see what was sealed, where, and to which tested system without asking questions.
Goal 02
Make it repeatable
Lock item IDs, reference systems from the catalogue, and capture the during-photo before the seal is closed. A broken link at any stage — renamed item, missing during-photo, no system reference — stops the evidence being defensible.
Goal 03
In Fire Door App
The penetration register, tested systems catalogue, photos, and Client Portal handover all map to the same survey record. Capture on site, reference the system, generate the survey PDF — the evidence trail is built in, not assembled after the fact.
Item identity
Stable item IDs and a consistent compartment line help the same penetration keep one record across time — no duplicates, no guessing which seal is which.
Build-up evidence
Evidence photos attached to the record — as found on a survey, or before/during/after at the point of work, because on new work the finished face hides the build-up that proves the seal was installed correctly.
System reference & export
The tested system, its classification and cert reference, and the survey PDF that traces back to the same underlying record — not assembled manually from separate files.
Use this to spot gaps
before the seal is closed up
Five areas — each a potential break in the chain. If any link is missing, the evidence stops being defensible. Check them while the build-up is still visible, not after the finished face has hidden it.
Five things every penetration record needs
Item identity + location
Stable item IDs, a consistent compartment line, and the substrate the barrier is made of.
Services + tested system
The services passing through, the tested system the seal references, and its classification — all in fields, not buried in free text.
Build-up photos
Evidence photos per item — the seal as found on a survey, or before, during, and after on new work (the during-photo captured while the build-up is still visible, before the finished face hides it).
Exports
Branded survey PDFs and portal handovers generated from the source record — so they trace back to the items, systems, and photos that produced them.
Capture + who/when
Who captured the item and when, recorded on the record itself — pulled from the assigned users, not added as a standalone note in the output.
Think of the evidence as connected records,
not one final report
If any link breaks — renamed item, missing during-photo, no system reference — the evidence stops being defensible. Six steps that keep every link intact from the point of work to the issued handover.
Six steps · keep every link intact
Step 01
Start with stable item IDs
Create one record per penetration and keep the item ID stable across visits and projects. This is the anchor — the substrate, services, system, and photos all hang off it.
Agreed before capture startsStep 02
Record the substrate and services
Capture what the barrier is made of and the services passing through it — pipe, cable, duct, or tray. Each in a field, not buried in free text, so the record can be filtered and audited.
Same vocabulary across surveyorsStep 03
Capture the during-photo
Photograph the build-up before the finished face hides it — the during-photo is the evidence the seal was installed correctly. Keep it on the item record, not in a shared folder.
Captured at the point of workStep 04
Reference the tested system
Link the seal to the tested system it was installed to — manufacturer, product, EI classification, and cert reference. The app records which certified system was used; it doesn't certify the work.
From the catalogue · not free-typedStep 05
Close the loop with proof
When a defect is remediated, attach before/after evidence and record who captured it. An item marked "sealed" without a during-photo and system reference is a statement, not a proof.
Evidence photos + who + whenStep 06
Hand over from the source record
Generate the survey PDF and portal handover from the same underlying data so they trace back to items, systems, and photos — not assembled separately in Word or a spreadsheet.
Live record → handover · no manual assemblyWhat "audit-friendly" means in practice
The smallest set per item that tends to satisfy
client QA and third-party audits
Your contracts may require more. These six fields are the baseline — the point at which a penetration record can stand on its own in an audit without someone reconstructing the build-up from memory after the face is closed.
01
Item ID + compartment
Item ID, building, and the compartment line
Item ID, building name, and a consistent compartment line — Site / Block / Floor / Wall or floor. The physical penetration must map to one record, consistently, across every visit.
02
Substrate + services
What the barrier is, and what passes through
The substrate (blockwork, plasterboard, slab), the services passing through from a shared list, and the annular gap. Each in a field — not buried in the notes column.
03
Build-up photos
On new work — before, during, and after, captured at the point of work
Overview plus a during-photo before the face hides the build-up, then an after-photo. The during-photo is the evidence; without it, the finished face proves nothing. Surveying an existing seal is different — the as-found photo is the record.
04
Tested system reference
The certified system the seal was installed to
The tested system — manufacturer, product, EI classification, and cert reference — linked to the item, not free-typed. The app records which certified system was used; it doesn't certify the work.
05
Remediation proof
Evidence the defect was sealed and what changed
Before and after photos at the same angle, plus capture date and who sealed it. This is the evidence that distinguishes "the seal is in" from "we said the seal is in".
06
Outputs
Survey PDFs generated from the same record
Survey PDFs and portal handovers generated from the source record — not assembled manually in Word or spreadsheet. The output should trace back to the same items, systems, and photos that produced it.
Quick QA checks
Before you hand over a PDF — four things to verify
Each item has a during-photo
At least one during-photo and one after-photo attached to every penetration — not just a finished-face shot that hides the build-up.
Item IDs unique and consistent
No duplicates within the building, and IDs match any on-site labels or QR tags in use on the penetrations.
Each seal references a tested system
Every sealed item points to a tested system with its classification and cert reference — not a blank or free-typed system field.
PDF links back to record + date
The shared PDF is clearly linked to the same survey record, capture date, and visit context — not an orphaned file.
Self-audit prompts
Five questions to test your evidence trail before a third party does
Identity: Can you find "Penetration X" again on the next visit without guesswork — using just the item ID and compartment line in the record?
Build-up: Can you show the during-photo that justifies the seal — without relying on the finished face that hides what's behind it?
System: Can you show which tested system the seal references, its classification, and the cert reference — attached to the item, not free-typed?
Outputs: Can you show which PDF was handed over and demonstrate it traces back to the same record — not a separately assembled document?
Captured by: Can you show who captured each item, when, and under what account — with it attached to the record rather than just mentioned in an email?
Audit-ready
The evidence is most useful when it feeds the record,
not just the PDF
For higher-risk buildings, the Building Safety Act 2022 expects a maintained "golden thread" of safety information. Fire-stopping evidence — what system, where, the photos, who, and when — feeds that thread when it lives on the record, not only in an exported document.
Four handover rules that keep the golden thread intact
Keep what the Responsible Person needs
The Responsible Person is accountable for fire safety, so the handover should answer what was sealed, where, and to which system — item ID, compartment line, tested system, classification, and cert reference, all linked.
Keep the build-up evidence with the asset
Keep the during-photo and system reference attached to the item so the golden thread carries the asset data, not just a finished-face image — the digital, maintained record the Act describes.
Hand over without rebuilding it
Generate the survey PDF and Client Portal handover from the source record so the thread can be reissued without re-typing it. If the PDF is the only place the evidence lives, reissuing risks losing it.
Handle gaps explicitly
Keep the workflow visible when evidence is missing — a clearly flagged item without a during-photo is better than a silently complete-looking one. Gaps should not be hidden in the handover; recording evidence helps you keep defensible records, it does not guarantee compliance.
Common handover pitfalls
Three patterns that break the golden thread at the last step
Photos as loose image files
Build-up photos saved as loose files with no link to a specific penetration — they appear in the handover but can't be traced back to which item, which system, and which compartment line they belong to.
"Final" PDFs assembled in Word
Handovers manually assembled from finished-face photos, spreadsheet rows, and pasted system names — the golden thread lives somewhere else (or nowhere), and the PDF can't be traced back to the source record.
System named, not referenced
A system written into a notes field with no classification or cert reference attached to the item — at audit there's no way to confirm the seal was installed to a real tested system, and the thread has a hole in it.
Most evidence problems come from
broken links between steps
Four patterns that cause a previously coherent evidence trail to become untrustworthy — usually discovered once the face is closed and the build-up can't be seen again. Each has a clear prevention.
Hidden build-up
No during-photo before close-up
The only photo is of the finished face, which hides the build-up. Once the seal is closed, there's no way to prove it was installed correctly — and you can't reopen it to re-photograph it without destroying the seal.
Fix: capture the during-photo at the point of work, before the face is closed — make it a required field per item.
Detached evidence
Photos live in shared folders
Build-up photos stored in shared drives and named by date or job number — no stable link to the item record. When the folder is renamed or reorganised, there's no way to say which photo belongs to which penetration.
Fix: attach photos to the item record at the time of capture — not filed separately and linked later.
Broken link
No tested-system reference
A seal recorded with a free-typed product name and no link to a tested system — no classification, no cert reference. The item may look complete but there's no way to confirm it was installed to a real certified system.
Fix: reference the tested system from the catalogue so each item inherits its classification and cert reference automatically.
Orphaned output
Orphaned records and detached PDFs
Handovers manually assembled from spreadsheets, pasted finished-face photos, and email threads — stored in a folder with no reference back to the item IDs, systems, or photos that produced them. Impossible to verify at audit.
Fix: generate the handover from the source record so every PDF references the item IDs, systems, and photos it came from.
QR tags help keep the right penetration record in view on repeat visits — by opening the correct item instantly when scanned, they reduce the risk of surveyors creating a new record for a seal that already has one.
See the QR tags for penetrations checklistQuick answers for teams moving
from finished-face photos to a joined-up evidence trail
Four questions that come up when teams are building or tightening a fire-stopping evidence trail for the first time. Deeper guidance is in the related guides.
What counts & what's needed
A seal-by-seal history that keeps the item ID, the compartment line, the substrate and services, the tested system referenced with its classification and cert reference, evidence photos, and who captured it — all linked to the same record, so you can open any penetration and see what was sealed and to which system without reconstructing it from memory.
The key word is "linked". A folder of finished-face photos doesn't constitute a trail — the finished face hides the build-up. The connection between item, system, and the during-photo is what makes it defensible rather than just a collection of images. Recording it helps you keep defensible records; it does not guarantee compliance.
Because the finished face hides the build-up. A photo of a sealed penetration shows a flat surface — it can't show whether the annular gap was fully sealed with a compatible fire-rated system underneath. The during-photo, captured before the face is closed, is the evidence the seal was installed correctly.
Once a seal is closed up you can't reopen it to re-photograph it without destroying it. That's why the during-photo is the one shot you can't recover later — capture it at the point of work, attached to the item record.
Golden thread & handover
For higher-risk buildings, the Building Safety Act 2022 expects the client to keep a maintained "golden thread" of safety information — a digital, kept-up-to-date record of decisions and asset data. Fire-stopping evidence (what system, where, the photos, who, and when) feeds that thread when it lives on the record, attached to each penetration, rather than only in an exported PDF.
The Responsible Person is accountable for fire safety, so the handover should let them answer what was sealed, where, and to which tested system. The failure mode to avoid is a "v3-FINAL.pdf" in a folder with no reference to the items, systems, or photos behind it.
Generate the survey PDF and Client Portal handover from the source record rather than assembling them manually in Word or a spreadsheet. When the output is generated from the live survey, it inherits the item IDs, tested systems, classifications, and the photos that produced it — so any auditor or Responsible Person can trace it back without asking you to explain it.
The failure mode is a handover pasted together from finished-face photos and free-typed system names, stored with no reference to the specific items, systems, or build-up photos it summarises. That file is a statement, not a proof.
Quick facts
Evidence trail at a glance
What it is
Seal-by-seal history: item, substrate, services, system, photos, who/when — all linked
Minimum pack
Item ID + substrate + services + during-photo + tested system + traceable PDF
During-photo
The one shot you can't recover — the finished face hides the build-up underneath
Golden thread
Building Safety Act 2022 — HRBs keep a maintained digital record of asset data
Tested system
Referenced from the catalogue — classification + cert ref, not free-typed
Core test
Can you open any penetration and prove the build-up without reopening the seal?
Get started
Make your next audit boring
Keep everything attached to each penetration — substrate, services, tested system, evidence photos — all tracing back to the same survey record.
Prove the trail on a small pilot first.
Then scale the same structure site-wide.
Run a few penetrations end-to-end — capture, during-photo, tested-system reference, after-photo, and an issued handover — and check every output still points back to the same penetration record.