Determine temporary construction-fence requirements for site security, distinguishing genuine OSHA obligations from local-ordinance practice.
domain: osha.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Recognize that OSHA does not have one blanket standard mandating temporary construction-site perimeter fencing for every job; obligations instead flow from hazard-specific standards (e.g., excavation and fall-protection rules) and the general duty clause, plus local ordinance/permit conditions.
Check 29 CFR 1926 Subpart G (Signs, Signals, and Barricades) / 1926.202 only where it actually applies (largely a traffic-control/roadway-work barricade standard referencing the MUTCD) rather than assuming it sets a universal fence-height rule.
Confirm whether the local building/public-works permit independently mandates a perimeter construction fence (height, opacity, and locking requirements are set locally; confirm the specific ordinance rather than assuming a fixed number applies everywhere).
Ensure gates in the perimeter fence don't block a required means of egress and remain openable from inside during working hours, per general life-safety principles.
Document periodic fence inspection where the site's safety plan or local permit requires it.
Known gotchas
Don't cite a specific OSHA CFR section as the source of a universal construction-fence height rule — commonly-cited height figures typically come from local ordinance or industry practice, not a federal OSHA mandate.
A locked, opaque perimeter fence can create an egress violation if it blocks the site's required emergency exit path; egress and security needs must both be satisfied.
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?