Resources • remedials • prioritisation • sign-off
Fire door remedials prioritisation: from findings to sign-off
A practical checklist for turning inspection findings into prioritised remedials, grouping work into projects, and keeping sign‑off evidence attached to the right doors.
- Remedials
- Prioritisation
- Sign-off
- Projects
- Quotes
Turn findings into deliverable work
then close out with proof that stays linked to the right doors
A practical checklist for turning inspection findings into prioritised remedials, grouping work into projects, and keeping sign-off evidence attached to the right doors from defect to completion.
Goal 01
Prioritise
Make severity explicit so scheduling and reporting are consistent. When severity is hidden in notes or left to individual judgment, the office and site teams sort the same work differently — creating plan vs reality drift on every project.
Goal 02
Keep context
Tasks point back to the door record and inspection evidence that created them. When a remedial is tracked in a spreadsheet, that link is severed — the site crew doesn't know which door, which finding, or what the inspection showed.
Goal 03
Close out
Before/after evidence, sign-off, and PDF outputs trace back to the same door history. "Completed" means little without proof of what was done, when it was done, and who signed it off — especially when an auditor or client asks six months later.
Teams moving findings into work
Use this when you need repeatable prioritisation across inspectors — especially before scaling remedials across multiple buildings or handing work to a different crew.
Site teams
Consistent configurations and task context — each remedial task links back to the door, the finding, and the photo evidence so the site crew know exactly what needs doing and why.
Clients & auditors
Close-out evidence that traces back to the original door record — before/after photos, sign-off, and PDF outputs that answer "was this fixed, when, and who confirmed it?" without email chains.
Teams lose time when severity is hidden in notes.
Use a consistent scheme everyone can sort the same way.
Three rules for keeping severity explicit and usable, then a rubric to adapt to your own workflow — so the office and site crews are working from the same priority order, not individual judgment calls.
Three rules · define · separate · agree
Rule 01
Define severity
Use a simple Low / Medium / High scheme — or equivalent — so severity is reportable and filterable. "See notes" and "needs doing" are not severity levels. The value comes from the field existing, not from it being perfect.
Rule 02
Separate "what" vs "how urgent"
Keep fail reasons consistent — what was wrong with the door — then add severity as its own separate field. Mixing them creates labels like "urgently replace closer" where the urgency is buried in the description rather than in a dedicated field.
Rule 03
Agree the rules upfront
Decide what qualifies as "High" for your workflow before the first inspection, not mid-project when the site crew and office are already sorting differently. Write it down — even a brief note is enough to prevent disagreement.
Severity rubric · adapt to your policy
Example Low / Medium / High definitions — a starting point, not a compliance rule
Requires prompt action
Issues your competent person policy treats as urgent — requiring prompt action and clear evidence of closure. Typically includes compromised fire integrity, missing critical components, or issues that directly affect the door's rated performance.
Plan into a visit window
Issues that need remediation but can be scheduled within a planned project or maintenance visit. Typically includes worn components, partial defects, or issues that don't immediately compromise door integrity but will deteriorate if left.
Bundle or monitor
Minor issues to address during planned maintenance, bundle with a larger visit, or monitor for change. Typically includes cosmetic issues, very minor gaps, or single-component defects that don't affect door performance at current state.
Remedials should inherit context
which door, what failed, what evidence exists, what needs to happen
Three rules for keeping task context intact, plus the four most common workflow mistakes that sever the link between a remedial task and the door evidence that created it.
Three rules · group · link · scope
Group by site or building
Keep work deliverable: one crew, one visit plan, one clear list of doors per building. Mixing doors from different buildings in a single project makes scheduling ambiguous and site team prep harder — they can't plan the visit efficiently.
Keep tasks tied to doors
A remedial task should always point back to the door record that created it. The door ID, inspection finding, photos, and severity should be accessible from the task — not stored separately where they can diverge or get lost.
Keep scope clear
Scope creep happens when tasks are vague. Make the "action required" explicit on every task — "Replace FD60 bottom seal" not "fix door". Vague scope leads to site teams doing different work than the office expected, then disagreements on sign-off.
Common mistakes
Four patterns that sever the link between task and door evidence
01
Detached tasks
Remedials tracked in spreadsheets lose the door context and evidence trail — when the crew arrives on site, they have a list of work but no access to the photos or findings that raised it.
→ Keep tasks in the platform, tied to door records
02
Duplicate work items
The same door issue appearing in multiple lists — one in the system, one in the PM's spreadsheet, one in the site crew's email — creates conflicting status and missed close-outs.
→ One source of truth · remove duplicates early
03
Scope drift
Unclear "action required" leads to site teams doing different work than the office expected — then sign-off disputes. "Fix door" vs "Replace FD60 bottom seal" are very different tasks.
→ Explicit action on every task before it goes to site
04
No closure proof
"Completed" means nothing without before/after evidence and a named sign-off. The audit question isn't "was it done?" but "what evidence proves it was done correctly?"
→ Before/after photos + sign-off attached before close
Audits don't just ask "was it fixed?"
they ask "what evidence proves it?"
Four steps from scheduling by project through to PDF outputs traceable back to the door history — and a minimum close-out pack that makes client questions and audits straightforward to answer.
Four steps · schedule · capture · sign-off · export
Step 01
Schedule by project
Plan visits by building or block so work is deliverable on site — one crew, one day, one building. Don't mix buildings across a single project unless the crew is visiting multiple sites on the same visit.
Step 02
Capture completion evidence
Attach before and after photos and notes to the door record — not filed elsewhere and linked by reference. The evidence needs to be accessible from the door history, not reconstructed later from the site crew's phone gallery.
Step 03
Record sign-off
Record who approved completion, when, and their role. "Completed" on a status field is not a sign-off. The question in six months is "who confirmed this was done correctly?" — the answer needs to be in the record.
Step 04
Export from the source record
PDFs and portal outputs should trace back to door history — generated from the live record, not assembled manually in Word from screenshots. The output and the history are the same thing.
Minimum close-out pack · per door
Four fields that make audits and client questions easy to answer
01
Before/after photos
Overview + detail
Both the full door view and the specific component or defect area — enough to show the pre-existing state and confirm what was done.
02
What was done
Short factual note
A brief, factual description of the work done — tied to the door or task, not a general site note. "Replaced bottom seal with 4mm intumescent" not "seal fixed".
03
When it was done
Date + visit reference
The date the work was completed and the visit or job reference — so the completion can be placed in the audit timeline alongside any previous inspections.
04
Who signed off
Name + role
Name and role of whoever confirmed completion — where required by your process. "Completed by site crew" is not a sign-off. A named, responsible individual is.
Close the loop on one building.
Inspection → prioritised remedials → sign-off → client outputs.
Run a full cycle on one site so severity, tasks, and evidence stay on the door record end to end.