Resources • rollout • evidence • security

Practical guides for fire door inspection teams

Use the resource library to review rollout, evidence capture, outputs and access controls before you roll the workflow out across more buildings, teams or clients.

  • Start with the three setup guides that stop records drifting early.
  • Go deeper into inspection evidence, remedials, outputs and portal delivery.
  • Use security and IT pages when internal stakeholders need cleaner answers.

7‑day trial. No card required. Cancel anytime.

  • Start here
  • Inspection guides
  • Outputs + billing
  • Portal + security

Supports compliance workflows and evidence retention (not legal advice). No compliance guarantee. See scope notes →

Resource library
Fire Door App overview showing inspection planning and delivery. Click to enlarge
Home Resources
Best for
Teams rolling out inspections, outputs or portal workflows
Practical guides for fire door inspection teams - covering rollout, evidence capture, outputs, portal delivery and access controls before you scale across more buildings, teams or clients.
Start 7-day free trial See inspection app
7-day trial · No card required
Covers
Start here Inspection guides Outputs + billing Portal + security
Start here

A simple
rollout path.

If you're new to Fire Door App, these three steps keep door identity and evidence consistent from day one - before records have a chance to drift.

1
Identity
Lock door IDs
& locations
Pick a stable door ID scheme and location hierarchy before the first inspection. Records that start with a clean identity don't need reconciling later - and repeat visits automatically stay attached to the right doors.
Guide Door register & door IDs
2
Evidence
Standardise the
evidence pack
Use a consistent checklist and photo set so inspection outputs are comparable across buildings, inspectors and time. One standard format means the third visit is directly comparable to the first without manual interpretation.
Guide Fire door inspection checklist
3
Trail
Keep the audit
trail joined up
Make sure inspections flow into remedials and exports without rebuilding the story in spreadsheets. A joined-up trail means the door record at sign-off contains everything that happened - without manual assembly before each handover or audit.
Guide Fire door audit trail checklist
Guide library

Short checklists you can hand
to a team before the next rollout or audit.

21 practical guides covering setup, inspections, outputs, billing, portal and security.

21 guides
No guides match. Try a different search or category.
Setup guide
How to use the app
  • Setup checklist - security, team, branding
  • Inspections -> remedials -> PDFs workflow
  • Quotes, invoices and Client Portal handoff
Setup guide
Workspace setup checklist
  • Roles and access model - who gets what
  • 2FA policy and recovery notes
  • Branding and default settings checklist
Register guide
Door register & door IDs
  • Simple rules for stable IDs - don't reuse, don't drift
  • Location hierarchy checklist for clean reporting
  • Edge-case playbook - replacements, duplicates, unknowns
Migration guide
Import existing PDF reports
  • Start from scratch vs import PDFs
  • Extraction checklist and common gotchas
  • Review steps before saving
Reference
Glossary hub
  • Definitions and why it matters for key terms
  • Common failure modes to avoid
  • Links to the relevant playbooks
Standards guide
BS 8214 inspection records
  • Minimum record template - IDs, outcomes, evidence, history
  • Photo evidence set that makes before/after clear
  • Consistency rules for teams and handover-friendly records
Field guide
Fire door inspection checklist
  • Door identity and location checklist
  • Minimum dataset per door - outcomes, notes, severity
  • Photo evidence checklist for audits and handover
Field playbook
On-site inspections playbook
  • Pre-site prep and scope checks
  • Fast capture tips and photo standards
  • Offline and sync expectations
Audit guide
Fire door audit trail checklist
  • Repeatable process - inspections -> remedials -> proof
  • Minimum evidence pack per door for QA and audits
  • How signatures on PDFs stay tied to the record
Tagging guide
QR tagging for door registers
  • Rollout checklist - ID strategy, print, install, QA
  • Safe placement and replacement runbooks
  • Scan logs and access control basics for shared links
Navigation guide
Floorplans & door navigation
  • Site -> building -> floor -> area model
  • Floorplan upload and pinning playbook
  • Edge cases - multi-block, duplicates
Workflow guide
Findings -> quote -> approval
  • Pre-visit and capture consistency checklist
  • Quote scope and approval loop runbook
  • Handover to remedials and scheduling
Delivery guide
RAMs: from scope to PDF pack
  • When to create RAMs in the workflow
  • Template/preset strategy and versioning tips
  • Issuing PDFs and linking to evidence
Reporting guide
Reports & exports playbook
  • PDF vs CSV guidance by audience
  • Naming and retention conventions
  • Suggested handover pack contents
Pricing guide
Pricing & quotes line items (CSV)
  • Minimum viable pricing setup checklist
  • Export -> edit -> import safety checks
  • Presets vs overrides guidance
Billing guide
Invoices & payments
  • Setup defaults - VAT, deposits, terms
  • Issue -> remind -> paid lifecycle
  • Online vs offline reconciliation tips
Integration guide
Accounting & CRM integrations
  • Which integrations are available and what they do
  • What syncs - payments, payouts, invoices, clients
  • Setup checklist and reliability notes
Builder guide
Fire door builder guide
  • Preset strategy for standardisation
  • Pricing overrides - when to use them
  • Rollout checklist for installers
Planning guide
Remedials prioritisation
  • Simple severity scheme and team rules
  • Project grouping and scheduling checklist
  • Close-out evidence and outputs checklist
Portal guide
Client Portal rollout checklist
  • Access and notification checklist
  • Handover expectations and comms copy
  • Safe sharing and access control notes
IT guide
Security & IT overview
  • Roles and 2FA overview - high-level
  • Audit trail and export expectations
  • Customer-side security checklist
Secure by design
Separate workspaces and role-based access keep inspection evidence protected
Security & IT overview

Workspace separation

Separate customer workspaces help keep records scoped to the right organisation.

Role-based access

Invite teams by role so office, site and managers have the access they need. 2FA can be enabled as part of your workspace policy.

Audit-friendly trail

Inspections, remedials and outputs stay linked back to the same door record. What changed, when, and who updated it is visible in the history.

Exports anytime

Export PDFs and CSVs as you go for audits, handover and retention. You own the exports and can store and share them under your own policies.

Use the guides, then test the workflow

See the whole process on
one real building.

Use the resources to tighten IDs, evidence, outputs and portal handover, then run one building through Fire Door App so the whole record stays joined up from inspection to sign-off.

7-day trial No card required Use your own workflow on day one