Book a demo Start free trial

Compliance • Golden Thread‑ready records • UK teams

Golden Thread‑ready records for door‑by‑door fire door work.

Keep inspections, remedials, photos and exports attached to the right doors — so evidence stays usable from first visit to handover.

Start free trial Book a demo

7‑day trial. No card. Cancel anytime.

  • Stable door IDs
  • Door-level evidence packs
  • PDF/CSV exports
  • Portal sharing
  • Audit trail

Last updated:

Supports compliance workflows and evidence retention (not legal advice). No compliance guarantee. Boundaries →

Door record
Door register showing door history and evidence. Click to enlarge
What is the Golden Thread

A usable evidence trail -
door by door, over time.

Correct door identity, linked history and exports that match the underlying dataset. Three things that keep the record usable when it matters.

FD-007 - record state
Inspection finding - Jun 2025 Attached
Remedial raised - same record Attached
PDF export - same record Attached
No separate email thread One record
Principle 01
Single source
of truth.
Inspections, remedials, photos and outputs stay connected to the same door record - so the story doesn't split across emails, spreadsheets and filing systems when someone needs to reconstruct it.
  • All evidence types attached to the same door record
  • Outputs generated from the live record, not rebuilt separately
  • No reconstruction needed when someone asks for evidence
FD-007 - change history
Inspection - J. Marsh · 14 Jun Logged
Remedial raised - J. Marsh · 14 Jun Raised
Sign-off - T. Hughes · 2 Jul Signed
Export matches history exactly Traceable
Principle 02
Traceable
history.
Door histories show what changed, when it changed and who made the update - with exports generated from the same underlying records, not a separate document that might have drifted from the live state.
  • Who updated the record, and when, visible in the history
  • Exports match the live dataset at the point of generation
  • Changes visible across visits without manual cross-referencing
FD-007 - handover outputs
Inspection report PDF Export
Remedials summary CSV Export
Portal view - live status Live
Evidence usable at handover Ready
Principle 03
Handover-friendly
outputs.
Export PDFs and CSVs and share portal views so evidence stays usable over time - not just at the moment of inspection. Outputs are generated from the live dataset so they don't drift from the underlying records before handover.
  • PDF and CSV exports on demand, not on a manual cycle
  • Portal views give stakeholders access without resending files
  • Evidence remains usable through to building handover
Supports compliance workflows and evidence retention - not legal advice. No compliance guarantee. Joined-up records strengthen the evidence trail, but legal duties and competent-person decisions remain with your organisation.
Read boundaries
How this works at door level

Three mechanics that keep
evidence attached and usable.

Practical record-keeping behaviours - not features - that keep the compliance story intact from first visit to handover.

1
Identity
Stable door
identity
Door IDs and registers stay consistent across visits and across contractors. Histories remain attached to the correct openings over time - not reset, renamed or lost when a new team takes over the programme.
  • Door IDs persist across every visit and contractor change
  • Register stays consistent regardless of who runs the programme
  • Location, attributes and opening identity fixed to the record
Output Door record reusable for audits and handover
2
Evidence
Evidence stays
attached
Photos, findings, remedials and sign-off remain linked to the same door - door by door, visit by visit. Clients and teams see the same story without chasing email threads to reconstruct it before an audit or handover.
  • Photos and findings linked to the door, not to the visit alone
  • Remedials and sign-off attached to the same opening
  • Full story visible without cross-referencing separate systems
Output Joined-up audit story - door by door
3
Exports
Exports from
the same records
Generate PDFs and CSVs when clients or auditors request evidence - from the live dataset, not a rebuilt spreadsheet. Share portal views so stakeholders can see the latest documents and status without the team having to resend anything.
  • PDFs and CSVs generated from the live record on demand
  • Portal views give stakeholders current status without email
  • Exports match the underlying dataset at the point of generation
Output Evidence packs and handover-friendly exports
Platform
Inspections & door register Documents, PDFs & exports Client portal & billing
For reviewers & procurement
What stakeholders usually need to see before they trust the record
Four questions this page addresses directly.
Repeatable history
Every revisit starts from the same door identity and a visible record of what changed last time - so evidence accumulates rather than being re-entered from scratch.
Evidence in context
Photos, findings, remedials and sign-off attached to the same opening - not scattered across folders, emails and filing systems that need to be reconciled before an audit.
Exports from live records
PDFs, CSVs and portal views come from the live dataset - not a separate spreadsheet rebuild. What the export shows matches the underlying record at the point of generation.
Clear boundaries
This page explains what the platform supports and what still depends on your organisation's competent-person decisions, policies and legal responsibilities.
See boundaries
Supports compliance workflows and evidence retention - not legal advice. No compliance guarantee. Your organisation retains responsibility for legal duties, competent-person decisions and how evidence is interpreted.
Practical reference Minimum evidence pack per door
Four components teams use to keep evidence usable
01
Identity
Stable door ID, location and key attributes - so the record stays usable when the door is revisited, handed over, or reviewed by someone who was not present at the original inspection.
  • Stable door ID consistent across visits
  • Location and floor reference
  • Key door attributes captured at first inspection
02
Findings
Consistent inspection fields and outcomes recorded in the same format across visits - so findings from visit two can be compared against visit one without manual interpretation.
  • Consistent fields across all inspection visits
  • Pass/fail outcomes recorded per component
  • Findings comparable across the programme history
