How to Document Wind Damage to Shingles for an Insurance Estimate (Field Workflow for Roofers)

The difference between a wind claim that gets paid and one that gets denied usually has nothing to do with how bad the roof actually is. It comes down to whether the damage was documented in a way an adjuster can verify, defend to their own desk reviewer, and tie to a covered cause of loss on a specific date. A roof can be genuinely wrecked by a 70 mph gust line and still get a denial letter if the photos are blurry, the date of loss is fuzzy, and the report reads like a sales pitch instead of an inspection.

This is the part of storm restoration that separates crews who close consistently from crews who chase. The inspection isn't where you find damage to sell. It's where you build a record. The estimate that comes out the other end is only as strong as the field documentation underneath it, and most of the documentation problems are created in the first twenty minutes on a roof, long before anyone opens estimating software.

What follows is the workflow I'd hand a new field rep on day one: how to read a roof for wind, what photos actually carry weight, how to cut and document a test square, how to separate wind damage from age and manufacturing defects, and how to assemble all of it into a report an adjuster can approve without a fight. It assumes you already know how to walk a roof safely. It assumes nothing about how well you document one.

Why wind documentation is its own discipline

Hail gets most of the attention in storm restoration, and it's the easier loss to document because it tends to leave a uniform, random, scattered pattern across the field, and because there are established protocols for it. Wind is messier. Wind damage to shingles is directional, it concentrates on specific slopes and edges, and a lot of what it does is invisible from the ground and even from a casual roof walk. The single most missed wind defect in the field is a sealed-down shingle that has been broken free at the adhesive strip but hasn't blown off yet. It looks fine. It is not fine.

Adjusters know this, which is why they scrutinize wind claims harder for two specific things: cause and date. "Cause" means proving the shingle failed because of wind rather than because it was 22 years old and brittle. "Date" means tying the damage to a specific covered weather event, because a homeowner's policy covers a sudden loss on a date, not gradual deterioration over a decade. Your documentation has to answer both questions before anyone even gets to scope and price. If your photos prove damage but can't speak to cause and date, you've documented a maintenance problem, not a claim.

That framing should drive everything you do on the roof. Every photo, every measurement, every note is evidence for one of three propositions:

1. The shingles are physically damaged in a way consistent with wind (creasing, tearing, missing tabs, broken seals).
2. The damage pattern matches wind behavior, not age or defect (directional, edge-concentrated, on the windward and leeward slopes a storm would actually hit).
3. The damage is recent and consistent with a known weather event on a specific date.

Keep those three jobs in your head and the inspection organizes itself.

Before you climb: the desk work that wins half the case

The strongest wind files are half-built before anyone gets on a ladder. The pre-inspection desk work establishes the date of loss and the plausibility of the cause, and it does it with third-party data the adjuster's own carrier respects. Skip it and you're asking the adjuster to take your word for the storm.

Pull the weather history for the address

You need a defensible answer to "what storm, what day, how strong." The free, citable sources:

• NWS Storm Events Database and local National Weather Service event summaries for confirmed wind events, gust reports, and damage surveys in that county.
• NOAA Storm Prediction Center storm reports for daily logs of measured wind gusts and damage reports by location.
• Local airport METAR/ASOS observations for peak gust readings near the property on the date in question.

What you're building is a one-page weather summary: date of loss, nearest confirmed gust speed, the source, and the distance from that observation to the property. A line like "NWS confirmed 68 mph thunderstorm wind gusts in [county] on [date], measured 4.2 miles from the property" does more to anchor a claim than a dozen roof photos. Get the homeowner to confirm they first noticed the problem after that date, and note it.

Know the shingle's wind rating and what it means

Asphalt shingles carry a wind-resistance rating from ASTM D7158 (Class D, G, or H, corresponding roughly to 90, 120, and 150 mph) or the older ASTM D3161. A Class D shingle rated to 90 mph that fails in a confirmed 70 mph event is a stronger story than a 150 mph shingle that failed at 70, where you'd expect an installation or product defect angle instead. The rating is a lab number under ideal install conditions, not a guarantee, and you should never present it as one, but knowing it tells you whether the failure is plausible for the wind speed on record. It also tells you when to look harder at installation, because a properly nailed, properly sealed shingle shouldn't lose its seal at half its rated speed.

Pull the manufacturer's wind warranty and install requirements

