Overview
In residential blocks, fire door programmes often split into two operational worlds:
- communal doors (corridors, stair cores, risers)
- flat entrance doors (access constraints and resident coordination)
Communal doors (common parts)
Typical characteristics:
- straightforward access
- easier re-inspection
- defects often related to wear and traffic
Common communal door defect patterns (table)
| Pattern | Why it happens | Typical first action |
|---|---|---|
| Closer issues (slam/creep/doesn’t close) | heavy traffic + poor adjustment | adjust/repair; check latch engagement |
| Damaged seals | wear and impacts | replace like-for-like; re-check gaps |
| Hold-open misuse (wedges/hooks) | operational pressure | remove wedge and solve root cause; consider compliant device |
| Frame/leaf damage | trolleys, deliveries, misuse | repair; assess if door set performance is affected |
| Missing signage/labels | works/painting cycles | replace consistently; keep records tidy |
Flat entrance doors
Typical characteristics:
- access planning required
- higher no-access rates
- defects may vary widely by door type and resident alterations
What changes operationally (the key differences)
The biggest difference isn’t the door — it’s the workflow:
- Access planning (appointments, comms, re-visits)
- Evidence of best endeavours when access fails
- Variation (resident alterations, mixed door types across blocks)
Common flat entrance door issues (table)
| Issue | Why it matters | What to do |
|---|---|---|
| No access | you can’t verify condition | log attempts + plan re-visit |
| Alterations (letterplates, cat flaps, trimming) | may compromise fire/smoke performance | escalate for competent assessment |
| Poor self-closing | door may not provide protection when needed | adjust/repair closer; verify latch |
| Damage to seals/threshold | smoke leakage risk | repair/replace; re-check gaps |
| Unknown door set type | hard to specify like-for-like repairs | record photos/labels; build a register |
A simple programme model that works
For many teams, the most reliable model is:
- communal doors: routine programme (easy access, easy re-check)
- flat entrance doors: scheduled campaign with comms + re-visits
Practical programme checklist (table)
| Item | Communal doors | Flat entrance doors |
|---|---|---|
| Access needed | usually none | always planned |
| Re-visits | simple | expected (mop-up) |
| Key output | defects + close-out | access logs + defects + close-out |
| Biggest risk | slow close-out | no-access drift |
| Best improvement lever | defect tracking | resident comms + scheduling |
Records to standardise (so audits are painless)
Minimum record set (table)
| Record | Why it matters |
|---|---|
| Door register with stable IDs | lets you re-check the same door |
| Inspection log (date, inspector, scope) | proves what was covered |
| Defect register (priority, owner, target date) | turns inspection into action |
| Close-out evidence (note + photo where helpful) | prevents disputes |
| No-access log (attempts + next action) | makes “best endeavours” defensible |
Access planning tips for flat entrance doors
Practical approaches that reduce no-access rates:
- clear notice with a simple time window (and why it matters)
- a contact route to rearrange
- a planned second visit for mop-up
- coordination with housing/care teams for vulnerable residents
Simple no-access workflow (table)
| If access fails | Record | Next step |
|---|---|---|
| resident not home | date/time + method | rebook window |
| resident refuses | note refusal politely | escalate per building policy |
| safety concerns | note constraint | arrange accompanied visit |
FAQs
Do we need the same checklist for communal and flat entrance doors?
Use the same baseline checks (self-closing, latching, seals, damage), but add access/evidence steps for flat entrance doors.
What’s the fastest way to improve outcomes?
Two things: stable door IDs and a close-out loop. Without those, programmes turn into repeated surveys with no improvement.
What to standardise across both
- door IDs and location references
- defect categories and priorities
- close-out evidence
Regulatory context (why flat entrance doors feel harder)
In England, residential portfolios are under increasing scrutiny around door management and records. The practical impact is that programmes need to be repeatable and defensible.
For many buildings, the operational headline is:
- communal doors are straightforward to check and re-check
- flat entrance doors need best-endeavours access management and evidence when access isn’t achieved
If you’re managing buildings that fall under specific requirements (e.g., certain higher multi-occupied residential buildings), make sure your programme reflects those expectations, but keep the same core disciplines: IDs, defect tracking, and close-out.
Inspection frequency: a sensible way to set it
Rather than one fixed frequency, use risk tiers.
Example frequency bands (table)
| Door type / context | Typical frequency band | Why |
|---|---|---|
| Protected routes (stairs/lobbies) | monthly to quarterly | highest consequence if door fails |
| General communal doors | quarterly to 6‑monthly | wear + traffic |
| Flat entrance doors (in scope) | annual programme + mop-up visits | access is the constraint |
A simple annual plan (so it doesn’t drift)
Programme rhythm (table)
| Quarter | Communal doors | Flat entrance doors |
|---|---|---|
| Q1 | baseline inspection + triage | comms + first campaign |
| Q2 | re-check P1/P2 close-outs | mop-up no-access |
| Q3 | routine inspection | second campaign (if needed) |
| Q4 | governance review + planning | mop-up + next-year access plan |
Resident communication: what actually reduces no-access
People respond better when the message is simple and practical.
Comms content that works (table)
| Include | Example |
|---|---|
| Why it matters | “This is a safety check to ensure your flat entrance door closes and seals correctly.” |
| What will happen | “We’ll be in your doorway for 5–10 minutes.” |
| When | “Tuesday 10am–1pm (please be available during this window).” |
| How to rearrange | phone/email contact |
| What if no access | “We will re-attend on X date and record attempts.” |
Evidence packs: what good looks like for both door types
Evidence pack checklist (table)
| Evidence | Communal doors | Flat entrance doors |
|---|---|---|
| Door ID + location | yes | yes |
| Pass/fail notes | yes | yes |
| Photos for P1/P2 defects | recommended | strongly recommended |
| Close-out record | required | required |
| No-access log | usually not needed | required |
Related pages
Note
This article is general information. Align your programme to the building’s fire risk assessment and competent guidance.