Fire Code Upgrade Documentation Guide

• →Confirm adopted building, fire, electrical, plumbing, mechanical, and energy code editions for the property address.
• →Determine repair scope trigger: spot repair, room rebuild, elevation replacement, or substantial reconstruction.
• →Identify common fire-rebuild triggers: electrical replacement, fire blocking, draft stopping, rated assemblies, life-safety alarms.
• →Research local amendments and municipal ordinances that exceed model code — especially on commercial and multi-family occupancy.
• →Document code research before carrier estimate lock-in so code scope is anticipated, not discovered only at supplement.

Code research at intake prevents under-scoped original estimates that carriers treat as baseline.

• →Review policy declarations and endorsements for ordinance and law limits when owner provides policy documents.
• →Understand Coverage A (undamaged portion demolition), Coverage B (increased cost of construction), and Coverage C (contingent liability) where listed — availability varies by policy.
• →Separate code-required upgrade scope from like-kind repair scope in estimate organization.
• →Do not assume coverage exists; document code requirements regardless and let carrier apply policy language.
• →Note policy limits and sublimits in supplement cover letter when ordinance and law endorsement is confirmed.

Coverage availability depends on the individual insurance policy. This guide addresses documentation, not policy interpretation or legal advice.

• →Submit permit application with scope aligned to insurance claim rebuild — not cash-bid scope that omits code items.
• →Track plan review comments and correction notices; save all written AHJ communication in code folder.
• →Schedule inspections at rough-in, framing, electrical, and final phases; photograph conditions inspectors will verify.
• →Log inspector name, date, inspection type, pass/fail status, and cited code sections for each visit.
• →Obtain written approval or correction notice before proceeding when inspector disputes scope — verbal-only guidance is weak supplement support.

AHJ documentation is primary evidence carriers accept over contractor code opinions alone.

• →Create indexed code-upgrade folder: permits, inspections, citations, photos, engineering, manufacturer specs.
• →Assign one citation document or cover-sheet row per upgrade line with photo cross-references.
• →Capture tear-out and pre-install photos before new assemblies close access.
• →Attach municipal requirement letters or inspector emails when they exceed model code citations.
• →Update scope revision log when each code discovery changes estimate lines.

• →Electrical: full circuit replacement, AFCI/GFCI protection, panel upgrade, service capacity, smoke/CO detector interconnect.
• →Framing: fire blocking, draft stopping, fire-rated wall and ceiling assemblies, structural connectors at rebuilt joints.
• →Envelope: roof ventilation rebalance, fire-rated doors, garage separation, tempered glazing at code locations.
• →Life safety: hardwired smoke alarms, CO detectors, fire alarm panels, sprinkler systems where ordinance requires.
• →Egress and stairs: handrail height, tread/run geometry, emergency egress windows where triggered by rebuild scope.
• →MEP: HVAC replacement triggering efficiency code, duct sealing, mechanical ventilation, plumbing fixture upgrades.
• →Accessibility: ADA-compliant routes, fixtures, and parking where commercial or multi-family rebuild triggers compliance.
• →Separate legitimate code items from owner preference upgrades — finish upgrades are not code arguments.

• →Create separate estimate section or grouping for code-required upgrades — distinct from fire damage repair lines.
• →Assign line items with supporting notes referencing code section, permit number, and photo folder.
• →Include permit fees, plan review fees, and engineering costs as separate lines when receipts exist.
• →Cross-reference demolition scope that triggered code requirement — partial repair versus full room rebuild.
• →Avoid burying code lines inside general repair macros that desk reviewers cannot audit line by line.

• →Write one paragraph per line: trigger → code citation → photo reference → quantity.
• →State repair scope that activated the requirement — what was demolished or opened.
• →Quote operative code sentence; do not attach entire code chapters without job-specific application.
• →Include attachment index mapping filenames to line numbers for desk reviewer navigation.
• →Submit phased code supplements when demolition discovers additional triggers — contemporaneous evidence beats end-of-job dumps.

• →"Not required" — attach AHJ correction notice, failed inspection, or plan review comment citing section.
• →"Pre-existing" — tear-out photos showing prior non-compliant condition before upgrade install.
• →"Betterment" — separate code mandate from finish upgrades; cite inspector requirement versus owner selection.
• →"Maintenance" — document that code triggered at repair/rebuild event, not deferred maintenance argument.
• →"Not covered" — reference ordinance and law endorsement when confirmed; document code requirement regardless for file completeness.
• →Resubmit with indexed evidence quoting denial language — see Fire Damage Supplement Denial Recovery blog.

• →Multi-family and hotel: common-area fire alarms, sprinkler retrofits, rated corridor assemblies, egress signage.
• →Retail and office: ADA path of travel, accessible fixtures, fire separation between tenants, commercial electrical loads.
• →Industrial and healthcare: specialized fire suppression, clean-room or hood systems, occupancy-specific life-safety mandates.
• →Coordinate code scope with tenant versus owner responsibility on shell-and-tenant improvements.
• →Index engineering and fire marshal reports separately from residential-style photo packages.

Commercial code upgrades are often more complex than single-family fire rebuilds — see the Commercial Fire Claims Guide for large-loss workflow.