The 5 Insurance Claim Documents Every Roofer Should Nail: Photos, Measurements, Writing

A clean roofing insurance file comes down to five documents: a property and inspection summary, a labeled photo set, defensible measurements, a storm-context record, and a written scope with a communication log. Get those five right and an adjuster can review the claim without calling you back. Get them sloppy and the file stalls, the supplement gets denied, or the homeowner ends up confused about what you actually found.

Here is the short version, because you are busy. Photograph context and detail for every condition you intend to scope. Measure the roof so the numbers match the photos and the estimate. Pull the storm date from a real source and write down what that source actually says, not what you wish it said. Write your scope in plain field language that describes observed conditions and stops short of deciding coverage. Then store the whole thing under the property address so the office, the estimator, and production are reading the same file.

Notice what is missing from that list: any promise about whether the claim gets paid. That is the line good documentation respects. Your job is to make the facts easy to review. Coverage is the carrier's call, and it runs on the policy language, the deductible, the roof's age, and the depreciation math, none of which a contractor controls. The files that win are the ones that show the property and its condition so clearly that the adjuster has nothing to argue with and nothing to guess at.

This is the way a veteran estimator builds a storm file, document by document, with the field detail that keeps it from coming back. It also covers the parts most roofers skip: the matching and code-upgrade rules that change what a fair scope looks like, the difference between an ACV and RCV settlement and why roof age drives it, and the photo and measurement habits that separate a file an adjuster trusts from one they pick apart.

Why documentation is the whole game in restoration work

Retail roofing is simple to document. You measure, you quote, the homeowner says yes or no. Insurance restoration is different. A third party who never saw the roof has to decide, from your file and the carrier's own inspection, what the loss is worth. Every weak spot in your documentation becomes a reason to deny a line item, depreciate harder, or kick the file back for clarification.

The carrier's adjuster is building their own record at the same time. They run their own scope, often in Xactimate, and produce an estimate. When the adjuster's scope and your scope disagree, the file that has photos, measurements, and written notes lined up wins the conversation. The file that is a phone full of unlabeled images loses it, even when the roof is genuinely worn out.

There is a second audience that roofers forget: the homeowner. They are nervous, they do not understand their policy, and they will repeat to the adjuster whatever you told them. If your documents are clear and your language is careful, the homeowner becomes a calm, accurate narrator of the loss. If your documents overpromise, the homeowner expects a check the policy was never going to write, and you own that disappointment.

The carriers themselves have been tightening up. Plenty of homeowners now carry roof coverage on an actual cash value basis instead of replacement cost, especially on older roofs, which means age and depreciation decide a huge share of what gets paid. State legislatures have been busy too: Florida eliminated assignment of benefits for new policies, and several states have put matching requirements into statute. The rules around your documentation move every year. The documents below are built to hold up regardless of which way they move.

The 5 documents at a glance

#	Document	Core question it answers	Worst failure mode
1	Property & inspection summary	What property, what date, who looked, what was and wasn't checked	Photos with no anchor; mixed-up addresses
2	Labeled photo set	Where is each condition and what does it look like up close	Unlabeled close-ups nobody can place
3	Measurements & scope notes	How much roof, which slopes, how many of each component	Estimate covers slopes the photos never show
4	Storm-context record	What event, what date, what the source actually reports	Claiming a storm report "proves" the damage
5	Written scope & comms log	Observed conditions, proposed work, exclusions, who owns next step	Insurance conclusions a contractor isn't qualified to make

Each one stands alone, but they only earn their value together. A photo set with no measurements is a slideshow. Measurements with no photos are unverified numbers. A scope with neither is an opinion. Build all five, keep them consistent, and the file reviews itself.

Document 1: The property and inspection summary

The first page of any storm file should let a stranger identify the job before they see a single shingle. An adjuster opening your packet, an estimator three desks over, or a production manager next spring should never have to infer the address from a photo of a house number.

This is the cheapest document to get right and the one roofers skip most. It takes ninety seconds at the truck and it anchors everything that follows.

Capture all of this:

