Identity
Door ID, location, and any tag/label identifier used on site.
Resources
BS 8214 inspection records: what to keep and why
A practical checklist for keeping inspection evidence consistent across inspectors, visits, and buildings — without losing traceability.
Inspection records
Photo evidence
Team consistency
Checklist
Consistent evidence
Door-level records Keep IDs, photos and outcomes attached to each door across repeat visits.What to capture per door
Avoid “notes in a spreadsheet” by keeping the same core evidence attached to the same door ID.
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.
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.
Try it on one real building.
Capture a small set of doors, generate a PDF, and compare it to your current process.