Inspections, and the evidence that has to survive them

The question that decides an inspection is never "do you do inspections". It is "show me the one for this room, on this date". Teams that fail that question are almost never teams that skipped the work. They are teams whose evidence is scattered.

This guide covers what a complete record contains, which inspections are not yours to schedule, and how to make the evidence fall out of the work instead of being assembled afterwards.

What a complete record contains

Strip away the format and every regulator, insurer and owner wants the same five things. If your record has all five, the format rarely matters.

• •Who did it, by name, and whether they work for you
• •When, to the minute, from something other than their memory
• •Where, specifically enough to identify one room or one machine
• •What they found, including the things that passed
• •What happened next about anything that failed, and the proof it closed

The fifth one is where programmes fail

The first four are a filing exercise. The fifth is a process. A finding that is noticed and never closed is worse than a finding that was never noticed, because it proves you knew.

The fix is to make the follow-up part of the same record rather than a separate system. When a failed check raises tracked work automatically, with the photograph and the location already attached, the loop closes because closing it is the path of least resistance.

Know which inspections are not yours to schedule

Most maintenance intervals are yours to tune. A subset are set by law, by standard or by your insurer, and those are a floor rather than a plan. In the United States the common ones in a commercial building include water-based fire protection under NFPA 25, fire doors under NFPA 80, emergency lighting and egress under NFPA 101, emergency power under NFPA 110, hazardous energy control under 29 CFR 1910.147, and powered industrial trucks under 29 CFR 1910.178. Requirements differ by country and by state, so check what applies where you operate.

Mark statutory items in your schedule so that a well-meaning pruning exercise cannot shorten or remove them, and so anybody can tell the required from the chosen.

Four places evidence goes to die

• •A paper form in a filing cabinet nobody can search
• •A photograph on the personal phone of somebody who has left
• •A spreadsheet that records the result but not what was seen
• •A work order system that knows about the fix but not the round that found it

Proof of presence, without surveillance

Location tracking on technicians is bad for morale and often legally awkward. A code on the door does the same job with none of the problems: scanning it records that this person was at this equipment at this time, and it happens because scanning is also the fastest way to open the job.

Record the passes, not only the failures

An inspection that only records exceptions cannot prove the rest was looked at. This is the most common structural weakness in inspection records, and it is the one that turns a good programme into an unprovable one. Every item gets an answer.

Say what you could not check

Equipment behind a locked door, running and unable to be stopped, or obstructed by stored goods. Recorded as not assessed, with a photograph, it is a finding. Left blank, it silently reads as a pass, which is the worst outcome available.

Keep the certificate and the findings together

A completed statutory inspection with open recommendations is not compliance. The most common serious gap in this whole area is a report that arrived, was filed, and contained actions nobody tracked. Every inspection with findings should raise work automatically.

Start with the round that scares you

Teams that try to move everything at once move nothing. Pick the round you would least like to be asked about, put that one on a phone, and run it for a month. The second one takes a fraction of the effort, because you will have learned how your team actually works.