Photo and Measurement Documentation Standards for Roof Claim Files

A roof claim file is only as strong as the photos and measurements behind it. The estimate is the number, but the photos and the diagram are the evidence that the number is real. When an adjuster opens your file and can reconstruct the entire roof in their head without ever leaving their desk, you have done your job. When they have to call you for a missing slope, a missing test square, or a measurement that does not tie to the diagram, you have given them a reason to delay, and delay is where scope and dollars quietly disappear.

This is a working standard for the document side of a roof claim: what to photograph, in what order, how to measure, how to label, and how to assemble the packet so it reads cleanly on the first pass. It is written for the people who actually climb the roof and build the file, production managers, supplement managers, and owners who are tired of files coming back with the same gaps.

One boundary up front, because it shapes everything below. As a roofing contractor you can inspect the roof, document the condition of the property, measure it precisely, and write an accurate repair estimate for your own scope of work. You hand that documented estimate to the homeowner. The homeowner files the claim, and the insurer decides what is covered. You are documenting facts and pricing your own labor and materials, not negotiating the claim, not interpreting the policy, and not promising any outcome. Keep your file on the facts-and-estimate side of that line and it does double duty: it is good business and it keeps you clear of unlicensed public adjusting. We will come back to the specific language that crosses the line, because the words on your paperwork matter as much as the photos.

Why documentation standards exist at all

The carrier's adjuster is reconciling your file against their own inspection, against the desk reviewer who never saw the roof, and sometimes against a re-inspection months later when the original adjuster has moved on. Memory is gone. The only thing that survives is the file. A standard exists so that any reader, the field adjuster, the desk reviewer, the re-inspector, your own supplement manager three weeks later, can open the packet and arrive at the same understanding of the roof.

Three failures cause most of the friction:

1. Incompleteness. A slope is missing, a penetration is undocumented, the ridge cap was never photographed. The reader cannot confirm scope they cannot see, so they leave it out.
2. Ambiguity. A photo shows damage but nothing tells the reader where it is, how big it is, or what they are looking at. A bare close-up of a shingle could be from any roof, any slope, any date.
3. Inconsistency. The measurement report says 32 squares, the diagram says 28, and the estimate is built on 30. Now every number in the file is suspect, including the ones that are correct.

A documentation standard kills all three. It forces completeness through a shot list, kills ambiguity through context-and-detail pairing plus metadata, and kills inconsistency by tying every measurement back to a single source diagram.

The two-photo rule: context then detail

The single most useful discipline in roof photography is pairing. Almost every damage photo should come in two parts, and they should be adjacent in the file.

• Context shot: a wider frame that establishes where on the roof you are. It shows the slope, a reference landmark (a vent, the ridge, a valley, the chimney), and ideally the area of interest within the larger plane. The reader should be able to point to this spot on the diagram.
• Detail shot: the tight frame that shows what the damage actually is. Hail bruise, mat fracture, granule loss, a creased tab, a punctured pipe boot.

A detail shot with no context is an orphan. It proves damage exists somewhere in the world but not that it exists on this slope of this roof. A context shot with no detail proves you stood on a slope but not that anything was wrong with it. Paired, they are a complete statement: on the front-left slope, eight feet up from the eave near the plumbing vent, there is a fractured hail impact. That is a sentence an adjuster can verify and an estimator can scope.

Make the pairing physical in the file. Context immediately followed by its detail, captioned as a pair. Do not bury twenty detail shots in a row and expect anyone to map them back to locations.

A repeatable capture sequence

Shoot the same way on every roof. A fixed sequence means you never wonder whether you got the back slope, and it means your files all read the same way, which is exactly what a reviewer wants. Walk the roof in this order:

1. Address and arrival (3-5 photos)

Establish that this file belongs to this property on this date.

• The house number on the mailbox or front of the home.
• A full front elevation of the house showing the roof.
• One photo of each elevation (front, both sides, back) for orientation. These also catch collateral: dented gutters, downspouts, fascia, and wraps that corroborate a hail event and are part of an honest repair estimate.

2. Front-of-house overview and slope map (4-8 photos)

Before you climb, shoot the roof from the ground at angles that show overall geometry, the number of slopes, dormers, and the general layout. These ground overviews become your orientation key. Assign every slope a consistent label now and use it for the rest of the inspection. A simple convention: Front, Right, Back, Left (as you face the front of the house), and for complex roofs add the feature (Front-Dormer, Back-Garage). Whatever you choose, use the exact same labels in the photos, the diagram, and the estimate. Inconsistent slope naming is one of the most common reasons a file reads as sloppy.