Every shingle line has published installation requirements, nailing patterns, and high-wind application instructions. These matter because adjusters and their re-inspectors will sometimes argue a shingle blew off because it was nailed wrong, which would shift the loss from a covered wind event to an excluded workmanship issue. If you can show correct nail placement in your tear-off or test-square photos, you close that door before it opens.

Establish a roof-age range, honestly

Age is the hinge of every wind claim because the carrier's whole denial strategy on a borderline roof is "this is old and worn, not storm-damaged." You need a defensible estimate of how old the roof actually is. Permit records, the homeowner's recollection, prior real-estate listings, and the physical condition of the shingles all feed into a range rather than a precise date. Be careful here: you cannot manufacture a date you don't have, and you should never present an estimated age as a confirmed installation date. A roof that's plausibly 8 to 12 years old with a confirmed wind event is a clean story. A roof that's plausibly 20 to 25 years old needs your documentation to work much harder to separate storm damage from end-of-life curl and brittleness, and sometimes the honest answer is that it can't be separated, which is a conversation to have with the homeowner before you waste a day building a file that won't hold.

The ground inspection: don't waste it

Most reps treat the ground walk as a formality before the real inspection on the roof. It's not. The ground is where you catch the evidence that's hardest to fake and easiest to lose: blown-off shingles in the yard, debris in the gutters, damage to soft metals and accessories that corroborates wind, and the directional story of the whole property.

Walk the full perimeter and shoot:

• Shingle debris on the ground and in gutters. Loose granules, tab fragments, and whole shingles in the yard or flowerbeds are your most direct corroboration. Photograph them where they lie, then photograph them next to the slope they came from.
• Collateral wind damage. Bent or detached gutters, displaced ridge caps visible from below, damaged fascia, a leaning fence, lost fence boards, downed limbs, damaged screens or soft metal on vents. Collateral damage on the same azimuth as the roof damage builds the directional case that this was wind, not wear.
• The neighborhood. If three roofs on the same side of the street show tarps or missing shingles, that's a storm pattern, and it's worth a wide establishing shot. Adjusters work whole neighborhoods after a storm; consistency helps you.
• Each elevation, full and labeled. One clear photo of each side of the house (front/north, right/east, etc.) so the file shows the roof in context and a reviewer can orient every close-up later.

Note wind direction. The damage should concentrate where the wind hit. If your documented gust came out of the southwest, expect the worst on the southwest-facing slopes and the leeward edges where uplift peels tabs back. Damage that ignores the storm's direction invites the question your file exists to answer.

On the roof: how to actually read wind damage

Now the roof. Safety first and always: tie off where you can, respect the OSHA fall-protection threshold, stay off wet or frosted slopes, and never put a rep on a roof that's too steep or too far gone to walk. A roof you can't safely walk gets documented from a drone or a ladder at the eave, and that's a legitimate method, not a cop-out.

Wind does a handful of distinct things to asphalt shingles. Learn to recognize each because they get scoped differently and they make different arguments to an adjuster.

Creasing (the one everyone misses)

The most important and most overlooked wind defect is creasing. When wind lifts a shingle and folds it back, the asphalt mat creases along the fold line. The wind passes, the shingle lays back down, and from above it looks normal. But the mat is cracked through at the crease, the protective granules have fractured off along the line, and that shingle is now a leak waiting for the next rain. Creases are usually horizontal, running across the shingle, and they show as a line of disturbed or missing granules with a visible fold mark.

To find them you have to lift and inspect rather than only look from above. Run your hand or a flat tool under the leading edge of shingles on the windward slopes and the field, and bend them gently back to the angle the wind would have folded them. A creased shingle will show the crack; an undamaged one flexes and returns. Photograph the crease with the shingle in the folded position so the fracture is visible, then again laying flat to show how invisible it is from above. That pairing, hidden-then-revealed, is some of the most persuasive documentation you'll capture, because it shows the adjuster exactly what they'd miss on a fast walk.

Broken or compromised seal strips

Shingles seal to the course below via a thermally activated adhesive strip. Wind breaks that bond. A shingle with a broken seal isn't visibly damaged, but it's no longer wind-resistant and will progressively fail. Test it by lifting the tab: a properly sealed shingle resists and tears the mat slightly when you pull; an unsealed one lifts freely with no resistance. Document broken seals by lifting the tab and photographing the clean, unsealed underside, ideally with the surrounding sealed shingles for contrast. This is the defect adjusters most often dispute ("it was never sealed" or "it's just hot and re-sealed"), so the comparison shot matters.

