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 can also be the least organized, especially after a change of manager: 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 a simple request from the fire marshal — show me the last twelve months — without a two-day scramble through three vendors’ archives.

That gap is usually not a safety decision. It is a records problem that can become 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 (the 2021 International Fire Code (opens in a new tab) sends extinguishers to NFPA 10, water-based systems to NFPA 25 and fire alarms to NFPA 72), and the conditions your own insurer attaches to your policy. They overlap heavily but they are not identical, and since you have to meet all three, the strictest one governs in practice.

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 in-building emergency responder radio coverage, which the model fire code requires in new buildings (IFC Section 510).

Two of those are worth calling out because they get orphaned. Fire doors are a passive containment system with a real annual inspection requirement: NFPA 80 calls for each fire door assembly to be inspected and tested at least annually, with a written record (NFPA’s fire door FAQ (opens in a new tab)). The checks — legible labels, damage, clearances, closing and latching — cover exactly what daily use wears down, and the fire code bars blocking or disabling fire doors (IFC Section 705.2). They stay compliant only if someone owns them. And egress is not a device at all; it is a condition, which means it can go out of compliance any day 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 come from the NFPA standards the region’s fire codes reference. Treat them as the planning baseline, then reconcile against the code edition your jurisdiction enforces and your insurance policy: intervals change between editions, and either can add requirements.

• Fire alarm system (NFPA 72) — annual inspection and testing of the system, with certain devices and functions on their own cycles. Smoke detector sensitivity is checked within a year of installation and every other year after that, stretching to as long as five years once results stay in range (IFC Section 907.8.3). Batteries, notification appliances, and initiating devices all carry their own test requirements.
• Sprinkler systems (NFPA 25) — a layered schedule rather than one date (NFPA’s summary of NFPA 25 frequencies (opens in a new tab)): control valves weekly, or monthly if locked and quarterly if electrically supervised; gauges monthly; waterflow alarms inspected quarterly and tested semiannually; an annual inspection with a main drain test; and a five-year internal assessment of the piping (NFPA 25, Section 14.2) that is easy to forget because four years pass between reminders.
• Standpipes (NFPA 25) — annual inspection, plus a five-year flow test on automatic standpipes and a five-year hydrostatic test on manual and semiautomatic dry standpipes.
• Fire pump (NFPA 25) — a no-flow churn test weekly for diesel pumps and monthly for most electric pumps (NFPA on churn tests (opens in a new tab)), plus an annual full-flow test.
• Backflow preventers — annual testing by a certified tester, with results filed with the water purveyor (in Virginia, 13VAC5-63-530 (opens in a new tab)). This one has two masters: the fire code cares that the water gets to the sprinklers, and the water utility cares that nothing flows backward into the main and sets its own filing rules, covered in our backflow testing guide.
• Portable extinguishers (NFPA 10) — a monthly visual inspection (which building staff can perform and record), annual maintenance by a certified servicer, internal maintenance every six years for stored-pressure dry chemical units, and hydrostatic testing at 5 or 12 years depending on type. OSHA 29 CFR 1910.157 (opens in a new tab) sets the same monthly, annual and six-year rules for employers.
• Emergency and exit lighting (NFPA 101) — a monthly function test of at least 30 seconds and an annual full-duration test, in which battery units must carry their load for 90 minutes (NFPA Journal on emergency lighting (opens in a new tab)).
• Fire doors (NFPA 80) — annual inspection and testing of fire door assemblies, documented per opening.
• Kitchen hood suppression (NFPA 96 and 17A) — suppression system service at least every six months (IFC Section 904.13.5.2); hood and duct inspection set by cooking type, from monthly for solid-fuel cooking and quarterly for high-volume operations to annually for low-volume use, with cleaning when grease builds up (IFC Table 606.3.3.1 (opens in a new tab)).
• Emergency and standby generators (NFPA 110) — weekly inspection, a monthly exercise under load, an annual supplemental load test for diesel units whose monthly runs are too lightly loaded, and an extended run at least every 36 months for Level 1 systems (NFPA on emergency power maintenance (opens in a new tab)). Our generator testing guide has the detail.
• Elevator firefighters’ emergency operation — ASME A17.1 (Section 8.6.11.1) calls for a monthly, logged test of Phase I recall by key switch and at least a one-floor Phase II operation, 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 come with a vendor and an invoice, so they get booked; the monthly and multi-year items are the easy ones to miss. Monthly items belong to staff, not to a vendor with an invoice; multi-year items slip 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 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. Credential rules vary by system and jurisdiction. As of October 2026, Virginia’s fire code (opens in a new tab) requires a valid certificate to service extinguishers and hood suppression systems and holds fire alarm technicians to NFPA 72’s qualification rules, and Maryland requires a State Fire Marshal license (opens in a new tab) to inspect or test sprinkler systems, apart from an owner’s own full-time maintenance employee. 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 — as of October 2026 the 2017 DC Construction Codes (opens in a new tab), which incorporate the 2015 International Fire Code with District amendments — through DC Fire and EMS. Its Office of the Fire Marshal (opens in a new tab) runs routine maintenance inspections of all buildings except federal buildings and single-family homes.