3. Collateral / soft metals (6-12 photos)

Soft metals tell the storm's story because they dent at lower energy than a shingle bruises. Document, with context and detail:

• Gutters and gutter aprons (top and face).
• Downspouts.
• Metal fascia, drip edge, and rake metal.
• Roof vents, turbines, turtle vents, and any soft-metal vent caps.
• HVAC condenser fins, window screens, garage door panels, mailbox, and any other soft-metal collateral on the property.
• Window wraps and aluminum trim.

Collateral matters because it is hard to fake and easy to corroborate. A roof full of "hail hits" with zero collateral anywhere on the property invites doubt. Consistent collateral across multiple directions supports the event being real and roughly omnidirectional, which is what genuine hail looks like.

4. Each slope: overview, then test square, then detail (per slope)

This is the core of the file. For every slope, in order:

• Slope overview. One or two wide shots of the entire plane, labeled with the slope name. This is the context anchor for everything on that slope.
• Test square. Mark a 10-foot by 10-foot square (100 sq ft) with chalk on the slope, count and document the impacts within it, and photograph it. More on this below, because the test square is where a lot of files fall apart.
• Detail pairs. Context-then-detail for representative impacts, creases, and any mechanical damage on that slope.

Do this for the front, then the right, then the back, then the left, in the same order every time. When the file follows the same slope order as your sequence, a reviewer can flip through it like reading a map.

5. Penetrations and details (varies)

Every penetration is both a potential damage point and a code/flashing item that belongs in an accurate estimate:

• Pipe boots and plumbing vents (the rubber collar cracks and is frequently damaged or aged out).
• Furnace/B-vent flashing and storm collars.
• Chimney flashing, counterflashing, and crickets.
• Skylights and their flashing kits.
• Step flashing and headwall/sidewall flashing at walls.
• Valleys (open metal or closed-cut), with attention to displaced granules and metal dents.
• Ridge and hip caps, including any high-profile ridge vent.
• Drip edge and rake edge condition.

6. Layers, deck, and edge conditions (varies)

• A rake or eave edge photo that shows the number of shingle layers. This drives tear-off scope and is a routine point of dispute.
• Any exposed decking, spaced sheathing, or deteriorated substrate visible from the edge or at any lifted area.
• Underlayment type where visible.

7. Existing conditions and pre-existing wear (varies)

Document honestly: prior repairs, mismatched shingles, blistering, prior mechanical damage, foot traffic, and ordinary aging. Two reasons. First, an honest file is a credible file; hiding wear gets you caught and torches your reputation with that desk. Second, age matters to scope, and roof age is a range, not an exact birth certificate. You can read approximate age from granule loss, brittleness, sealant condition, and layer count, but state it as a band (for example, "consistent with a 15 to 20 year service life"), never as a fabricated install date. If you have a real install record, cite it; if you do not, describe the observed condition and let it stand as a range.

Test squares: the part most files get wrong

The hail test square is the single most scrutinized piece of a hail file, and it is where sloppy documentation is most expensive. The convention is a 10' x 10' = 100 sq ft square, chalked directly on the slope, within which you identify and count individual impacts.

Do it like this:

1. Mark the square in chalk. The chalk lines must be visible in the photo. A test square nobody can see in the picture is not a test square; it is a claim about a test square.
2. Mark each impact. Circle or mark each hit inside the square so the count is visible and repeatable. Use a contrasting chalk or keel.
3. Shoot the whole square first, then shoot detail of representative impacts inside it.
4. Label the slope and the count. "Front slope, 12 impacts in test square" written in your caption, and ideally chalked near the square so it shows in-frame.
5. One test square per slope, minimum. Each plane faces a different direction and takes a different storm exposure. A single test square on one slope does not represent the roof.
6. Put a reference object in frame for at least one detail shot per square so size is legible (more on reference objects next).

What goes wrong: a single test square for the whole roof; chalk lines that do not appear in the photo; impacts marked but never tied to a slope; a count in the notes that does not match the marked hits in the picture; or a "test square" that is actually just a random close-up with one chalk circle. Each of these gives a reviewer a clean reason to discount the hail finding.

