Determine the scope boundary between NFPA 80 fire door requirements and firestop/joint scope on a project
domain: nfpa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify which openings in the project are discrete opening protectives (doors, fire/smoke dampers, windows) governed by NFPA 80's installation, inspection, and maintenance requirements, versus penetrations for pipes/cables/ducts governed by firestop scope.
Route fire-door hardware, clearance, and labeling compliance questions to the NFPA 80 inspection/maintenance process rather than the firestop special-inspection process (ASTM E2174/E2393).
Where a fire door assembly has an adjacent penetration (e.g., cable/conduit through the frame area or adjacent wall), clarify in the project specifications which scope covers which physical element to avoid a coverage gap.
Confirm recurring fire-door inspection requirements under NFPA 80 are tracked separately from the barrier-management program covering firestop penetrations.
When a specific condition is ambiguous, consult the AHJ on which standard/inspection applies rather than assuming either scope defaults to cover it.
Known gotchas
Assuming firestop contractors or their E2174/E2393 inspections also cover fire-door compliance (or vice versa) creates a documentation gap — these are separate standards with separate inspection regimes.
NFPA 80 requires its own recurring inspection cycle distinct from any one-time construction special inspection — don't conflate the two schedules.
Confirm the current NFPA 80 edition adopted by the jurisdiction before citing specific inspection intervals, since requirements can change edition to edition.
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?