Ordinance & Law: When Code Compliance Is Not Optional
- Chris Johnson
- Mar 2
- 4 min read
When a building is damaged, the discussion usually begins with scope and pricing. But in many losses, the real complexity emerges in a different place:
What does the law require at the time of repair?
Ordinance & Law (O&L) coverage exists to address that question — but only if it has been properly added to the policy.

That distinction is fundamental.
Ordinance & Law Is Initially Excluded
In most property forms, Ordinance or Law is excluded in the base policy language.
In other words:
Without an endorsement, increased costs due to code enforcement are excluded.
Insurance carriers typically restore limited coverage through a specific Ordinance & Law endorsement. That endorsement defines:
The scope of coverage
The limits applicable
The categories covered (often A, B, and C)
Whether coverage applies to undamaged portions
Whether demolition is required as a condition of payment
Whether enforcement must be mandatory
Because O&L begins as an exclusion and is then partially reinstated by endorsement, the endorsement must always be carefully reviewed.
The coverage is not automatic.
It is contractual.
The Practical Tension in Ordinance & Law

In a recent wind-related roof loss (details intentionally omitted), two estimates approached the reconstruction differently:
One focused primarily on observed physical damage.
The other incorporated additional compliance measures tied to current adopted code.
Both positions were technically grounded.
The tension emerged around issues such as:
Insulation thickness required by current energy code
Underlayment standards tied to slope and wind classification
Flashing termination heights impacted by code-driven system changes
Integration adjustments between roofing assemblies and parapet walls
Safety compliance measures required to lawfully execute the repair
The central question was not simply: “Was it there before?”
The better question was:
“Is this required now as a condition of lawful reconstruction — and is it covered by the specific O&L endorsement?”
Those are two separate inquiries.
Code Compliance vs. Scope Expansion
Ordinance & Law is often evaluated line-by-line. But building systems do not operate line-by-line.

O&L must be evaluated through two filters:
Is the requirement mandated by adopted and enforced code?
Does the endorsement provide coverage for that category of cost?
For example:
If insulation thickness must increase to meet current energy code, that change may affect:
Parapet flashing elevations
Termination bar placement
Curb transitions
Drain interfaces
If the insulation upgrade is truly code-required and falls within the endorsement’s coverage grant, then the necessary integration work that allows that system to function properly should also be evaluated.
O&L is not limited to the isolated component.
It may extend to system compatibility adjustments necessary for lawful performance.
However, not every system modification qualifies.
It is essential to separate:
Code-mandated work
from
Preferences, enhancements, or contractor means-and-methods.
from
Betterment or elective improvements
Precision protects both sides.
Safety Compliance: Covered or Overhead?
Another frequent source of tension involves jobsite safety requirements.
General contractor overhead and profit are typically accounted for within estimates. However, legally mandated compliance measures are not elective business practices. When specific site conditions trigger regulatory requirements—fall protection systems, controlled access zones, lift radius constraints, public protection measures—those are compliance conditions that must be satisfied before work can lawfully proceed.
The analytical inquiry should not be categorical. It should be fact-driven:
Is the cost general overhead? Or is it a direct, compliance-driven condition required to perform the covered repair?
Does the endorsement contemplate coverage for increased costs required by enforcement?
Again, the policy language governs.
“Incurred” and Ordinance & Law
O&L issues also intersect with replacement cost timing and incurred obligations.
Property owners may:
Execute a binding roofing contract
Authorize mitigation to prevent further damage
Commit to code-compliant reconstruction
Secure temporary protection while coverage investigation continues
The legal and practical definition of “incurred” can materially affect how O&L benefits are evaluated, especially where code compliance drives contractor scope. However, the existence of a contract does not override endorsement limits or conditions. Incurred obligation and endorsement scope are distinct analytical inquiries.
Coverage analysis must follow the structure:
Base policy exclusion
Endorsement grant of coverage
Limits and sublimits
Enforcement requirements
Conditions precedent
This sequence matters.
This is not about accelerating payment.
It is about understanding when legal obligation and code enforcement converge.
The Risk of a Narrow or Expansive View
An overly restrictive view of O&L may result in:

Incomplete compliance with adopted building code
Systems rebuilt to legacy standards that are no longer permissible
Secondary modifications later required during inspection
Increased overall cost due to sequencing delays
An overly expansive view may improperly convert elective improvements into insured obligations.
Balanced evaluation requires:
Verification of the adopted code version
Confirmation of enforcement triggers
Evaluation of system integration impacts
Careful reading of the O&L endorsement
Separation of covered increased costs from excluded upgrades
O&L analysis is not emotional.
It is contractual and technical.
A Structured Framework for Both Sides
For carriers:
Confirm the specific O&L endorsement language.
Verify limits and sublimits.
Confirm enforcement requirements.
(Check local and/or state websites.)
Review supplied estimates/invoices/contracts where items may be applied to O&L coverage.
Evaluate whether costs fall within the defined coverage categories.
(Utilize estimating software Coverage Specific categorization to apply the coverage in a visual way on the Summary pages.)
For policyholders and representatives:
Anchor arguments to adopted and enforced code.
(Check local and/or state websites.)
Separate compliance from contractor preference.
(Help the carrier see the difference for proper enforcement application to help expedite their review.)
Confirm that the claimed cost fits within the endorsement grant.
(Beware state specific UPPA violations. Hiring a licensed Public Adjuster can help with this portion if necessary.)
Document how code-triggered changes affect adjacent systems.
For both:
Avoid assuming that “not previously existing” equals “not covered.”
Avoid assuming that “code-related” equals “automatically covered.”
Read the endorsement carefully.
The policy language governs.
The adopted code informs.
The facts control.
The Purpose of Ordinance & Law
Ordinance & Law coverage exists because buildings and codes evolve.
Its role is to bridge the gap between:
Pre-loss condition and Lawful reconstruction under current enforced standards.

But it does so only within the limits and structure of the endorsement that restores it.
When properly applied, O&L protects:
The structural integrity of the building
The financial position of the insured
The contractual integrity of the policy
The defensibility of the carrier’s claim decision
It is not adversarial by design.
It becomes contentious only when either the code or the policy language is misapplied.
Handled correctly, Ordinance & Law does exactly what it was designed to do:
It allows buildings to be repaired.
Lawfully. Contractually. Defensibly.




Comments