What an inspector actually asks for, and how to have it ready

An inspector walking a building is trying to establish one thing: that the life-safety equipment in front of them is real, accounted for, and has been looked after on some schedule by someone who knew what they were doing. Whatever they ask for — a log, a tag, a report, a list — it is a way of getting at that.

Which means the contractor who can produce a per-unit history, on the spot, is finished with the conversation in a minute. The contractor who has to go looking is the one who ends up with a note in the file.

• An inventory: what devices exist in this building, and where each one is.
• Evidence of the last service on a specific unit, with a date.
• Who performed it — a name, not a company logo.
• Open deficiencies: what is wrong right now, how bad, and what is being done about it.
• What happened to the deficiencies from last time — the closure trail, not just the finding.
• The next scheduled visit.

Notice how much of that is history rather than current state. A tag on the wall can show the last date. It cannot show the trail.

The tag is genuinely useful — it is readable by anyone standing there, it needs no battery and no signal. The problem is that it is a single line of the story, stored in the worst possible place: the building you do not control.

Tags get painted over, torn off during a remodel, soaked, or filled in by three different hands in three different pens. And a tag never answers “show me the last four visits.” The comparison in full is here.

Readiness is not a filing exercise you do at the end of the quarter. It is a by-product of capturing the visit properly while you are standing in the building:

• Give every device a durable identifier, and put a scannable tag on it so anyone can pull up its history.
• Record each checklist item as you go, offline if the building has no signal, and let it sync when you are back in range.
• Photograph every deficiency at the moment you find it, attached to that unit.
• Generate the report before you leave the parking lot and email it to the building owner the same day.
• Let the next due date be calculated from the visit, so the schedule maintains itself.

Do that and “audit readiness” stops being a project. It is just what your records already look like.

Here is the honest way to find out where you stand. Pick a building you serviced four months ago. Without calling anyone, produce: the device list, the last inspection date for one specific unit, the technician’s name, the open deficiencies, and a photo of one of them. If that takes longer than a minute, the gap is not in your fieldwork — it is in where the record lives.

What does an inspector usually want to see first?

A list of the devices in the building and evidence that each one was checked on its cycle. The question underneath it is always the same: can you show me this specific unit, and when someone last touched it.

How long should inspection records be kept?

Longer than you think, and the exact expectation varies by jurisdiction and by the authority having jurisdiction. The practical rule is that a record should outlive the technician who created it and the phone the photos were taken on.

Does the building owner get a copy?

They should, and it is a good habit even where nobody insists on it. A report emailed to the owner the day of the visit ends most disputes before they start, and it is the cheapest marketing a contractor has.