Set up fire door inspection recordkeeping that will hold up to an AHJ audit under NFPA 80.
domain: fire-door-compliance · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the inspection/testing frequency required — NFPA 80 requires fire door assemblies be inspected and tested not less than annually.
Create a written record for each individual door/opening rather than a single blanket facility record, and keep the opening identifiers consistent with how the doors are labeled elsewhere in the facility's documentation.
Ensure each record captures, at minimum: inspection date, inspector name, the specific opening/door identified, deficiencies found, and corrective action taken.
Retain records on premises in a form accessible for AHJ review; note that NFPA 80 itself does not specify an exact numeric retention period — as a matter of practice, many facilities retain records for a minimum of several years or the life of the assembly, and NFPA 105 (smoke door assemblies) does specify an explicit minimum retention period, which some facilities apply by analogy.
Check for local AHJ amendments that may impose stricter frequency or documentation requirements than the NFPA 80 baseline.
Known gotchas
Do not cite a specific numeric retention period as an NFPA 80 requirement — NFPA 80 does not itself state one; only draw the 3-year figure from NFPA 105 and label it as that standard's requirement for smoke doors, not NFPA 80's.
A single combined inspection log covering multiple doors without individual per-opening records may not satisfy an auditor looking for a discrete record per assembly.
Local AHJs can and do layer additional requirements on top of the NFPA 80 baseline — don't assume the NFPA baseline is the complete compliance picture.
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?