Torn, missing, and displaced tabs

The obvious stuff: shingles partially torn, tabs missing entirely, shingles shifted out of alignment. Photograph missing tabs with a measuring tape or ruler in frame, capture the exposed underlayment or felt, and note whether the nails are still in place (nails present with the shingle gone says the tab tore off under uplift, which is a clean wind story; the whole shingle gone with nails pulled is a different and sometimes weaker argument that points at fastening).

Granule loss along stress lines

Wind-driven movement and folding strip granules along specific lines, not the uniform thinning you'd see from age. Concentrated granule loss along a crease or a wind-flexed edge is wind; broad even thinning across whole slopes is wear. Knowing the difference is how you avoid building a claim on an age problem.

What is NOT wind damage

Be honest about this on the roof, because an adjuster will be honest about it in the report, and a file that claims clearly-not-wind defects as wind loses credibility on the legitimate ones. Common non-wind conditions:

• Thermal cracking / age curling: shingles cupping or curling at the edges from age and heat, cracking in random craze patterns rather than clean fold lines.
• Manufacturing defects: blistering, factory edge defects, racking/install pattern problems. These may be a manufacturer warranty claim, not a wind claim.
• Mechanical damage: foot traffic, satellite-dish or HVAC-tech damage, tree-branch abrasion. Real damage, wrong cause of loss.
• Improper installation: high nails, exposed nails, insufficient nailing. This is a workmanship issue that can actually be used against your wind claim, so document correct nailing where it exists and be straight about where it doesn't.

Calling a defect correctly is what makes an adjuster trust the rest of your file. Reps who flag the non-wind conditions themselves get the benefit of the doubt on the close calls.

The test square: the centerpiece of credible documentation

The test square is the single most powerful piece of wind documentation you can produce, and most reps either skip it or do it sloppily. A test square is a marked-off representative area of a slope where you systematically document every defect within a known area, which lets you (and the adjuster) extrapolate damage density to the whole slope. It's the same logic adjusters use for hail, and applying it to wind reads as professional.

How to set and document a test square

1. Pick a representative area on the most-damaged slope, typically a 10 ft by 10 ft (100 sq ft) square, away from edges and penetrations unless edge behavior is the point. Mark the corners with chalk so they're visible in photos.
2. Photograph the empty square first, wide, with the chalk corners visible, so the area is established before you start marking defects.
3. Work the square methodically, lifting and checking every shingle in it. Mark each defect with chalk, a creasing crease with a line, a broken seal with a circle, missing tabs with an X, whatever system you use consistently. Consistency matters because the photos have to be self-explanatory to someone who wasn't there.
4. Photograph the marked square wide so the density of marks is visible at a glance, then shoot each individual defect close-up.
5. Count and record: number of creased shingles, broken seals, missing tabs, etc., within the square. "14 wind-creased shingles and 9 broken seals in a representative 100 sq ft test square on the SW slope" is a number an adjuster can work with.
6. Repeat on a second slope for contrast, ideally a slope the storm wouldn't have hit as hard, to show the directional gradient. A SW slope with 14 defects and a NE slope with 1 is the directional wind story told in numbers.

The test square does something subtle and important: it turns your inspection from "trust me, it's bad" into a sampled, countable, repeatable measurement. When the carrier sends a re-inspector, your marked squares are still on the roof for them to verify, which makes your file harder to wave off.

The repairability question (and why it belongs in your documentation)

At some point the conversation turns to repair versus replace, and your documentation should set that up rather than argue it. The relevant, defensible facts to capture: whether matching shingles are still available (discontinued color/profile is a documentable fact, photograph the existing shingle and note the line if you can identify it), whether the shingles are brittle enough that adjacent tabs break during a repair attempt (document a careful test lift that fractures neighboring shingles), and whether the damage is confined to a slope or spread across the roof. You document the conditions. You do not promise an outcome, declare the roof a total, or tell the homeowner what the carrier will pay. The adjuster scopes and the carrier decides; your job is to make sure they're deciding with complete, accurate information.

Photography that holds up: the standard, not the suggestion

