Fire & Life Safety Inspection Requirements

Fire and life safety is the one area of building operations where the consequences of a missed date are not measured in dollars. It is also, in most buildings we are asked to take over, the least organized: the sprinkler contractor’s reports live in one inbox, the alarm certificates in a filing cabinet, the extinguisher tags on the extinguishers themselves, and nobody can answer the fire marshal’s actual question — show me the last twelve months — without a two-day scramble through three vendors’ archives.

That gap is almost never a safety decision. It is a records decision that became a safety problem. This guide lays out what a commercial building in the DC, Northern Virginia, and Maryland market is generally expected to inspect, how often, who is permitted to perform and certify each item, and what a defensible record actually looks like — the same structure Levaru builds when we take on compliance inspections for a property.

One framing note before the schedule. Fire and life safety requirements come from three stacked sources: the model codes your jurisdiction adopts, the NFPA standards those codes reference by number, and the conditions your own insurer attaches to your policy. They overlap heavily but they are not identical, and the strictest of the three is the one you actually have to meet.

What counts as a fire and life safety inspection?

Broader than most owners assume. The category covers every system whose job is to detect a fire, suppress it, contain it, or get people out of the building — plus the systems that keep those working when normal power does not.

In a typical commercial building that means: the fire alarm and detection system; water-based suppression (sprinklers, standpipes, fire pump, and the backflow preventers feeding them); portable fire extinguishers; emergency and exit lighting and the egress path itself; fire doors and other rated barriers; kitchen hood suppression where there is commercial cooking; smoke control where the building has it; emergency and standby power; elevator firefighters’ emergency operation; and, increasingly, in-building emergency responder radio coverage.

Two of those are worth calling out because they get orphaned. Fire doors are a suppression-adjacent system with a real annual inspection requirement under NFPA 80, and they fail constantly in occupied buildings — propped open, painted hardware, damaged edges, missing labels — because nobody owns them. And egress is not a device at all; it is a condition, which means it is the only item on the list that can go out of compliance between inspections because a tenant stacked boxes in a corridor. Anything that can degrade daily needs a daily-life owner, not an annual contractor.

Which inspections does a commercial building need, and how often?

The intervals below are the NFPA-referenced conventions most DMV jurisdictions build on. Treat them as the planning baseline, then reconcile against your local code and your insurance policy — both can be stricter, and neither is ever more permissive.

• Fire alarm system (NFPA 72) — annual inspection and testing of the full system, with certain devices and functions on their own cycles. Smoke detector sensitivity is verified on a multi-year cycle rather than every year. Batteries, notification appliances, and initiating devices all carry their own test requirements.
• Sprinkler systems (NFPA 25) — a layered schedule rather than one date: gauges and control valves on short monthly-to-quarterly cycles depending on whether valves are locked or electrically supervised; waterflow alarm devices quarterly; a full annual inspection; and a five-year internal obstruction investigation that owners routinely forget because four years pass between reminders.
• Standpipes (NFPA 25) — annual inspection plus a five-year flow test.
• Fire pump (NFPA 25) — a weekly or monthly no-flow churn test depending on pump type, plus an annual flow test at rated capacity.
• Backflow preventers — annual testing by a certified tester, with results filed with the water purveyor. This one has two masters: the fire code cares that the water gets to the sprinklers, the water utility cares that nothing flows backward into the main, and the utility usually has the shorter fuse on a late report.
• Portable extinguishers (NFPA 10) — a monthly visual inspection (which building staff can perform and record), annual maintenance by a licensed servicer, internal maintenance on a six-year cycle for most stored-pressure units, and hydrostatic testing on a longer cycle that varies by extinguisher type.
• Emergency and exit lighting (NFPA 101) — a brief monthly function test and an annual full-duration test, in which battery units must carry their load for 90 minutes.
• Fire doors (NFPA 80) — annual inspection of fire door assemblies, documented per opening.
• Kitchen hood suppression (NFPA 96) — semiannual inspection of the suppression system; hood and duct cleaning on a frequency driven by cooking volume, from monthly for high-volume operations to annually for light use.
• Emergency and standby generators (NFPA 110) — weekly inspection, monthly exercise under load, and a longer load-bank test on a multi-year cycle for systems where one is required.
• Elevator firefighters’ emergency operation — Phase I recall tested monthly and Phase II tested annually, separate from the elevator’s own periodic inspection and certificate. Our elevator compliance guide covers that side in detail.

The pattern worth noticing: the annual items are the ones everybody remembers, and the monthly and multi-year items are the ones that get missed. Monthly items get missed because they belong to staff, not to a vendor with an invoice; multi-year items get missed because no habit forms around a five-year interval.

Who is allowed to perform and sign off on each inspection?

There are effectively three tiers, and mixing them up is how buildings end up with records that do not survive review.

Building staff can legitimately perform and document the routine observational layer: monthly extinguisher visual checks, monthly emergency light function tests, egress and fire-door walkthroughs, generator weekly visual inspections, and housekeeping of anything blocking a device or an exit. These are real compliance activities and they belong in the same record as the contracted work, not in a separate notebook.

Licensed and certified specialists must perform the tested-and-certified layer: fire alarm inspection and testing, sprinkler and standpipe inspection and testing, fire pump flow tests, backflow testing, extinguisher annual and internal maintenance, hood suppression service, and elevator inspections. In Virginia, Maryland, and the District these are licensed activities, and in several cases the technician’s certification is what gives the report its standing. That is the model Levaru runs across the regulated trades generally: the routine layer self-performed by our own staff, the licensed layer performed by licensed subcontractors we procure, supervise, and hold to the schedule — the same hybrid approach described in our commercial electrical maintenance guide.

