Door register
One door, one record: identity, evidence, and history.
Resources
Glossary: fire door inspection workflow terms
Quick definitions for the terms used across FireDoorApp resources: door registers, door IDs, audit trails, BS 8214 record-keeping, and remedials severity.
Top terms
Most common failure mode
Broken links IDs drift, evidence is detached, remedials lose context, and exports don’t trace back.
Door register
Identity + evidence per door.
Audit trail
History across visits and sign-off.
Remedials
Tasks + evidence attached to doors.
How to use this glossary
Audit trail
Inspections → remedials → outputs, with links intact.
BS 8214 records
Consistent evidence packs that survive handover.
Door register
A door-by-door dataset that stays stable over time so inspections, photos, remedials, and outputs remain linked.
What it should include
- Identity: door ID, location hierarchy, and tag/label identifiers (if used).
- Inspection evidence: outcomes, notes, severity, and consistent photo evidence per door.
- History: dates, inspectors, re-inspections, and changes over time.
Common mistakes
- IDs drift: the same physical door becomes multiple records across visits.
- Evidence detached: photos stored in folders instead of attached to the door record.
- Inconsistent checklist: pass/fail and severity vary by inspector.
Audit trail
A chain of evidence that answers: what was inspected, what changed, what work was done, and who signed it off.
Step
Inspections
Door-by-door evidence captured consistently (outcomes, notes, severity, photos).
Step
Remedials
Tasks inherit context and keep before/after evidence attached to the same door record.
Step
Outputs & sign-off
PDFs and signatures trace back to the underlying record and history.
BS 8214 inspection records
A practical way to think about record-keeping: what you must keep, how you keep it consistent, and how you prove continuity across visits.
Consistency rules
- Minimum dataset: define the fields you always record per door.
- Evidence pack: define the photo set that makes before/after clear.
- QA checks: validate missing IDs, missing photos, and inconsistent ratings before exporting.
Why it matters
- Handover friendly: new inspectors can follow the same structure.
- Audit friendly: the story reads door-by-door without hunting through folders.
- Client friendly: reports stay comparable year to year.
Remedials severity
A workflow tool: make urgency explicit so teams can plan work consistently and report progress clearly.
What “severity” means here
Severity is the field you use to prioritise work in your workflow (e.g. Low/Medium/High) so it is filterable, schedulable, and reportable.
Important note
This glossary describes workflow concepts, not legal or competent person guidance. Always follow your organisation’s policies, building owner requirements, and applicable standards when assessing risk and urgency.
Want the full playbooks?
Use the resources hub for checklists on inspection evidence, audit trails, tagging, and onboarding.