Identify exactly which real-world conditions require a NFPA 211 Level II chimney inspection
domain: nfpa.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Reference the current edition of NFPA 211 for the defined Level II triggering conditions rather than relying on secondary summaries
Confirm property-transfer triggers: NFPA 211 calls for a Level II inspection at the sale or transfer of real property
Confirm appliance/system-change triggers: a change in fuel type, a change in the flue's shape or lining material (e.g., relining), or addition/replacement of an appliance with a dissimilar type, input rating, or efficiency
Confirm event-based triggers: an operational malfunction or an external event (chimney fire, building fire, seismic event, severe weather) reasonably likely to have caused damage
Scope the Level II inspection to include everything in Level I plus accessible interior spaces (attic, crawlspace, basement) and an internal video scan of all flue liners
Provide the client a written report distinguishing the Level II trigger reason, since insurers and buyers often require that documentation
Known gotchas
A routine annual cleaning does not by itself require a Level II inspection — only the specific defined triggers do; do not over-scope (and over-bill) without a documented trigger
Video/internal scanning of the flue is a required element of Level II, not optional — a Level II report without interior scan documentation is incomplete
Confirm the exact wording of the triggers in the current NFPA 211 edition adopted locally, since paraphrased trigger lists on third-party sites can drift from the standard's actual language
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?