Annual fire alarm inspection schedule
The annual is one date on the calendar. Monthly batteries and quarterly devices are what make logs look complete when the fire marshal asks.
Get an email before the next inspection is due. Compare a due date tracker with field service suites.
An annual fire alarm inspection is the full system test your licensed fire alarm contractor signs under NFPA 72. It sits on the same calendar as monthly battery checks, quarterly device exercises, and the weekly or monthly control-equipment walk your program may require. When every task shares one spreadsheet row labeled "alarm," the annual hides behind monthlies nobody filed. Split the control equipment, the battery task, the device tests, and the annual visit onto dates you can see. Use the NFPA 72 preset in FireCert Clock as a start, then change intervals when your adopted edition or your authority having jurisdiction differs. The product tracks due dates and stores reports. It does not replace your alarm contractor or interpret the code for you.
When you already know the last test date, calculate the next visual due and the next test due with the fire inspection due date calculator.
Buildings outside the NFPA 72 habit have their own date rules. New South Wales owners tracking an Annual Fire Safety Statement start at the NSW Annual Fire Safety Statement page. Victoria owners tracking an annual essential safety measures report start at Victorian essential safety measures. South Australia owners tracking Form 3 proof start at South Australian essential safety provisions. New Zealand owners tracking a warrant and Form 12A start at the New Zealand building warrant of fitness page. Responsible Persons in England who need a log of reviews and 2022 door checks start at the England fire safety logbook page. Singapore owners tracking a Fire Certificate start at the Singapore Fire Certificate page. Those notes do not replace this alarm schedule.
NFPA 72 2022 component test and inspection rhythm
NFPA 72, National Fire Alarm and Signaling Code, organizes recurring work by component type, not by a single "annual" checkbox. The 2022 edition is widely referenced in the US, but your city may still enforce an older edition or local amendments. The tables below list periodic visual inspections and functional tests from Chapter 14. They are not a copy of the standard and not legal advice. Confirm every row against the edition your AHJ adopted and your occupancy chapter.
The rows below follow NFPA 72 (2022) Table 14.3.1 (visual inspection) and Table 14.4.3.2 (testing). They are a readable summary for scheduling, not a substitute for the code. Typically done by is not an NFPA column. Section 14.2 makes the owner responsible for inspection, testing, and maintenance, and it allows that work under a written contract. Qualified people can be owner staff or a contractor, so every row says Owner or contractor. Source: Building Fire Alarm Association of Maryland, NFPA 72 Chapter 14 training notes, checked 30 Oct 2026, https://www.bfaam.org/_files/ugd/3c5721_0e779a2fd01b4e079d8c8b5e5f429f4d.pdf. Your authority having jurisdiction picks the adopted edition and can require shorter intervals.
Table 14.3.1: Visual inspection intervals (2022 edition)
| Component (summary) | Periodic visual inspection | Typically done by | NFPA 72 (2022) reference |
|---|---|---|---|
| All equipment (building changes, damage, obstructions) | Annual | Owner or contractor | Table 14.3.1 item 1 |
| Control unit, monitored for alarm, supervisory, and trouble (fuses, interfaced equipment, lamps/LEDs, primary power) | Annual | Owner or contractor | Table 14.3.1 item 2(1)(a) to (d) |
| Control unit, monitored trouble signals | Semiannual | Owner or contractor | Table 14.3.1 item 2(1)(e) |
| Control unit, unmonitored for alarm, supervisory, and trouble (same subcomponents) | Weekly | Owner or contractor | Table 14.3.1 item 2(2)(a) to (e) |
| Supervising-station transmitters on premises (DACT, DART, radio, other) | Annual | Owner or contractor | Table 14.3.1 item 4 |
| In-building fire emergency voice/alarm communications equipment | Semiannual | Owner or contractor | Table 14.3.1 item 5 |
| VRLA batteries, marking and physical condition | Semiannual | Owner or contractor | Table 14.3.1 item 9(1)(a) to (b) |
| Primary (dry-cell) batteries (non-wireless) | Semiannual | Owner or contractor | Table 14.3.1 item 9(2) |
| Remote annunciators | Semiannual | Owner or contractor | Table 14.3.1 item 11 |
| Notification appliance circuit power extenders | Annual | Owner or contractor | Table 14.3.1 item 12 |
| Remote power supplies | Annual | Owner or contractor | Table 14.3.1 item 13 |
| Surge protective devices | Semiannual | Owner or contractor | Table 14.3.1 item 14 |
| Initiating devices, location and condition (manual boxes, smoke, heat, duct, beam, CO, and related types) | Semiannual (quarterly for some radiant/video and duct sampling tubes per table notes) | Owner or contractor | Table 14.3.1 item 17 |
| Supervisory signal devices (valve tamper switches) | Semiannual | Owner or contractor | Table 14.3.1 item 18(1) |
| Waterflow devices | Semiannual | Owner or contractor | Table 14.3.1 item 18(2) |
| Notification appliances (horns, speakers, strobes) | Semiannual | Owner or contractor | Table 14.3.1 item 22(1) to (3)(a) |
Table 14.4.3.2: Functional test intervals (2022 edition)
| Component (summary) | Functional test interval | Typically done by | NFPA 72 (2022) reference |
|---|---|---|---|
| Control unit, functions, fuses, interfaced equipment, lamps/LEDs, primary power at maximum load with battery disconnected | Annual | Owner or contractor | Table 14.4.3.2 item 2(1)(a) to (d) |
| Control unit, trouble signals, disconnect switches, ground-fault monitoring, off-premises trouble transmission | Annual | Owner or contractor | Table 14.4.3.2 item 2(1)(e) and related |
| Supervising-station transmission equipment on premises | Annual | Owner or contractor | Table 14.4.3.2 item 4 |
| VRLA batteries, temperature, charger, cell voltage, ohmic values | Semiannual | Owner or contractor | Table 14.4.3.2 item 9(1) |
| Secondary (standby) power, loss of AC, capacity for standby and alarm load (5 minutes general alarm; 15 minutes voice) | Annual | Owner or contractor | Table 14.4.3.2 item 9(2) |
| VRLA batteries, load test or replacement at end of service life | Every 3 years (or per manufacturer) | Owner or contractor | Table 14.4.3.2 item 9(3) |
| Engine-driven generator dedicated to the fire alarm system | Monthly | Owner or contractor | Table 14.4.3.2 item 9(4) |
| Manual fire alarm boxes (pull stations) | Annual | Owner or contractor | Table 14.4.3.2 item 17(1) |
| Smoke detectors, functional test with smoke entry | Annual | Owner or contractor | Table 14.4.3.2 item 17(2) |
| Smoke detectors, sensitivity (within listed range) | Within 1 year of install, then every other year; up to 5 years between tests when within marked range after second test | Owner or contractor | Table 14.4.3.2 item 17(3) |
| Restorable spot heat detectors | At least 2 on each initiating circuit each year, rotating until every detector tested within 5 years | Owner or contractor | Table 14.4.3.2 item 17(4) |
| Non-restorable fixed-temperature spot heat detectors | Replace after 15 years or test sample per table | Owner or contractor | Table 14.4.3.2 item 17(5) |
| Duct smoke detectors (including airflow through sampling tubes) | Annual | Owner or contractor | Table 14.4.3.2 item 17(6) to (7) |
| Projected-beam smoke detectors | Annual | Owner or contractor | Table 14.4.3.2 item 17(8) |
| Valve tamper switches | Semiannual | Owner or contractor | Table 14.4.3.2 item 18(1) |
| Waterflow devices (inspector's test connection flow) | Semiannual | Owner or contractor | Table 14.4.3.2 item 18(2) |
| Other supervisory switches (air pressure, temperature, water level, and similar) | Semiannual | Owner or contractor | Table 14.4.3.2 item 18(3) |
| Audible notification appliances, operation | Annual | Owner or contractor | Table 14.4.3.2 item 22(1) |
| Loudspeakers and audible textual appliances | Annual | Owner or contractor | Table 14.4.3.2 item 22(2) |
| Visual notification appliances, each appliance flashes | Annual | Owner or contractor | Table 14.4.3.2 item 22(3) |
| Emergency control functions (elevator recall, fan shutdown, door release, and similar) | Annual | Owner or contractor | Table 14.4.3.2 item 23 |
High-rise residential, detention, and industrial occupancies can add rows your contractor already knows from the project submittal. Voice evacuation and mass notification may use different cycles than the main panel. Split assets when two tasks on one system use different intervals.
Authority having jurisdiction (AHJ)
Your AHJ is usually the local fire department or building official who names which NFPA 72 edition applies and whether they accept electronic records. Some jurisdictions require a paper log in the panel room even when you store PDFs elsewhere. Others want the licensed contractor's form, not a generic template. When the fire marshal's letter disagrees with a blog table, the AHJ wins. FireCert Clock is not an AHJ. It stores the dates and files you confirm after each visit.
Before you load presets, ask your alarm vendor which edition they test to on your contract. Match that edition on each asset. If enforcement changes mid-year, add a new asset with the new interval rather than silently editing history.
Who owns which date
Building staff often own a weekly or monthly visual of the panel, trouble signals, and basic function checks your program requires between vendor visits.
The licensed fire alarm contractor owns the annual inspection, sensitivity work where applicable, and many device-level tests spelled out in NFPA 72 for your occupancy.
Two assets mean two sets of reminders and one site PDF when someone asks for the year. One asset is fine if one person owns every task and you accept a single next due date.
Technicians can subscribe to iCal feeds for assigned alarm assets so field staff see upcoming panel work without opening the full site list.
Document the annual with a fire alarm report form
After the annual, you need a defensible file: site identity, devices exercised, deficiencies, signer, and next due dates. Use the fire alarm inspection report page for downloads at the top, or the fire inspection report template page for the full multi-system pack:
Upload the finished PDF to the asset in FireCert Clock. On Starter and above, confirm the service date and next due date the product reads from the file. Notices email you at 30 days, 14 days, 7 days, 3 days, and the last day before each due date. Add the building contact as a client contact on Starter if they need the same warning without you forwarding mail.
Log a visit only when the work passes, since logging moves the next due date.
Monthly and quarterly work between annuals
The annual does not replace monthly battery visuals or quarterly waterflow exercises where your table requires them. Treat each recurring task as its own asset when you want separate reminders.
Batteries. A green power light does not prove the last discharge test happened. Track the battery task on its own interval.
Initiating devices. Sample testing and full counts depend on edition and system size. Your contractor's proposal should list how many devices they touch each year.
Notification appliances. Annual functional tests are common; strobe coverage changes after remodels need a new walk, not an assumption.
Interfaces. Elevator recall and fan shutdown tests are easy to defer because they need coordination. Give them a visible due date before the owner schedules the annual walk with the AHJ.
Cross-check intervals with the NFPA inspection frequency lookup and the walk list on the NFPA 72 inspection checklist. The annual fire inspection checklist helps when the marshal asks about extinguishers and sprinklers on the same visit.
After a test or inspection
Upload the report PDF or photo of the service tag. Confirm dates on Starter so mail matches the ticket, not an old guess. Keep whatever log your AHJ wants on site. The product is the schedule and the file store, not a panel monitor over the network.
When the central station also sends reports, store the vendor PDF on the asset. The reminder still fires from the next due date you confirmed.
Plans and proof
Free is $0 a month for 1 site and 25 assets with email reminders. Starter is $39 a month for 10 sites, 500 assets, client reminder emails and AI date reading from reports. Pro is $79 a month for 50 sites with no asset cap, five users and branded client PDFs. Business adds unlimited sites, 15 users, API access and CSV export. Yearly billing on paid tiers is two months free. See pricing.
The site export lists every asset, last service, next due and status. Contractors hand the same PDF to the property manager. In-house teams use it for Monday standups before the fire marshal arrives.
CSV import with site, asset type, location and last service date fills next due from the preset when you already have a device list from the last vendor.
UK alarm servicing stored as 182 days, kept off this NFPA 72 schedule, is BS 5839-1 fire alarm servicing.
FAQ
Can technicians subscribe only to alarm assets?
Assign those assets to that technician. Their iCal feed follows the assignment.
Does this replace the alarm log in the panel room?
Keep whatever log your AHJ wants on site. The product is the schedule and the file store.
Can I track multiple panels in one building?
Yes. Add an asset per panel or per floor, whichever matches how you walk the site.
Does FireCert Clock monitor the panel over the network?
No. It tracks dates and paperwork you upload after visits.
What if our central station also sends reports?
Store the vendor PDF on the asset. The reminder still fires from the next due date you confirmed.
Can I import a device list?
Yes. CSV with site, type, location and last service. Pick the NFPA 72 preset when you add each asset.
Is the table above the official NFPA 72 text?
No. It is a plain-language summary for scheduling. Your contractor and AHJ define enforceable intervals.
What if we are still on the 2019 or 2016 edition?
Set the interval when you add each asset to match your contract. Presets are a shortcut, not a legal opinion.
Voice evacuation and mass notification
Some campuses add mass notification appliances on a different service cycle than the main panel. Split assets so a quarterly voice test does not hide an annual panel inspection.
Battery replacement years
When a tech replaces batteries early, confirm the new next due on Starter so mail matches the ticket, not the old interval guess.
Tenant improvement seasons
Construction often disables devices temporarily. Log the outage visit and the return visit as separate entries so the history shows when the system was fully restored.
Mixed-use and campus buildings
Retail wings and residential towers in one address often carry different device counts and test samples. Separate assets per wing when intervals differ so one overdue row does not mask another.
Insurance and property manager packets
Risk engineers ask for alarm evidence separate from extinguisher tags. Export one site PDF with attachments before renewal instead of searching email for last year's annual.
Rehearsals with the fire department
Some AHJs witness a test during a scheduled drill. Note that visit on the asset with the report or letter they sign so the next due date reflects the witnessed test, not an informal walk-through.
Build a route calendar from the two interval columns
Dispatchers should treat the visual column and the functional column as two calendars that sometimes share a truck and sometimes do not. A weekly look at an unmonitored panel can be a building engineer on Monday morning. A semiannual waterflow exercise needs the monitoring company on the phone and a tech who can open the inspector's test valve. Putting both on one work order without two lines makes the office mark the weekly row done when only the valve was flowed.
Cluster sites by travel, not by anniversary month alone. If three downtown panels all need semiannual battery marking in the same fortnight, book them on one loop and leave the annual smoke entry tests on a later loop when the lift and the after hours access are already promised. Do not slide a weekly unmonitored control unit visual onto that loop just because the van is nearby. Weekly means weekly. The route software should show a separate chip for that row so a holiday Monday does not silently become a fourteen day gap.
Holiday and shutdown weeks need a named backup person before the week starts. If the only qualified person is on leave, move the visit earlier and write the reason on the asset, or bring in the contracted company under the written agreement you already have. Skipping and hoping the next annual covers it leaves a hole an auditor can see.
When a frequency in the table is conditional, the route note should repeat the condition in plain words. Sensitivity work that starts within a year of install and then stretches only while results stay in range is not "annual forever." Heat detector sampling that rotates until every head has been tested inside five years needs a tally, not a single checkbox. The schedule page is where that tally lives. The person who builds the year should copy the condition into the asset nickname so the tech sees it on the phone without opening the code book.
Campus jobs with several wings should not share one next due date. A retail wing with a different device mix can be due for notification appliance visuals while the tower is only due for a generator run. Two assets, two dates, one site export. Property managers then see which wing slipped.
After you publish the year, spot check five assets against the table reference in the last column. If the asset says annual and the reference says semiannual, fix the asset before the first reminder goes out. Reminders at 30, 14, 7, 3, and 1 day only help when the date itself is the one your contract and the adopted edition actually require.
Friday desk review for the dispatcher
Once a week, sort the board by the next fourteen days and read it out loud with the service manager. Call out any row whose interval chip does not match the reference printed in the shared table. A generator run that shows up once a quarter on the board is wrong even if the customer has been quiet. Move it back to monthly and tell the customer why the cadence changed, in writing, before the next invoice.
Watch travel density. If Thursday has four annuals in four cities, pull one forward to Wednesday only when access and the monitoring window still work. Do not pull a weekly unmonitored panel visual forward by six days and call the gap closed. The gap is still there. Offer the contracted company a paid extra stop or assign the building engineer who was trained for that look.
Keep a short exception log for weather, failed access, and parts on order. Each line needs the asset, the date you intended, the date you will actually go, and who agreed. Exception logs that live in chat scroll away. The asset note is the log. When the marshal asks why March was empty, you open the asset and read the sentence.
New sales should not inherit a blank year. The estimator copies interval rows from the table into the proposal as line items with the reference number, then operations turns those lines into assets on day one. A proposal that says "annual inspection" and nothing else will be fought in month six when semiannual battery marking was never priced. Price the rows you intend to perform. Leave the others off the proposal and off the reminder list.
Color the board by cadence, not by customer logo. Weekly chips in one hue, monthly generator runs in another, semiannual battery and waterflow rows in a third, annual smoke entry and notification tests in a fourth. A dispatcher who sorts by color catches a missing hue faster than one who reads every nickname. When a hue disappears for a zip code, that is a staffing problem, not a software glitch. Fill it before reminders start apologizing for you.
Print a one page route strip for each van on Sunday night. The strip lists stops in drive order, the cadence hue, the gate code, and the monitoring phone. Techs should not hunt the full table from a rooftop. If a stop drops off the strip because access was refused, the dispatcher puts it back on Tuesday's strip the same evening, with a new gate contact. Strips that die in the glove box are why a monthly generator run becomes a rumor.
Name assets the way the route strip reads them. Start with the street number, then the wing, then the cadence word, then the table item number. "410 Elm B weekly 2(2)" beats "Panel 2." When a tech radios dispatch, both people can find the row without a meeting. Rename old nicknames during the Friday review instead of living with codes only the founder remembers. A clean name also makes the site export readable for a property manager who has never seen your internal shorthand.
Support and Terms. Calculator.