Skip to content

Insights

Commercial Building Compliance Calendar (What's Due When)

Levaru Operations TeamUpdated October 5, 202612 min read

On this page · 5 sections

A building compliance calendar is the single document that keeps a commercial property out of violation-by-forgetting territory. Almost no owner fails a fire alarm test on purpose. What usually happens is quieter: the sprinkler contractor changed, the five-year internal pipe inspection fell off nobody’s list, the backflow test certificate expired in a drawer, and the first anyone hears about it is a notice from the water authority or a red flag during a sale’s due diligence. Many compliance failures in commercial buildings are calendar failures.

This article lays out the recurring obligations that apply to most commercial buildings in DC, Northern Virginia, and Maryland — fire protection, elevators, backflow prevention, emergency generators, boilers, cooling towers, and energy benchmarking — organized two ways: by frequency (what repeats weekly, monthly, quarterly, annually, and on multi-year cycles) and as a month-by-month planning grid you can adapt to your own buildings.

Two caveats. First, the frequencies below reflect the national standards (NFPA 10, 25, 72, 80, 101 and 110, ASME A17.1) and federal and state rules as of October 2026; your jurisdiction may amend them, and anniversary-based items land on your building’s dates, not calendar months. Second, this list covers the recurring systems obligations common to office, retail, and industrial buildings — specialized occupancies (healthcare, assembly, high-rise) carry more.

What inspections and tests are due at each frequency?

The fastest way to build the calendar is to group obligations by how often they repeat, then assign each to a month. Here is the core recurring set for a typical DMV commercial building.

Weekly / monthly (mostly in-house staff tasks):

Quarterly:

  • Sprinkler system: quarterly inspection items per NFPA 25 (waterflow alarm devices, valve supervisory devices, alarm valve exterior), plus semiannual tests of waterflow alarms and valve supervisory devices
  • Fire department connections: quarterly visual inspection
  • Kitchen hood suppression systems (if any food service): maintenance at least every 6 months under NFPA 96, according to NFPA’s restaurant fire protection overview (opens in a new tab); schedule the two visits six months apart (February and August in the grid below)

Annual (the heavy layer):

Multi-year cycles (the ones that get forgotten):

  • Sprinkler: 5-year internal assessment of the piping (NFPA 25, Chapter 14, as the National Fire Sprinkler Association’s summary (opens in a new tab) explains); gauges replaced or tested every 5 years; alarm and check valve internals every 5 years; standpipe flow and hydrostatic tests on the cycles NFPA 25 sets
  • Elevator: Category 5 full-load safety test every 5 years. DC requires a Category 5 inspection every 60 months, and Maryland’s comprehensive 5-year inspection adds a full-load test for rope-suspended (traction) units
  • Fire alarm: smoke detector sensitivity testing and battery replacement on the schedules NFPA 72 and the manufacturer set
  • Extinguishers: 6-year internal maintenance and 12-year hydrostatic test for stored-pressure dry-chemical units; 5-year hydrostatic test for water and carbon dioxide units (OSHA 29 CFR 1910.157, Table L-1)
  • Fire and smoke dampers: test 1 year after installation, then every 4 years (every 6 years in hospitals), per NFPA 80 and NFPA 105 as NFPA’s damper maintenance guidance (opens in a new tab) explains
  • Sprinkler dry systems: full-flow trip test every 3 years

From 2017 to 2021, sprinklers operated in 92 percent of U.S. structure fires large enough to activate them, and were effective at controlling the fire in 97 percent of the fires in which they operated. — NFPA, “U.S. Experience with Sprinklers” (April 2024) (opens in a new tab)

Those numbers are the argument for the whole calendar: the systems work almost every time when maintained. The same NFPA report found that the most common reason sprinklers failed to operate was that the system had been shut off before the fire, and it lists lack of maintenance among the other causes: calendar failures, again.

What does a month-by-month compliance calendar look like?

Anniversary items float, but a well-run building pins them to deliberate months so the workload spreads and seasonal work lands in season. Here is a planning grid we consider sensible for a DMV commercial building — shift items to your own anniversaries, but keep the seasonal logic:

Month Compliance focus
January Annual fire alarm test (NFPA 72); review last year’s open deficiencies; confirm all certificates posted and current
February Fire extinguisher annual maintenance; emergency lighting 90-minute test; kitchen hood suppression semiannual service; verify benchmarking data access (utility accounts, ENERGY STAR Portfolio Manager)
March Backflow preventer annual tests and reports (in Fairfax County, use the test month the county assigns); start assembling the prior year’s energy benchmarking data
April Finish and check benchmarking submissions in Portfolio Manager; cooling tower startup cleaning and disinfection, and water management program review; spring roof inspection
May DC benchmarking due May 1; elevator inspection or Category 1 test (first half of year keeps summer free; where the two alternate, as in DC, the other lands in November); fire pump annual flow test
June Maryland and Montgomery County benchmarking due June 1; sprinkler annual inspection and main drain test; verify any 5-year items due this year (piping internal assessment, standpipe, Cat 5) are scheduled
July Generator annual service and fuel quality test; review load bank need
August Kitchen hood suppression semiannual service; fire/smoke damper testing if due this cycle
September Boiler certificate inspection if due this year (yearly or every two years, by jurisdiction and boiler type); combustion service before heating season
October Fall roof inspection; cooling tower shutdown/winterization with documented cleaning and disinfection; freeze-protection checks
November Fire alarm deficiency corrections closed out before year end; second elevator inspection where your jurisdiction alternates them; verify snow/ice vendor insurance certificates current
December Annual calendar review: next year’s multi-year items (Cat 5, 5-year sprinkler internals, 6/12-year extinguisher work), certificate expiration audit, contractor PO renewals

The quarterly sprinkler items, monthly generator runs, and weekly checks run continuously underneath this grid — the grid is for the contractor-scheduled, certificate-producing events.

What are the BEPS and benchmarking deadlines in DC and Maryland?

Energy compliance is the newest layer on the calendar, and in this region it has real teeth. Washington, DC requires annual energy and water benchmarking, due May 1 for private buildings over 10,000 square feet, according to DOEE’s energy benchmarking page (opens in a new tab) (as of October 2026). Its Building Energy Performance Standards (BEPS) program sets performance targets on multi-year compliance cycles, with financial penalties for buildings that neither meet the standard nor complete a compliance pathway; DOEE’s BEPS helpdesk (opens in a new tab) has the program rules. Maryland’s statewide BEPS program requires covered buildings of 35,000 square feet and up to benchmark by June 1 each year, with performance targets starting in 2030, according to MDE’s BEPS program overview (opens in a new tab). Montgomery County runs its own, earlier program (benchmarking also due June 1, per Montgomery County’s covered-buildings page (opens in a new tab)), and since October 1, 2025 buildings in the county follow the county program instead of the state’s. Our DC and Maryland energy benchmarking guide has the full comparison.

Thresholds, cycle dates, and rules have been actively evolving in both jurisdictions, so treat BEPS as a named line on the compliance calendar with an owner assigned — not a task your engineer discovers in March. We maintain a separate breakdown of covered buildings, dates, and penalty mechanics in our guide to BEPS deadlines in DC and Maryland. As of October 2026, Virginia has no statewide BEPS or benchmarking mandate for private buildings, but DMV portfolios that cross the river need the DC and Maryland dates on the master calendar regardless of where the headquarters sits.

Who should own the compliance calendar?

One named person — with the calendar in a system, not a spreadsheet on someone’s desktop. In practice the failure mode is diffusion: the fire vendor “handles” fire dates, the elevator company “handles” elevator dates, and no one reconciles what actually got done against what was due. Vendors schedule work; they do not carry your legal obligations, and a building can drop off a vendor’s scheduling system without anyone noticing.

The workable model assigns every obligation four fields: the requirement and its source (NFPA 25 annual, AHJ certificate, warranty condition), the frequency, the responsible vendor or staff member, and the proof — the certificate, report, or filed test record. Then every completed item closes with its document attached, and every upcoming item generates lead-time alerts at 90 and 30 days. This is exactly the kind of recurring, documentation-heavy scheduling a structured preventive maintenance program exists to run: statutory dates tracked as recurring work orders, proof attached at closeout, and one dashboard that answers “are we current, and what’s due in the next 90 days?” for every building in the portfolio.

Two final habits that separate clean portfolios from lucky ones. First, audit certificates twice a year — physically confirm the elevator certificate, boiler certificate, and backflow filings are current, because “the vendor was here” and “the certificate issued” are different facts. Second, when a building changes hands or a vendor changes, treat the compliance record as a deliverable: the incoming team should receive the full test history, not start guessing at anniversaries.

Frequently asked questions

What happens if we miss a required inspection?

Consequences scale from correction orders and fines to systems red-tagged out of service, and the exposure compounds: an incident involving an untested system is a serious liability fact, and insurers can ask for inspection records at renewal and after claims. Lapses also surface during sale due diligence, where a thin compliance file translates directly into price negotiation.

Do these requirements apply to small commercial buildings?

Mostly yes. Fire alarm and sprinkler systems (where installed), extinguishers, backflow assemblies, and elevators (where present) carry their obligations regardless of building size; what changes with size is the count of systems and whether energy benchmarking thresholds are triggered. A 20,000-square-foot building has a shorter calendar than a 200,000-square-foot one — but not an empty one.

Can our maintenance vendors just manage their own schedules?

They can schedule their own work, but the owner must own the reconciliation. Vendors change staff, drop buildings from route schedules, and go out of business, and none of that transfers the compliance obligation. Keep the master calendar in-house (or with your facility management provider) and verify each item against the resulting certificate or report.

How do I build a compliance calendar for a building we just acquired?

Start with the paper: collect every current certificate (elevator, boiler, backflow filings), the last fire alarm and sprinkler reports, generator logs, and the roof warranty, and extract the dates and deficiencies. Then walk the building against the list in this article to find systems with no records at all — those go to the front of the schedule, because without a record you cannot show the test was done.

Are fire inspection frequencies the same in DC, Virginia, and Maryland?

The underlying standards (NFPA 25 and 72) are broadly consistent across the region, but each jurisdiction adopts its own fire code edition with local amendments, and inspection filing procedures vary by fire marshal. Maryland’s State Fire Prevention Code, for example, incorporates the 2024 editions of NFPA 1 and NFPA 101 (COMAR 29.06.01, as of October 2026). The frequencies in this article are planning defaults; confirm specifics with the fire code official for each building’s jurisdiction.

General information, not legal or engineering advice. Rules change; check the official source before you act. How we source, date and correct our guides: editorial standards.

Keep reading

More guides on this topic

Next step

Rather have answers about your specific building?

Curious how it works? See how our 360° walkthroughs work →