A note on directionality and corroboration that keeps you honest: real hail tends to show up across multiple slopes and on soft-metal collateral facing several directions, with a spatter pattern on oxidized surfaces. Damage isolated to a single slope with no collateral and no spatter is worth a second, skeptical look before you build scope on it. Your job is to document what is there, accurately, not to manufacture a pattern.

Reference objects and scale

A detail photo without scale is guesswork. Always give the reader a way to judge size and depth:

• A coin, a chalk circle of known diameter, a tape measure, a pencil tip, or a spuds/keel mark beside the impact.
• For depth or fracture, a raking-light angle (shoot with the sun low or use a flashlight from the side) so the bruise or mat fracture casts a shadow and becomes legible. A bruise shot straight-on in flat light often photographs as nothing.
• For mat fractures, lift or press the impact to show the cracked fiberglass mat where appropriate, and photograph that. The granule loss is the surface; the mat fracture is the structural failure underneath, and it is the part that matters for whether the shingle is functionally damaged.

Consistency helps here too. If you always place the same chalk circle (say, a 2-inch circle) around impacts, every reviewer of every file learns your scale instantly.

Drone, aerial report, or hand measurement: matching the method to the roof

The measurement method you choose changes what you can prove and where the errors hide. None is automatically "right." Match the method to the roof and to what the file needs.

Aerial-imagery reports. Ordered from a provider that traces the roof from overhead photography, these give you a clean labeled diagram, per-facet areas, pitch, and linear measurements with no time on the roof. They are fast and consistent, which is their value, and the diagram they produce is exactly the kind of map a reviewer wants up front. Their weakness is currency and obstruction: the imagery can be months or years old, so a recent addition, a new dormer, or a tree that has grown over a slope can throw the trace off. Always sanity-check the report's roof shape against your ground overview photos before you trust it. If the report shows four facets and you photographed six, the report is stale.

Drone measurement. Flying the roof yourself captures current condition and lets you photograph high, steep, or fragile slopes you should not walk. A drone is the safest way to document a roof that is too steep or too brittle to set foot on, and it produces current imagery you control. The tradeoff is that turning drone imagery into reliable linear measurements takes either good software or careful manual work, and you still owe the file the same per-facet and linear numbers an aerial report would give you. Drone photos also need the same metadata discipline as ground photos; confirm the flight is geotagged and time-stamped.

Hand measurement. A tape, a ladder, and a pitch gauge still produce the most defensible numbers when done with discipline, because every figure is something you physically touched and can photograph. Hand measurement is also the fallback when the roof geometry defeats an aerial trace. The cost is time and exposure; you are on the roof, so fall protection per OSHA is not optional, and a steep or high roof may push you to a drone instead.

The professional move is to cross-check at least two methods on anything complex or high-dollar. Order the aerial report and verify it against your own ground and roof photos, or fly the drone and reconcile against a hand-measured eave or two. When two independent methods land within a few percent, the number is bulletproof. When they diverge, you have found a problem before the reviewer does, which is the entire point of measuring twice.

A safety note that is also a documentation note: OSHA fall-protection rules apply the moment you are working at height, and a roof that is too steep, too high, too wet, or too brittle to walk safely is a roof you document from a drone or a ladder at the edge. A photo is never worth a fall. Building the drone-first habit for unsafe slopes protects your crew and still produces a complete file.

Metadata: the quiet backbone of a credible file

Great photos with no metadata are a weak file. The data attached to each image is what defends the file when someone, months later, questions whether the photos are from this roof, this date, this storm.

Capture and preserve:

• Date and time. Every photo should carry an accurate capture timestamp. This ties the inspection to the loss date and to the storm. Make sure the device clock is correct before the season starts; a wrong clock undermines every file you shoot.
• GPS coordinates. Geotagged photos prove the images were taken at the property. This is one of the strongest, hardest-to-argue pieces of corroboration you can attach, so enable location on your capture device and confirm it is writing to the image.
• Sequence/order. The order of capture should match your inspection sequence so the file tells a coherent walk-through.
• Inspector and equipment. Who took the photos and on what device.

Two cautions. First, do not strip metadata. Some apps and messaging services re-compress images and drop EXIF data; if you text photos to yourself or pull them through a channel that strips data, you can lose the timestamp and GPS that made them valuable. Move full-resolution originals straight from the device into the file. Second, never alter timestamps or edit images beyond honest cropping and lightening for visibility. Cloning, content-aware fill, or backdating is fraud, full stop, and modern review can often detect it. The whole value of metadata is that it is trustworthy; do not poison it.

