The safety inspection isn't finished when you've walked it

The manager and the safety rep walked the site in March. They found eleven things. Nine were small and got fixed that week. Two were not: the kitchen extraction, and a fire exit blocked by deliveries every Tuesday. The report was written up, signed and filed.

It is now September. The extraction has not been dealt with, and nobody can say whose job it was. The deliveries are still in the way on Tuesdays.

The walk itself went fine. What failed came afterwards — and that is the part this guide spends most of its time on.

What a safety inspection is for

A safety inspection is a systematic walk through a workplace to find risks before they hurt someone. A manager and a safety representative go together, look, ask, and write down what they find.

It is a method, not an end in itself. It belongs inside a loop that repeats: investigate, assess, act, follow up. The walk is the “investigate” step. If you only ever walk, you have done a quarter of the work.

Exactly what is required of you — how often, what has to be recorded, who has to be involved — depends on where you operate and how many people you employ. Check the specifics with someone qualified locally. What follows is the practical shape of a good inspection, not legal advice.

Who should walk it

At minimum, the manager responsible for the area and a safety representative where you have one. Where you do not, give the people who work there a genuine way to take part — an inspection done to a team finds less than one done with it.

Two additions are worth the trouble:

• Someone from outside the area. A colleague from another site notices what the people who work there every day have stopped seeing. Familiarity is the inspection’s worst enemy.
• Someone who actually works in the space. The manager and the safety rep know where the risks ought to be. The person on the pass knows where they are.

How often

Frequency follows risk, not the calendar. An office is often fine annually. A kitchen, a stockroom or a plant room needs far more. Quarterly is a sensible starting point for restaurants, hotels and stores, with shorter intervals for the areas where most happens.

Walk it on an ordinary working day, in normal operation. An inspection at nine on a Tuesday in July, with half the team on holiday and the kitchen cold, shows you a workplace that does not exist.

The checklist, by area

Walk area by area rather than risk by risk. It follows how people actually move through the building, and it makes it much harder to miss a room entirely.

The building

• lighting, including stairwells, cold rooms and spaces with no windows
• noise and ventilation
• temperature and draughts
• floors: slip risk, thresholds, damaged surfaces
• housekeeping and clutter, especially in walkways

Fire and evacuation

• escape routes clear, the whole way out
• exit signage visible and lit
• extinguishers and fire blankets in place and in date
• assembly point known by the team, not just marked on a plan
• alarm procedure: who does what, and who accounts for people

Kitchens

• hot surfaces, fryers and burn risk
• knives: storage, sharpening, guards
• slip risk at the wash-up and cold room
• manual handling and the aids available
• chemicals: labelling, storage, safety data sheets, eye wash

Stockroom and deliveries

• lifting, lifting aids and working heights
• pallet trucks and forklifts: authorisation and condition
• stacking heights and collapse risk
• transport routes clear of deliveries that were never put away

Front of house, shop floor and till

• lone working: when, where, and what the procedure is
• threats and violence, including cash handling and closing up
• alarms and a way to call for help
• ergonomics at the till and terminal

What a walk does not show you

• induction of new starters and temporary staff
• first aid: equipment, and who is trained
• near misses reported since the last inspection
• things the team has raised that never became a job

That last one earns its place. Ask it directly: what have we said we would fix that is still not fixed?

The part that decides everything

An inspection produces findings. Findings that are not dealt with on the spot need two things written next to them, and almost nothing else matters as much:

When it will be done, and who will make sure it happens.

Two fields. That is the whole difference between a report and a safety programme. In most places that record anything at all, some version of this is what you are actually required to keep — but even where it is not, it is the only thing that turns a list into work that gets done.

Read the opening of this guide again with that in mind. The kitchen extraction had neither field. It was written down, which felt like something had happened, but it did not sit with anyone.

Why inspections die in a folder

It is rarely indifference. It is almost always the format.

The report is written on paper or in a document. It goes by email to the people who were there, and maybe into a folder. None of them has it open next week. There is no reminder, no owner in any system, nothing that speaks up when the date passes. The next inspection starts from zero and often finds the same things again.

The fix is not writing better reports. It is that a finding stops being a line in a document and becomes a job that someone owns and that stays open until it is closed.

Running it on a phone instead

Set the inspection up as a checklist per area and walk it on a phone. Put a QR code at each location — kitchen, stockroom, entrance — so whoever is walking opens the right checklist where they are standing, and the scan is logged with their name and the time.

Items are answered yes or no, with text, multiple choice, a temperature or a photo. A photo of the blocked fire exit says more than a line of text, and it is much harder to argue away.

Anything that is not right is raised there and then as a deviation with an owner and a due date — the two things a finding needs. It stays open until it is closed, and the whole walk is stored with who did it, when, and what was answered. When an inspector, an insurer or a new manager asks what you did about it, the history is there.

The safety programme is still yours. Todolo is not a safety management system and does not run it for you. What it does is make sure every finding has a when and a who from the moment it is spotted, rather than afterwards.

Common questions

How often should we inspect?

There is no single right frequency; it follows the risks. Offices are often fine annually, kitchens and stockrooms need more. Quarterly is a reasonable starting point in hospitality and retail.

Who should take part?

The manager responsible for the area and a safety representative where you have one, plus — if you can — someone from another site and someone who works in the space every day.

What is the difference between a safety inspection and a food safety check?

A safety inspection is about risks to the people working. A food safety self-check is about the business meeting the requirements that apply to it. They often cover the same room and can run in the same app, but they answer different questions under different rules.

Can software replace our safety programme?

No. The duty sits with the employer and cannot be handed to a system. Todolo is the checklist you walk with and the follow-up afterwards: every finding gets an owner and a due date, and the history is there when someone asks.

Start with your last report

You do not need to change anything to try this. Pull up the report from your most recent inspection and go through it with two questions per line: who owns this, and when is it due? The lines with neither answer are the ones that will still be there at the next inspection.

In thirty minutes we will walk through what your own inspection checklist would look like in Todolo, area by area. There is no long contract to sign, and there is a 30-day money-back guarantee.

Book a 30-minute demo