The gap between a file that gets paid and one that gets questioned is usually photo quality and organization. Adjusters review dozens of files; yours has to be legible at speed and verifiable on challenge. The standard:

• Establishing-to-detail sequence for every defect. Wide shot showing the defect's location on the slope, medium shot, then tight close-up. A close-up with no context shot is an orphan; a reviewer can't place it, so they can discount it.
• Scale in frame. A tape measure, a ruler, or a coin in the close-ups so size and severity are objective, not implied.
• Geotag and timestamp on. Photos with embedded date, time, and GPS are dramatically harder to dispute and directly support your date-of-loss argument. Use a documentation app that locks EXIF metadata. Never alter a photo; a single edited image can taint the whole file.
• Slope labeling. Every photo tied to a slope (front/north, etc.) so the file maps to the diagram.
• The pairing shots. Hidden-then-revealed for creasing; sealed-vs-unsealed for seal failures; damaged-slope-vs-protected-slope for direction. Pairings make arguments single photos can't.
• Enough volume, not too much. A thorough wind file commonly runs many dozens of photos. But 200 redundant blurry shots is worse than 60 clean labeled ones; volume without organization reads as noise and buries your best evidence.

A quick field checklist for photo coverage:

• All four elevations from the ground, labeled
• Ground/gutter debris where it lies
• Collateral wind damage (gutters, fence, vents, neighbors)
• Each roof slope, wide
• Test square: empty, marked-wide, each defect close-up with scale
• Creasing pairs (folded-revealed + flat-hidden)
• Seal failures (lifted tab, with sealed-shingle contrast)
• Missing/torn tabs with scale and nail condition
• Penetrations, flashing, ridge, hip, eave/rake edges
• Any non-wind conditions, honestly captured

Measuring and diagramming for the estimate

Documentation and the estimate meet at the measurements. The adjuster's scope and your estimate both run on accurate slope-by-slope areas, pitches, and linear footage of edges, ridges, hips, and valleys. Whether you measure by hand, by aerial measurement report, or by drone, the deliverable is the same: a labeled roof diagram with each facet's square footage, the pitch, and accurate linear measurements for ridge, hip, valley, eave, and rake. That diagram is what lets a reviewer match your photos to slopes and your estimate line items to real quantities.

Tie your damage findings to the diagram explicitly. "Test square A on the SW slope (Facet 3, 412 sq ft, 6/12)" connects the evidence to the geometry. When the photos, the diagram, and the line items all reference the same facet labels, the file reads as one coherent document instead of three loosely related ones, and coherence is what gets approvals without callbacks.

Where roof-due intelligence changes the field workflow

Everything above is what you do once you're standing on a roof you've decided to inspect. The harder operational problem in storm restoration is upstream: after a wind event rolls through a service area, which roofs do you actually walk, and in what order, when you have a finite crew and a closing window before the competition and the homeowner's memory both fade? Canvassing a whole damage swath door by door burns days on roofs that were too new, too sheltered, or not actually in the storm's path, while the roofs most likely to have a documentable, fundable wind loss sit unvisited.

This is the gap RoofPredict is built for, and it's worth being precise about what it does and doesn't do. RoofPredict models storm physics per individual roof, going past a coarse "this ZIP got wind" assumption, and combines that with a roof-age range estimated from aerial imagery for each address. The output is a ranked list of which roofs in a swath are most likely due, the ones an aging roof and a modeled wind exposure both point at, so your reps spend their inspection hours on the addresses where a credible wind file is most likely to exist. It's a targeting and routing tool that puts your documentation effort where it'll pay off; it ranks doors, it doesn't knock them, and it doesn't replace a single step of the inspection workflow above.

What it explicitly is not: it is not proof of damage on any specific house, and you must never present a storm model or a roof-age estimate as if it documented a loss. The model says a roof is likely aged into its replacement window and likely took meaningful wind exposure, which is odds, not evidence. The roof-age figure is a range, not an installation date, and it never goes in an insurance file as a date. The actual claim still stands entirely on what your rep photographs, lifts, marks, and measures on that specific roof on that specific day. The honest value is narrow and real: it gets the right rep to the right roof faster, so the documentation work, which is the only thing that wins claims, happens on the roofs where it counts instead of being sprayed across a neighborhood. Used that way it's a force multiplier on your field hours. Used as a substitute for inspection, it's worse than useless, because a model that's confident about a roof you didn't properly document is a denial waiting to happen.

