A property manager called me on a Friday, annoyed, wanting to know why the annual sprinkler report hadn't shown up yet. I'd run the test three weeks before. The report itself was sitting half filled out in a folder on a laptop, because I got pulled onto an emergency call the same afternoon and never circled back. Nothing was wrong with the system. The paperwork just fell through a gap that had nothing to do with fire protection and everything to do with tracking.
That's basically what "NFPA 25 software" means when someone types it into Google mid job. Not a fancy platform. Just something that remembers what's due, when, and on which riser, so it doesn't live in your head or a folder that only you can find.
What NFPA 25 actually makes you track
NFPA 25 covers inspection, testing, and maintenance of water based fire protection systems, sprinklers, standpipes, fire pumps, private hydrants, the works. The standard itself is mostly frequency tables. Weekly on some things, monthly on others, quarterly, annual, and a handful that only come around every three or five years. On a single mid sized building you can easily have twenty or thirty separate due dates running on different clocks at once, and they don't reset in sync.
That's the part that breaks people, not the actual testing. A gauge test takes ten minutes. Remembering that this particular dry valve's full trip test was due eleven months ago, on a building you haven't been back to since, is the hard part.
The frequency table, roughly (check your adopted edition)
Table and section numbers moved some between the 2020 and 2023 editions of NFPA 25, and not every AHJ has adopted the same one yet, so treat the reference column as a starting point, not gospel.
| Component | Test/Inspection | Typical Frequency |
|---|---|---|
| Sprinkler heads (wet system) | Visual inspection | Quarterly |
| Fire pump | No flow (churn) test | Weekly |
| Standpipe hose valves | Visual inspection | Annual |
| Backflow preventer | Forward flow test | Annual |
| Dry pipe valve | Full trip test | Every 3 years, or per AHJ |
| Underground/lead in pipe | 5 year internal obstruction investigation | Every 5 years |
I've had two AHJs in the same state read the dry valve trip frequency differently. One wanted it every three years no exceptions, the other let a full trip ride longer if the quick opening device got tested annually. Don't assume, call and ask, or check what's actually adopted locally.
Main drain tests are the one that trends, not just passes
A main drain test is quick, mostly a pass or fail on paper. But the number underneath it is the useful part, and it only means something next to last year's number. Here's an anonymized run from one riser I've serviced for a few years:
| Year | Static (psi) | Residual (psi) | Change from baseline |
|---|---|---|---|
| 2023 | 82 | 61 | baseline |
| 2024 | 80 | 58 | about 5% down |
| 2025 | 79 | 52 | about 15% down |
A drop like that 15% usually means go look upstream before you write "satisfactory" and move on, a partially closed control valve, something changed on the supply side, a PIV that didn't get reopened all the way after work. I wrote more on how to actually run and read that test in the main drain test breakdown. Point here is just that this number is worthless as a single data point. It only tells you anything sitting next to three or four years of itself, which means whatever you're using to log it needs to actually keep the history, not just the pass/fail box for this visit.
What the "software" part needs to actually do
Strip away the sales pitch and it's really four things. Know what's due and when, per component, not per building. Keep enough history on the numeric stuff (main drain, fire pump churn pressures, gauge readings) that a trend shows up instead of getting buried in last year's PDF. Tag a deficiency to the actual device or valve it came from, not a vague note in a paragraph, so when you're back on site in six months you know exactly what you tagged and why. And spit out a report in the shape your AHJ or the building owner's insurer actually wants, signed, dated, without you retyping the same address and system info for the fourth time this month.
None of that is exotic. Most of it is just refusing to let a due date live only in someone's memory. If a system's under impairment for any of this, that's its own tracking problem on a tighter clock, worth reading up on separately if you haven't already: impairment procedures under NFPA 25.
Where the spreadsheet approach falls apart
Works fine solo, for a while. Then a second tech gets added, or you win a contract with sixty buildings, and now there's a shared drive with three versions of the same file and nobody's sure which one has this month's readings. I've seen an inspection company miss a five year internal pipe inspection by almost a full year because the due date lived in a column on a sheet nobody opened between annual visits. Nothing failed. It just sat there quietly getting later.
Full disclosure, chasing that same due date problem on the fire alarm side of my own work is a chunk of why I ended up building FireDeck, mostly submittals right now, but the tracking gap is the same animal whether it's a battery calc or a main drain reading. Anyway. hope the frequency table saves somebody a phone call to their AHJ.