• Property address, and a job ID if your shop uses one
• Homeowner or site-contact name and best phone
• Inspection date and time
• Inspector name (the person who was actually on the roof)
• Reason for the visit (storm response, homeowner request, follow-up, re-inspection with adjuster)
• Reported loss date, if the homeowner gave one
• Weather at the time of inspection (you do not measure granule loss reliably on a wet roof at dusk)
• Roof areas inspected, slope by slope
• Areas you did not inspect, and why
• Access or safety limits that shaped what you could see

That list of what you did not inspect matters more than it looks. An honest "north slope not accessed, 8/12 pitch, no safe anchor point, ground photos only" protects you twice. It tells the adjuster your scope is built on what you actually observed, and it stops production from being blindsided by a slope nobody walked.

The IRS recordkeeping guidance for small businesses is written for taxes, but the underlying principle fits perfectly: records should support decisions and be easy to retrieve. A storm file living on one salesperson's phone, in a text thread, or in an untagged camera roll is not a documentation system. It is a liability waiting for that phone to break or that rep to quit mid-season.

A summary template you can copy

PROPERTY & INSPECTION SUMMARY
Job ID / Address: ______________________________
Homeowner: ____________  Phone: _______________
Inspection date/time: ___________  Inspector: __________
Reason for visit: _______________________________
Reported loss date (per homeowner): _______________
Weather at inspection: __________________________

SLOPES INSPECTED (walked):  Front [ ] Rear [ ] L [ ] R [ ] ___
SLOPES VIEWED FROM GROUND ONLY: ________________
NOT INSPECTED (reason): _________________________
Access / safety limits: _________________________
Material observed: ____  Approx layers: ____  Penetrations noted: ____

Keep it boring. Boring is retrievable. The moment a denial letter, carrier estimate, or set of adjuster photos shows up months later, you attach them to this record instead of starting a second, conflicting file.

Document 2: The photo set that survives review

Photos are where most roofers think they are strong and are actually weak. The problem is rarely too few photos. It is photos that prove nothing because no one can tell where they were taken or how bad the condition really is.

The fix is a rule every estimator learns early: shoot context, then detail, for every condition you plan to scope. A tight shot of a cracked shingle shows a condition but not a location. A wide shot of a slope shows location but not severity. Pair them, and you have evidence. Use one without the other and you have a question.

Build the set in sequence

Shoot the same way every time so nobody has to think about it on the roof:

1. Property identifier — front elevation with the house visible, the address if it is legible. This is the cover photo that ties the rest to a real address.
2. One wide shot per elevation — all four sides from the ground. Collateral damage on gutters, downspouts, fascia, screens, and AC fins lives here, and collateral is some of the most persuasive evidence you will collect.
3. One wide shot per roof plane — from on the roof or from a ladder at the eave, showing the whole slope.
4. Detail shots tied to a plane — each condition you intend to scope, photographed close, with something in frame that gives location and scale.
5. The interfaces — valleys, ridges, hips, step and headwall flashing, drip edge, pipe boots, vents, and chimney counterflashing. These are where roofs leak and where adjusters look hardest.
6. Interior conditions — active leaks or ceiling stains, photographed and tied to a named room ("rear bedroom ceiling, NE corner").
7. Temporary repairs — before and after the tarp or the patch, every time, no exceptions.
8. The limits — anything you could see but could not safely reach, photographed from where you stood.

Hail and wind get their own discipline

Generic storm photos do not hold up. Hail and wind each leave a signature, and the documentation that survives review captures that signature on purpose.

For hail, the field standard is the test square — a marked 10-by-10-foot, 100-square-foot area where you do a slow up-close inspection and mark what you find. The method traces back to Haag's hail assessment protocol and has been adopted widely enough that a version has circulated through the National Roofing Contractors Association for years. Mark hits with chalk so the camera can see them, circle a representative cluster, and photograph the square wide enough to show the slope and tight enough to show the bruising or granule loss inside the circles. Adjusters run their own test squares; when yours and theirs line up, the conversation is short.

A quick reference for what tends to read as storm-created hail damage on asphalt versus what does not:

Indicator	Reads as hail	Reads as something else
Mat bruise	Soft, round, dark spot; mat fractured under granule loss	Sharp-edged gouge (foot traffic, tool)
Granule loss	Random splatter pattern, fresh black asphalt exposed	Uniform wear along walk paths or shaded slopes
Pattern	Random across slope, density follows storm direction	Lined up with rafters, valleys, or traffic
Collateral	Matching dents on soft metals, screens, vents, gutters	No soft-metal damage anywhere on the property
Directionality	Heavier on slopes facing the storm	Even on all slopes regardless of exposure

For wind, document the failure mode, not the abstraction. Creased shingles, lifted tabs with broken seal strips, fully missing shingles with the nail line exposed, and torn underlayment all tell a wind story when photographed in place against a wide shot. A pile of shingles in the yard means little; a bare nail line on the slope above that pile means a lot.

Label like the file leaves your hands

Assume every photo will be viewed by someone who was not there, because it will. Label by location and condition: "east slope, missing field shingles above valley," "north slope test square, 9 hits in circle," "rear bedroom ceiling stain." File names like 123-main-2026-06-14_eastslope_hail-testsquare.jpg beat IMG_4471.jpg every time, and they survive the trip into a carrier portal that strips your folder structure.

Keeping that structure intact under one property record is exactly the kind of recordkeeping discipline that breaks down during a busy storm week. Contractors who run a property-level system, whether a full operations platform or a targeting tool like RoofPredict that keeps storm date, photos, and the estimate tied to the same address, stop losing photo sets to a rep's camera roll. The point is one file per roof, not five copies in five inboxes.

Keep the timestamps and the metadata

One quiet advantage of phone and drone photos is the embedded metadata: the capture date, and often the GPS coordinates. That timestamp is part of why the photo is believable, because it ties the image to the inspection date in your summary. Two habits protect it. First, do not screenshot photos to share them; a screenshot strips the original capture data and resets the date to the day you took the screenshot, which makes a clean photo look manipulated. Second, when you share into a carrier portal that compresses or re-dates images, keep the originals in your system of record so you can produce the unaltered file if anyone questions timing. Shoot in good light when you can. A test square photographed at dusk under a phone flash hides the exact bruising and granule loss you went up there to show, and a reshoot the next morning costs a second trip. If weather forces a poor-light inspection, note it in the summary and plan the reshoot rather than submitting images that undersell the damage.

One hard line on photos: they show what was visible at inspection. They do not prove causation, coverage, or policy obligation by themselves. Storm history, roof age, prior repairs, installation quality, and the policy terms all sit alongside the photo in deciding a claim. Let the photo do its one job well and do not ask it to carry the whole argument.

Document 3: Measurements and scope notes that hold up

Measurements turn observation into a repair you can price and a number an adjuster can check. They are also where small mistakes turn into big disputes, because the carrier is measuring the same roof and a meaningful gap between your number and theirs reads as either sloppiness or padding.

The industry has standardized hard here. Carriers and adjusters work in Xactimate, and its native ESX file is the format estimates move in. Aerial measurement reports from satellite and drone providers now come tight enough that the working expectation in 2026 is roughly a one-percent margin of error on a measurement report. You do not have to use any one vendor, but you do have to hit that level of precision, because the other side already is.

Capture every dimension that drives scope

• Total roof area, in squares, by slope
• Which slopes or sections are affected versus undamaged
• Predominant pitch per slope (it drives labor, waste, and steep charges)
• Linear footage: ridge, hip, valley, eave, rake, step flashing, headwall, drip edge
• Counted components: pipe boots, box and turbine vents, ridge vent LF, skylights, chimneys, satellite mounts
• Layers present and decking type, where visible
• Stories and access notes that affect labor
• Anything you flagged as "verify at tear-off"

Scope the things adjusters routinely miss

The carrier's first scope is often light, and not always on purpose. Line items get dropped, waste factors come in low, and code-required materials get left out. Your measurement notes are what let you write a defensible supplement later, so capture the supporting items now, while you are on the roof:

• Starter course and ridge cap as separate line items, by LF, not bundled into field shingles
• Ice-and-water shield where code requires it (valleys, eaves, penetrations)
• Drip edge, which code requires on most jobs but legacy scopes omit
• Steep and high charges where pitch and stories trigger them
• Detach-and-reset for solar, satellite, gutters, and HVAC line sets in the work zone
• Proper waste percentage for cut-up roofs, hips, and valleys

None of this is padding. It is the difference between the carrier's opening number and what the job actually costs to build to code. Document the conditions that justify each item and the supplement writes itself.

Measure within your fall-protection limits

Some of these numbers require getting on the roof, and not every roof is safe to walk on the first visit. OSHA's fall-protection rules trigger at six feet in construction, and the agency has specific guidance for residential construction. A steep, wet, or frosted roof with no anchor point is a roof you measure another way. When access is unsafe, say so in the notes, use aerial measurement or ground methods, and mark the affected numbers as preliminary. A measurement is never worth a fall, and a file that says "measured by aerial report, pitch confirmed from ground" is more honest than one that pretends a crew walked a slope they never touched.

Make the numbers match the story

The single best quality check on a measurement set is to lay it next to the photos and the scope. If the photos show damage on two slopes and the estimate prices four, the file must explain why, in writing, before it leaves your office. If decking, ventilation, or layer count cannot be confirmed until tear-off, write exactly that. "Decking condition unknown until tear-off; estimate assumes sound deck, change order if rot found" is the kind of sentence that prevents a fight in week three of the job.

Document 4: The storm-context record

Storm context explains why this inspection is happening. After a hail, wind, tornado, or severe-thunderstorm event, the record should tie the property to a real, dated, sourced event, and stop precisely there.

The authoritative sources are public and free. The NOAA Storm Events Database catalogs events by county and date. The Storm Prediction Center's storm reports log hail and wind reports day by day, including hail size. The National Weather Service severe weather pages give event context and definitions. Pull the event, save the link or report ID, and record what it says.

Capture this:

• Source name (SPC, NOAA Storm Events, local NWS office)
• Source URL or report identifier
• Event date
• Reported hazard and magnitude (e.g., 1.75-inch hail, 70 mph gust)
• Reported location relative to the property
• The homeowner's stated timeline, recorded as their statement
• What your own inspection found, recorded separately

That separation is the whole discipline. A storm report near an address establishes that a hazard occurred in the area on a date. It does not prove that one specific roof was damaged, and it does not decide coverage. Property-level damage is established by inspection and documentation, full stop. Keep the source's claim and your finding as two distinct facts and the record stays defensible.

Wording that holds up	Wording that overreaches
"SPC report logs 1.75-inch hail in the county on 5/14/26; field inspection documented conditions below."	"NOAA proves this roof was destroyed by the May hailstorm."
"Homeowner reports roof was sound before the 5/14 storm; no prior claims known to contractor."	"This is 100% storm damage, no question."
"Hail size reported supports the bruising documented in the test square."	"The storm report means the claim has to be paid."

The right-hand column is how files get flagged and how contractors invite trouble. The left-hand column is how a record stays useful to everyone who reads it.

This is also where roofers who target their outbound by storm exposure have a quiet advantage on accuracy. When the storm date and the affected area are already attached to the property before anyone knocks, the field rep is documenting against a known event instead of guessing. Tools that pair an estimated roof-age range with per-home storm modeling, RoofPredict among them, exist to point a crew at the homes a given storm most likely wore out, so the context record starts from a real event rather than a vague "there was a storm last spring." The inspection still has to confirm it. The targeting just gets the rep to the right roofs with the right date in hand.

Document 5: The written scope and communication log

The written scope is where the inspection becomes a recommendation, and the communication log is where you protect everyone's memory of who said what. Together they are the document most likely to get a contractor in trouble, because this is where the temptation to play insurance adjuster is strongest.

Resist it completely. Your scope describes what you observed and what you propose to do about it. It does not decide coverage, interpret policy language, or promise an outcome.

What the written scope contains

• Observed conditions, slope by slope
• Proposed repair or replacement scope
• Materials and components included, with quantities
• Explicit exclusions
• Unknown conditions that depend on tear-off
• Temporary work already performed
• Safety and access limitations that shaped the scope
• Follow-up tasks and who owns them