The authority having jurisdiction (AHJ) — usually the local fire marshal — performs its own inspections on its own cycle and can require correction of anything it finds regardless of what your contractor’s report said. The AHJ is not a fourth vendor; it is the party your records exist to satisfy.

How do DC, Virginia, and Maryland differ?

Enough to matter, not enough to justify three separate programs.

The District enforces the DC Construction Codes, which incorporate the International Fire Code with District amendments, through DC Fire and EMS. Reporting expectations for third-party inspection results are more formalized here than in much of the region, and downtown’s building stock — older, taller, heavily tenanted — tends to bring more systems into scope per building.

Virginia operates the Statewide Fire Prevention Code, an IFC-derived code adopted at the state level and enforced locally. The practical consequence is that the code text is consistent from Arlington to Fairfax to Alexandria while the enforcement posture is not: local fire marshals differ in inspection frequency, in how they want reports submitted, and in how quickly they follow up on a deficiency.

Maryland builds on the NFPA lineage — the State Fire Prevention Code adopts NFPA 1 with state amendments — enforced by the State Fire Marshal or by local fire authorities in the counties that have their own, Montgomery and Prince George’s being the two most owners in this market deal with.

For a portfolio spanning all three, the workable approach is a single program built to the strictest common denominator, with jurisdiction-specific reporting and follow-up handled as local variations rather than as separate calendars. Trying to run three parallel compliance programs is how a building in the third jurisdiction quietly gets less attention than the other two.

What happens when an inspection finds a deficiency?

A deficiency report is not the end of the inspection; it is the start of a work order, and the gap between those two is where most compliance programs actually fail. The contractor tests, the report lists three impairments and a dozen minor findings, the report is filed, and nothing is dispatched — so the next annual report lists the same findings, now a year older, in writing, with dates. A stack of reports documenting an uncorrected condition is materially worse for an owner than no stack at all.

Three habits close that gap. Every finding becomes a tracked work order the day the report lands, with an owner and a target date. Impairments get handled under an impairment procedure — tagged, communicated to the fire department and the insurer where required, with a fire watch if the system is out of service — rather than as ordinary maintenance. And the closeout evidence attaches to the original finding, so the record shows not only that a problem was found but when and how it was resolved.

What does a defensible record look like?

The test is simple: when the fire marshal or the insurer’s loss-control inspector asks for the last twelve months, can you produce it in minutes, from one place, complete?

That means every system inventoried with its make, model, location, and interval; every scheduled event generated in advance rather than remembered; every completed inspection stored with the technician’s certification, the date, and the findings; every deficiency tracked to closure with evidence; and the monthly staff-performed checks captured in the same system as the contracted work. Levaru runs this as a live calendar in our CMMS rather than as a folder of PDFs — the schedule generates the work, the work generates the record, and the record is queryable. That is the same discipline described in our building compliance calendar and in the broader preventive maintenance program approach; fire and life safety is simply the part of it where the stakes remove the option of doing it informally.

Frequently asked questions

What is the difference between an inspection, a test, and maintenance?

NFPA uses the three terms precisely. An inspection is a visual examination to confirm a system appears to be in operating condition and free of damage. A test is a procedure that verifies the system actually performs — flowing water, sounding notification devices, transferring the generator to load. Maintenance is the work that keeps it that way, including repair and replacement. A report that only documents inspection has not established that anything works, which is why the code assigns test intervals separately.

Who is the authority having jurisdiction for my building?

In most of Northern Virginia and Maryland it is the local fire marshal’s office for the county or city; in the District it is DC Fire and EMS. Some systems answer to a second authority as well — backflow preventers to the water utility, elevators to the state or county elevator authority. If you are not certain, the fire marshal’s office for your locality is the right first call, and it is worth making that call before there is a problem rather than during one.

Can building staff perform any of these inspections themselves?

Yes, and they should. Monthly extinguisher visual checks, monthly emergency light function tests, generator weekly inspections, and egress and fire-door walkthroughs are routine facility work that does not require a licensed contractor. What matters is that the results are recorded in the same system as the contracted inspections, with dates and locations. Tested-and-certified work — alarm, sprinkler, fire pump, backflow, hood suppression, extinguisher annual service — requires licensed technicians.

How long do we need to keep inspection records?

Longer than the interval, and longer than most owners assume. Retention requirements vary by jurisdiction and system, and insurers frequently ask for multi-year history during underwriting or after a loss. The practical answer for an owner is to keep everything indefinitely in a system that can retrieve it, because the cost of digital retention is nil and the cost of not producing a record when it is requested is not.

What does a fire watch actually require?

When a fire alarm or suppression system is out of service beyond the allowed window, the code generally requires a fire watch: trained personnel patrolling the affected areas on a defined route and interval, with no other duties, a means to notify the fire department, and a written log. The specifics — who qualifies, what interval, when the AHJ must be notified — are set locally, so the time to learn your jurisdiction’s rule is when you are planning a system outage, not when one starts unexpectedly.

Does insurance require anything beyond code?

Frequently. Property insurers commonly attach conditions that go past the fire code — more frequent testing, specific inspection scopes, documentation delivered on a schedule, or loss-control recommendations that become policy conditions on renewal. Those obligations sit in the policy, not the code, and they are enforced by a different mechanism: not a citation, but a coverage argument after a loss. Read them into the same compliance calendar as everything else.

Fire and life safety compliance is not intellectually difficult. It is an inventory problem, a scheduling problem, and a records problem — three things that are entirely solvable with a system and entirely unsolvable with good intentions. If your building’s evidence lives across several vendors’ inboxes, that is the thing worth fixing first, and it is what our compliance inspections program is built to do for properties across the DMV.