Determine and perform the correct NFPA 211 inspection level (I, II, or III) for a chimney venting system
domain: nfpa.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm you are referencing the current edition of NFPA 211, Standard for Chimneys, Fireplaces, Vents, and Solid Fuel-Burning Appliances, via nfpa.org/product/nfpa-211-standard
Perform a Level I inspection as the baseline for any chimney in continued service with no system changes: assess readily accessible portions of the chimney, appliance connections, and structural soundness
Escalate to Level II when the standard's triggering conditions apply (system/appliance changes, fuel-type change, relining, or an event affecting the chimney) — include internal flue surfaces via video scanning per the standard
Escalate to Level III when a Level I or II inspection reveals a suspected hidden hazard that cannot be evaluated without accessing concealed areas, which may require removal of components such as the crown or an interior wall
Document findings against each level's defined scope so the client and any downstream contractor have a clear record of what was and was not inspected
Cross-reference any deficiencies found against manufacturer listings and applicable mechanical/building code before recommending repair or replacement
Known gotchas
Do not perform only a Level I inspection when a triggering condition (sale, appliance swap, chimney fire, storm/seismic event) is present — NFPA 211 requires stepping up to Level II in those cases
Verify the specific edition year of NFPA 211 in force with the local AHJ, since adopted code editions lag the current published edition in many jurisdictions
Level III work often requires coordination with a mason or general contractor for the destructive-access portion — do not remove structural components beyond your scope of authorization
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?