Building the report an adjuster can approve

The field work is raw material. The report is the deliverable, and a good one is organized so an adjuster can verify your claim in the order they think about it: storm, cause, damage, scope. Structure it so the evidence answers their questions before they ask.

A report structure that works

1. Property and claim summary. Address, date of loss, claim/policy number if available, roof system (shingle line, approximate age range stated honestly as a range), and a one-line statement of the loss. Keep it factual and short.

2. Weather/event documentation. The one-page weather summary from your desk work: confirmed event, date, nearest measured gust, source, distance from property. This establishes covered cause and date before any roof photo appears, which is the order the adjuster's own reasoning runs in.

3. Roof diagram with measurements. The labeled facet diagram, square footages, pitches, and linear measurements. Everything downstream references these facet labels.

4. Ground and collateral documentation. Elevations, debris, collateral wind damage, neighborhood context. The corroboration that says "wind" before you even get to the shingles.

5. Slope-by-slope damage findings with test squares. The core. Each affected slope, its test-square counts, and the defect close-ups, organized by facet. Lead with the strongest slope. Pairing shots front and center.

6. Non-wind conditions, noted honestly. A short section acknowledging any age, defect, or mechanical conditions you found. This is counterintuitive but it's what makes the rest credible; the adjuster sees you're not overreaching and trusts your wind findings more.

7. Scope/estimate. Line items tied to the diagram quantities, written to a recognized estimating standard, with quantities a reviewer can reconcile to the measurements. Document the repairability facts (matching availability, brittleness) where relevant, as facts, without declaring the carrier's decision for them.

Language discipline in the written report

How you write the narrative matters as much as what you found. A few rules that keep a report credible and keep you on the right side of the line:

• Describe, don't conclude on coverage. "Shingle exhibits a horizontal mat crease consistent with wind uplift" documents a condition. "This is covered wind damage and the carrier owes a full replacement" is a coverage determination that isn't yours to make and reads as adversarial.
• Say "range" for age, never a manufactured date. "Roof condition and available records indicate an approximate age of 9 to 13 years" is honest and defensible. A specific install date you can't document is a liability.
• Tie every claim to a photo. Every assertion in the narrative should point to a labeled image. Unsupported adjectives ("extensive," "catastrophic") without a referenced photo are just volume.
• Stay inside your lane. You document conditions and provide an estimate. The homeowner owns the claim and the policy relationship; the insurer determines coverage and what it pays; the adjuster scopes. Writing the report as if you're adjudicating the claim is both outside your role and a fast way to get a knowledgeable adjuster's back up.
• No promises about outcomes. Don't put deductible handling, "free" anything, or guaranteed approvals in writing. Beyond being bad practice, depending on your state these can run afoul of insurance and consumer-protection rules, and they make your otherwise-solid file look like a sales document.

Worked example: a borderline file done right

Make it concrete. A homeowner calls eleven days after a line of severe thunderstorms; they've noticed a couple of shingles in the yard. The roof is an architectural shingle, mid-grade, that the homeowner thinks is "maybe ten years old." This is a winnable file or a wasted day depending entirely on documentation. Here's the run:

Desk work (30 minutes): NWS Storm Events confirms 65 mph thunderstorm wind gusts in the county on the date the homeowner cites; the nearest ASOS station logged a 61 mph gust 3.8 miles away. The shingle line is a Class D (90 mph) product; failure at 65 mph is plausible but not a slam dunk, which tells you the file has to be clean. Permit records put the roof at 8 to 11 years old. Honest age range, plausible cause, confirmed date. Worth the trip.

Ground (15 minutes): Two whole shingles in the side yard on the southwest elevation, photographed where they lie. Granules in the gutters. The neighbor's fence lost two boards on the same southwest line. One house down has a tarp. Wide elevation shots, all labeled. The directional story is already forming and the storm came out of the southwest.

Roof (45 minutes): The SW slope is the story. A test square (Facet 2, 100 sq ft) reveals 11 wind-creased shingles and 7 broken seals; each photographed folded-revealed and flat-hidden, plus three missing tabs with nails still seated, photographed with a tape. The NE slope test square shows 1 marginal seal and no creasing, the directional contrast that says wind, not age. The rep also notes mild edge curl on the north slope and photographs it honestly as an age condition, not a wind claim. Correct nailing is visible on a lifted shingle and gets a photo, closing the workmanship door.

