What are the different fire-inspection service intervals?

Owner-level monthly visual checks on each extinguisher (the customer’s job), semi-annual service on kitchen hood suppression under NFPA 96 and UL-300, annual external maintenance on portable extinguishers under NFPA 10 and a full-duration annual test on exit and emergency lighting under NFPA 101, plus multi-year internal exams and hydrostatic shell tests. Requirements vary by jurisdiction, so verify the intervals with your AHJ.

How do these clocks add up to recurring work?

Each asset comes due again on its own clock whether you return or not, so a book of accounts anchored to the months you first serviced them produces due dates in every month of the year. A single restaurant can be three or four scheduled touches a year once its hood, extinguishers, and lighting are counted. Renewals are last year’s customers coming due, not new sales.

How do I smooth out a route that bunches up?

Because every asset is anchored to its own due date, you can steer new accounts toward slower months, book semi-annual hood visits opposite the annual rush, and schedule multi-year internal and hydrostatic work into the gaps. You cannot erase seasonality, but anchoring each asset to its own clock lets you level the load instead of riding a spike.

Why anchor each asset to its own due date instead of the building?

A building has no single due date; its extinguishers, hood system, and lights each run on different intervals keyed to their own agent, type, and manufacture date. Anchoring each asset individually and re-anchoring it at every service is what lets the calendar assemble itself and keeps your own recorded date authoritative.

Can tracking the schedule make a site compliant?

No. Records and software track the clocks, send the reminders, and hold the dated proof, but they do not determine a site’s status or certify the work. That rests with you, the licensed operator, and the AHJ. The honest framing is that you record and remind, then you and the authority certify.

Monthly, semi-annual, and annual: shaping the work of the year

A fire-equipment route is not one job repeated. It is a stack of clocks running at once: quick owner checks every month, hood systems every six months, extinguisher tags and lighting every year, internals and shell tests every several years. Each one comes due on its own schedule, for its own asset, on its own day.

Managed well, that stack is the best thing about the business, because it turns into a calendar that fills itself. Managed on memory, it is how you miss a due date and hand a competitor an opening. This chapter is about shaping those clocks into a workable year. The mechanics of each interval live in the cadence guides; here we look at how they add up to scheduled, recurring route work.

The clocks that make the year

Line the intervals up and the shape of the year appears. The owner monthly visual check on each extinguisher is the fastest and most frequent, but it is the customer’s job, not a route stop. You coach it and leave a log; you do not drive it.

The semi-annual clock is the kitchen hood suppression system, serviced every six months under NFPA 96 and UL-300. Any restaurant, cafeteria, or commercial kitchen on your book is two scheduled visits a year on that asset alone.

The annual clock carries the most volume: the external maintenance and fresh tag on every portable extinguisher under NFPA 10, and the full-duration test on emergency and exit lighting under NFPA 101. These are the visits that touch nearly every account once a year.

The multi-year clocks run underneath: the 6-year internal examination on most dry-chemical units, and the hydrostatic shell test at 5 or 12 years depending on the agent. These do not come due often on any one unit, but across a full book a steady fraction land every year.

Five clocks, one route. The owner-monthly one you hand to the customer; the other four are your scheduled work.

How the clocks stack into scheduled work

Follow one restaurant through a year and the stacking is obvious. Its hood system is due twice. Its portable extinguishers are due once for annual maintenance, with a Class K unit over the fryer also on a 5-year shell-test clock. Its exit and emergency lights are due once for the full-duration test. That single account can be three or four scheduled touches across the year, not one.

Now multiply by a book of accounts, each anchored to the month you first serviced it. A site you tagged in March is due next March; a hood you serviced in September returns in March and September. Spread across enough accounts, the due dates land in every month, and the year stops being a scramble for new work and becomes a calendar of returns you already own.

Renewals are not new sales. They are last year’s customers coming due on a clock that runs whether you show up or not. The operational job is simply to see each due date coming and get back to it before it lapses.

The multi-year clocks add a forecastable baseline on top of that. Across a mature book, a roughly steady fraction of dry-chemical units reach their 6-year internal each year, and a roughly steady fraction of shells reach a 5- or 12-year hydrostatic test. You cannot predict which unit fails a check, but you can predict, months ahead, about how many internals and shell tests the year will hold, and staff and stock to it. That turns the higher-ticket work from a surprise into a planned share of the calendar.

Smoothing the seasonality