Measurements: one source of truth, total agreement

Measurements are the other half of the file, and the rule is simple: every number in the file must agree. The measurement report, the slope diagram, and the estimate are three views of the same roof and they must reconcile to the square.

What a measurement report must contain

Whether you measure by drone, by aerial-imagery report, or by hand with a ladder and a tape, the deliverable should include:

• Total roof area in squares (1 square = 100 sq ft).
• Per-slope (per-facet) areas, so each plane you photographed has a number.
• Pitch / slope for each facet (e.g., 6/12). Pitch drives both the area calculation and the labor/steep-charge logic in the estimate.
• Predominant pitch for the roof overall.
• Linear measurements: total eave length, total rake length, ridge length, hip length, valley length (open and closed), and step-flashing/wall-flashing lengths.
• Penetration count and types.
• A labeled diagram that ties every facet to a label you also used in the photos.

Those linear measurements are not busywork. Ridge and hip lengths drive ridge-cap quantity. Valley length drives valley material and labor. Eave and rake lengths drive drip edge, starter, and ice-and-water shield. Step-flashing length drives wall flashing. A measurement report that gives you only total squares and nothing else forces the estimator to guess every accessory quantity, and guesses are exactly what a reviewer cuts.

Waste, starter, and ridge: get the math explicit

Three numbers cause more measurement disputes than anything else:

• Waste. Complex roofs, lots of hips and valleys, and certain shingle layouts drive cut waste. State your waste percentage and tie it to the roof's complexity rather than dropping in a flat number. A simple gable roof and a cut-up hip roof with six valleys do not carry the same waste, and a reviewer knows it.
• Starter course. Eave starter (and often rake starter) is a real, separate line driven by your eave/rake linear footage, not something baked invisibly into field shingles.
• Ridge/hip cap. Cap is its own material and labor line driven by your ridge + hip linear footage. Pulling the number straight from the measurement report's ridge and hip lengths makes it instantly verifiable.

When these three are shown explicitly and tied to the linear measurements in the report, the estimate stops looking padded and starts looking calculated. That is the difference between a supplement that gets read and one that gets bounced.

Hand-measurement discipline

If you measure by hand, photograph your measurements: the tape laid along an eave with the reading legible, the pitch gauge on the slope, the layer count at the edge. A measurement you can see in a photo is a measurement nobody re-argues. And reconcile your hand numbers against an aerial or drone figure when you can; if they disagree by more than a few percent, find out why before the number goes in the estimate.

Wind versus hail: the documentation is not the same

Hail and wind damage tell different stories, and a file that documents one as if it were the other reads as confused. Know which event you are documenting and shoot for it.

Hail is about impacts: round or irregular bruises, granule displacement exposing the mat, fractured fiberglass mat, and a spatter pattern on oxidized soft metals and accessories. The hail file lives or dies on test squares, marked impacts, soft-metal collateral across multiple directions, and the mat-fracture detail under raking light. Directionality matters: genuine hail usually shows on multiple slopes.

Wind is about displacement and tearing: creased and folded shingle tabs, torn or missing shingles, lifted and unsealed tabs, and damage that often concentrates on the windward slopes, rakes, ridges, and field edges where uplift is highest. The wind file leans on context shots showing where shingles are missing or creased across a slope, detail shots of individual creases (a crease is a fracture line across the tab, distinct from a manufacturing crease or thermal seam), and documentation of the seal strip where tabs have unsealed. Photograph the pattern of loss, not only single tabs, because wind damage is read as a distribution across a slope.

Where wind and hail overlap on the same roof after a single storm, document both clearly and keep them labeled separately in the file. Do not blur a wind crease into a hail call or vice versa; a reviewer who catches a misclassified mechanism discounts the whole file. Reference the relevant shingle wind-resistance context (ASTM D3161 / D7158 class ratings appear on the product) where it supports an honest description of the failure, and let the photos carry the rest.

Building the packet: order, labels, and reconciliation

A pile of correct photos is not a claim file. The packet is the product, and its job is to let a reader move through the roof without friction. Assemble it like this:

Recommended packet order

