Determine sprinkler head replacement/testing due dates and pull the required sample for laboratory testing
domain: NFPA 25 ch. 5, sprinkler sampling program · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify sprinkler type and manufacture date from head markings (standard-response, fast/quick-response, ESFR/CMSA, dry-type, or residential) since each has a different first-test age
Apply first-test intervals: standard-response at 50 years; fast/quick-response at 25 years; ESFR/CMSA at 20 years; dry-type sprinklers at 20 years -- each retested every 10 years thereafter
Pull a representative sample (minimum of 4 sprinklers or 1% of heads of that type/area, whichever is greater) for the age/type group being tested
Ship the sample to a recognized testing laboratory for functional and, where required, thermal sensitivity testing rather than testing in the field
If any sprinkler in a sample group fails, replace all sprinklers represented by that sample per NFPA 25's failure-response rule
Replace pulled sprinklers with new listed heads of the same type/rating and document the event to reset the interval clock
Known gotchas
Mixed sprinkler populations in one building (original standard-response heads plus a renovation-era quick-response upgrade) run on separate age clocks -- treating the whole building as one sample group under-samples the newer heads
A sprinkler that looks fine visually can still fail lab response-time testing; field-only visual inspection is not an acceptable substitute for the lab sample requirement
One failed sprinkler in a sample forces replacement of the entire population that sample represents, which can turn a small test into a large unplanned change-out
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?