Determine residential pool-barrier/fence requirements under the International Swimming Pool and Spa Code (ISPSC) Chapter 3
domain: codes.iccsafe.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Access the current adopted ISPSC edition for the jurisdiction (2021 or 2024 text available free to read at codes.iccsafe.org, e.g., codes.iccsafe.org/content/ISPSC2021P3/chapter-3-general-compliance) since barrier requirements can shift slightly between code cycles
Confirm minimum barrier height of 48 inches and that the barrier prevents passage of a 4-inch-diameter sphere through any opening (picket spacing, mesh, ornamental infill) per ISPSC Section 305
For mesh fence barriers specifically, confirm the bottom of the mesh sits no more than 1 inch above grade/deck, vertical clearance doesn't allow the fence to be lifted more than 4 inches from grade, and mesh fencing is not installed atop on-ground residential pools
Confirm gates are self-closing and self-latching, with the release/latch mechanism mounted at least 45 inches above grade (or otherwise inaccessible to young children per the code's release-height provisions)
Check the ISPSC's safety-cover alternative: pools/spas equipped with a powered safety cover complying with ASTM F1346 can be exempted from Sections 305.2-305.7's barrier requirements
Always verify against the specific state/local amendment in force, since many jurisdictions adopt the ISPSC with local modifications to barrier height, setback, or gate hardware requirements
Known gotchas
The ISPSC is a model code — the actual enforceable requirement depends on which edition (and with what local amendments) the specific state/county has adopted; codes.iccsafe.org lets you read multiple editions (2015/2018/2021/2024) so confirm you're citing the one actually in force locally
The ASTM F1346 safety-cover exemption only applies to the specific ISPSC sections it names (305.2 through 305.7) — it does not blanket-exempt a pool from all other barrier/enclosure requirements
This governs pool barriers generally (which are frequently built as standard perimeter fencing); it is not itself a gate-automation standard — pair with ASTM F2200/UL 325 if the pool-area gate is also automated
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?