Identity first
Stable door IDs + locations prevent “record drift” across years.
Resources • inspection records • evidence • consistency
BS 8214 inspection records and what to keep
A practical checklist for keeping inspection evidence consistent across inspectors, visits, and buildings without losing traceability.
- Inspection records
- Photo evidence
- Team consistency
Click to enlarge
Guide summary
Evidence pack
Outcomes + notes + consistent photos per door make audits boring.
In Fire Door App
Door register + inspections + remedials + documents.
At a glance
Good inspection records make audits boring: consistent door identity, consistent evidence, and clear history.
Identity stays stable
Door IDs and locations should be consistent across visits so you can prove you’re talking about the same door.
Evidence is repeatable
Use a minimum dataset per door (outcomes, notes, severity, photos) so reports are comparable.
QA is built-in
Review for missing IDs, missing photos, and inconsistent ratings before exporting PDFs for clients or audits.
What to capture per door
Avoid “notes in a spreadsheet” by keeping the same core evidence attached to the same door ID.
Identity
Door ID, location, and any tag/label identifier used on site.
Outcome
Pass/fail, severity, and clear fail reasons so follow-up work is unambiguous.
Evidence
Photos and notes tied to the door record (not a folder) so audits don’t turn into a treasure hunt.
History
Prior visits, changes, and remedial sign-off so “what changed?” is always answerable.
Minimum viable inspection record
If you standardise the fields below, most “audit pain” disappears — because the record is readable even when a different person revisits the door later.
Where
Building, floor/zone, and a location string that stays stable (avoid “near the stairs” if it changes later).
What
Door type/leaf set, rating context (where known), and any tag/label ID used on site.
When
Inspection date/time and visit context (routine, re‑inspection, post‑remedial check).
Findings
Clear outcomes with consistent fail reasons (so reports compare across buildings and time).
Evidence
Photos/notes tied to the door record, plus the remediation link when follow‑up work is raised.
Example fields teams commonly include
- Unique door ID, location hierarchy, and tag/label identifier (if used).
- Inspector name, organisation/team, and visit date/time.
- Overall outcome, severity/priority, and a short “why” statement.
- Structured checklist items with pass/fail/NA, plus standard fail reasons.
- Notes (what was observed), recommended action, and any immediate risk flags.
- Photo evidence (overview + detail) linked to the same door record.
- Remedial status history (raised, in progress, completed) and sign‑off evidence when closed.
Quick QA checks before you mark an inspection “done”
- No missing doors: confirm each expected area/floor has been walked and recorded.
- No missing evidence: failed doors have at least one overview + one detail photo where policy expects it.
- No location drift: location labels are consistent (e.g. “Floor 02” vs “2nd floor”).
- No duplicate IDs: the same physical door isn’t recorded twice under two names.
- Outputs trace back: if you issue a PDF, it should reference the same door record identifiers and findings.
Photo evidence that holds up
The goal is to show: which door this is, what you saw, and what changed later. A few disciplined photos beat dozens of blurry ones.
- Take an “identity” photo: include the door label/tag (if present) and enough context to recognise location.
- Capture the finding: a wide shot for context plus a close-up that makes the defect obvious.
- Repeat the same angles: consistency makes before/after comparisons fast.
- Write the caption in the record: avoid relying on filenames; keep the explanation next to the door evidence.
Suggested photo set per issue (quick template)
- 1× door overview (shows leaf, frame, and location context).
- 1× label/tag/identifier (if applicable).
- 1× close-up of the defect (sharp, well lit).
- 1× “measuring” or reference shot (if you record gaps/clearances).
- After remedial: repeat the same set to show what changed.
Write findings that survive handover
Most “dense” reports come from trying to explain everything in prose. Keep the record structured, then use the PDF output to summarise.
- One point per note: split issues instead of writing one long paragraph.
- Use consistent terms: standardise fail reasons so teams don’t invent new wording per visit.
- Separate observation vs action: what you saw vs what needs doing.
- Keep “why it matters” short: one line is enough when the evidence is attached.
Example note format (copy/paste structure)
- Component: e.g. closer / seals / frame.
- Observation: what you saw (objective, not a guess).
- Outcome: pass/fail/NA + severity/priority (your team’s scheme).
- Action: what needs doing, by whom, by when (if you record it).
- Evidence: reference the attached photos in the same door record.
How to keep it consistent across a team
Consistency is usually a process problem, not an inspector problem.
- Standardise checklists: keep a single checklist/fail-reason set per workflow and update centrally.
- Use one door ID system: avoid renaming doors between visits; keep identifiers stable.
- Attach remedials to the same door: make remedial projects reference the door record that created them.
- Share outputs from the same record: generate PDFs and portal exports from one source of truth.
Common questions
Short answers that help teams standardise records without losing the “why”.
Is this guide legal advice or a substitute for a competent person?
No. It’s a practical workflow checklist for consistent records. Always follow your organisation’s policies, building owner requirements, and applicable standards.
What’s the minimum “record” that keeps audits simple?
Stable door identity + consistent outcomes + enough photos/notes to justify findings + a change history that shows what happened after remedials.
How do we keep records consistent across multiple inspectors?
Standardise door IDs/locations, use shared checklists and fail reasons, and run a quick QA pass for missing doors/photos before exporting PDFs.
Where does this sit in Fire Door App?
It maps to the door register (identity + history), inspections (outcomes + evidence), remedials (tasks + close-out proof), and documents (PDF outputs).
Next step
Try it on one real building.
Capture a small set of doors, generate a PDF, and compare it to your current process.