What should be checked during a monthly fire-extinguisher inspection?

A monthly visual typically covers the pressure gauge, the safety pin and tamper seal, the hose or nozzle, the body for corrosion or damage, the label, the mounting, and whether the unit is visible and accessible. Requirements vary by jurisdiction, so confirm what your AHJ expects.

What information should be recorded, not just checked?

Record the identifying fields — customer, site, location within the site, asset ID, type, size, and manufacture date — along with the result of each condition check, the technician's name, the date and time, and the next-due date. Identity fields are the ones most often skipped and most often needed later.

Why does an asset ID matter so much?

An asset ID is what ties this year's inspection to last year's. Without one, you have a collection of separate visits rather than a history for a specific extinguisher, and any question about one unit turns into a manual search.

Should photos be part of an inspection record?

They help when a finding is disputed or hard to describe — a corroded cylinder, a blocked cabinet, a damaged bracket. InspectWarden allows photo evidence to be attached to a deficiency.

Does this checklist make my inspections compliant?

No. It is a practical field list, not a compliance determination. Inspection and documentation requirements vary by jurisdiction and by the authority having jurisdiction, and their requirements are the ones that apply.

What to Record During a Fire-Extinguisher Inspection

Most inspection checklists tell you what to look at. Fewer tell you what to write down.

That gap is where records fail. A technician can do a careful, correct inspection and still leave behind a record that cannot answer a question asked six months later. The work was fine. The record was thin.

This guide covers the fields that make an inspection record hold up: what identifies the asset, what describes its condition, and what closes the loop on the outcome.

Three kinds of fields

Every useful inspection record does three jobs.

Identity answers which unit is this? Condition answers what did you find? Outcome answers what happens now?

Most paper tags do the second job well and the other two barely at all. That is why a shoebox of tags is hard to turn into an answer.

Identity — which unit is this?

Identity fields are the ones techs are most tempted to skip, because on site the answer is obvious. It stops being obvious the moment you are not standing in front of the unit.

Customer or account — who this belongs to
Property or site — the building, with an address
Location within the property — "Lobby, south wall," not just "Lobby"
Asset ID or tag number — a number that stays with the unit for its whole life
Type and size — ABC dry chemical 10 lb, CO2 5 lb, K-class
Manufacture date — drives hydrostatic test and internal maintenance intervals

The location field earns its keep on the second visit. "Third floor, north stairwell landing" is the difference between a technician finding a unit in ten seconds and wandering a building.

Asset ID deserves the same care. It does not need to be sophisticated — a sequential number on a durable label is enough. What matters is that it never changes and never gets reused. An ID that gets recycled onto a replacement unit quietly corrupts the history of both.

Condition — what did you find?

These are the checks a monthly visual covers. They are quick, and they are the reason the visit exists.

Pressure gauge — needle in the operable range
Safety pin and tamper seal — present and intact
Hose, nozzle, or horn — clear, uncracked, unobstructed
Body condition — no corrosion, dents, or damage
Label and instructions — present and legible
Mounting or bracket — secure, at correct height
Access and visibility — nothing stacked in front of it

The last one is the most common real-world failure and the least often recorded. An extinguisher behind a pallet is a problem, and it is a problem the customer can fix that afternoon — but only if somebody wrote it down.

Record each check as a clear pass or fail rather than a checkmark. A checkmark tells you a tech looked. A pass or fail tells you what they saw.

Leave room for a short comment on any item, and use it when the answer is not binary. "Gauge reads at the low edge of green" is a genuinely useful note — it is not a failure today, but it is the sentence that explains a recharge three months from now.

Outcome — what happens now?

Overall result — pass or fail for the unit
Deficiency detail — what is wrong, and how serious
Action taken — recharged, tagged out, replaced, or referred
Next due date — carried forward automatically, not remembered
Technician name — who performed the work
Date and time — when it happened
Photo evidence — where the finding benefits from one

A deficiency with no severity is hard to schedule against. A blocked extinguisher and a missing unit are not the same call, and a record that flattens both into "fail" pushes the triage back onto whoever reads it later.

