Resources • inspection checklist
Fire door inspection checklist: minimum evidence pack
Use this guide to standardise door identity, checklist outcomes, photo evidence and audit-trail expectations so inspection records stay comparable across inspectors, sites and repeat visits.
- Inspection checklist
- Evidence
- Consistency
- Photos
- Severity
Standardise capture —
so remedials and outputs stay comparable
Four steps — identity, minimum dataset, photo evidence, audit trail — applied consistently across inspectors, sites, and repeat visits so findings flow cleanly into remedials and sign-off.
Focus 01
Outcome
Door identity and evidence stays attached and readable — whoever opens the record next visit, next year, or at handover can follow the story without asking questions.
Focus 02
Minimum dataset
Outcomes, severity, notes, and a consistent fail-reason set. When every inspector uses the same structure, doors are comparable across buildings and time without reconciliation.
Focus 03
Photo evidence
An overview plus one clear close-up per issue is usually enough. Consistency beats quantity — same angles, attached to the door record, so before/after comparisons take seconds rather than searches.
Identify the door
Stable door IDs and consistent locations so repeat visits open the same record every time — no duplicates, no guessing.
Capture the minimum
Outcomes, severity, notes, and the same photo set so doors are comparable across inspectors and visits without extra work.
Keep the trail joined
Failed items flow into remedials and outputs, with sign-off evidence tied back to the door record that raised them.
Lock in door identity
before recording anything
Before you record findings, make sure you can reliably identify the door again next visit — and the visit after that. Identity is the anchor for everything else.
Three things to confirm before capture starts
Door ID
Stable, unique, human-readable identifier used in outputs and remedials. Agreed before capture starts — BKA-014 not a filename or a spreadsheet row number. Never rename a live ID.
Location
Consistent hierarchy — Site / Block / Floor / Area — so filters and reports are clean. Avoid ambiguous labels like "near the stairs" or "corridor door" that might mean different things next visit.
Optional tags
QR labels that open the correct door record instantly on site. The tag points to the ID — it doesn't replace it. Roll out tags after the ID scheme is stable, not before.
Pre-visit preparation
Five things to confirm before anyone arrives on site
Confirm scope
Which buildings and blocks are in scope and who will be on site — no surprises on the day.
Access notes
Keys, concierge contacts, restricted areas, and any sequencing constraints confirmed in advance.
Checklist and fail reasons
Agree one shared set so all inspectors record findings consistently — not inventing wording per visit.
Floorplans and reference photos
If you use pinning or location aids, load them before the visit — not while standing in the corridor.
Door IDs confirmed
Whether you are using existing IDs, creating new ones, or tagging for first-time onboarding — decided before capture starts.
Ready to capture
Capture the same four things
for every door
Keep the checklist consistent across inspectors so doors are comparable across buildings and time. Capture while you're at the door — not later from memory.
Record 01
Door details
Type, rating context, dimensions if used, and any access notes. These make the record useful to someone who wasn't there and give context to the findings that follow.
Record 02
Checklist outcomes
Pass / Fail / NA per component using a shared fail-reason set. When outcomes and wording are standardised, trends emerge, remedials are unambiguous, and reports compare across buildings and time.
Tip: prefer structured selections over free text, then add a short note for context. Free text alone drifts across inspectors within weeks.
Record 03
Severity / priority
Simple severity flags make it easier to prioritise remedials and communicate risk clearly. A field — not a note. Filterable, schedulable, and reportable across any number of buildings.
Severity belongs in a structured field, not buried in notes. "urgent — fix asap" in a note can't be filtered or scheduled across a portfolio.
Record 04
Notes
Short, factual notes: what you saw and what action is recommended. Captured while you're at the door, not reconstructed from memory back at the office — the observation should be objective, not interpretive.
Per-door rhythm
Five steps so nothing is missed at each door
01
Identify
Confirm door ID, location, and tag scan if used.
02
Record
Capture outcomes and severity while at the door — not later.
03
Evidence
Overview + at least one detail photo per issue recorded.
04
Note
Short factual note — what you saw and action recommended.
05
QA
Spot-check for missing doors, photos, or obvious duplicates before leaving the area.
Photos are most useful when consistent
and attached to the right record
A few disciplined photos beat dozens of blurry ones. Consistency and attachment matter more than quantity — the goal is evidence that can be understood by someone who wasn't there.
Four things to capture per door
Overview photo
Door in context — so location is obvious later. Include the frame, surrounding wall, and any visible label or tag. This is the "which door?" shot.
Detail photos
Close-up of each specific issue — one photo per issue if possible. Sharp and well lit. If you can't see the defect clearly, the photo won't help at audit.
Label / ID photo
Optional but recommended — shows the door ID or QR tag placement for traceability. Confirms the photo set is attached to the right record.
Before / after (follow-ups)
When remedials are completed, repeat the same angles so the change is obvious without explanation. Consistency makes comparison instant.
Photo tips · to make audits easier
Consistency beats artistry — same angles and framing make before/after comparisons faster than perfectly composed shots taken from different positions each visit.
One issue, one close-up — avoid "collages" where multiple issues are hard to interpret later. One defect, one frame.
Attach, don't file — the most common audit pain is photos in shared folders with no link back to the door. Attach to the record at the time of capture.
Respect privacy — avoid capturing personal items or identifiable people where possible. Follow building owner policy.
Inspection evidence is most valuable
when it connects without re-typing
A consistent inspection record makes everything downstream easier — remedials inherit the right context, outputs trace back to the right door, and sign-off has the evidence to support it.
Trail 01
Attach remedials to the same door
Tasks should inherit the findings context and photos from the inspection that raised them. When they're linked to the same door record, status is visible in one place and the trail is intact at any point in time.
Trail 02
Export from the source record
PDFs and portal outputs should trace back to the door history — not assembled separately from spreadsheets, emails, or memory. When every output comes from the live record, there is only one version of the truth.
Trail 03
Capture sign-off evidence
Who approved, when, and what evidence supports closure. Sign-off without evidence attached is a statement, not a proof. The chain of evidence is only complete when before/after photos and approval are on the same door record.
This is a practical checklist, not a substitute for relevant standards, policies, or competent person guidance.
Quick answers on
evidence, consistency, and remedials
Four questions that come up when teams standardise inspections. Deeper guidance is in the related guides below.
Evidence & minimum pack
Stable identity — a door ID and location that don't drift — plus outcomes with severity, a short note covering what you saw and what action is needed, and enough photos to identify the door and justify the finding.
That's it. Anything beyond that is useful context but the minimum is the identity, the outcome, the note, and the photos — all attached to the same door record rather than scattered across folders and spreadsheets.
Not necessarily. Consistency comes from using the same structure and fail-reason set across the team, then adding a short note where needed — not from a longer list. A short shared checklist applied consistently beats a long one applied differently per inspector.
The length matters less than the discipline. One shared source, one set of fail reasons, and a quarterly review to prevent wording drift is more valuable than adding more fields.
Photos & remedials
Two things matter most. Use an overview photo for context and one clear close-up per issue. And attach them to the door record at capture — not stored in loose folders, not named by date, not emailed back to the office.
When photos live in a shared folder without a stable link to the door record, they become useless at audit. The attachment is what makes them evidence — not the photo itself.
When the inspection record is consistent — stable IDs, structured outcomes, severity in a field — remedial tasks can be raised directly from the finding, prioritised by severity, and assigned without re-explaining context.
Sign-off then closes on the same record. Before/after evidence, approval name, and date are all attached to the door that raised the remedial. The chain reads end to end without anyone having to reassemble it from emails or spreadsheets.
Quick facts
Inspection checklist at a glance
Minimum pack
Stable ID + outcome + severity + note + photos attached
Checklist consistency
Same structure + shared fail reasons beats a longer list
Photos
Overview + one close-up per issue, attached at capture not filed
Capture timing
At the door, not later from memory — especially on large estates
Remedials flow
Raised from finding → prioritised by severity → closed with sign-off on same door
This guide is
A practical checklist — not a substitute for standards or competent person guidance
Get started
Run one inspection end-to-end
Capture doors, generate outputs, and see how findings flow into remedials and sign-off without rebuilding the story elsewhere.
Run one inspection end‑to‑end.
Then see findings flow without rebuilding the story.
Capture doors, generate outputs, and compare how remedials and sign-off stay attached when evidence lives on each door record.