STATE LAW – OREGON LIBRARY – GUIDE 07
Policy Interpretation & Reading the Insurance Contract
An insurance claim is governed by more than the declarations page. Oregon reads the complete insurance contract together with the statutes that regulate it. This guide explains how Oregon courts determine what policy language means, when ambiguity is resolved against an insurer, and what happens when policy language conflicts with Oregon insurance law.
Read the insurance policy as a legal system
A declarations page may show vehicles, limits and selected coverages,
but those numbers do not explain who is insured, what events are covered,
what exclusions apply, what conditions must be satisfied or how Oregon
statutes alter the contract.
Begin with the declarations, insuring agreement, definitions,
limits, exclusions, conditions and endorsements.
Liability, PIP and UM/UIM policies contain substantial protections
controlled or supplemented by Oregon statute.
Oregon courts use a structured method rather than immediately
declaring every disputed phrase ambiguous.
Oregon’s Hoffman method controls policy interpretation
Hoffman Construction Co. v. Fred S. James & Co.,
313 Or 464, 836 P2d 703 (1992), supplies Oregon’s foundational framework
for resolving disputed insurance-policy language.
Identify the exact word, phrase or clause controlling the coverage
dispute rather than arguing generally about what the policy “means.”
If the policy expressly defines the disputed term, Oregon courts
ordinarily apply that contractual definition.
If the policy does not define the term, determine whether it has
only one plausible ordinary meaning.
If more than one plausible meaning remains, read how the term is
used within that specific provision.
Compare related definitions, conditions, exclusions and coverage
provisions rather than isolating one sentence.
Ask whether two or more competing interpretations remain reasonable
after the contextual analysis.
Only when competing reasonable interpretations survive the preceding
steps does Oregon apply the rule against the drafter.
Even unambiguous wording cannot necessarily defeat coverage that
Oregon law requires the policy to provide.
Read the policy in a disciplined order
Insurance policies are easier to understand when each section is assigned
a specific function.
Named insured, vehicles, policy dates, selected coverages,
limits, deductibles and endorsements.
Identify what loss the insurer initially promises to pay,
defend or indemnify.
Terms such as insured, family member, covered auto, occupying,
accident and bodily injury can decide coverage.
Insured status often changes by coverage section.
A person insured for liability is not necessarily insured in exactly
the same way for every other coverage.
Owned auto, newly acquired auto, temporary substitute,
nonowned auto and permissive-use terms require separate review.
Identify per-person, per-accident, property-damage and other limits
and determine whether several policies or limits may apply.
Never assume an exclusion is valid merely because it appears
in the policy.
Notice, cooperation, proof, consent, legal action and other
requirements may become separate coverage defenses.
Determine whether the provision creates primary, excess or prorated
coverage and whether Oregon law permits the claimed result.
Endorsements may add, delete or replace policy terms and must be read
with the declarations and base contract.
ORS 742.016 limits when an insurer may use the written application
as part of the insurance contract.
Mandatory liability, UM/UIM, PIP and other statutory rules can alter
or invalidate policy restrictions.
Policy definitions usually come first
Oregon Supreme Court decisions consistently begin by asking whether
the insurer expressly defined the disputed term.
A word can take meaning from the sentence, paragraph or coverage
provision in which the insurer placed it.
Another definition or provision may resolve a meaning that initially
appeared uncertain.
Ambiguity is the end of the analysis—not the beginning
Oregon’s rule construing unresolved ambiguity against the insurance
company is important, but Hoffman deliberately places it at the end
of the interpretive process.
This begins the contextual inquiry but does not necessarily establish
the ultimate ambiguity required to invoke the rule against the insurer.
A proposed interpretation may cease to be reasonable when related
provisions are considered.
If competing interpretations remain reasonable after contextual
analysis, Oregon resolves the remaining doubt against the insurer.
Oregon statutes can override the printed contract
Insurance is contractual, but automobile insurance is also heavily
regulated. A policy form cannot simply contract around mandatory Oregon
protection.
ORS 742.021 requires standard or uniform provisions required by the
Insurance Code and limits inconsistent policy wording.
ORS 742.028 permits additional provisions when they are not prohibited
and do not conflict with required provisions of Oregon law.
The insurance application is not automatically part of the policy
ORS 742.016 places meaningful limits on using application statements
to interpret or defeat insurance coverage.
Misrepresentation and rescission questions also implicate ORS 742.013
and are addressed more fully in Guide 07 when exclusions, conditions
and coverage defenses are examined.
Oregon requires access to the actual policy
A consumer cannot meaningfully investigate coverage from a declarations
page alone. Oregon therefore regulates delivery of policy forms and
endorsements.
Oregon permits qualifying standard property and casualty policies and
endorsements to be posted online instead of physically mailed, but the
insurer must provide identifying information, maintain access, archive
expired forms for the statutory period and advise the insured of the
right to request a printed copy without charge.
Oregon automobile policies contain rules imposed by statute
Automobile policies deserve separate treatment because Oregon expressly
regulates their required terms.
| Authority | Interpretive effect |
|---|---|
| ORS 742.450 |
Requires the policy to identify the named insured, coverage, premium, period and liability limits and to contain Oregon’s required motor-vehicle liability protection. |
| ORS 742.456 |
For qualifying required liability policies, insurer liability becomes absolute upon covered injury or damage and may not later be canceled or annulled by insurer-insured agreement. |
| ORS 742.458 |
Makes the policy, applicable written application and lawful endorsements the automobile insurance contract and imposes provisions whether or not physically printed in the policy. |
| ORS 742.464 |
Permits lawful additional or excess coverage and distinguishes mandatory statutory coverage from insurance purchased above the required amount. |
| ORS 742.504 |
Establishes Oregon’s comprehensive statutory UM/UIM model. Required UM/UIM protection may not be less favorable than that model. |
| ORS 742.520–742.532 |
Establish Oregon’s mandatory PIP structure and identify required benefits, exclusions and the ability to provide more favorable benefits. |
Required minimum coverage and excess contractual coverage may differ
Oregon automobile liability law sometimes preserves coverage required by
statute while permitting the same exclusion to operate against insurance
purchased above the statutory minimum.
Oregon Supreme Court held that a liability exclusion could not
eliminate coverage required by Oregon’s Financial Responsibility Law.
The Supreme Court later reaffirmed that the exclusion could remain
enforceable against liability limits purchased above the statutory
minimum.
UM/UIM policy interpretation has an additional statutory test
Ordinary contract interpretation is only part of Oregon UM/UIM analysis.
Oregon has prescribed a comprehensive statutory model in ORS 742.504.
This doctrine was important again in
Batten v. State Farm, where the Oregon Supreme Court rejected an
insurer’s anti-stacking provision because the provision restricted coverage
beyond what Oregon’s current statutory model permitted.
Coverage and exclusion burdens are ordinarily separated
Oregon cases generally place the initial burden of establishing coverage
within the policy’s grant on the party seeking coverage, while the insurer
bears the burden of proving an exclusion.
Identify the insured, covered vehicle, occurrence or accident,
bodily injury or property damage and the other elements of the
insuring agreement.
Once coverage is otherwise established, Oregon generally places the
burden of proving a policy exclusion on the insurer.
Policy interpretation generally begins within the four corners
Oregon treats interpretation of insurance-policy language as a question
of law based primarily on the policy’s terms and conditions.
Duty-to-defend interpretation has its own Oregon rules involving the
complaint and the insurance policy. Those issues are developed separately
in Guide 08.
Leading Oregon policy-interpretation authorities
Oregon’s foundational insurance-policy interpretation case.
Establishes the defined-term, plain-meaning, context and
unresolved-ambiguity methodology.
Reaffirms that policy interpretation is a legal question and applies
the Hoffman sequence to an undefined term.
Restates Oregon’s modern interpretation methodology: express
definition, ordinary meaning, immediate context, policy-wide context
and only then construction against the insurer.
Applies the Hoffman/Holloway framework and reinforces the importance
of policy definitions and whole-contract context.
Illustrates Oregon’s use of ordinary meaning and dictionary analysis
where the policy leaves a disputed term undefined.
Critical automobile authority. UM/UIM policy provisions cannot
provide protection less favorable than Oregon’s comprehensive
statutory model.
Distinguishes the mandatory liability-insurance floor from
additional contractual limits and reaffirms the earlier
Collins rule.
Important burden-of-proof authority distinguishing proof of the
coverage grant from the insurer’s burden to establish policy
exclusions.
Reaffirms Oregon’s policy-text methodology and describes ordinary
policy interpretation as a four-corners analysis.
Citizen workflow for reading an Oregon auto policy
Declarations, base form, endorsements, applications incorporated
into the policy and Oregon-specific amendments.
Liability, collision, PIP, UM/UIM or another coverage section.
Determine exactly why the person qualifies—or allegedly fails to
qualify—as an insured for that coverage.
Identify what event and loss the insurer initially promises to cover.
Use the policy’s own definition before searching for an ordinary
meaning.
Determine precisely what the insurer contends is removed from
otherwise applicable coverage.
Notice, cooperation, consent, proof and suit provisions can create
distinct defenses.
An endorsement can modify or replace the language in the base form.
Definition → ordinary meaning → immediate context → policy as whole
→ unresolved ambiguity against drafter.
Determine whether the policy supplies at least the mandatory
liability, PIP or UM/UIM protection Oregon requires.
An exclusion may produce a different result against statutory
minimum coverage than against excess contractual limits.
Preserve the insurer’s cited provisions, factual assumptions and
explanation so each can be tested against the contract and Oregon law.
Oregon Guide 06 statutory map
| Authority | Interpretation function |
|---|---|
| ORS 742.005 |
Requires disapproval of policy forms that are unlawful, unintelligible, uncertain, ambiguous, misleading, unjust, unfair or inequitable under the statutory standards. |
| ORS 742.013 |
Governs when misrepresentations, omissions or incorrect statements in a written insurance application can prevent recovery. |
| ORS 742.016 |
Directs construction according to policy terms and controls when an application or oral representation forms part of the contract. |
| ORS 742.018 |
Invalidates policy provisions requiring construction under another state’s or country’s law. |
| ORS 742.021 |
Regulates mandatory standard policy provisions and prohibits inconsistent policy language. |
| ORS 742.023 |
Identifies basic information and provisions an insurance policy generally must specify. |
| ORS 742.028 |
Allows additional policy terms only when permitted and not inconsistent with the Insurance Code. |
| ORS 742.038 |
Reforms otherwise binding policies that fail to comply with the Insurance Code so they operate as Oregon law requires. |
| ORS 742.046 |
Governs delivery and permitted electronic posting of policies and endorsements. |
| ORS 742.450 |
Supplies required content and statutory coverage rules for Oregon motor-vehicle liability policies. |
| ORS 742.456–742.464 |
Supply additional statutory rules governing automobile liability policies, mandatory protection and additional/excess coverage. |
| ORS 742.504 | Creates Oregon’s comprehensive statutory UM/UIM policy model. |
Official Oregon sources for Guide 06
Policy forms, contract construction, automobile liability,
UM/UIM, PIP and related statutory requirements.
Oregon Legislature’s case annotations for policy statutes and
automobile-insurance provisions.
Oregon Supreme Court’s foundational insurance-policy interpretation
methodology.
Leading authority explaining Oregon’s statutory UM/UIM model
and the prohibition on less-favorable policy terms.
Check current session law before relying solely on Oregon’s
online 2025 codification.
Guide 07 applies the interpretation framework to exclusions,
notice, cooperation, misrepresentation and other insurer defenses.
Stacking, Multiple Policies & Other Insurance
Guide 08 → Oregon Coverage Disclosure & Insurer Duties
Read the contract—but also read the Oregon law that governs it.
Begin with the complete policy rather than the declarations page.
Identify the coverage grant, insured, covered vehicle, definitions,
limits, exclusions, conditions and endorsements. Apply Oregon’s Hoffman
interpretation method to disputed wording. Then compare the contractual
result with Oregon’s mandatory liability, PIP and UM/UIM statutes.
A policy is a contract, but it is a contract operating inside Oregon’s
Insurance Code.
Public-interest education only. No legal services offered or accepted.
No attorney-client relationship created.