Language that describes versus language that decides

Write like an inspector, not like a claims attorney. The pattern is simple: state what you saw, state what you propose, flag what you do not know.

Use language like this:

• "Observed missing field shingles on rear slope above valley; nail line exposed."
• "Estimate includes replacement of damaged pipe boot observed at inspection."
• "Test square on north slope showed bruising consistent with hail; collateral dents on gutter and AC fins documented."
• "Decking condition unknown until tear-off; sound deck assumed."
• "Interior staining at hallway ceiling observed; source not confirmed from roof inspection alone."
• "Storm source included for context only; coverage is the carrier's determination."

Stay away from language like this:

• "Carrier owes a full replacement."
• "This damage is definitely covered."
• "This will get approved."
• "There is no prior damage" — with no prior records to support it.
• "All of this came from the storm" — when causation has not been established.

The first list keeps you in your lane as the contractor who documents the roof. The second list puts you in a lane you are not licensed for and hands the carrier an easy reason to distrust the file.

The communication log

Keep it factual and chronological. Record who said what and who owns the next step:

COMMUNICATION LOG
Date ____  Channel ____  With ____
Summary: ________________________________
Next step: __________  Owner: ____  Due: ____

Example entries:
6/14  Site visit. Homeowner reports leak in rear bedroom after 5/14 storm.
      Inspection completed. Photo set + measurements captured. Estimate to follow.
6/16  Emailed homeowner inspection summary, photos, estimate. Advised policy
      questions go to carrier/agent. Homeowner to schedule adjuster.
6/22  Adjuster inspection scheduled 6/27, 10am. Contractor to attend.

Neutral entries. "Homeowner forwarded carrier estimate and asked contractor to review scope for missing line items" is a useful, true note. "The insurer is wrong and lowballing" is not a field note; it is an opinion that does not belong in the record.

Know where your authority ends

The legal ground under contractor involvement in claims has shifted, and it shifts by state. Florida no longer allows homeowners to assign their insurance benefits to a contractor on policies issued after the reform took effect, which changed how restoration shops there structure their agreements. Many states regulate or prohibit a contractor from negotiating a claim or advertising to "handle the insurance." When the conversation moves from documenting the roof to interpreting the policy, the homeowner should be pointed to their insurer, agent, a licensed public adjuster, or an attorney. The NAIC's consumer resources are a fair, neutral place to send a homeowner who wants to understand their coverage.

If you market documentation help, the FTC's advertising guidance applies. Do not advertise guaranteed approval, guaranteed reimbursement, or a promised outcome. Advertise the real service: thorough inspection records, labeled photos, accurate measurements, a clean written scope, and organized follow-up. That is what you actually deliver, and it is plenty.

The settlement math behind your documentation: ACV, RCV, and roof age

Here is the part that explains why so many well-documented claims still leave homeowners frustrated, and why roof age belongs in your file from the first visit.

Most policies settle a roof claim one of two ways. Replacement cost value (RCV) pays to replace the roof with new materials of like kind and quality, typically in two checks: an initial actual-cash-value payment, then the recoverable depreciation released after the work is done and invoiced. Actual cash value (ACV) pays replacement cost minus depreciation and never releases that depreciation back. On an ACV settlement, the homeowner eats the depreciation plus the deductible out of pocket.

Depreciation is driven mostly by roof age against expected service life. The United Policyholders explainer on ACV versus replacement cost lays out the mechanics, and carriers have been moving older roofs onto ACV-only coverage as roofs cross age thresholds, often somewhere past the ten-to-twenty-year mark depending on material and carrier.

Settlement type	What's paid	Who eats depreciation	Common trigger
RCV	Full replacement cost, depreciation recoverable after completion	Carrier (released on completion)	Newer roofs, RCV endorsement
ACV	Replacement cost minus depreciation, deductible on top	Homeowner	Older roofs, ACV-only schedules

