ScopeQueue Carrier estimate in, justified supplement package out.

Roof Decking: The Most-Denied Line You Write, and the Photo That Denies It

You already know how this one goes. You tear off, you find five bad sheets, you shoot them, you send them in. The response says the deterioration is pre-existing and excluded.

Here is the part worth your morning: on this line, the photo you took to prove the item is frequently the photo the carrier uses to deny it. That is not bad luck. It is built into how the item works.

Why decking behaves differently from every other line you supplement

Three things stack against it, and they stack every single time.

Timing. The adjuster inspected a roof with shingles on it. Deck condition is discovered after tear-off, by definition. So you are asking someone to pay for a condition their inspector never saw and can no longer see, because it left in a dumpster.

Vocabulary. The words you reach for first — rotted, decayed, deteriorated, worn — are the words the usual exclusion language is built around. Whatever the specific form on this claim says, when your own note supplies those words, the denial comes back in your handwriting. Write what you can actually see instead: fractured, punctured, delaminated, fastener pulled through, panel edge lifted.

Evidence. A photo of bare deck shows a condition. It does not show a cause and it does not show a date. Punky sheathing looks the same in week one as in year twelve. Nothing in that frame says which.

Put those together and the denial writes itself — and it is defensible from their side. More words on the same evidence do not add evidence. The evidence is the problem.

Change one habit tomorrow: shoot before, not only after

One rule fixes most of this. Every deck photo needs a partner taken before tear-off, from the same slope and the same position.

The pairing is the argument

What separates an event from age is not the deck photo alone. It is the relationship between the top-side photo and the deck photo at the same coordinates. Deck damage directly beneath a documented wind-creased area, a missing tab section, or a punctured underlayment reads as event-related. The same defect sitting alone next to a plumbing boot reads as a chronic leak, which reads as maintenance.

Shoot the top side first. Then open exactly there. Then shoot again.

Wide, medium, close — in that order, in one walk

A close-up of splintered sheathing with nothing else in frame is unlocatable. It could be any roof, any slope, any year. Every close-up needs a parent wide shot from the same walk so it inherits a location. A reviewer who cannot place a photo on the roof cannot verify anything that is in it.

Chalk the roof before you open it

Grid the slopes with chalk, photograph the grid, then work. Now every later frame has an address instead of a description.

Get underneath while the roof is still intact

Where there is attic access, shoot the deck from below before anything comes off — ideally before the adjuster's inspection. That is the only look at deck condition that exists while the covering is still on. Daylight through a joint, fresh wet sheathing in one rafter bay, staining confined to a specific location: dated, located, and taken before there was any tear-off to argue about.

What actually reads as event damage

No photo forces an outcome. But this is the distinction an experienced reviewer is looking for, and most crews shoot right past it.

Both can be present on the same roof. Say so. Claiming every bad sheet as storm damage when your own photos show three of them chronic hands the reviewer a reason to re-check everything else in the packet. Separate them yourself: these panels tie to documented impact, these are noted as pre-existing and not claimed. That costs you a few sheets and leaves the rest standing on its own.

Quantity: count panels, do not estimate area

Re-nailing is a different line and a different argument

This is where good decking supplements die.

Re-nailing to code is not damage. The panels are sound. You are adding fasteners to undamaged decking because the jurisdiction requires it once the covering is off. File that inside your storm-damage argument and it gets denied as not damaged — correctly — and that denial colors how the reviewer reads the sheets that genuinely were damaged.

Re-nailing belongs under code upgrade, which is where ordinance and law questions live. That is a coverage question, not a roofing question. You state the code requirement and the inspection reality. You do not interpret the policy, you do not tell the homeowner what their coverage includes, and you do not predict what gets paid. Point them at their carrier and their own documents.

Florida is the clearest statewide example. The wind-mitigation reroofing provisions of the Florida Building Code, Residential reach existing wood roof decks when the covering is removed and replaced: deck attachment has to be brought up to the fastening schedule the code specifies, and the same reroofing run — R908.7.2 — calls for a secondary water barrier, with exceptions written into the section itself. That barrier goes onto your panels and their joints, so it moves with any decking you replace. Pull the edition your jurisdiction currently enforces before you cite either one in a supplement.

Everywhere else, assume nothing. Some jurisdictions require re-nailing by local amendment; many do not. Your exhibit is the code edition your authority having jurisdiction actually adopted, any local amendment, that office's own reroofing handout, plus your permit and inspection record. A jurisdiction's published handout is a document the reviewer can pull up and read. A sentence beginning "code requires" is not.

Four separate triggers — keep them apart

  1. Deterioration: the panel no longer holds a fastener.
  2. Delamination: plies separated. Not a fastening surface even when it looks flat from above.
  3. Spacing and gaps: spaced boards or skip sheathing under asphalt shingles. Whether the existing boards can be covered as they are or need an overlay panel first comes out of your adopted code and the shingle manufacturer's installation instructions — read both for this jurisdiction instead of carrying a rule of thumb over from the last one.
  4. Thickness and span: required panel thickness is tied to framing spacing in the tables your jurisdiction adopted. A deck thinner than the adopted requirement is a code issue, not storm damage.

Only the first — and part of the second — belong in your storm-damage section. Three and four are code arguments and go in the code section with code evidence. Merging all four into one paragraph gives the reviewer a single sentence to deny instead of four items to evaluate separately.

What rides on top of new decking

Replacing a panel consumes whatever was over it. Underlayment, the ice barrier where your jurisdiction's table calls for one, valley lining, and the drip edge along eave and rake if the replacement reaches the perimeter. In the base IRC the ice barrier is R905.1.2, valley lining is R905.2.8.2, and drip edge is R905.2.8.5; underlayment carries its own section in the same run. The ice-barrier trigger is keyed to your jurisdiction's entry in the R301.2 climatic and geographic design criteria table — not to an adjuster's read of last winter.

Write it as "[your state] adopted the [year] edition, amended as follows" rather than "the IRC says." States adopt specific editions and amend them, and section numbers move between editions, so cite the one your jurisdiction is actually enforcing. Drip edge has its own denial pattern, covered here: the drip edge supplement. The broader item list and the standard denial language sit here: supplement items and why they get denied.

The packet

None of this makes the packet longer. It makes it earlier. Decking is the one line where the evidence has to exist before the work starts, which means the fix is not a better document — it is what your crew does in the first twenty minutes on the roof tomorrow.

This is general information for contractors, not legal advice and not insurance advice. Code adoption, amendments, and inspection practice vary by state and by jurisdiction — verify current requirements with your authority having jurisdiction. Nothing here interprets any insurance policy or predicts the outcome of any claim.

This is what ScopeQueue does with a file

You can work through all of this by hand, and plenty of good contractors do. ScopeQueue reads the carrier estimate and your photographs and drafts the same file for you to check — with the reason written under each item, and the code section left blank wherever it cannot be verified.

Try it on one file — free

More