Making a roof insurance claim in Bell

What follows is how the process actually runs, in the order it runs in. It is not advice about your policy — nobody can give you that without reading it — and it is not a promise about any outcome. It is the map.

In Bell the failure that leads is sudden dry winds that test every lifted edge on the roof, and that shapes what a claim here usually looks like. Dry offshore wind lifts material that damp coastal air had been holding down. Most wind losses here happen on a handful of nights a year.

The sequence, start to finish

There are roughly seven steps and they do not reorder. Document the damage. Make it safe. Report it to the insurer. Meet the adjuster. Receive a scope and an estimate. Have the work done. Submit proof of completion if your policy holds back depreciation until then. Every step depends on the one before it having been done properly, which is why the first one — photographs, before anything is touched — carries more weight than it looks like it should.

Homeowners tend to think the adjuster visit is the decisive moment. It is not. The decisive moment is the hour after the storm, when the evidence either gets recorded or does not.

Evidence, before anything else

The file you want by the time an adjuster arrives contains: dated photographs from before anything was moved, the receipts for anything you spent making it safe, a copy of your policy declarations page, any prior roof paperwork you have, and a written note of the sequence of events. That is not a burdensome list and assembling it is the highest-value hour you will spend on the whole claim.

Prior paperwork matters more than people expect. If you have the invoice from when the roof was last replaced, it establishes the age of the roof, which is the number the entire depreciation calculation runs on.

What to have ready:

• Interior photographs, including the attic and the underside of the deck
• The contractor’s written assessment, if you have had one done
• Photographs of undamaged sections of the same roof, for comparison
• Receipts for tarps, emergency call-outs and anything else spent making it safe
• Dated photographs taken before anything was moved, cleared or covered
• Any paperwork from when the roof was last replaced or repaired
• Your policy declarations page, showing the deductible and the settlement basis

What the adjuster looks at

An adjuster is not deciding whether your roof is old. They are deciding two things: whether the damage was caused by a peril the policy covers, and whether it happened during the policy period. Everything they do on the roof serves those two questions. They will look for a consistent pattern of damage on the slopes facing the weather, for damage to soft metal that corroborates the story, and for signs that the roof was already failing before the event.

The word that decides most claims is "sudden". Damage that is clearly the result of one event is covered; wear, deterioration, poor maintenance and long-term leaks generally are not, and are usually excluded in so many words.

Actual cash value, replacement cost, and the money held back

Replacement cost, actual cash value, and recoverable depreciation are three terms worth learning before the first phone call. Replacement cost is today’s price for the work. Actual cash value is that price reduced for the years the roof has already served. Recoverable depreciation is the gap between them, which a replacement cost policy will pay once the work is done and documented, and which an actual cash value policy will not pay at all.

Some policies apply a different, harsher schedule to roofs specifically — a roof surfacing payment schedule, or a scheduled roof endorsement — which pays a declining percentage based on the roof’s age regardless of the rest of the policy. If your policy has one, it will be named on the declarations page, and it changes the arithmetic completely.

The deductible, and the thing no honest contractor will offer

Your deductible is your share of the loss, and it is a term of the contract rather than a suggestion. It is worth being blunt about what follows from that: a contractor who offers to waive it, absorb it, discount it, "work with you on it", eat it, or cover it with a rebate or a free upgrade is proposing insurance fraud, and in most states that is a criminal offence for both of you. It is prosecuted in roofing more than in any other trade, precisely because the offer is made so often after storms.

The mechanism is straightforward and so is the illegality: the contractor bills the insurer for the full amount while collecting less than the full amount from you, which means the invoice sent to the insurer is false. The homeowner who agreed to it is a party to that. No amount of friendly framing on a doorstep changes what it is.

The things that turn a claim into a criminal matter

Insurance fraud is not a technicality and it does not require anybody to feel like a criminal while doing it. Adding damage that was already there to a new claim, describing wear as storm damage, allowing an invoice to show a figure that was not actually paid, or accepting a waived deductible are all fraud, and all four are ordinary enough after a storm that homeowners agree to them without recognising what they are agreeing to.

The homeowner is a party to it, not a bystander. The contractor who suggested it will not be the one explaining it later.

Repair, replace, and the matching problem

Insurers pay to restore what was damaged, not to improve the house. So the fight is rarely about whether there is damage; it is about how much of the roof has to come off to fix it. An insurer may scope one slope. A contractor may say the slope cannot be repaired without the replacement being obvious, or that the material is no longer made in that colour, or that repairing into brittle old shingles will damage more than it fixes.

This is the single most common point of disagreement in roof claims, and it is a technical argument rather than a moral one. It is resolved by a contractor and an adjuster looking at the same roof and talking, which is why having your contractor present is worth arranging.

The clock, in both directions

Two clocks run and only one of them is obvious. The visible one is how long the insurer takes: most states set regulatory deadlines for acknowledging a claim, for deciding it, and for paying once it is accepted, and these are usually counted in days rather than months. Your state insurance department publishes the actual numbers, and they are enforceable.

The other clock is yours, and it is the one that ends claims. Policies require prompt notice of a loss and set an outer limit on how long after the event you can report it. Damage discovered late — hail in particular, because it hides — is denied on this basis more often than on any question about the damage itself.

What to do when the answer is no

A denial has to be in writing and it has to give reasons, usually citing the specific policy provision relied on. That letter is the most useful thing in the file, because it tells you exactly what has to be answered. Read it against your policy and identify which of three things has happened: the insurer does not accept the damage exists, does not accept the cause is covered, or does not accept the amount.

Those are three different problems with three different answers, and treating a denial as one undifferentiated "no" is why so many are never successfully challenged.

Mitigation: the step that is required of you

Mitigation is not repair, and the distinction matters. Making the roof watertight for a fortnight is mitigation and should be documented as such. Beginning the permanent repair before the adjuster has seen the damage is not mitigation, and it removes the evidence the claim depends on. If circumstances force a permanent repair immediately, photograph everything exhaustively first and tell the insurer why it could not wait.

Keep any material that was removed if it is practical to do so — a bundle of damaged shingles in the garage has settled more than one disagreement about what the roof was like.

What it comes down to

Document first, make it safe second, report third, and get the scope in writing before anybody starts work. In that order it usually goes smoothly. In any other order it usually does not.