1. Cover sheet. Property address, date of inspection, date of loss (as reported), inspector, and your company contact. Keep it factual.
2. Measurement report and labeled diagram. Put the map up front so every photo that follows has a place to land.
3. Address and elevations. Proof of property and orientation.
4. Collateral / soft metals. The corroboration block.
5. Slope-by-slope sections, in your fixed order (Front, Right, Back, Left). Each slope: overview, test square, detail pairs.
6. Penetrations and flashings.
7. Layers, deck, edges.
8. Existing conditions / pre-existing wear, documented honestly.
9. Estimate, built line-by-line, every quantity traceable to the measurement report.
10. Annotated summary diagram (optional but powerful): the roof diagram with damage locations and test squares marked on it, so the reader sees the whole story on one page.

Name and organize the files themselves

The packet order is the document a reviewer reads, but the raw files behind it need their own discipline or you will lose photos and break metadata. Two habits:

• A consistent file-naming convention. Even a simple scheme pays off: address_slope_type_sequence (for example, 1428Oak_Front_TestSquare_01). Named files sort into order on their own, survive being moved between systems, and make it obvious at a glance when a slope's photos are missing. Numbered-only filenames straight off a camera are how photos get orphaned.
• One folder per property, originals preserved. Keep the full-resolution originals untouched in a per-property folder and do any cropping or lightening on copies. The original with intact EXIF is your evidence of record; the edited copy is for legibility in the packet. If you ever have to defend a timestamp or a GPS tag, you reach for the untouched original.

Decide both conventions once, write them into the standard, and make every inspector follow them. The goal is that any file your company produces can be picked up by anyone else and read without translation.

Caption every photo

A caption is one short, factual line: slope, location, what it shows. "Right slope, mid-field, fractured hail impact with mat crack, 2-inch chalk reference." No interpretation of coverage, no conclusions about the claim. Just what the camera saw and where. Captions are what turn a folder of images into a readable document, and they are what a desk reviewer who never saw the roof relies on entirely.

Reconcile before you send

Run a final reconciliation pass, every time, before the file leaves your hands:

• Does the total square count on the estimate match the measurement report?
• Does every facet in the diagram have at least an overview photo?
• Does every slope have a test square (for a hail file)?
• Do the ridge-cap, starter, drip-edge, and valley quantities on the estimate trace to the linear measurements?
• Does every detail photo have a context photo and a caption?
• Is the metadata intact on the originals?
• Are slope labels identical across photos, diagram, and estimate?

If any answer is no, the file is not done. This five-minute pass is the cheapest insurance in the entire process, because the alternative is a callback, a re-inspection, or a quietly reduced scope.

A worked example: walking one roof

Consider a two-story home with a cut-up hip roof, asphalt shingles, after a reported hail event. Here is the file as a complete walk-through.

Arrival. Mailbox number, full front elevation, four elevation shots. The front elevation shows dented gutters and a bent downspout. Already the collateral story is starting.

Ground overviews. Four angled ground shots. You name the slopes: Front, Right, Back, Left, plus Front-Dormer and Back-Garage. You will use these exact names everywhere.

Collateral. Gutters (top and face) showing oval dents, downspout dents, two roof vents with dinged caps, the HVAC condenser fins showing impact, the metal mailbox dented, and a window screen with spatter. Context-and-detail on each. The collateral is on multiple sides of the house, which is consistent with genuine hail.

Front slope. Overview shot labeled "Front." Chalk a 10x10 square, mark the impacts, count 14, write "Front, 14" in chalk in-frame, shoot the full square, then three detail pairs with a 2-inch chalk reference and raking light. One detail lifts a tab to show the fractured mat.

Right slope. Same sequence. Test square count 9. Two detail pairs.

Back slope. Same sequence. Test square count 11.

Left slope. Same sequence. Test square count 8.

Dormer and garage facets. Overview each, plus a test square on the garage (count 7). The dormer is too small for a full square, so you document representative impacts with reference objects and note the facet's small size.

Penetrations. Two pipe boots (one cracked from age, documented honestly as wear), furnace flashing, a skylight with a dinged flashing kit, chimney counterflashing, and the open valleys showing displaced granules and a few metal dents.

Edges and layers. A rake-edge shot showing a single shingle layer. Drip edge present, dented on the front-facing run.

Existing conditions. A prior repair patch on the back slope, mismatched, and ordinary granule loss consistent with a roof in the mid-to-late portion of its service life. Documented, not hidden.

Measurements. Aerial report: 31.4 squares total, per-facet areas, predominant 7/12 pitch, eave 188 ft, rake 142 ft, ridge 34 ft, hip 96 ft, valley 52 ft, 6 penetrations. Labeled diagram matching your slope names.

