How owners read the twelve months of visits they have already promised their customers, and level the year for the technicians who carry it, whether they ever sell or not.
Fire Prevention Week, held October 4 through 10, 2026, falls just as the weeks left in the year start to run short.
NFPA sponsors the week, and its 2026 theme speaks to the public: charging lithium-ion batteries safely at home. We are borrowing the date for a subject closer to the shop.
Once this week passes on the 2026 calendar, fewer than twelve weeks remain in the year, and the 2027 calendar is being built at the same time. This piece is about that calendar: twelve months of visits your company has already promised its customers, and two ways to read it.
An inspection has a month. Put every one of those months in one table and you are looking at the part of the recurring business where the work comes with a date attached. Reading it pays off whether you ever sell the company or not.
The year has a shape
The calendar is a table for the whole company: twelve columns, one for each month. Behind each column is the list of visits due that month, the fire alarm inspections and tests under contract, and the preventive maintenance visits your service agreements schedule on intrusion, access control, and video systems. On the face of the table go two totals for each month: the number of visits, and the hours planned for them.
In most companies we know, the visits already sit in the scheduling software or in the agreements themselves, and a service manager can lay out a first version from those two places.
In our experience the twelve totals are seldom level. A fire alarm system usually takes its inspection month from the month it was first tested and accepted, and the visit has returned to that month every year since. A strong spring of construction ten years ago can still be a heavy May.
Each date made sense for its own building on the day it was set. The shape is what those dates add up to. It now sets the team’s year: fuller weeks in the months where the work stacks and lighter ones in between, worked by the same technicians.
What a level year gives back
A level year is the same work and the same hours across the year for the same team, in steadier weeks. Steadier weeks leave more time to train, and time to train is how a company brings on its next technician.
In many of the companies we know, a new technician’s first months are spent on the inspection route: a planned day beside the senior technician who is qualified to do the work and signs the report, in a different building every morning. Inspection is a career in its own right, and the person who has made it one is the company’s teacher. A stacked month leaves little time for teaching. A level year leaves time to bring a second person along on a planned visit, which is how the depth chart gets filled in, and it leaves vacations that hold.
Two records from earlier pieces, the site record and the key ring, both get written mostly on visits already scheduled. The visits on this calendar are those visits, and a level calendar is what leaves time for both records.
Once a year, with room to plan
Leveling a year means giving some visits a different month. For fire alarm visits, the code is the place to start.
The 2025 edition of NFPA 72 defines an annual frequency as once per year, with a minimum of nine months and a maximum of 15 between events. Semiannual is twice per year, with a minimum of four months and a maximum of eight. The 2019 and 2013 editions carry the same wording.
That definition leaves room to give a system a better month, in one direction. A visit that sits in a stacked month can move a few weeks earlier, into a lighter one, and return to its new month every year after. Twelve months stays the rhythm. The move happens once, in writing, with the customer’s agreement, and then the calendar holds.
Four things get checked before any visit moves. The edition in force for a building is the one its jurisdiction adopted, and NFPA itself notes that jurisdictions adopt different editions and that many amend them. The 2019 edition lets the local fire authority require visits more often than its own schedules do. The customer may have requirements of their own. The service agreement may name the month. The tightest of the four governs.
Whose calendar it is
The dates sit in your software, and the responsibility they come from starts with your customer. In the 2019 edition of NFPA 72, the property, building, or system owner, or the owner’s designated representative, is responsible for inspection, testing, and maintenance, and the work may be done by another organization under a written contract.
Under that contract, your company is the organization they chose. Every fire alarm visit on the calendar is a responsibility a customer trusted you to carry with them.
We wrote in the key ring that a customer hands over each key for one reason: they trust the company to hold it. A date works the same way. The customer has trusted you to arrive in the month you promised and tell them what you found. That is why a visit moves only with their agreement, and why the calendar deserves as close a reading as anything else you hold for them.
Read it two ways
How level the year sits
Set each month’s hours beside the hours your inspection team has that month. The months where the first number is larger are the stacked ones, and the gap is how many hours need a new home. A level year still has heavier and lighter months, because some customers have good reasons for a season.
Then list the systems in each stacked month whose customers would welcome you a few weeks sooner. Those are the candidates for a new month.
What each visit puts in writing
An inspection ends with a report. In some cities the report has a clock of its own. As of October 2026, Seattle’s fire department requires test reports for many systems within seven calendar days of the work, and San José and Colorado Springs each allow no more than 30 days. Seattle and Colorado Springs also require an impaired system to be reported immediately. The deadline is the jurisdiction’s, and it belongs on the calendar beside the visit.
The customer hears sooner. In the 2019 edition of NFPA 72, when anything the code counts as a deficiency is still uncorrected at the end of a visit, the system owner or the owner’s representative, in most cases your customer, is told in writing within 24 hours.
Your reading starts there. Every item found on a visit should end the year with its status in writing and a date beside it: corrected, scheduled, or still open, with the customer told in writing and the report filed wherever the jurisdiction asks for one. The same edition calls for inspection records to be retained until the next test and for a year after it.
The list is a plain record of what was found in a customer’s building and what happened next, and it tells the customer nothing found in their building was left to memory.
The visits you and the customer chose
Some companies carry no fire work at all. Most established companies we know carry service agreements, and many of those schedule a preventive maintenance visit on an intrusion, access control, or video system.
Outside fire and a few fire-code rules tied to specific hardware, those visits exist because the agreement puts them there. One state’s fire code, as of October 2026, sets a testing schedule for sensor-release locks on exit doors. Where no rule like that applies, you and the customer chose the visit.
For a customer with no fire system, that visit is often the one time your company is in the building when nothing is wrong, and it is usually where that customer’s site record and key ring get written.
What a serious reader sees
We wrote in the five fundamentals that drive the value of a commercial security company that the first is recurring revenue with real roots. A visit that lands in its month and puts what it found in writing is one of those roots. A company that can show twelve months of them knows how its recurring revenue is earned.
Where we stand
A visit kept in its month is a small promise, and a calendar holds a year of them. We built Halo Service Partners on the conviction that in commercial security, trust is the product, and a kept calendar is that trust one month at a time. Continuity is the center of how we partner, because the trusted local company is the thing worth protecting. The name stays, the team stays, and the customer relationships stay. What changes is what stands behind them: resources across the network, technology and finance among them, so an owner taking on work like this has support behind it, and a company can take the step it has been weighing. Founders choose their own path forward: step back, stay on to lead, or take a larger role across the network.
ProTech Security and Verified Security both run under their own names today, with the leaders and teams who built them still serving the customers who know them.
If you’re thinking about the future
If you own a commercial security company and you are thinking about its future, in any direction, we are glad to compare notes: on how companies like yours lay out the year, on the market, and on what your next chapter could look like. Count next year’s visits by month either way. Twelve numbers will tell you more about the year ahead than we can.