What this means for your documentation is concrete. A roof's age and visible condition are facts you should record at inspection, because they shape the settlement the homeowner can realistically expect. You do not certify remaining roof life; that is not your role, and no contractor should pretend to. But noting an approximate age range and the condition you observed lets you set honest expectations instead of selling a homeowner on a replacement check the policy was never going to fully fund.

This is also where targeting before the knock pays off. A roof you can already estimate as eight to twelve years old is a very different sales and documentation conversation than one that is likely past twenty and headed for an ACV settlement. Knowing the likely age range house by house, the core of what a tool like RoofPredict provides alongside its storm modeling, helps a rep walk up already understanding which homes are worth a thorough inspection and which conversation the homeowner is about to have with their carrier. The age estimate is a planning range, not an exact date, and the roof still has to be inspected. It just keeps the crew from wasting a documentation push on a roof that was clearly re-done last year, and keeps them from overpromising on one that depreciation is going to gut.

Matching and code-upgrade: the rules that change a fair scope

Two legal concepts quietly decide whether your scope is complete, and most field reps cannot explain either one. Learn them, because they change what "the right scope" even means.

Matching

When storm-damaged materials are replaced and the new materials will not reasonably match the surrounding undamaged roof, matching coverage can require the carrier to pay to replace enough of the roof to achieve a reasonably uniform appearance. Whether and how strongly this applies depends on the state and the policy. As of this writing, roughly thirteen states have codified matching requirements into statute or regulation. Your role is not to argue the law; it is to document the condition that makes matching relevant. Photograph the existing material, note the manufacturer and product line if you can read it, and document discontinued or weathered colors that a partial repair would leave mismatched. That documentation is what a homeowner or their public adjuster needs to even raise the issue.

Ordinance or law (code upgrade)

When a covered loss forces a repair, current building code often requires work the old roof never had: ice-and-water shield, drip edge, updated ventilation, additional fasteners, sometimes a full deck upgrade. Ordinance or law coverage, where the policy includes it, helps pay for bringing the structure up to current code during a covered repair. Regulators have been active here. The Oklahoma Insurance Department issued a 2025 notice directing carriers that code-upgrade coverage must be honored even where local officials do not strictly enforce every code provision. Some states now require carriers to offer endorsements to upgrade to fortified-roof standards on replacement.

What you document: the code-required items your jurisdiction enforces, with reference to the applicable code edition, so the supplement for ice-and-water, drip edge, and ventilation is supported by code rather than presented as a contractor preference. The International Residential Code is the base most jurisdictions adopt with local amendments; cite the version your area enforces.

File naming, storage, and privacy

A documentation system dies when files cannot be found. Pick one naming convention and make everyone use it.

A structure that works:

[address-or-jobID]_[date]_[doctype]_[area-or-topic]

So 123-main-st_2026-06-14_photos_east-slope-hail beats new folder final (2) in every way that matters. The date stays sortable in YYYY-MM-DD form, the doctype lets you filter to just photos or just measurements, and the area tells you what is inside without opening it.

Storage and access deserve real rules, because storm files hold sensitive material: home addresses, phone numbers, interior photos, policy documents, adjuster reports, and homeowner statements. Set them once:

Rule	Default that works
Where files live	The company system of record, not personal phones
Who can edit	Estimators and the assigned PM
Who can export	Office manager and owner
How customer docs are shared	Secure portal or email, never group texts
When records archive	Per your retention policy, after job close + warranty window
Marketing reuse	Written permission first; strip address, plate, and interior detail

That last row catches a lot of shops. A photo collected for a claim is not automatically a marketing asset. Before a before-and-after goes on social media, get permission and scrub the private details. The FTC's guidance on disclosures in digital advertising is a reasonable backstop on handling customer information and claims in marketing carefully.

The pre-send quality check

Before any file goes to a homeowner, an adjuster, or into production, run it past one short gate. If any answer is no, fix it before the file moves.

