Perform quarterly waterflow alarm device testing, including self-testing alarm programs
domain: NFPA 25 ch. 13, waterflow alarm and detection devices · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify device type -- vane/paddle waterflow switch, pressure switch, or water-motor gong -- since test method differs
For mechanical/pressure-type devices, induce flow through the inspector's test connection and confirm the local alarm and remote signal both activate within the specified time
Where an approved self-testing waterflow alarm program is used, confirm the self-test is actually being performed and logged, and confirm the separate requirement to physically flow water through the system at least every 3 years even when self-testing is used
Reset the device and system to normal after the test and confirm the restoral signal transmits
Document alarm activation time and confirm it falls within the manufacturer/listing-specified delay window
Known gotchas
A self-testing waterflow alarm satisfies the routine functional test but does NOT eliminate the periodic requirement to actually flow water through the system -- relying entirely on self-test data is a common compliance gap under the current edition's provisions
Excess retard-chamber delay, or the absence of one on a device that should have it, can indicate a maintenance issue even if the alarm eventually activates and technically passes
Testing waterflow without coordinating a hold with the central station can trigger an unwanted fire department dispatch
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?