Conduct and document an NFPA 80 annual functional inspection of fire door assemblies across a commercial building.
domain: nfpa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm which edition of NFPA 80 is adopted by the local jurisdiction's building/fire code before inspecting, since editions differ (e.g., the 2025 edition reorganized chapters and added horizontal fire door assembly provisions).
Walk each rated opening against the field checklist: label legible and unaltered, clearances within listed tolerances, no unauthorized field modifications or holes, self-closing device functions, and the door achieves full positive latching.
Verify glazing, louvers, and hardware match the types/sizes on the door's listing and haven't been field-substituted.
Document each opening's inspection in writing (with photos where useful), noting deficiencies and required corrective actions.
Prioritize and report life-safety deficiencies (doors that won't self-close or latch) to the building owner for immediate repair.
Known gotchas
The annual NFPA 80 inspection is a functional field inspection, not a full listing re-certification — that is a separate process handled through a field-labeling program.
Jurisdictions frequently lag behind the newest published NFPA 80 edition — inspect against the edition actually adopted locally, not automatically the latest one.
Field-applied kickplates, paint, or hardware covering the fire label can silently void it — check that the label is legible, not just present.
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?