Apply UL 325's monitored entrapment-protection requirements to a commercial (non-vehicular-gate) door operator installation.
domain: operator-safety-compliance · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the operator is a commercial door/grille application (rolling door, sectional door, etc.) under UL 325's scope, which covers door, drapery, gate, louver, and window operators and their entrapment/fire/electric-shock hazards.
Determine whether the installation uses constant-pressure-to-close operation or a compatible, monitored entrapment-protection device — UL 325 requires one or the other.
If the door lacks a monitored, properly functioning primary entrapment-protection device, confirm the operator is limited to constant-pressure operation only.
For rolling doors/grilles with the operator mounted less than 8 feet above the door, verify manufacturer-supplied covers protect all exposed pinch points.
Provide at least two entrapment-protection devices for each potential entrapment area in each direction of travel where the installation requires monitored protection rather than constant pressure.
Known gotchas
Don't conflate UL 325's commercial door operator provisions with its vehicular gate operator class system (Class I–IV) — those are a separate part of the same standard and use different terminology.
A sensing device that isn't monitorable by the operator does not satisfy the monitored-device requirement even if it functions mechanically — the operator must be able to detect its failure.
8-foot mounting-height and pinch-point cover rules apply specifically to rolling doors/grilles, not uniformly to every commercial door type.
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?