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
- Door identity
- Team consistency
- PDF outputs
Standardise what you capture —
records stay readable across years
Three things to get right so door records stay audit-friendly and easier to hand over. Identity, evidence, and consistency — each failing silently when skipped.
Step 01
Identity first
Stable door IDs and consistent location labels prevent "record drift" across years. The same physical door should open the same record on every visit — no duplicates, no guessing.
Step 02
Evidence pack
Outcomes, notes, severity, and consistent photos per door — attached to the record, not a folder. A few disciplined photos beat dozens of blurry ones. Makes audits boring, not painful.
Step 03
In Fire Door App
Door register, inspections, remedials, and documents all map to the same door record. Capture on site, generate PDFs, raise remedials, and share with clients — without retyping between stages.
Identity stays stable
Door IDs and locations consistent across visits so you can prove you're talking about the same door — even years later.
Evidence is repeatable
Minimum dataset per door — outcomes, notes, severity, photos — so reports are comparable across inspectors and visits.
QA is built in
Review for missing IDs, photos, and inconsistent ratings before exporting. Catch gaps before the report leaves the building.
Four things attached to
every door record
Avoid "notes in a spreadsheet" by keeping the same core evidence attached to the same door ID — every inspector, every visit, every building.
01 — Identity
Door ID, location, and any tag identifier
The anchor for everything else. Stable identity means repeat visits open the same record and evidence accumulates in one place — not scattered across duplicate entries.
02 — Outcome
Pass/fail, severity, and clear fail reasons
Outcomes drive everything downstream — remedials, prioritisation, client reports. Vague outcomes ("needs attention") can't be filtered, scheduled, or reported against. Specific outcomes can.
03 — Evidence
Photos and notes tied to the door record, not a folder
Evidence detached from the record creates a treasure hunt at audit time. When photos live in a shared folder and notes live in a spreadsheet, the "which photo belongs to which door?" question becomes unanswerable.
04 — History
Prior visits, changes, and remedial sign-off
History is what makes "what changed?" answerable without digging through archived folders. When remedials close on the same record that raised them, the chain of evidence is intact — and provable years later.
Standardise these fields and
most "audit pain" disappears
The record is readable even when a different person revisits the door later. Five fields are the foundation — everything else builds on top of them.
01
Where
Building, floor/zone, and a stable location string — not "near the stairs" if that description might change.
02
What
Door type/leaf set, rating context where known, and any tag or label ID used on site.
03
When
Inspection date and time, plus visit context — routine, re-inspection, or post-remedial check.
04
Findings
Clear outcomes with consistent fail reasons — so reports compare across buildings and time.
05
Evidence
Photos and notes tied to the door record, plus the remediation link when follow-up work is raised.
Example fields
Fields teams commonly include beyond the minimum
Unique door ID — location hierarchy and tag/label identifier if used on site
Inspector name — organisation/team and visit date/time
Overall outcome — severity/priority and a short "why" statement
Structured checklist items — pass/fail/NA with standard fail reasons per component
Notes — what was observed (objective), recommended action, and any immediate risk flags
Photo evidence — overview and detail shots linked to the same door record
Remedial status history — raised, in progress, completed, and sign-off evidence when closed
Prior visit reference — link or date of last inspection for comparison
Quick QA checks
Before you mark an inspection done — five things to verify
No missing doors. Confirm each expected area and floor has been walked and recorded — not skipped because access was difficult.
No missing evidence. Failed doors have at least one overview and one detail photo where your policy expects it — not just a note.
No location drift. Location labels are consistent — "Floor 02" not "2nd floor", "Stair A" not "stairwell A". Check against the glossary before exporting.
No duplicate IDs. The same physical door isn't recorded twice under two slightly different names — resolve before the inspection is saved.
Outputs trace back. If you issue a PDF, it references the same door record identifiers and findings — not a separately assembled document.
This is a practical checklist, not a substitute for BS 8214 and your own policies. When in doubt, follow the standard, the building owner requirements, and competent person guidance.
Show which door, what you saw,
and what changed
A few disciplined photos beat dozens of blurry ones. The goal is a before/after record that holds up without explanation — anyone picking up the report later can follow it without asking.
Four rules for evidence that holds up
Take an identity photo
Include the door label or tag and enough surrounding context to recognise the location — floor, area, frame. This is the "which door is this?" shot.
Capture the finding
A wide context shot plus a close-up that makes the defect obvious. The close-up should be sharp and well lit — if you can't see the defect clearly, the photo doesn't help at audit.
Repeat the same angles
Consistency makes before/after comparisons fast. When re-inspecting the same door, recreate the same framing so differences are immediately visible without guessing.
Write the caption in the record
Don't rely on filenames. Keep the explanation next to the door evidence — what the photo shows, which component, and what outcome it supports. See PDF outputs →
Suggested photo set per issue
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, consistent terms, and a clear split between what you saw and what needs doing.
Four rules for findings that travel
One point per note
Split issues instead of writing one long paragraph that mixes the defect, the severity, and the action into a wall of text. One finding, one note. Easier to remediate, easier to close out.
Use consistent terms
Standardise fail reasons so teams don't invent new wording per visit. "Closer inoperative" not "closer broken", "closer not working", and "Closer-faulty" — three strings for the same finding break cross-building comparison.
Separate observation from action
What you saw vs what needs doing. Observation is objective fact ("door closer does not return door to latch"). Action is the instruction ("replace closer unit"). Mixing them makes findings ambiguous at handover.
Keep "why it matters" short
One line is enough when the evidence is attached. The photo explains the severity — the note doesn't need to repeat it. Save the explanation for the PDF summary, not the field note.
Example note format
Copy/paste structure per finding
Closer / Seals / Frame / Glazing
Use this structure per finding, not per door. One finding, one note block — split issues so each can be remediated and closed individually.
Consistency is a process problem,
not an inspector problem
Four things to standardise centrally so individual inspectors don't have to remember every rule — and new team members start correctly from day one.
01 — Checklists
Standardise checklists and fail reasons centrally
Keep a single checklist and fail-reason set per workflow and update it centrally. When every inspector works from the same list, outputs compare across visits, buildings, and inspectors without reconciliation.
02 — Door IDs
Use one door ID system — never rename between visits
Renaming doors between visits is the single most common cause of record fragmentation. When IDs drift, inspection history splits into orphaned records that can't be reconciled without manual detective work.
03 — Remedials
Attach remedials to the door record that created them
Remedial tasks must reference the door record that raised them — not a separate project, spreadsheet, or email thread. When they're linked, status and evidence stay in one place and the audit trail is intact.
04 — Outputs
Generate PDFs and exports from one source of truth
When different inspectors or admin staff assemble reports separately, you end up with multiple versions of the truth. Generate every output — PDFs, portal shares, CSVs — from the live record, not from copies.
Short answers on records, consistency,
and Fire Door App
Four questions that come up when teams start standardising inspection records. Deeper guidance is in the related guides.
Standards & compliance
No — and it's not designed to be. This is a practical workflow checklist for keeping inspection records consistent and auditable. It describes how to structure evidence, not how to assess risk or determine compliance.
Always follow your organisation's policies, building owner requirements, applicable standards including BS 8214, and competent person guidance when assessing door condition and recording findings.
Stable door identity — a unique ID and consistent location that don't drift between visits — plus consistent outcomes, enough photos and notes to justify findings, and a change history that shows what happened after remedials.
When those four things are in place, a new inspector or auditor can pick up any door record and follow the story without asking questions. That's the practical test for "minimum viable".
Team & workflow
Three things in combination. Standardise door IDs and locations before anyone starts capturing — agree the format centrally and share it with every inspector. Use shared checklists and fail reasons so outcomes and wording are comparable across people and visits. Run a QA pass for missing doors, missing photos, and location drift before exporting PDFs.
Consistency is usually a process problem, not an inspector problem. When the structure is in place, individual inspectors don't need to remember every rule.
The guide maps directly to four areas of the platform. The door register holds identity and history — stable door IDs and location hierarchy. Inspections capture outcomes, severity, notes, and photos attached to each door record. Remedials inherit the finding context and keep before/after evidence on the same record. Documents generate PDFs from the live record without reassembly.
Quick facts
BS 8214 records at a glance
This guide is
A practical workflow checklist — not legal advice or a substitute for BS 8214
Minimum record
Stable ID + consistent outcomes + photos/notes + change history
Consistency root cause
Process problem, not inspector problem — fix the structure first
QA before export
Check missing doors, photos, location drift, and duplicate IDs
Platform mapping
Door register → Inspections → Remedials → Documents
Photo rule
A few disciplined photos beat dozens of blurry ones — same angles every time
Get started
Try it on one real building first
Capture a small set of doors, generate a PDF, and compare it to your current process.
Try it on one real building first.
Then compare to your current process.
Capture a small set of doors, generate a PDF, and compare it to your current inspection record workflow.