Estimate. Built from those numbers. Field shingles from total squares with a stated waste tied to the hip/valley complexity. Starter from eave + rake footage. Ridge cap from ridge + hip footage. Drip edge from eave + rake. Valley metal and labor from valley footage. Pipe boots and flashings itemized from the penetration count. Steep and two-story charges from pitch and height. Every quantity points back to a line in the measurement report.

Reconciliation. Squares match. Every facet has a photo. Every slope has a test square. Accessory quantities trace to linear measurements. Captions present. Metadata intact. Labels consistent. The file goes out.

That file does not need a phone call to be understood. That is the entire goal.

The compliance line, in plain words

The documentation and the estimate are yours to make. The claim is the homeowner's to file and the insurer's to decide. Keep your file and your paperwork on the right side of that, and write it in language that stays there.

Safe to do and say:

• Inspect the roof and document its condition with photos and measurements.
• Write an accurate, Xactimate-aligned estimate to repair your scope of work.
• State facts about your scope and the documented condition.
• Hand the documented estimate to the homeowner for them to submit.

Do not say or promise (this is unlicensed public adjusting or deceptive practice, depending on your state):

• That you will "handle," "negotiate," or "adjust" the claim for the homeowner.
• Any interpretation of what the policy covers or whether a given item is covered.
• A promised payout, a promised approval, or a guaranteed claim outcome.
• That the deductible will be waived, absorbed, eaten, or made to disappear. The deductible is the homeowner's legal obligation; rebating or absorbing it is illegal in many states and a fast way to lose a license and a reputation.
• A "free roof."
• Anything representing the homeowner against their insurer.

The documentation standard is your protection here too. A file that sticks to observable facts, photographed and measured, with an estimate that prices your own labor and materials, cannot drift into adjusting because it never makes a coverage claim. The cleaner your documentation discipline, the easier it is to stay compliant, because you are always talking about the roof, never about the policy.

A word on contracts that pairs with this: keep the estimate and any agreement contingent on what the homeowner and insurer actually do, written in plain language, and disclose anything your state requires for storm/insurance restoration work. When in doubt about your state's specific rules, check your state's Department of Insurance and contractor-licensing guidance; the lines on public adjusting and deductible handling vary by state.

Documenting for a re-inspection or a disputed scope

Not every file is approved on the first read. When a scope item is left out or a finding is questioned, the documentation you already have is what gets it a second look, and the way you handle a re-inspection determines whether it goes anywhere. Stay on the documentation side here too: you are clarifying and completing the factual record, not arguing coverage.

A few practices make disputed files manageable:

• Keep the original file frozen. When a re-inspection is scheduled, do not quietly swap or edit the original photos. Preserve the as-submitted file and add a clearly dated supplemental set if you capture new documentation. A file that visibly changed between submissions invites distrust.
• Document the specific gap, not the whole roof again. If the question is a missing valley quantity, your supplemental documentation is the valley: a context shot, a detail shot, the valley footage from the measurement report, and the line item it supports. Tight, specific, traceable. A wall of new photos with no focus reads as noise.
• Tie every supplemental item to evidence and a measurement. A scope item that belongs in the estimate should point to a photo that shows the condition and a measurement that sizes it. "Drip edge, 188 ft of eave plus 142 ft of rake, code-required, photographed at the front-facing run" is a complete, factual case. It is not a coverage argument; it is the documented basis for a line in your own repair estimate.
• Document conditions, never decisions. Your supplemental record describes the roof and prices your scope. Whether an item is covered is the insurer's call. Keep the language on the condition and the estimate, exactly as on the first pass.

When a claim is denied, the contractor's lane is narrow and worth respecting: you can make sure your documented estimate and the condition record are complete and accurate, and you hand that to the homeowner. The homeowner pursues the claim and any appeal with their insurer. You do not represent the homeowner against the carrier, interpret the denial's coverage language, or promise to overturn it. A complete, honest documentation file is the most useful thing you can put in the homeowner's hands, and it is squarely on the right side of the line.

What pros get wrong (a field punch list)

After enough files, the same mistakes repeat. Audit your own team against these:

• One test square for the whole roof. Every slope, every time.
• Orphan detail shots. No context, no caption, no place on the diagram.
• Invisible chalk. Test-square and impact marks that do not show in the photo.
• Flat-light bruise shots that photograph as nothing. Use raking light.
• Mismatched slope names across photos, diagram, and estimate.
• Square counts that disagree between report, diagram, and estimate.
• Accessory quantities pulled from the air instead of from linear measurements.
• Stripped metadata from texting photos through compression.
• Hidden wear that gets the whole file labeled as unreliable when it surfaces.
• Coverage language on the paperwork that drifts into adjusting.
• No layer photo, then a tear-off scope dispute with nothing to point to.
• Missing collateral, leaving a hail finding with no corroboration.

Every one of these is preventable with a fixed sequence and a reconciliation pass. None of them requires more talent, just discipline.

Standardize it once, then run it on every roof

The reason files come back inconsistent is almost never skill. It is that every inspector improvises, so every file is shaped differently and every gap is a surprise. The fix is a written standard, a fixed shot list, a fixed packet order, a reconciliation checklist, applied identically by everyone who climbs a roof for your company. Train to it, audit against it, and your worst file becomes your average file.

The payoff is concrete. A complete, internally consistent, honestly-documented file is the one that gets read on the first pass, the one where the estimator's quantities are obvious, and the one where a supplement, if the scope genuinely warrants it, lands on evidence instead of an argument. The roof did not change. The documentation did.

Where RoofPredict fits: turning the standard into a repeatable file

A standard is only as good as your ability to run it the same way on every roof, and that is where most of the breakdown happens, in the field, under time pressure, across a team. RoofPredict is the operations platform contractors run this on, and two parts of it map directly to the photo-and-measurement problem.

RoofClaim, the claim documentation and revenue-cycle side. When you build a claim file, RoofClaim links it to the specific home and lets you upload, auto-classify, and OCR the documents that make up the file: carrier and contractor estimates, photos, denial letters, and invoices. The part that does real work on the estimate side is opportunity detection: it maps the line items in an estimate against a roofing knowledge base and flags missing scope, code-required items, and missed supplement opportunities, each with an evidence anchor and pricing. So when your reconciliation pass asks "did the ridge cap, starter, drip edge, and flashing quantities make it into the estimate," you are not eyeballing it, the scope-gap flags surface the line items your linear measurements support but the estimate is missing, with the evidence pointing back at the documentation. Supplements run on a tracked cadence with packet-completeness scoring, which is exactly the reconciliation discipline from the section above, turned into a score you can see before the file goes out: it tells you the slope that is missing a photo or the test square that never got documented, while you can still fix it. Recoverable-depreciation release and deductible tracking sit on the same locked, UPPA-gated templates, so the documents you generate, supplement packets, depreciation-release letters, missing-docs letters, audit reports, stay on the contractor-documentation side of the compliance line by design. The templates are built so you are documenting and estimating, never adjusting.

It is honest about what it is. The opportunity detection flags scope gaps against a knowledge base and prices them; it does not, and cannot, promise a payout or decide coverage. That stays with the homeowner and the insurer, which is exactly where the compliance line puts it.

Where the file starts: which roofs to document in the first place

The other half of the platform sits upstream of the file. Before anyone climbs a roof, RoofPredict scores every home in a service area by roof-age band, recent, mid-life, due, overdue, layered with per-roof storm exposure and an opportunity score, and produces a ranked, house-by-house target audience with a "why this home" evidence chain. After a storm rolls through, you filter that ranked list by storm-hit area and territory, so the roofs you send a crew to inspect and document are the ones where age and exposure actually line up, not a random door-knock. Roof age there is a band, not a fabricated date, and a storm forecast is odds of exposure, not proof of damage on any one roof, the same honesty the documentation standard demands.

From that ranked list the platform builds the front end of the funnel that feeds your claim files: tracked direct-mail campaigns with personalized proofs and per-piece delivery tracking, a personalized microsite and PDF report per home with a lead-capture form, per-home QR codes for mail and door hangers, and door-knock routes with a mobile field app for canvassers. Leads land in a pipeline (new, contacting, appointment, inspected, won, lost) with an immutable first-touch source and two-way sync to the CRM you already run, including JobNimbus, AccuLynx, ServiceTitan, HubSpot, Roofr, CompanyCam, and others. The results funnel then shows delivered, views, form fills, calls, leads, and wins, with cost-per-lead and cost-per-win measured actual-versus-estimate against a benchmark, so you can see which targeting actually produced inspections worth documenting.