Virginia operates the Statewide Fire Prevention Code, an IFC-derived code adopted at the state level (as of October 2026, the 2021 edition, in effect since January 18, 2024 (opens in a new tab)) and enforced by localities that choose to, with the State Fire Marshal enforcing elsewhere (13VAC5-52-40 (opens in a new tab)). The practical consequence is that the base code is the same from Arlington to Fairfax to Alexandria while the local layer is not: localities may adopt more restrictive fire prevention rules (Code of Virginia § 27-97 (opens in a new tab)) and set their own enforcement procedures, so inspection frequency, report submittal, and deficiency follow-up can differ.

Maryland builds on the NFPA lineage — the State Fire Prevention Code adopts NFPA 1 and NFPA 101, 2024 editions (opens in a new tab) (as of October 2026) with state amendments — enforced by the State Fire Marshal or by a designated county or municipal fire official (COMAR 29.06.01.04). The State Fire Marshal’s office (opens in a new tab) lists Montgomery and Prince George’s among the counties with their own fire marshal or inspection departments.

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 compliance programs quietly 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. That stack is a dated record that the owner knew and did not act, and NFPA 25 puts the duty to correct on the owner (NFPA on owner responsibilities (opens in a new tab)).

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, with notice to the fire department, the insurer, and the alarm company, and a fire watch or other measure if the system will be out more than 10 hours in a 24-hour period (NFPA’s impairment guidance (opens in a new tab)) — rather than as ordinary maintenance. Local rules can be tighter: the District’s fire watch bulletin (opens in a new tab) applies to alarm or suppression outages of 4 hours or longer. 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 25 defines the three terms precisely. An inspection is a visual examination to confirm a system appears to be in operating condition and free of physical damage. A test is a procedure that determines whether the system actually operates — flowing water, running the fire pump, sounding the alarm. Maintenance is the work that keeps equipment operable, including repairs. A report that only documents inspection has not established that anything works, which is why the standards assign 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, with the State Fire Marshal covering places that do not enforce locally; 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 elevator inspection 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 — generally requires credentialed technicians, such as a State Fire Marshal sprinkler license in Maryland.

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: the model International Fire Code (2021 edition) sets a floor of three years unless a code section or referenced standard says otherwise, adopted versions can differ, and insurers may ask for multi-year history during underwriting or after a loss. We suggest keeping everything indefinitely in a system that can retrieve it, because the cost of not producing a record when it is requested is far higher than the cost of keeping it.

What does a fire watch actually require?

When a required fire alarm or suppression system is out of service, the International Fire Code requires immediate notice to the fire department and the fire code official and, where the fire code official requires it, evacuation or an approved fire watch: personnel whose only duty is constant patrol, with a way to notify the fire department. NFPA 25 adds a fire watch or similar measure when a water-based system will be out more than 10 hours in a 24-hour period. Local rules can be stricter: DC’s bulletin applies to outages of 4 hours or longer and requires a written plan, dedicated personnel, hourly checks of the whole building, and a log. 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?

It can. Property insurers can 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.