PRE-SEND QUALITY CHECK
[ ] Property identity is unmistakable (address + cover photo)
[ ] Inspection date and inspector are recorded
[ ] Every scoped condition has a wide + detail photo
[ ] Hail documented with a chalked test square; wind shows failure mode
[ ] Measurements match the photographed slopes
[ ] Supplement-supporting items captured (starter, ridge, I&W, drip edge, steep)
[ ] Storm source saved with URL/report ID and date
[ ] Homeowner statements are separated from contractor observations
[ ] Safety / access limits are listed; preliminary numbers flagged
[ ] No coverage conclusions in the contractor's writing
[ ] Roof age range + condition noted for expectation-setting
[ ] File stored under the right property record with correct naming
[ ] Next task is assigned with an owner and a date

Rework before the file ships is cheap. Rework after it is in a carrier portal, quoted to a homeowner, or handed to a crew is expensive and embarrassing. Spend the two minutes.

Common mistakes that sink restoration files

After enough storm seasons, the same handful of failures show up again and again. Each one is avoidable.

• Close-ups with no context. A bruised shingle nobody can place on the roof proves nothing. Always pair detail with a wide shot.
• Skipping collateral. Dented gutters, screens, AC fins, and soft-metal vents are some of your best hail evidence, and they sit at ground level where they are easy to shoot. Reps who only photograph the field shingles leave the strongest evidence on the table.
• Measurements that do not match the photos. A four-slope estimate over a two-slope photo set reads as padding, even when it is an honest oversight.
• Treating a storm report as proof of damage. It is context, not a verdict. Inspection establishes property-level damage.
• Playing adjuster. "This is covered, this will get approved" is outside the contractor's role and outside many states' law. Document; do not adjudicate.
• Ignoring matching and code-upgrade. A scope that omits code-required drip edge or ignores a discontinued shingle color is an incomplete scope, and the homeowner pays for the gap.
• No record of what was not inspected. Unwalked slopes that surface during the job blow up your schedule and your credibility.
• Selling a replacement check on an ACV roof. Overpromising on an old roof headed for a depreciated settlement burns the relationship the moment the carrier's number lands.
• The phone as the filing system. One broken phone or one departed rep, and the file is gone.

What to ask and confirm before the file is final

A short set of questions, asked at the right moment, closes most of the gaps above. Walk through them before you call a file done.

• Does the homeowner know their settlement basis, ACV or RCV, and roughly what that means for their out-of-pocket?
• Is the loss date the homeowner gave consistent with the storm source on record?
• Were all the slopes in the estimate actually inspected, or are some priced from the ground? Is that flagged?
• Are the supplement-supporting items documented now, while access is easy, instead of discovered later?
• Does the state where this roof sits restrict contractor involvement in the claim, and is the agreement structured accordingly?
• Is there any prior claim or prior repair the homeowner is aware of, recorded as their statement?
• Has the homeowner been told, in writing, that coverage questions go to the carrier, agent, or a public adjuster?

None of these slows a clean file down. They keep a messy one from reaching the carrier.

Training the crew so the standard survives storm season

Documentation quality is a habit, and habits drift under pressure. The week the hail hits is exactly when shortcuts creep in, so the standard has to be trained, modeled, and reviewed rather than written down once and forgotten.

Train the crew on the things that actually go wrong:

• The photo sequence, shot the same way on every roof
• How to run and photograph a test square
• How to label by location and condition
• The measurement standard and the supplement-supporting items to capture
• How to write an observed condition without writing a coverage conclusion
• How to record an unknown condition honestly
• How to document a safety or access limit
• How to upload the full file before leaving the job

Then review. Pull a sample of files each week during season and look for the usual failures: unlabeled photos, mismatched measurements, vague scope language, coverage conclusions that should not be there. When the same miss shows up twice, fix the checklist or retrain instead of sighing about it. One clean, retrievable file is worth more than a fat folder nobody can parse, and the crew learns fastest when a manager walks them through a real file that reviewed cleanly and a real file that came back, side by side.

Give the standard an owner. Without one person responsible for the templates, the file reviews, and the naming convention, the whole system erodes the first busy week. The owner keeps the checklist aligned with how crews actually work, updates it when the law or the carriers move, and makes sure new estimators study strong example files before they ever write a customer-facing report.

That ownership is what keeps documentation quality from depending on memory during the exact weeks when memory fails. Build the five documents the same way every time, keep them consistent with each other, store them under one property record, and the file does its job: it makes the facts easy to review and keeps the contractor squarely in the contractor's lane.