The visit is not the only thing being recorded

Monthly visuals are not the whole picture, and the record should make clear which kind of visit it was.

A monthly visual is quick and mostly external. An annual maintenance check goes further. Internal maintenance and hydrostatic testing happen on much longer intervals, driven by the manufacture date and the type of unit. Those intervals are the reason the manufacture date belongs in the identity fields — it is the field that tells you a unit is approaching a test it cannot skip.

A record that captures only "inspected, passed" leaves the reader to work out which of those visits happened. Naming the visit type takes one field and removes the ambiguity permanently.

What a good record looks like six months later

The real test of an inspection record is not how it looks on the day. It is whether it answers a question you did not anticipate.

The questions that actually arrive tend to be specific. A property manager asks when the extinguisher outside suite 300 was last serviced. An inspector asks to see the history for one building. A customer disputes an invoice for a recharge. A tech who no longer works for you left a note that now needs interpreting.

Every one of those is answerable in seconds if the identity fields were captured, and painful if they were not. That is the whole argument for the boring fields. They are not for the technician doing the work — they are for whoever has to defend the work later, which is usually the owner.

The three fields shops skip and regret

Asset ID. Without a persistent ID, this year's inspection cannot be tied to last year's. You have a stack of visits rather than a history for a unit. Every question about a specific extinguisher becomes a manual search.

Photo. A photo of a corroded cylinder or a blocked cabinet ends a disagreement before it starts. It also spares the tech from writing a paragraph.

Technician name. Not to assign blame — to answer questions. Six months later, someone will ask what a note meant. Knowing who wrote it is the shortest route to the answer.

A printable version

The checklist below is a one-page field sheet covering the identity, condition, and outcome fields on this page. It is free, requires no signup, and is meant to be printed and put on a clipboard.

Download the printable field checklist (PDF)

If you already use a sheet that works, keep it. The point is not the format — it is that the same fields get captured on every visit.

How InspectWarden handles these fields

InspectWarden runs the monthly visual as a guided checklist. Each item is recorded as a pass or fail with an optional comment, and the saved record keeps the site, the asset, the inspector, the timestamp, and the next-due date together.

Deficiencies are recorded against the inspection with a severity, a status of open or resolved, notes, and timestamps, and photo evidence can be attached. Saved inspections can be downloaded as a PDF report covering the inspection summary, site and asset details, checklist results, and deficiencies.

Today the product is built around portable fire extinguishers. Other system types, a customer-facing portal, and barcode or QR scanning are not built yet.

A note on requirements

Inspection frequency, documentation, and retention requirements vary by jurisdiction and by the authority having jurisdiction (AHJ). The field lists on this page are a practical starting point drawn from common monthly visual practice — they are not a compliance determination. Confirm what your AHJ requires, and treat their answer as the one that counts.

Questions in the field

Frequently asked questions

What should be checked during a monthly fire-extinguisher inspection?: A monthly visual typically covers the pressure gauge, the safety pin and tamper seal, the hose or nozzle, the body for corrosion or damage, the label, the mounting, and whether the unit is visible and accessible. Requirements vary by jurisdiction, so confirm what your AHJ expects.
What information should be recorded, not just checked?: Record the identifying fields — customer, site, location within the site, asset ID, type, size, and manufacture date — along with the result of each condition check, the technician's name, the date and time, and the next-due date. Identity fields are the ones most often skipped and most often needed later.
Why does an asset ID matter so much?: An asset ID is what ties this year's inspection to last year's. Without one, you have a collection of separate visits rather than a history for a specific extinguisher, and any question about one unit turns into a manual search.
Should photos be part of an inspection record?: They help when a finding is disputed or hard to describe — a corroded cylinder, a blocked cabinet, a damaged bracket. InspectWarden allows photo evidence to be attached to a deficiency.
Does this checklist make my inspections compliant?: No. It is a practical field list, not a compliance determination. Inspection and documentation requirements vary by jurisdiction and by the authority having jurisdiction, and their requirements are the ones that apply.