Read the Policy First. Build the Estimate Second.
Most claims start the same way: something gets damaged, and the first instinct — for a policyholder, a contractor, sometimes even an adjuster — is to go measure it. Walk the property, photograph the damage, price out materials and labor, arrive at a number. It feels like the productive first step, because it's the one you can actually see and touch.
It's also, almost always, the wrong place to start.
Why the estimate-first instinct is so common
Damage is tangible. A collapsed ceiling, a scorched wall, a soaked subfloor — these are things you can point a camera at and start pricing the same afternoon. A policy, by contrast, is dense, unglamorous, and easy to treat as a formality: something to glance at for the coverage limit and the deductible, then set aside while the real work of measuring the loss begins.
That instinct isn't unreasonable. It's just backwards.
What gets lost when the estimate comes first
Building the estimate before reading the policy costs more than it looks like it saves, in three specific ways:
You can spend real time estimating something that was never going to be paid. If a loss falls under an exclusion, or a category is capped well below what the damage actually costs, a fully built-out estimate for that scope was work spent proving a number the policy was never going to honor. Reading the policy first tells you where that line sits before you spend a day measuring around it.
You can miss coverage nobody thought to look for. Ordinance-or-law upgrades, additional living expenses, debris removal, code-compliance costs — these show up in the policy, not in the damage. An estimate built purely off what's visibly broken won't include a category nobody knew to check for. You don't estimate what you haven't found.
You can build proof that doesn't match what the policy actually requires. Different policies value a loss differently — replacement cost, actual cash value, sometimes functional replacement cost — and some carry specific documentation requirements for how that value gets substantiated. An estimate built to a generic standard, without knowing which standard the policy actually calls for, can end up short of what the policy needs to see before it will pay.
What reading the policy first actually means
In practice, this means going through the declarations page, the policy forms, and every endorsement before a single line item gets written — identifying the coverage limits, the sublimits, the named exclusions, the valuation method, and any conditions that affect how a claim has to be documented. It's building the map before measuring the terrain, so the estimate that eventually gets built is aimed at something the policy can actually pay.
The real payoff: an estimate that can't be picked apart
Everything above is really building toward one outcome, and it's worth naming directly: an estimate that's already been tested against the one document that decides whether it gets paid.
Build the estimate first, and every line item is an argument you haven't made yet — which means every line item is also a place for an insurer to push back. Each pushback you didn't see coming sends you back to rewrite, re-justify, or re-price something that should have been settled before it was ever submitted. That's real hours spent defending a category of damage that turns out to be excluded, or capped, or valued differently than you assumed — rework that exists only because the policy got read second instead of first.
Read the policy first, and that entire category of rework disappears. You're not defending a number and hoping the policy backs it up after the fact — you already know it does, because the number was built from the policy outward instead of the other way around. Nothing on the estimate is there by accident, and nothing on it is vulnerable to a challenge you didn't already account for. That's what makes it bulletproof: not that it's aggressive, but that it's already been checked against every objection before the insurer gets a chance to raise one.
There's a sharper way to put it. The policy is the insurance company's own document, written on their terms, to protect their own position. Reading it first and building the estimate to match it means using that same document — their document — to build a claim they can't easily argue with. You're not fighting the policy. You're using it.
Why this is the first thing I do, every time
This is the discipline behind the last two things I've written about here. An estimate proves the loss — but only the policy decides what's even possible to pay for it. Reading the policy first isn't a formality before the real work starts. It is the first part of the real work, because it's what turns an accurate estimate into a strategically built one. That's also why I wrote Policy vs. Estimate: The Estimate Says What It Costs. The Policy Says What Gets Paid. as its own post. This is the practice; that one is the reasoning behind it.
If you're staring at a stack of repair quotes and a policy you haven't read past the declarations page, that's the order worth reversing before you go any further.
Gabriel Antoine is a licensed Public Adjuster in New York (PA-1819103), New Jersey (3002844026), and Indiana (Certificate of Authority No. 4242786). Request a consultation.