Writing a fire safety log people will actually maintain

Almost every building has a fire safety log. Far fewer have one that is current. The gap between those two facts is where most fire safety record-keeping quietly fails. A log that is filled in diligently for three months and then abandoned is not a half-success; it is a liability, because it shows that checks were once being done and then stopped. The skill is not in designing a thorough log. It is in designing one that the people on the ground will keep up when nobody is watching, week after dull week.

Why logs get abandoned

Logs are abandoned for reasons that have little to do with how seriously people take fire safety. They are abandoned because the log is too long, so completing it feels like a chore disproportionate to the task. They are abandoned because it is unclear who is responsible, so everyone assumes someone else has it. They are abandoned because the log lives somewhere inconvenient, so checking the lift on the top floor and recording it in an office two floors down becomes two jobs instead of one. And they are abandoned because nobody ever looks at them, so the person filling them in concludes, reasonably, that nobody cares.

Each of these is a design problem, not a discipline problem. Fix the design and the discipline tends to follow.

What the log has to carry

A fire safety log records that the recurring fire safety duties are being done, and provides the evidence that they were. The Fire Safety (England) Regulations 2022, in force 23 January 2023, require responsible persons of high-rise residential buildings to carry out monthly checks of firefighters' lifts and key firefighting equipment, among other duties. The log is how you prove those checks happened. So at minimum it needs to capture, for each check: what was checked, when, by whom, the result, and what was done about anything found wrong.

The temptation is to add more. Resist it. Every field that does not earn its place is a field that makes the log slower to complete and likelier to be skipped.

Design for the person holding the clipboard

The single most useful design principle is to write the log for the person who fills it in, not the person who audits it. The auditor reads the log a few times a year. The caretaker fills it in every week. If those two interests conflict, the day-to-day user has to win, because a log that is auditor-perfect but never completed audits to nothing.

In practice that means:

• Short, fixed items. The same checks each time, phrased as questions with a clear yes or no, not free-text prompts that invite essays or silence.
• Recorded where the check happens. A check completed on a phone at the point of inspection beats one transcribed later from memory or a scrap of paper.
• An obvious owner. Each recurring check has a named person and a clear schedule, so it is never nobody's job.
• A visible exception path. When something is wrong, recording it should trigger an action, not just sit as a note that no one revisits.

A simple weekly and monthly shape

Most residential fire safety logs settle into a rhythm. Setting that rhythm out explicitly helps people keep to it.

The exact items depend on the building and its fire risk assessment. The point of the table is the rhythm: a small, predictable set of things on a known cadence is far more maintainable than a long, occasional audit. The monthly checks in particular map directly onto duties we cover in monthly checks that keep a high-rise compliant.

Close the loop on what is found

A log that records faults but does nothing with them trains people to record less, because they learn that flagging a problem creates work for them and resolution from no one. The opposite habit is what keeps a log alive: when a check finds a fault, it becomes a tracked action with an owner and a date, and the person who flagged it sees it get dealt with. That feedback is what turns the log from a paperwork exercise into a tool people trust, and trust is what sustains a record over years rather than months.

The test of a good log

Hand your fire safety log to someone who has never seen it and ask them to complete this week's checks using only what is in front of them. If they can, without asking who is responsible or where to record it, the log is well designed. If they cannot, the gaps you see are the same gaps that appear when the regular person is on holiday or has left. A log that depends on one person's memory is a log waiting to lapse.

SAMRISK is built so that recurring fire safety checks have owners and due dates, faults become tracked actions, and the record is kept at the point of inspection rather than copied up later. You can see how this fits with the wider record on the compliance calendar and risk assessments pages. A log only protects a building if it is kept, so the worthwhile work is making it easy to keep.