The through-line: rank the right roofs, get to the door, inspect and document to a fixed standard, and let RoofClaim score the file for completeness and surface the scope your measurements support, all on templates that keep you on the documentation-and-estimate side of the line. If your files keep coming back with the same gaps, standardize the capture, then run it on a platform that scores the packet before it ever leaves your hands. That is how the worst file your team produces becomes the average one.

FAQ

How many test squares should a hail roof claim file have?

At minimum, one 10' x 10' (100 sq ft) test square per slope, because each plane faces a different direction and takes a different storm exposure. A single test square representing an entire roof is one of the most common reasons a hail file gets discounted. Chalk the square so the lines are visible in the photo, mark each impact, write the slope name and count in-frame, shoot the full square first, then detail representative impacts with a scale reference.

What metadata should roof claim photos carry?

Accurate date and time, GPS coordinates, capture sequence, and the inspector and device. Geotagged, time-stamped photos prove the images were taken at this property on this date and tie the inspection to the loss and the storm. Set your device clock correctly before the season, enable location, and move full-resolution originals straight off the device into the file, do not text them through services that re-compress and strip EXIF. Never alter or backdate metadata; that is fraud and modern review can often detect it.

What is the two-photo rule for roof damage documentation?

Almost every damage photo should be a pair: a context shot that establishes where on the roof you are (slope, a landmark, the area within the plane) immediately followed by a detail shot showing what the damage is. A detail shot with no context is an orphan, it proves damage exists somewhere but not on this slope of this roof. Keep the pair adjacent in the file and caption it with slope and location.

What measurements belong in a roof claim measurement report?

Total area in squares, per-facet areas, pitch for each facet and the predominant pitch, and the linear measurements that drive accessory quantities: eave, rake, ridge, hip, and valley lengths plus wall/step-flashing lengths, along with a penetration count and a labeled diagram. Those linear numbers are what let the estimator calculate drip edge, starter, ridge cap, and valley material instead of guessing, which is exactly what a reviewer cuts.

Why do the square counts on my estimate and measurement report need to match?

Because the measurement report, the diagram, and the estimate are three views of the same roof, and if they disagree, every number in the file becomes suspect, including the correct ones. A mismatch (report says 31 squares, diagram says 28, estimate is built on 30) gives a reviewer a clean reason to discount the file. Run a reconciliation pass before sending and confirm the squares and every accessory quantity trace back to a single source diagram.

How do I photograph a hail bruise so it actually shows up?

Use raking light, shoot with the sun low or use a flashlight from the side so the impact casts a shadow and becomes legible; a bruise shot straight-on in flat light often photographs as nothing. Put a scale reference in frame (a coin, a known-diameter chalk circle, a tape), and where appropriate lift or press the impact to show the fractured fiberglass mat underneath, which is the structural failure that matters rather than only the surface granule loss.

Can a roofing contractor document damage and write the estimate without becoming a public adjuster?

Yes. A contractor can inspect, document condition with photos and measurements, write an accurate repair estimate for their own scope, state facts about that scope, and hand the documented estimate to the homeowner, who files the claim. The line is crossed when you negotiate or handle the claim for a fee, interpret policy or coverage, promise a payout or approval, or represent the homeowner against the insurer, that is unlicensed public adjusting. Keep your file on observable facts and your own pricing and you stay clear.

Why does soft-metal collateral matter in a hail file?

Soft metals (gutters, downspouts, vent caps, fascia, HVAC fins, window screens, mailbox) dent at lower energy than a shingle bruises, so they tell the storm's story and are hard to fake. Consistent collateral across multiple directions corroborates a genuine, roughly omnidirectional hail event. A roof full of claimed hits with zero collateral anywhere on the property invites doubt and should prompt a second, skeptical look before you build scope.

How should I document roof age when I do not have an install date?

State age as a range, never as a fabricated date. You can read approximate age from granule loss, brittleness, sealant condition, and layer count, and describe it as a band such as 'consistent with a 15 to 20 year service life.' If you have a real install record, cite it. Documenting age honestly as a range keeps the file credible and keeps you out of claiming a specific install date you cannot prove.

What order should a roof claim packet be assembled in?

Cover sheet, then the measurement report and labeled diagram up front so every photo has a place to land, then address and elevations, collateral, slope-by-slope sections in a fixed order (each with overview, test square, and detail pairs), penetrations and flashings, layers and edges, existing conditions documented honestly, the line-by-line estimate, and an optional annotated summary diagram. A fixed order means any reviewer can move through the roof like reading a map without calling you for a missing piece.