Skip to content
Two modules, one subscription EU hosted Built inside a working fire door company
On site

Every door gets an ID, and keeps it.

The door register is the spine of the whole system. Each door carries its own identity, its component checks, its measurements, its photographs and its full history — so a repeat visit eighteen months later still lands on the same record.

7-day trial · No card required · Cancel anytime

Offline captureDoor registerGap measurementsFloorplan taggingQR asset labelsPDF import
Photo evidence page from a real fire door inspection report
FIG. 01  Photo evidence — per door, per component
Fully offline Risers, basements and plant rooms. Capture without signal; it syncs when you resurface. No lost mornings
3 reasons Up to three failure reasons per component, each fanning out to quotes, remedials and invoices. Per component
Measured Gap readings taken positionally against a door diagram, flagged when tighter or wider than nominal. Not guessed
Import Third-party inspection PDFs extracted for review, then committed to your master record. Stay the record
01 See it in action

See a fire door inspection run end to end.

Create the inspection, tag each door on the floorplan, capture components, measurements and photographs, and generate the signed-off report.

Run a fire door inspection, end to end Run a fire door inspection, end to endNo signup

What you will see

Create the inspection, tag each door on the floorplan, capture the evidence, and generate the final report — the whole workflow in one pass.

InspectionsFloorplansReports

One of several short walkthroughs — each a real workflow, start to finish. See all walkthroughs →

02What it does

In this area, Fire Door App can:

  • Build a door register per property, each door keeping a stable ID for its whole life
  • Inspect against twelve components, turning off the ones your methodology does not use and writing your own failure reasons for the rest
  • Record up to three failure reasons on a single component, not just one
  • Capture edge gaps in millimetres on a door diagram, up to three readings per edge
  • Flag a perimeter gap that is too tight (under 2mm) as well as one that is too wide (over 4mm)
  • Apply a 3mm undercut tolerance on smoke-rated doors and 8mm elsewhere, read from the door’s own rating
  • Record no access as its own outcome, so an unreachable door is never counted as a pass
  • Photograph every component, and choose which photographs appear on the report
  • Work fully offline in risers, basements and plant rooms, syncing when you resurface
  • Pin doors onto an uploaded floorplan, and print QR labels in three formats
  • Import an existing PDF inspection report from another contractor and review it before committing
  • Keep a timestamped per-door history and export it as CSV

Tolerances are advisory. The app does not set pass or fail itself — the inspector does, and the record says who and when.

03How it runs

The way this actually works on a job.

  1. 01

    Build the register once

    Property, floors and doors, each with a stable ID. Tag doors on the uploaded floorplan so anyone can find them next time, and print QR asset labels so a scan opens the right record on site.

    Floorplan taggingQR labelsStable IDs
  2. 02

    Capture on the door

    Component by component, with photographs and gap measurements taken against a door diagram. Record up to three failure reasons per component. Mark a door No Access when the riser is locked, and keep walking.

    Component checksGap measurementsNo Access
  3. 03

    Nothing needs signal

    Photos, measurements and results sit on the device and sync when it reconnects. Stairwells, basements and plant rooms are where signal fails and where the doors are.

    Offline firstAutomatic sync
  4. 04

    Issue the report

    Cover sheet, methodology, one or more pages per door with its photographs, and a summary of what failed and why — generated from the record in one action, with the page numbers right whether it covers four doors or four hundred.

    Inspection reportCSV exportYour own terms
04What’s in it

The parts you will use every week.

Repeat-visit history

Every check stays attached to its door: dated, photographed and attributable. The second visit reads the first.

Gap measurements

Recorded positionally against a door diagram and flagged when outside nominal — tighter as well as wider.

Multiple failure reasons

Up to three per component, each carried through into the remedial, the quoted line and the invoice.

QR asset labels

Print labels for the door or the frame. A scan opens that door’s record, gated behind a PIN where the detail is sensitive.

Import third-party PDFs

When an external inspector insists on their own app, upload the PDF they email over. Property, doors, components, pass/fail and notes are extracted for review before you commit them.

Works Completed Report

Prove what was closed out, with the evidence attached, without assembling it by hand.

05The output

What comes out of it

The register is not a list — it is the thing every downstream document is built from.

Inspection report
PDF — cover, methodology, one or more pages per door, and a failure summary. The published sample runs 34 pages for 8 doors
Door register export
CSV of every door, component and result
Per-door report
A single door’s full history, for a landlord or a leaseholder
Evidence pack
Assembled per closed remedial, photographs and certificates included
QR label sheet
Printable asset labels, standard or tape format
Your wording
Terms and report wording editable, applied to all thirteen documents
06 Quick questions

Questions this area gets asked.

Q01

Does capture really work with no signal at all?

Yes. Photos, measurements and pass/fail results are stored on the device and sync automatically when signal returns, so an inspector never loses a morning to a dead bar of reception.
Q02

What happens on a repeat visit?

You inspect against the existing register rather than starting again. The door keeps its ID and its history, so the new result sits on top of the old one and the trail stays intact.
Q03

Can we bring in reports from inspectors who use other software?

Yes — upload the PDF through Import PDF and the property, doors, components, pass/fail and notes are extracted for review before you commit them to the master record. See the import workflow →
More detail in the full FAQ Browse full FAQ
Start today

Run one building. Then look at the report.

Build a register, capture a set of doors, and generate the report that comes out. Twenty minutes is enough to see whether it fits how your team already works.

No card. Cancel anytime.