Roof Insurance Supplement Checklist for Small Roofing Contractors

When a roof supplement gets pushed back, the problem is often not the existence of the missing scope. The problem is the way the request is packaged.

Small insurance-restoration roofing contractors do not have time for endless back-and-forth with carriers. But they also cannot afford to send a supplement packet that reads like a loose collection of photos, notes, and line items. A supplement has to function as a review package: clear, bounded, and easy to verify.

This checklist is designed to help contractors and estimators tighten that package before submission.

1. Confirm that the supplement stays inside the actual roof scope

Before you add a single line item, define the boundary.

• Is this item part of the originally submitted roof job?
• Was it visible in the original evidence set, or only discovered later?
• Does this belong in a revision, or is it actually a new claim issue?

One of the fastest ways to create friction is to mix original scope, newly discovered scope, and adjacent non-roof items into one request. A reviewer who cannot tell where the boundary is will slow down immediately.

2. Make the quantity source obvious

Every disputed line item should have a quantity trail.

• Perimeter-based accessory quantities tied to the measurement report
• Ridge or hip cap footage reconciled against the carrier estimate and the uploaded roof report
• Haul-off tied to tear-off volume and the number of mobilizations
• Starter or drip edge quantities tied to eaves or rakes instead of a free-floating lump number

If the number feels detached from a source, the line item becomes much easier to challenge.

3. Anchor each important request to a photo callout

Bulk photo dumps create work for the reviewer. A better approach is to identify the exact image or marked callout that supports the request.

• What condition is visible
• Where it is located
• How that condition connects to the requested line item

4. Separate code support from policy assumptions

A common supplement mistake is treating “code-required” as if it automatically means “carrier-approved.” Those are different questions.

• The code family or municipal source being relied on
• The edition or adoption year where applicable
• The jurisdiction or municipality the note applies to
• A short explanation of how the requirement ties to the requested scope

The tighter and more edition-specific the note is, the more credible it feels.

5. Show the narrowest defensible explanation

The best supplement packets do not sound argumentative. They sound documented.

• What is missing
• What evidence supports it
• Why it belongs inside the submitted roof scope

6. Double-check disposal, permit, and edge-case math

• The requested amount is tied to a visible logic path
• The jurisdiction path has been checked where applicable
• The math is consistent with the size and complexity of the roof
• The request is not duplicative of another line item or allowance

7. Review the packet as if you were seeing it cold

If someone unfamiliar with this job opened this packet for the first time, could they understand the request quickly? If the answer is no, simplify.

A roof supplement should not require trust as its main support. It should require verification. If you want to see how PactPack structures line-item support, annotated photo callouts, coverage gating, and revision boundaries, review the public sample pack, coverage page, and pricing details before you buy anything.