Sources checked: June 18, 2026.

FAQ

What documents does a roofer need for an insurance claim inspection?

Five core documents carry a storm file: a property and inspection summary that identifies the job and what was and wasn't inspected; a labeled photo set pairing wide context shots with close-up detail for every scoped condition; measurements and scope notes precise enough to match an adjuster's Xactimate estimate; a storm-context record citing a real dated source; and a written scope with a communication log. Together they let an adjuster review the loss without calling you back for clarification.

Do photos prove a roof insurance claim should be paid?

No. Photos document conditions that were visible at inspection, but they do not decide coverage. Causation, the roof's age, prior repairs, the deductible, and the specific policy language all factor into a carrier's decision, and none of those live in a single photo. Strong photos make the facts easy to review and hard to argue with, which is the contractor's actual job. Coverage determinations belong to the homeowner's insurer, agent, a licensed public adjuster, or an attorney.

How do you document hail damage so it survives adjuster review?

Use a test square, a marked 100-square-foot area where you inspect up close and chalk the hits, then photograph it wide enough to show the slope and tight enough to show bruising and granule loss inside the circles. This method, traceable to Haag's hail protocol, is what adjusters run too, so matching squares shorten the conversation. Back it with collateral evidence: matching dents on gutters, screens, vents, and AC fins prove a hail event better than the field shingles alone.

How precise do roof measurements need to be for an insurance estimate?

Tight. Carriers and adjusters work in Xactimate, and aerial measurement reports in 2026 are expected to land around a one-percent margin of error, so a loose number reads as either sloppiness or padding next to theirs. Capture area by slope in squares, pitch per slope, and linear footage for ridge, hip, valley, eave, rake, and flashing, plus counted components like pipe boots and vents. Note anything measured from the ground rather than walked, and flag it as preliminary.

Why does roof age matter so much to an insurance claim?

Roof age drives depreciation, and depreciation drives the settlement. On a replacement-cost policy the carrier eventually pays full replacement, releasing depreciation after the work is done. On an actual-cash-value settlement, common on older roofs, the homeowner eats the depreciation plus the deductible out of pocket. Many carriers now move roofs onto ACV-only coverage past a certain age. Noting an approximate age range at inspection lets a contractor set honest expectations instead of overpromising a replacement check.

Can a contractor negotiate or handle the insurance claim for a homeowner?

It depends heavily on the state, and the rules have tightened. Florida eliminated assignment of benefits for new policies, and many states restrict or prohibit a contractor from negotiating a claim or advertising to handle the insurance. The safe lane is documentation: inspect the roof, photograph it, measure it, write a factual scope, and point coverage questions to the carrier, agent, a licensed public adjuster, or an attorney. Structure your homeowner agreement to match your state's current law.

What is matching coverage and why should I document for it?

Matching coverage is the principle that when damaged roofing is replaced and the new material won't reasonably match the surrounding undamaged roof, the carrier may owe enough replacement to restore a uniform appearance. Roughly thirteen states have codified it. A contractor's role isn't to argue the law but to document the condition: photograph the existing material, note the manufacturer and product line, and record discontinued or weathered colors that a partial repair would leave visibly mismatched.

What line items do adjusters commonly miss on a roof scope?

Opening carrier scopes often omit starter course and ridge cap as separate items, code-required ice-and-water shield and drip edge, proper waste percentages on cut-up roofs, steep and high charges, and detach-and-reset for solar, satellite, gutters, and HVAC in the work zone. Capture the conditions that justify each item while you're on the roof so a later supplement is supported by documented fact and applicable code rather than presented as contractor preference. Cite the code edition your jurisdiction enforces.

How should storm files be named and stored?

Use one consistent convention everyone follows, such as address or job ID, then a YYYY-MM-DD date, then document type and area, so files stay sortable and findable. Store them in the company system of record, not on personal phones, and limit who can edit and export. Storm files hold addresses, phone numbers, interior photos, and policy documents, so share through a secure channel, not group texts, and get written permission before reusing any photo for marketing.