03
Photos
Visual evidence attached to the door record - including before and after photos where a finding is raised and remedied. Photos stay linked to the door, not to a folder that gets moved or renamed.
  • Photos attached to the door record at capture
  • Before/after evidence where remedials are raised
  • Accessible in exports and portal views
04
Remedials & sign-off
Actions, completion and sign-off attached to the same door history as the finding that raised them - so the evidence trail runs from first inspection through to closed remedial without a gap.
  • Remedials raised from the finding on the same door
  • Completion recorded against the same record
  • Sign-off attached - visible in audit history and exports
Practical guide: See how these components work in a real inspection record, and what the exports look like for auditors and handover.
Inspections & door register Audit trail guide
Context only
BS 8214-style record-keeping concepts
Record-keeping practices built into the workflow that align with the standard's approach to consistent, door-level evidence.
BS 8214 inspection records guide
Concept 01
Repeatable fields
Consistent capture across visits makes comparisons easier and reduces the manual effort needed to establish whether a door's condition has changed, improved or deteriorated between inspections.
Concept 02
Door-level exports
Evidence packs built from the same underlying records - not assembled manually from separate sources. Exports reflect the actual door history rather than a summary prepared independently of it.
Keep the dataset clean. Exports are only as reliable as the door identity and history beneath them. Inconsistent capture at inspection produces inconsistent outputs at audit.
England context
Fire door checks & record keeping
Context only - we include this to help teams understand the regulatory background. Fire Door App supports evidence retention and joined-up records; it does not provide legal advice.
Context 01
Golden Thread context
Evidence needs to remain usable over time - not just at the moment of inspection. Door-by-door records with stable IDs, linked history and consistent exports support this requirement by keeping the evidence trail intact across visits, contractors and programmes.
Context 02
Door-level traceability
Stable door IDs and linked history reduce the gaps and rework that arise when records are inconsistent or held across separate systems. Evidence that can be traced back to a specific door at a specific visit is more robust than a summary assembled after the fact.
Context only - not legal advice. This section is included to help teams understand the regulatory background. Fire Door App supports evidence retention and joined-up records. It does not provide legal advice and makes no compliance guarantee.
Important boundaries

What Fire Door App
doesn't do.

These boundaries are here so stakeholders can interpret the evidence correctly. They are not a disclaimer in small print - they are a first-class part of how this platform describes itself.

Boundary 01
Not legal advice
We do not provide legal advice. Your organisation remains responsible for its own legal duties, competent-person decisions and how evidence is used or interpreted. Fire Door App provides tools that support evidence retention and record-keeping - not legal guidance on whether those records are sufficient for any particular purpose.
Your responsibility
Boundary 02
No compliance guarantee
Joined-up records support compliance workflows - they do not guarantee that a building is compliant. Whether a fire door meets the required standard is determined by a competent person during an inspection, not by the platform recording the outcome of that inspection. The record is evidence, not a verdict.
Evidence, not verdict
Boundary 03
Export and retention is yours
Export PDFs and CSVs from the platform when clients, auditors or regulators require evidence. How long you retain those exports, where you store them, and who you share them with is your organisation's responsibility - governed by your own retention policies and any applicable regulatory requirements.
Your retention policy
Supports compliance workflows and evidence retention - not legal advice. No compliance guarantee.
These boundaries apply to every section of this page. If you have questions about whether Fire Door App is appropriate for your compliance obligations, contact us before committing.
Compliance FAQ

Short answers to the
questions stakeholders ask.

Evidence, handover, and what the platform does and doesn't cover - answered directly.

No. Fire Door App supports compliance workflows and evidence retention, but it does not make a building compliant. Your organisation remains responsible for its own legal duties, competent-person decisions and how evidence is used or interpreted. Joined-up records strengthen the evidence trail - they do not replace the judgements that must be made by qualified people on site.
Door-by-door records stay usable over time: stable door IDs, linked inspections, remedials and photos, traceable history, and exports generated from the same underlying dataset - not rebuilt from separate sources for handover or audit. "Golden Thread-ready" describes the record-keeping structure, not a legal certification or a guarantee that any specific regulatory requirement is met.
We use BS 8214-style record-keeping concepts - consistent inspection records, repeatable fields across visits, and door-level evidence packs built from the same underlying data. This approach aligns with the standard's emphasis on systematic, traceable records. It is not a substitute for the standard itself, nor for your organisation's own policies, procedures and competent-person decisions. See the BS 8214 inspection records guide.
Yes. Export PDFs and CSVs on demand and share portal views so you can provide evidence without rebuilding the story in spreadsheets. Exports are generated from the live dataset - what they show reflects the underlying records at the point of generation. How you retain, store and share those exports remains your organisation's responsibility under your own policies and any applicable requirements.
Fire Door App supports UK/EU hosting arrangements and separate customer workspaces. If you have specific data residency or procurement requirements, contact usbefore signing up and we can confirm the details relevant to your situation.
More questions about evidence, handover or platform suitability?
Browse resources Contact us
Next step

Run one real building.
See what the evidence trail actually looks like.

Test the compliance workflow on live door data, generate exports, and review what the linked history, PDFs and portal views look like before you commit.

Start free trial Book a demo

7-day trial. No card. Cancel anytime.

One real building Door-level history PDF & CSV exports Portal-ready handover