Code Upgrade Coverage: Fighting for It Decision Tree
Why this matters
Code requires more than a simple like-for-like replacement almost every time you touch something old enough to have been grandfathered in, and the gap between "what was there" and "what code now requires" can be a meaningful share of the job. Whether the carrier pays for that gap depends on a specific, often-overlooked piece of coverage, and most homeowners have no idea whether they have it. Miss this conversation and you either eat the upgrade cost yourself trying to keep the customer happy, or you hand them a surprise bill after the work is done. Neither is a good outcome, and both are avoidable.
Start here: is this actually a code-triggered upgrade
Before you fight for coverage, confirm the upgrade is genuinely required, not just recommended or preferred.
- Genuinely code-required: the current code mandates this specifically because of the repair or replacement being done (a like-for-like swap is no longer legal to install as-is). This is what ordinance-and-law coverage addresses.
- Best practice but not mandated: an upgrade you would recommend because it is safer or more efficient, but the authority having jurisdiction would still approve the like-for-like replacement. This is a customer upsell conversation, not an insurance conversation, and billing it as insurance-covered when it is not is a documentation problem waiting to happen.
Confirm which one you are dealing with before you go further. Pull the specific code citation if you can, it is the single strongest piece of evidence in this entire conversation.
If it is genuinely code-required
- Check whether the policy has ordinance-and-law coverage at all. This is a specific coverage type, sometimes automatic, sometimes an optional endorsement, that pays for the increased cost of complying with current code when repairing or rebuilding after a covered loss. Not every policy carries it, and it is invisible to the homeowner until this exact moment.
- If the homeowner does not know, tell them to ask their agent directly whether ordinance-and-law coverage applies, and at what limit. Do not guess or assume it is or is not there.
- Document the code requirement precisely. Cite the specific code section, not just "code requires an upgrade." A specific citation is far harder for an adjuster to push back on than a general assertion.
- Photograph the existing, non-compliant condition before you touch it. Proving the old installation genuinely predates the current requirement (grandfathered) is often necessary to establish that the upgrade is code-triggered by this repair, not a pre-existing condition the homeowner should have already fixed.
- Submit it as a distinct, clearly labeled line item, not folded into the base repair. "Code-required upgrade per [citation]" reads very differently from an unexplained price jump on an otherwise like-for-like line.
If the adjuster pushes back
Pushback on code-upgrade line items is common, not a sign of bad faith. Work it like any other scope dispute.
- Lead with the code citation, not with an argument about fairness. "This is required by [specific code section]" is a fact the adjuster can verify. "This should obviously be covered" is not.
- Confirm the permit process actually requires it. If the local permitting authority will sign off on the work without the upgrade, your code-required argument weakens considerably. If they will not issue a permit or pass inspection without it, that is strong, verifiable leverage.
- Offer to have the adjuster confirm directly with the local building department if they are unfamiliar with the local code, especially likely with an out-of-area independent adjuster on a catastrophe deployment. See related: Building a Relationship with Independent Adjusters.
- If the policy limit for ordinance-and-law coverage is capped and the upgrade cost exceeds it, that is a policy-limit issue, not a scope dispute. The customer needs to understand the excess is their responsibility regardless of how solid your code citation is.
If there is no ordinance-and-law coverage at all
- Do not proceed as if it will be covered. Confirm this with the homeowner in writing before you build a repair plan around insurance paying for the upgrade.
- Explain plainly that the upgrade is still required by code regardless of what insurance pays. You cannot legally install a non-compliant like-for-like replacement just because the coverage gap is inconvenient.
- Quote the upgrade portion as a separate, customer-responsibility line item, same discipline as any upgrade a customer requests beyond the covered scope. See related: Billing the Insurance Job.
- Do not offer to skip the upgrade to save the customer money. Working around code to lower a bill is the kind of shortcut that ends licenses and creates real liability if it fails inspection or causes harm later.
Comparison: what determines the outcome
| Situation | Coverage likely | Your move |
|---|---|---|
| Genuinely code-mandated, policy has ordinance-and-law coverage | Likely covered up to policy limit | Cite code precisely, document pre-existing condition, submit as a distinct line |
| Genuinely code-mandated, no ordinance-and-law coverage | Not covered | Confirm in writing, bill as customer-responsibility, do not skip the code requirement |
| Genuinely code-mandated, coverage exists but capped below the upgrade cost | Partially covered | Explain the gap clearly before work starts, not after |
| Recommended but not code-mandated | Not an insurance question at all | Handle as a normal upsell conversation, separate from the claim entirely |
Quick recap
Confirm the upgrade is truly code-triggered before you frame it as an insurance fight. Get the exact code citation. Check for ordinance-and-law coverage rather than assuming either way. Document the pre-existing, grandfathered condition. Push back on adjuster skepticism with the citation, not with frustration. Never skip a genuine code requirement to save the customer money or speed up approval.
References
- ICC (International Code Council), model code adoption and enforcement basics
- Insurance Information Institute, ordinance or law coverage explainer
- Local building department permit and inspection requirements (jurisdiction-specific; confirm locally)
- See related: Building a Relationship with Independent Adjusters, Billing the Insurance Job