Report: Weather summary up front. Labeled diagram. Ground/collateral. SW slope leads with its 11-and-7 test-square counts and pairing shots; NE slope contrast follows; the north-slope age curl is acknowledged in its own short section. Estimate tied to facet quantities. Roof age stated as the 8-to-11-year range. Nowhere does the report declare coverage, promise a result, or treat the storm data as proof of this specific roof's loss.

That file gets approved or gets a fair scope conversation because every question the adjuster can ask is already answered with third-party data and verifiable, still-on-the-roof evidence. The marginal wind speed that could have sunk it is offset by a clean, honest, directional, well-photographed record. That's the whole game.

Edge cases that trip up otherwise-good documentation

The clean files are the ones where a plausible-age roof meets a confirmed storm and the damage is obvious once you lift. The files that get argued, denied, or re-inspected to death are the edge cases, and knowing how to document each one before you're standing on it is the difference between a fundable record and a wasted afternoon.

The high-wind-rated shingle that failed at low wind

When a Class G or H shingle (rated 120 or 150 mph) shows seal failure or blow-off after a 60 mph event, the carrier's first move is to argue install error or product defect, because a properly applied high-rated shingle shouldn't have let go. Your documentation has to get ahead of that. Photograph the nailing on any blown-off or lifted shingle to show correct placement and count, capture whether the seal strip ever bonded (a strip that's clean with no adhesive transfer to the shingle above can indicate it never sealed, which is a manufacturer or install issue, not a wind loss), and be honest in your read. Sometimes the right answer on a high-rated shingle that failed early is that this is a workmanship or warranty conversation, not a wind claim, and recognizing that on the roof saves everyone a fight.

Partial-slope damage and the matching problem

Wind frequently damages one slope or even one section of a slope while leaving the rest intact. The documentation challenge is the repair-versus-replace conversation, and it turns on matching. Capture the existing shingle's line and color where you can identify it, and document whether that product is still manufactured. A discontinued color or a profile that's been redesigned is a documentable fact, not an opinion: photograph the shingle, note the line, and record what you find about current availability. Also document brittleness with a careful test lift, if attempting to remove a damaged shingle fractures the adjacent sealed ones, that's evidence repair isn't viable without collateral damage, and you capture the fractured neighbors as proof. You're documenting conditions that bear on repairability; you are not declaring the roof a total or telling the carrier what to pay.

Layered roofs and tear-off evidence

On a two-layer roof, wind documentation gets more nuanced because the top layer's behavior depends on what's under it. If you're already in a tear-off, the exposed layers, decking condition, and prior installation are documentable and worth photographing, because decking damage or prior storm repair tells part of the roof's history. Never represent a multi-layer condition as something it isn't, and remember that local code and the IRC limit how many layers can stay, which can independently drive a full replacement scope regardless of how the wind argument lands.

Older roofs where wind and wear overlap

The hardest honest case is the 20-to-25-year roof in a confirmed wind event. The shingles are brittle and curling from age, and wind exploits exactly that brittleness. Some of the damage is genuinely storm-caused and some is end-of-life, and they're physically intertwined. The honest documentation move is to capture the clean wind signatures that exist (fresh creases, broken seals, torn tabs with seated nails) separately from the age conditions, and to be straight with the homeowner that an old roof makes the wind argument harder, not easier. Sometimes the file holds and sometimes it doesn't, but a file that pretends end-of-life curl is fresh wind damage will fail on inspection and take your credibility with it. Calling it honestly, even when the call costs you a job, is what makes adjusters trust your next ten files.

The re-inspection: documenting so it survives a second look

On any meaningful wind claim, assume a carrier re-inspector or a desk reviewer will scrutinize your file, and on a contested one, assume someone will climb the roof to check your work. Documentation that's built to survive that second look is built differently than documentation meant only to make a sale. Three habits matter most:

• Leave your evidence on the roof. Chalk-marked test squares, marked defects, and lifted shingles you photographed are still there for the re-inspector to verify. A file whose claims can be physically confirmed on site is far harder to wave off than one that exists only as photos.
• Lock your metadata. Geotagged, timestamped photos from a documentation app that preserves EXIF are exactly what a reviewer needs to confirm date and location. Never edit a photo beyond cropping; a single altered image gives a reviewer license to discount the entire file.
• Make it self-explanatory. The reviewer wasn't there. If your slope labels, facet references, and establishing-to-detail sequences are consistent, anyone can reconstruct the inspection from the file alone. If they can't, even legitimate damage reads as unverifiable.

The goal is a record where a skeptical second set of eyes reaches the same conclusion your rep did, from the evidence alone. That's the standard worth holding to, because the files that win contested claims are the ones that were documented as if they'd be contested.

What pros get wrong (the recurring failures)

After enough files you see the same mistakes sink claims that should have been paid:

• Skipping the lift test. Looking instead of lifting means missing creases and broken seals, the two most common and most defensible wind defects. The damage that's invisible from a standing walk is exactly the damage that wins.
• No date-of-loss anchor. Beautiful damage photos with no weather documentation tied to a specific date is a maintenance file dressed up as a claim. Cause and date first, always.
• Claiming everything. Calling age curl, blistering, and foot-traffic scuffs as wind damage poisons the credibility of the legitimate findings. Flag the non-wind conditions yourself.
• Orphan close-ups. Tight shots with no establishing context that a reviewer can't place on the roof. Every detail needs a wide shot above it.
• Manufactured precision on age. Putting a confident install date in a file you can't actually support. Range it, honestly, every time.
• Writing the report like a sales pitch. Coverage conclusions, outcome promises, and adversarial language make a strong file look weak. Document conditions; let the evidence argue.
• Treating storm or age data as proof. A storm model or an aerial age estimate targets where to look; it never documents what's on a specific roof. The claim lives or dies on the lift, the mark, and the measure.

A repeatable field workflow you can hand to a new rep

Put it together into a sequence a trained rep can run the same way every time:

1. Desk: confirm event, date, nearest gust, source; pull shingle wind rating and install spec; estimate roof-age range honestly from records and condition.
2. Ground: perimeter walk; debris where it lies; collateral and neighborhood; labeled elevations; note wind direction.
3. Roof, safely: read each slope for creasing, broken seals, torn/missing tabs, directional granule loss; lift, don't just look.
4. Test squares: mark and document a representative square on the worst slope and a contrast square on a protected slope; count and record defects.
5. Photograph to standard: establishing-to-detail, scale in frame, EXIF on, slope-labeled, pairing shots, honest capture of non-wind conditions.
6. Measure and diagram: labeled facets, areas, pitches, linear footage; tie damage findings to facet labels.
7. Report: summary, weather, diagram, ground/collateral, slope-by-slope with test squares, non-wind conditions noted, estimate tied to quantities, disciplined non-adjudicating language throughout.

Run that every time and your close rate stops depending on how bad each roof happens to be and starts depending on something you actually control: the quality and honesty of the record you build. The roofs are what they are. The documentation is yours, and it's the one variable on the whole job you fully control.

Treat the inspection as the place you build a record rather than the place you find a sale, and the rest of the file falls into line behind it. Confirm the storm and the date, read each slope by lifting instead of glancing, count your test squares, photograph to a standard a stranger could verify, measure to a labeled diagram, and write the report in language that documents conditions instead of arguing coverage. Do that consistently and the marginal files start landing on the strength of the record alone.

The crews that win wind claims consistently aren't finding more damage than everyone else. They're proving the damage they find, tying it to a covered cause on a real date, and handing the adjuster a file so clean and so honest that approving it is easier than fighting it. That's a discipline, it's learnable, and it starts in the first twenty minutes on the roof, with a hand under a shingle and a camera that knows what it's looking at.

FAQ

How do I prove shingle damage was caused by wind rather than old age?

Lean on three things: the defect type, the pattern, and the date. Wind produces clean fold-line creasing across the mat, broken adhesive seals, and torn tabs with nails still seated, while age produces random craze cracking, edge curling, and uniform granule thinning. Document a directional pattern (damage concentrated on the slopes the storm actually hit) using test-square counts on a hit slope versus a protected slope. Then anchor it to a confirmed weather event on a specific date using NWS or NOAA records. Cause plus pattern plus date is what separates a covered loss from a maintenance condition.

What is a test square and why does it matter for a wind claim?

A test square is a marked-off representative area of a slope, usually 10 ft by 10 ft (100 sq ft), where you lift and document every defect inside the known area so the density can be extrapolated to the whole slope. It matters because it turns a subjective 'this roof is bad' into a countable, sampled, repeatable measurement an adjuster can verify, and because the chalk-marked square stays on the roof for a carrier re-inspector to confirm. Photograph it empty, then marked-wide, then each defect close-up, and run a contrast square on a slope the storm wouldn't have hit as hard.

What's the most commonly missed type of wind damage to shingles?

Creasing. When wind folds a shingle back and it lays flat again, the asphalt mat is cracked through along the fold line but looks completely normal from a standing walk. You only find it by lifting and gently flexing shingles to the angle the wind would have folded them, which reveals the fracture and the line of lost granules. Photograph it folded-revealed and then flat-hidden so the adjuster sees exactly what a fast inspection would miss. A close second is broken seal strips, which are also invisible until you lift the tab.

How many photos should a wind damage inspection include?

There's no magic number, but a thorough file commonly runs many dozens of organized photos. Quality and organization beat raw volume: every defect needs an establishing wide shot, a medium, and a scaled close-up, plus labeled elevations, ground debris, collateral damage, and test squares. Sixty clean, labeled, geotagged photos in a logical sequence outperform two hundred redundant blurry ones, because volume without organization buries your best evidence and reads as noise to a reviewer working at speed.

Should I photograph damage that isn't from wind?

Yes, and you should call it out honestly in the report. Documenting age curl, blistering, or foot-traffic damage as the non-wind conditions they are actually strengthens your file, because it shows the adjuster you're not overreaching, which makes them trust your legitimate wind findings. Claiming clearly-non-wind defects as storm damage poisons the credibility of the real ones. Flag the non-wind conditions in their own short section and let your honestly-documented wind defects carry the claim.

How should I handle roof age in an insurance file?

State it as a range, never as a manufactured installation date you can't support. Build the range from permit records, the homeowner's recollection, prior listings, and the physical condition of the shingles, then write it as something like 'approximately 9 to 13 years.' A confident specific date you can't document is a liability that a knowledgeable adjuster can pull apart, while an honest range is defensible. Age matters because the carrier's denial strategy on borderline roofs is 'old, not storm-damaged,' so your documentation has to separate storm defects from end-of-life wear.

What weather data should I include to support the date of loss?

Build a one-page summary from third-party sources the carrier respects: the NWS Storm Events Database and local National Weather Service event summaries for confirmed wind events, NOAA Storm Prediction Center storm reports for measured gusts and damage logs, and the nearest airport METAR/ASOS observation for peak gust readings on the date. State the date, the nearest confirmed gust speed, the source, and the distance from that observation to the property. Confirm with the homeowner that they first noticed the problem after that date and note it.

Can storm modeling or aerial roof-age data prove a roof was damaged?

No. Storm physics modeling and aerial roof-age estimates tell you which roofs are most likely due and worth inspecting, which is odds, not evidence. The roof-age figure is a range, not an install date, and it never belongs in an insurance file as a date. A storm model says a roof probably took meaningful wind exposure, not that a specific shingle creased. The claim stands entirely on what your rep lifts, marks, photographs, and measures on that specific roof. Targeting tools get the right rep to the right roof faster; they don't document the loss.

Does the manufacturer's wind rating affect my claim?

It frames how plausible the failure is. Shingles carry an ASTM D7158 rating of Class D, G, or H (roughly 90, 120, and 150 mph) or an older ASTM D3161 rating. A 90 mph shingle that fails in a confirmed 70 mph event tells a believable wind story; a 150 mph shingle that fails at 70 points you toward an installation or product-defect angle instead. The rating is a lab number under ideal install conditions, never a guarantee, so present it as context for plausibility, not as proof of anything.

What language should I avoid in the written estimate and report?

Avoid making coverage determinations, promising outcomes, or writing like a salesperson. Describe conditions ('horizontal mat crease consistent with wind uplift') rather than concluding coverage ('the carrier owes a full replacement'). Never put guaranteed approvals, deductible handling, or 'free' anything in writing, since beyond being bad practice these can run afoul of insurance and consumer-protection rules in many states. You document conditions and provide an estimate; the homeowner owns the claim, the insurer determines coverage, and the adjuster scopes. Staying in your lane keeps a strong file credible.