Left alone, a route bunches. If you land a run of accounts in one busy stretch, they all come due together a year later, and you get a wall of work in one month and quiet in others. That is hard on a small crew and hard on cash flow.

The clocks give you tools to smooth it. Because each asset is anchored to its own due date, you can steer new accounts toward slower months as you sell them, book the semi-annual hood visits to fall opposite the annual rush, and schedule the multi-year internal and hydrostatic work into the gaps rather than piling it onto a peak. The goal is a level line of work across the year instead of a spike and a drought.

The owner monthly check is a quieter lever in the same direction. It is not your visit, but coaching the customer to run it and log it keeps small problems from piling into surprises you have to fix all at once on the annual. A unit found low in month three is a scheduled recharge, not a scramble on inspection day.

Seasonality never disappears entirely; some trades cluster and some months are always busier. But anchoring every asset to its own clock is what lets you shape the load instead of riding it.

Anchor each asset to its own due date

All of this depends on one discipline: every asset carries its own next-due date, keyed to its own interval, agent, and manufacture date. A building does not have a due date; its individual extinguishers, its hood system, and its lights each do, and they rarely align.

When each asset is anchored that way, the calendar assembles itself. You can look weeks ahead and see exactly what is due, at which site, on which clock, and plan a route day that hits several due assets in one neighborhood. A per-serial record that generates the next date for each asset is what turns five overlapping clocks into a single readable schedule.

Anchor it to the unit and re-anchor it each time you record a service, so your own date always wins. A missed due date is a lost renewal; a live, anchored record is what keeps the recurring route actually recurring.

What you record, and what you certify

Be honest about the line between the schedule and the authority. Software and records track the clocks, generate the reminders, and hold the dated proof of what was done. They do not determine whether a site is in good standing and they do not certify the work.

That determination rests with you, the licensed operator, and with the AHJ (authority having jurisdiction). Requirements vary by jurisdiction, and the adopted edition of each standard is the authority’s to set, not the record’s. The right way to say it: you record and you remind, and then you and the authority certify. Keeping that line clear is what keeps a register honest, so it never claims more than was actually done.

Fill the calendar neighborhood by neighborhood

A full calendar is worth more when the stops sit close together. Drive time between accounts is dead time, so ten due assets in one zip code are worth more per route day than ten scattered across a county. As you build the book, build it in clusters, so each month’s due dates fall in reachable groups.

Do that and the two forces compound: the clocks keep the calendar full, and density keeps each day short. The recurring schedule stops being a burden to manage and becomes the quiet engine of the business, one due date rolling into the next.

Go deeper

Frequently Asked Questions

What are the different fire-inspection service intervals?: Owner-level monthly visual checks on each extinguisher (the customer’s job), semi-annual service on kitchen hood suppression under NFPA 96 and UL-300, annual external maintenance on portable extinguishers under NFPA 10 and a full-duration annual test on exit and emergency lighting under NFPA 101, plus multi-year internal exams and hydrostatic shell tests. Requirements vary by jurisdiction, so verify the intervals with your AHJ.
How do these clocks add up to recurring work?: Each asset comes due again on its own clock whether you return or not, so a book of accounts anchored to the months you first serviced them produces due dates in every month of the year. A single restaurant can be three or four scheduled touches a year once its hood, extinguishers, and lighting are counted. Renewals are last year’s customers coming due, not new sales.
How do I smooth out a route that bunches up?: Because every asset is anchored to its own due date, you can steer new accounts toward slower months, book semi-annual hood visits opposite the annual rush, and schedule multi-year internal and hydrostatic work into the gaps. You cannot erase seasonality, but anchoring each asset to its own clock lets you level the load instead of riding a spike.
Why anchor each asset to its own due date instead of the building?: A building has no single due date; its extinguishers, hood system, and lights each run on different intervals keyed to their own agent, type, and manufacture date. Anchoring each asset individually and re-anchoring it at every service is what lets the calendar assemble itself and keeps your own recorded date authoritative.
Can tracking the schedule make a site compliant?: No. Records and software track the clocks, send the reminders, and hold the dated proof, but they do not determine a site’s status or certify the work. That rests with you, the licensed operator, and the AHJ. The honest framing is that you record and remind, then you and the authority certify.

Run the whole route in one place

GaugeRoute keeps every asset on its NFPA-keyed schedule, the inspection on the record, and the billing on your own rails — with unlimited technician seats. Free to start.

Start free