Overview
For most portfolios, the limiting factor in fire door remedials is not technical complexity. It’s operations:
- resident access and missed appointments
- noisy/dirty works in corridors
- coordinating joinery, ironmongery, and making good
- keeping evidence consistent across multiple sites
A simple programme structure
1) Prioritise the schedule
Use risk-based priorities (not “first come, first served”). Agree what “priority” means in your context.
2) Group by similar work types
- closer adjustments/replacements
- seal replacement
- leaf/frame repairs
- full door set replacement
Grouping reduces downtime and avoids returning to the same door repeatedly.
Before you start: get the basics in place
Build a door register that your programme can run on
If you don’t already have one, create a simple door register (even a spreadsheet) with stable IDs.
Minimum fields:
- door ID
- location (block / floor / corridor / flat)
- door type (flat entrance, corridor, stair, riser, plant)
- last inspected date
- status (pass / defects / unknown)
Define what “priority” means
Avoid vague priorities like “high/medium/low” without criteria.
| Priority | Typical triggers | What it usually means operationally |
|---|---|---|
| P1 | Door doesn’t self-close or doesn’t latch | Treat as urgent; plan rapid access and fix |
| P2 | Significant damage, missing seals, alignment issues | Programme quickly; likely repair/replace decision |
| P3 | Minor issues, early wear, monitoring items | Plan within routine cycle; prevent deterioration |
Your exact definitions should align with competent guidance and the building’s fire risk assessment.
3) Plan access windows
For occupied buildings:
- communicate early
- set realistic appointment blocks
- define how no-access doors are handled
“No access” is not a footnote
For occupied buildings, missed appointments happen. Make it part of the plan:
- define how many re-visit attempts will be made
- record each attempt against the door ID
- communicate clearly with residents/occupants
- escalate persistent no-access doors via the client’s process
4) Define close-out evidence
At minimum:
- updated remedial register
- photos where helpful
- note any exceptions or access constraints
A delivery workflow that scales across sites
For multi-site programmes, consistency wins.
- Inspect and generate a prioritised defect list (door IDs + clear defect language)
- Plan access and sequencing (cluster doors by area/work type)
- Deliver repairs/replacements with a consistent method statement
- Re-check and confirm doors close and latch in normal use
- Close out the register with evidence and exceptions
Communication and resident/occupant management
Even good technical work fails if access and expectations aren’t managed.
Practical steps that reduce programme friction:
- publish a simple resident/occupant note explaining why the works matter and what to expect
- use realistic appointment windows (and confirm reminders)
- plan for sensitive environments (care settings, night shifts, vulnerable residents)
- keep a clear escalation route for persistent no-access doors
Programme planning: a simple phasing model
| Phase | What you do | Output |
|---|---|---|
| Survey/inspect | Door-by-door checks with IDs | Defect register + priorities |
| Plan | Group works by type and location | Programme + access plan |
| Deliver | Repairs/replacements | Close-out evidence per door |
| Verify | Re-check close/latch and defects | Updated register (open/closed) |
How to measure progress (so it doesn’t drift)
For multi-site programmes, track:
- % doors inspected
- % defects closed out
- number of no-access doors (and ageing)
- repeat defects by type (e.g. closers vs seals)
If you can see trends, you can fix root causes (training, product choices, access approach) rather than re-visiting the same issues.
Repair vs replace: making consistent decisions
The programme usually slows down when every door becomes a debate.
Practical approach:
- define which defect types are typically repairable (adjustments, closer replacement, seals where appropriate)
- define which defect types usually trigger replacement assessment (severe damage, warped leaf, repeated failures)
- record the decision rationale in the register so it’s repeatable
Common programme pitfalls (and how to avoid them)
| Pitfall | What happens | Fix |
|---|---|---|
| No stable door IDs | Inspections and repairs can’t be matched | Create/register IDs before delivery |
| Access not planned | Programme stalls and defect ageing grows | Make access a dedicated workstream |
| Mixed scopes per visit | Same door is visited multiple times | Group by work type and area |
| Close-out not enforced | “Fixed” doors reappear as open defects | Require register updates + evidence |
What to include in a close-out pack
| Item | Why it matters |
|---|---|
| Updated door register (open/closed) | Shows progress and remaining risk |
| Before/after photos for key defects | Makes audits and handovers easier |
| Notes on repair method decisions | Supports governance (why repair vs replace) |
| Exceptions/no-access list | Prevents false confidence |
| Next actions / follow-on work | Stops issues reappearing later |
FAQs
Do we need to replace every non-compliant door immediately?
Not always. Many defects can be repaired, but only when repairs are appropriate to the door set and the defect type. Use a risk-based plan.
What’s the biggest reason programmes stall?
Access. Build your plan around it: communications, repeat visits, and a clear process for “no access” doors.
Related pages
Note
This article is general information. Align programmes to competent guidance and the building’s fire risk assessment.