Select exit devices for a required-egress opening and confirm the correct listing (panic hardware vs. fire exit hardware) applies.
domain: buildershardware.com (BHMA) / UL · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the exit device meets the applicable ANSI/BHMA exit device standard for the required grade and function (rim, surface vertical rod, mortise, or concealed vertical rod).
If the opening is fire-rated, specify fire exit hardware carrying a fire door listing with positive latching, not standard panic hardware.
If the opening is not fire-rated but still requires panic hardware by occupant load, confirm the device carries the applicable panic hardware listing.
Verify dogging (hold-open) features, if present, are disabled or removed on any fire-rated exit device, since dogging is prohibited on fire exit hardware.
Confirm mounting height and single-motion, maximum-force release requirements are met during final hardware inspection.
Known gotchas
Standard panic hardware and fire exit hardware look nearly identical but are separately listed products — installing standard panic hardware (which can be dogged/held open) on a rated opening is a common and serious compliance failure.
Positive-pressure fire testing has effectively superseded the older neutral-pressure basis for new fire door listings — an older device's fire listing basis should be checked against current listing requirements before assuming it's still an acceptable match for a new rated opening.
Field-dogging a fire exit device to prop a rated door open, even temporarily during move-in, defeats the self-latching requirement and is a code violation, not just a hardware misuse issue.
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?