Compile the semi-annual fire suppression system inspection documentation package required for the local fire AHJ
domain: commercial-kitchen-hood-exhaust · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the inspection was performed at least every 6 months (and after any system activation) by properly trained, qualified personnel per NFPA 96 and NFPA 17A
Ensure the inspection report covers every system component: detectors, agent containers, releasing devices, piping, hose assemblies, nozzles, signals, and auxiliary equipment, plus an evaluation of whether the protected hazard has changed since the last service
Verify fusible links, sprinkler heads, or other detection devices were serviced/replaced per the manufacturer's listed instructions and note the replacement interval actually used, since sources disagree between annual and semiannual replacement (see gotcha)
Collect the signed/dated service tag or certificate and forward copies of inspection/maintenance certificates to the AHJ where locally required
Confirm all shutoff devices, alarms, and monitoring circuits were tested and reset properly, and file the report where it is retrievable for the AHJ's next site visit
Known gotchas
Sources disagree on the fusible link replacement interval: some summaries of NFPA 96 describe annual replacement while other trade sources describe NFPA 17A as requiring replacement at every semiannual service — confirm the interval against the current adopted edition of NFPA 17A and the specific system's manufacturer manual rather than assuming one answer
Some AHJs require the inspection report to be actively submitted to them, not merely kept on file at the facility — confirm submittal expectations locally before assuming on-site retention is sufficient
A system that was only visually inspected without replacing due detection components (per its listed maintenance manual) is not a compliant semiannual service even if the paperwork looks complete
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?