// Fire protection contractors · A later job
Each building's three-year and five-year work, dated from the reports already in your files.
An NFPA 25 inspection schedule for the long intervals, tested as a free AI proof of concept on 20 to 30 buildings whose long-interval work your office has already booked. AI reads each building's past reports, finds every test and inspection due in the next year or two, and drafts its date with the report that supports it. Your service manager checks each draft against the schedule your office actually kept.
- Past buildings
- 20 to 30
- Dates fixed without a person
- None
- System access
- None
// The one job
The annual visit always gets booked. The five-year work is what slips.
Quarterly and annual visits recur on a fixed cycle, so they stay on the schedule. The longer items don't: a pipe assessment last done the year the building changed hands, a dry system's three-year tests, a standpipe hydro, heads in a corrosive area due for sampling early. Those dates sit in old reports, some from the company before you, and someone has to dig them out before the owner can budget the work.
In the proof of concept, AI reads copies of each building's reports and drafts a long-interval calendar for that building: each item on each system, when it was last done and which report says so, the next date that implies, and a flag wherever the history runs out or two reports disagree. It books nothing, tells no owner and changes no report. Your service manager lays each draft beside the dates your office really set.
item by item
// Where it gets hard
Why the next date isn't simply the last one plus five years
Some five-year items share a drain, and a drain can reset the clock. A 2022 PHC Pros article on NFPA 25's internal assessment of pipe notes that it shares a five-year cycle with the internal inspection of alarm and check valves, so one drain can serve all of them, and that a system drained for another reason can be assessed then, which starts the five years again. In a high-rise with one system per floor, the article describes assessing every other system each cycle, so each comes around every 10 years, and a system back in service after more than a year shut down triggers a full obstruction investigation rather than a routine date. The draft dates each item from the last time that system was opened, and names that report.
Dry systems and tanks run on three years. QRFS's guide to dry systems, quoting NFPA 25's 2020 edition, has each dry pipe valve trip tested at full flow every three years and the system tested for air leakage on the same cycle: 40 psi held for two hours with no more than 3 psi lost, or normal system pressure for four hours with the supply shut off. Steel tanks without verifiable corrosion protection get an interior inspection every three years, other tanks every five, and tank level indicators are tested for accuracy every five. A building with a dry system, a tank and a wet riser can carry cycles that never line up, so the draft keeps each separate.
Hydrostatic tests depend on what is installed and which edition applies. The FDC piping test, from the connection to its check valve at 150 psi for two hours at least once every five years, entered NFPA 25 in the 2014 edition as section 13.7.4, according to NFSA's history of the standard. New York's Department of State quotes it as 13.8.5 from the 2017 edition, the one its 2020 state fire code points to. Manual standpipes and semiautomatic dry standpipes carry a separate five-year hydro at 200 psi, or 50 psi over maximum pressure, for two hours. A building whose reports all predate that test may show no FDC hydro at all, which the draft marks as a gap.
Sampling ages change with the head and with the edition. QRFS's summary of NFPA 25's sprinkler rules puts heads in harsh or corrosive environments on five-year testing or replacement, listed corrosion-resistant heads at 10 years and every five after, and standard-response heads on five-year testing once they reach 75 years; heads made before 1920 are simply replaced. When one sample fails, every sprinkler that sample represents is replaced. Dry sprinklers show how far editions can drift: 10 years to the first test in the editions from 2002 to 2017, and 15 in the 2020 text QRFS quotes, before the 2023 edition moved it again. Each drafted date names the edition it assumes; choosing one stays with your service manager and the jurisdiction.
The history belongs to the owner, and it has holes. NFSA's guide to NFPA 25 record keeping has records kept for one year after the next test of the same type, three-year and five-year work included, and treats the reports as the property owner's, with acceptance test records kept for the life of the system. A building taken over from another company may arrive with one five-year report or none. Your service manager will check first: items missing from a building's calendar, dates borrowed from the wrong system, cycles a drain should have restarted, gauge and extinguisher hydrostatic dates left off, and any date stated with more confidence than its report supports.
// What you send
What the test needs from your service office
Reports for 20 to 30 buildings
Every report you hold for each building, annual and long-interval, far enough back to reach its last five-year visit, including any written by the company before you.
The schedule you actually kept
Your due-date list or service calendar for those buildings, the long-interval work you booked, and a note wherever a date moved and why.
What you know about each building
System lists, dry systems and tanks, standpipe types, acceptance test dates on file, and the edition of NFPA 25 each jurisdiction enforces, where you know it.
NDA first, look-alikes if needed
A building's report history shows what is overdue there, so the NDA is signed before any file moves. If an owner won't release copies, we build look-alike histories with your service manager.
// Before it starts
Settled before the first building is read
The owner decides two things up front: who judges the calendars, and what passing means.
- Reviewer
- Named by the owner. Usually the service manager or the scheduler who books five-year work.
- Success criteria
- In writing first, including how a missed item and a wrong date each count
- Due dates
- Drafted for a person to approve; none booked or sent by AI
- Price
- A range for the live job, given before the first building
- NDA
- Signed before any report leaves your office
// How it's judged
Each draft calendar beside the dates your office set
| Same 20 to 30 buildings | Your office's schedule | The proof of concept |
|---|---|---|
| Long-interval items found on each system | Filled in from your buildings | Filled in from your buildings |
| Last-done dates traced to a report | Filled in from your buildings | Filled in from your buildings |
| Cycles restarted by an earlier drain | Filled in from your buildings | Filled in from your buildings |
| Edition each date assumes | Filled in from your buildings | Filled in from your buildings |
| Gaps flagged rather than filled in | Filled in from your buildings | Filled in from your buildings |
| Dates that turned out wrong | Filled in from your buildings | Filled in from your buildings |
// After a yes
About 30 days on the buildings you service
Once your service manager says yes, the job runs for about 30 days, updating calendars as new reports arrive.
A person approves every date before it goes on your schedule or into a note to an owner. Each shows the item, the system, its report and its edition, and anything uncertain arrives flagged.
Before the live run, you sign a fixed price set once the test is over. Impairment paperwork, deficiency quotes or any other job is priced on its own, and monthly support begins once a job is live.
// After calendars
What could come next
- 01Next
Owner budget letters
Next year's long-interval work for each building written up for the owner to budget, sent only after your service manager approves it.
- 02Then
Impairment paperwork
Notices, fire watch logs and restoration records drafted when a person decides a system must come out of service for that work.
- 03After that
Takeover file reviews
A building won from another company read report by report, so its first calendar starts from what is actually on file.
// One hard limit
It drafts dates. A person decides which ones count.
The draft proposes due dates and shows where each came from. No date the owner or the authority having jurisdiction relies on is set until a person approves it, and the proof of concept notifies nobody. It never signs, certifies or alters an inspection report, and it never rules that a system is impaired, or that one meets code. Which edition applies, what counts as overdue and what an owner is told stay with your licensed staff and the jurisdiction.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
The range comes on the call, once we know roughly how many buildings you service and how many have dry systems, standpipes or tanks.
// Questions
Long-interval calendar questions from service managers
Will the AI set our five-year dates or tell owners what is due?
Which edition of NFPA 25 does it follow?
Some buildings came from another company with almost no history. Is the test still useful there?
Does it cover alarm and extinguisher dates as well?
Do you need access to our scheduling or inspection software?

Rob Eason, founder
// Book a proof-of-concept call
Bring the buildings whose five-year work comes due next.
Half an hour with Rob. Expect questions about your company, your role, which job you'd test first and how many buildings are on your inspection list. Keep every report in your office until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
