How to Scope a Roof for an Insurance Estimate, Step by Step

Scoping a roof is the part of insurance work that decides everything downstream, and it is the part most crews rush. The estimate that eventually goes to the carrier, the supplement that may or may not be needed later, the conversation with the adjuster on the roof, whether the homeowner trusts you, whether your margin survives the job: all of it traces back to one hour spent walking the slopes with a measuring tape, a chalk line, and a camera. Get the scope right and the rest is paperwork. Get it wrong and you spend the next three months chasing photos that prove nothing and arguing about quantities you guessed at.

A scope is a complete, quantified description of everything required to put the roof back to its pre-loss condition. It is not a sales pitch and it is not a number you back into. You build it from the roof up, component by component, so that every line item has a measured quantity, a documented reason, and a photo or a code citation behind it. When you scope this way, the insurance estimate becomes a structured statement of fact rather than an argument, and facts hold up far better than arguments.

What follows is the actual field workflow practitioners use, from the first call to the assembled package. It covers the measurements that anchor every quantity, the slope-by-slope hail and wind documentation that survives a desk review, the line items that get bundled away or forgotten, the code-driven items that turn a maybe into a requirement, and the edge cases that trip up even experienced estimators. It also stays carefully inside the contractor's lane. You document conditions and produce an accurate estimate of the work. The homeowner files the claim and the insurer decides coverage. Nothing here asks you to step over that line, and there is a section near the end on exactly where that line sits and why staying behind it protects your business.

What "scoping for an insurance estimate" actually means

There is a meaningful difference between a sales walk and a scope, and conflating the two is the single most expensive habit in restoration roofing.

A sales walk is what a rep does to decide whether there is a claimable event and to sign the homeowner. The rep climbs up, finds enough hail hits to believe a carrier will recognize damage, takes a few phone photos, comes down, and gets a contract signed. That is a legitimate and necessary job. It is also not a scope.

A scope is what an estimator does to describe the entire job in measured, defensible detail. The estimator treats the roof as if they had to hand a cash customer an exact, line-by-line number they could defend to the dollar, then documents every condition that supports each line. Only after that complete scope exists does anyone compare it to what the carrier's estimate accounts for. The comparison shows the gaps, and the gaps are what you document and, if needed, supplement later.

The reason this distinction matters so much is timing. Almost every line item in an insurance estimate is easiest to prove during the first thorough inspection and impossible to prove later. Hail bruises on a test square are there now; once the roof is torn off they are in a dumpster. Rotted decking is visible at tear-off and buried under new wood an hour later. Deteriorated flashing, layered roofs, soft-metal collateral on the gutters: all of it is evidence with a short shelf life. The scope is the act of capturing that evidence while it still exists.

The best companies separate the two roles deliberately. The salesperson signs the deal; a trained inspector or estimator builds the scope. In a small shop one person does both, and that is fine, but you have to switch hats consciously. Sign the customer, then go back up the ladder and scope like an estimator who has never met them.

Step 1: Prepare before you touch the ladder

The scope starts on the ground, before anyone climbs. Three pieces of preparation separate a smooth inspection from a sloppy one, and all three are cheap.

Pull the property and storm context

Know what you are walking into. Roughly how old is the roof likely to be? What storm event, if any, are you referencing, and what date did it occur? What direction did the weather come from? Older roofs are far more likely to lack drip edge, to be under-ventilated, and to carry brittle decking, which tells you which conditions to look for. A known storm date and direction tells you which slopes took the brunt and which storm to reference in your documentation. You are not deciding the outcome from a desk; you are deciding where to look hardest once you are up there.

Pull the local code edition

Building codes are adopted at the state and local level, and the edition in force in one county may not match the next one over. Before the climb, know which code edition the jurisdiction enforces and what it requires for a reroof. This is what lets you recognize a code-driven line item the moment you see it is missing on the roof, instead of discovering it three weeks later. The items most often code-driven are ice barrier at eaves, drip edge at all edges, underlayment type, decking attachment, and ventilation minimums. More on each below.

Confirm the basics with the homeowner

A short conversation up front saves rework. Confirm the address and the structures involved, ask whether there is more than one roof on the property, ask about any known prior repairs or leaks, and confirm the homeowner intends to file a claim so you scope to the right standard. You are not interpreting their policy or telling them what is covered. You are confirming the scope of the physical inspection.

Gear that makes the scope possible

A scope is only as good as the documentation it produces, and documentation depends on having the right tools on the roof. The working kit:

• A tape measure and a pitch gauge or a level and a short ruler
• Chalk, in a color that photographs against the shingle
• A camera or phone that timestamps and ideally geotags photos
• A ladder rated for the height, with proper setup and tie-off
• A way to record notes by slope, whether a printed form or an app
• Fall protection appropriate to the pitch and height

That last point is not a throwaway. Steep, high, wet, or frosted roofs are genuinely dangerous, and rushing a scope on a roof you should not be standing on is how people get hurt. Follow fall-protection practice, and when a roof is too dangerous to walk safely, document what you can from a ladder, a drone, or the ground rather than taking the risk.

Step 2: Get accurate measurements before anyone else does

You cannot estimate a quantity you did not measure. The foundation of the entire scope is an accurate measurement of the roof, and you want it in hand before the adjuster ever sets foot on the property. Serious estimators use a combination of an aerial report and hand verification.

The aerial measurement report

A report generated from aerial and satellite imagery gives you total roof area, a slope-by-slope area breakdown, ridge and hip lengths, valley lengths, eave and rake lengths, and pitch. This is the spine of the scope because almost every line item is a function of one of those numbers:

• Starter strip is a function of eave plus rake length
• Ridge cap is a function of ridge plus hip length
• Drip edge is a function of eave plus rake length
• Ice-and-water barrier is a function of eave length and code
• Valley metal is a function of valley length
• Field shingles are a function of total area plus a waste factor

If those measurements are right, the quantities defend themselves. Order the report early. The most common avoidable mistake is showing up to the adjuster meeting working from the carrier's squares because your own report was not ready. When you hold an independent, third-party measurement document, a quantity dispute stops being your word against the adjuster's and becomes a comparison of two documents, which the more detailed one usually wins.

Hand verification

Aerial reports are accurate but not infallible. Heavy tree cover, very recent construction, an addition not yet in the imagery, and complex architecture can all throw a number off. Verify the spots that matter. Walk the perimeter and confirm eave and rake lengths roughly track the report. Check pitch on a representative slope with a gauge. Note anything the imagery cannot see: a low porch roof tucked under a tree, a dormer cheek that the imagery flattens, a section the report split incorrectly. When your hand check and the report disagree by more than a few percent, find out why before the meeting, not during it.

Pitch, stories, and labor multipliers

Labor is not a flat rate per square, and the estimate has to reflect that. Steep and high roofs cost more to tear off and install, and estimating platforms carry specific line items for exactly this. Document the pitch of every slope, not only the predominant one. A roof that is mostly 6/12 with a 10/12 front gable owes steep charges on that gable. Document the number of stories and any two- or three-story sections, because high-roof labor modifiers are legitimate and routinely omitted from a thin estimate. Write all of it down in a structured way: area by slope, total squares with waste, pitch by slope, story height, and linear footage of every roof-edge feature. That measurement summary anchors the entire conversation that follows.

Step 3: Document the damage slope by slope

Measurements tell you the quantities. Damage documentation tells you why the roof needs to be restored. For an insurance estimate, the second is where most packages are weak, because reps document the drama and skip the coverage. A desk reviewer who never visits the property decides the claim from your photos, so the photos have to function as the property.

The test-square method, on every slope

The industry-standard way to document hail is a test square: a marked area, typically ten feet by ten feet, chalked on the slope, with the hits inside it circled and counted, plus a photo of the marked square and a note of the count. Do this on every slope, including the ones that look undamaged, because directional storms hit slopes unevenly and the carrier's threshold is often a hit count per square per slope. A north slope with eight hits and a south slope with two is a real and common pattern, and you can only establish it if you documented both. The slope that looks clean is often the slope that proves the storm's direction, which corroborates the damage on the slopes that took it head-on.

Distinguish hail from everything else

A credible scope shows you can tell storm damage from the other things that mark a roof, because a reviewer will look for exactly that. Hail bruising tends to be random in pattern, roughly circular, with a soft or fractured mat and granule loss exposing the asphalt, and it shows up on the soft metals nearby. Mechanical marks, foot traffic, blistering, manufacturing defects, and normal granule loss from age look different and land in different patterns. You do not need to argue the distinction in writing; you need to document the hail pattern clearly enough that it speaks for itself, and you need to not call something hail that plainly is not. Overreaching on one slope undermines your credibility on the slopes where the damage is real.

Wind damage is its own documentation

Wind damage is a separate category from hail and gets documented differently. Look for creased shingles, torn or missing shingles, unsealed tabs, and damage concentrated on the windward slopes and along the edges and ridges where uplift is strongest. A creased shingle is a shingle that was lifted and folded back by wind and will not reseal; photograph the crease line clearly. Missing shingles need an overview that shows the pattern across the slope rather than a single gap. Note the storm date and the reported wind direction so the damage pattern lines up with the event you are referencing.

Soft metals and ground collateral

While you are up there, photograph every soft metal: gutters, downspouts, fascia wraps, vents, valleys, and any aluminum or low-gauge steel. Hail dents soft metals, and those dents corroborate roof damage and help establish the storm's date and direction. Then work the ground: AC condenser fins, the mailbox, the garage door, window screens, painted surfaces. Collateral damage at ground level often makes the case for damage on the roof, and it is evidence a reviewer can read instantly. Crews that photograph only shingles leave this corroboration on the table.

The three-layer photo protocol

For every condition you intend to put in the estimate, shoot three kinds of photo:

1. Overview. A wide shot showing where on the roof this is, so a stranger can orient: which slope, which elevation, which area.
2. Detail. A closer shot showing the condition itself clearly.
3. Proof. A tight shot with scale or markup: chalk circles around hail hits, a tape across a quantity, a coin or chalk reference for the size of a bruise.

Three shots per condition feels excessive until the first time a desk reviewer denies a line item because "the photo is inconclusive." After that it feels like cheap insurance. The single dramatic photo of the worst bruise on the roof, the hero shot, is not a scope. A claim is built on the pattern across the whole roof plus the collateral. The hero shot belongs inside a proper detail-and-proof sequence, but a folder of ten hero shots with no test squares and no slope coverage is a weak package dressed up as a strong one. Coverage beats drama. Document the boring slopes.

A practical per-inspection shot list

Make the set readable by a stranger

The person who took the photos understands them. The desk reviewer three weeks later does not. Sequence and label the set so a stranger can reconstruct the whole inspection without you in the room. A simple convention works: tag each photo with the slope and the component, so "north slope, test square, 9 hits" reads at a glance. Use a camera or app that timestamps and geotags, because date and location metadata corroborate that the inspection happened when and where you say. When a reviewer can rebuild your entire inspection from the photos alone, the estimate stops depending on a phone call to explain it.

Step 4: Build the complete line-item scope

With measurements and damage documentation in hand, build the scope you would hand a cash customer. Go component by component. The goal is a list where every line has a quantity, a reason, and a photo or measurement behind it. Here is the component checklist a thorough estimator runs every time. Treat it as the skeleton and add anything specific to the property.

Several of these cannot be fully confirmed from the surface. Decking is the obvious one. You flag it now as a probable item and confirm it at tear-off with photos. That is normal. The point of the scope is to identify every probable line item, document what you can see, and set up what you will confirm later.

Quantities, not round numbers

For each line, write the actual quantity from your measurements. "Drip edge, 312 LF" is defensible. "Drip edge, all around" is not. Specific quantities tied to your measurement report move fast through review; vague quantities invite questions and delay.

Waste factors that hold up

Waste depends on roof complexity and shingle type. A simple gable with architectural shingles runs lower waste than a cut-up hip roof with multiple valleys. Use the waste factor your measurement report calculates from the actual geometry, and be ready to explain it. If you claim more waste than a simple roof generates, the geometry has to justify it, and your slope diagram is what does that.

Match the estimate to the carrier's format

The insurance estimate that goes out should, as much as you can manage, speak the same language as the carrier's estimating platform. Use the same line-item structure and the same units. This is not about gaming anything; it is about reducing friction. When your estimate and the carrier's estimate are laid out the same way, the comparison is line for line, and a reviewer can see exactly which quantities differ and why. An estimate written in your own idiosyncratic format forces the reviewer to translate, and translation is where line items get lost.

Step 5: Tie conditions to code

The strongest line items in an insurance estimate are the ones backed by code, because code is not negotiable the way opinion is. When a carrier's policy includes ordinance-or-law coverage, code-required upgrades triggered by the repair are owed. Your job during the scope is to know which code items apply to this specific roof and to document why.

Know your edition and amendments

The International Residential Code is the base most jurisdictions start from, but your county or city may be on a different edition or carry local amendments. Know which edition is enforced before the climb. The items that most often become code-driven:

• Ice barrier at eaves. In regions subject to ice, code requires an ice-and-water membrane extending a set distance up-slope past the interior wall line. If the existing roof lacks it and code requires it, that is a code item, not an optional upgrade.
• Drip edge. Modern code editions require drip edge at eaves and rakes. Older roofs frequently lack it. If the code in force requires it, installation is owed.
• Underlayment. Code may specify an underlayment requirement that differs from what is on the roof.
• Decking attachment. Some jurisdictions require re-nailing decking to a current fastening schedule during a reroof, and non-conforming or damaged decking must be brought to code.
• Ventilation. Code specifies a minimum net free ventilation area. An under-ventilated roof can require correction during the reroof.
• High-wind and impact zones. Coastal and high-wind regions carry additional fastening, sealing, and product requirements.

Write the specific code section next to each code-driven line. "Ice barrier required per [local code section], existing roof has none" is a sentence that ends an argument. A vague appeal to "code" with no citation gets waved off.

Manufacturer requirements

Beyond municipal code, manufacturer installation instructions carry weight, especially where a warranty is involved. If the manufacturer requires a specific starter, a specific underlayment, or a particular nail count in a wind zone, that requirement supports the corresponding line item. Keep the relevant instructions handy; they are public documents and they back the scope.

Stop calling code items upgrades

The most common miscategorization in the trade is treating drip edge, ice barrier, and ventilation as optional upgrades the homeowner can decline. Where code requires them and the policy carries ordinance-or-law coverage, they are required, not optional. Cite the section and call them what they are.

Step 6: Knowing which roofs to scope, and where RoofPredict fits

Everything above assumes you are already standing on the right roof. The harder problem upstream is knowing which roofs are worth climbing in the first place, and walking up with the storm and age context already in hand. That is where RoofPredict fits, and it is worth being precise about what it does and does not do, because overselling a data tool is its own kind of overreach.

RoofPredict tells roofing contractors which roofs in an area are due, house by house. For each address it produces a roof-age range estimated from aerial imagery, and it models storm physics per individual roof rather than treating a whole zip code as one undifferentiated event. The output is a ranked list of doors and routes so crews work the roofs a storm actually wore out plus the roofs simply aging out of their service life. It also enriches a contractor's own customer list with roof-age and storm signals, so the names already in your CRM get the same ranking.

For scoping, two pieces of that are directly useful.

First, the roof-age range. Age is a major driver of what a scope looks like. An older roof is more likely to lack drip edge, to be under-ventilated, to have brittle decking, and to be missing the code items modern editions require. Walking up already knowing the age range tells you which code-driven line items to look for. It is a range, not a manufacture date, and you confirm the actual condition on the roof. But starting from "this roof is probably in its later years" focuses the inspection on the items most likely to belong in the estimate.

Second, the per-roof storm modeling. Knowing the modeled hail or wind exposure for the specific address before you arrive tells you which slopes to scrutinize and which storm date to reference. A model is odds, not proof. It does not substitute for the test squares you chalk on the roof, and you should never present a model as evidence of damage in an estimate. What it does is point you at the slopes most likely to carry the damage so your physical documentation is thorough where it counts. The chalk square on the roof is the proof; the model just told you where to chalk first.

The honest limits matter. RoofPredict does not inspect the roof, does not measure your line items, does not document conditions, and has no role in whether a claim is covered. It ranks which roofs are worth your time and gives you context to scope smarter. The measurements, the photos, the line items, and the code citations are still your work, done on the roof. Used that way, it shortens the distance between "which roofs are due" and "this roof is fully documented before the adjuster arrives."

Step 7: Assemble the estimate package

A scope that lives in someone's head or a loose pile of phone photos is a weak estimate. Assemble everything into a single package you can hand over or walk through. A clean package signals that you are organized, and that changes how an adjuster engages with you. The package contains:

1. Measurement report. The third-party aerial report plus your hand-verification notes.
2. Line-item scope. The complete component list with measured quantities, formatted to match the carrier's estimating platform as closely as you can.
3. Photo set. Organized by slope and component, with test squares and hit counts visible, captioned so a stranger can follow it.
4. Code references. The specific section for every code-driven item, each with a one-line note on why it applies.
5. Conditions to confirm at tear-off. A short list of items, like decking and hidden flashing, that you are flagging now and will document with photos when the roof opens up.

That last item is underused and powerful. Telling the adjuster at the first meeting that you expect to find decking damage under the felt and will document it at tear-off pre-frames any later supplement. When it comes in with photos, it is the confirmation of something already discussed, not a surprise ask out of nowhere.

Step 8: Handle the adjuster meeting

The scope pays off in the meeting, so handle the meeting well. Be on the roof with the adjuster, not waiting in the driveway. Bring the package in printed or tablet form and let the documentation lead. When you point at a condition, you are confirming a photo and a measurement you already hold, which builds trust quickly.

A few habits separate a smooth meeting from a contentious one:

• Lead with measurements, not opinions. Open with the area and slope numbers from your report. Agreeing on quantities early removes the biggest source of friction before damage is even discussed.
• Walk every slope. Show the test squares on each one. An adjuster who sees you documented the clean slopes too tends to trust your damaged-slope documentation more.
• Name the code items plainly. Point at the missing drip edge or absent ice barrier and state the code section. Let the citation do the work.
• Flag the tear-off items out loud. Say which conditions you expect to confirm at tear-off so a later supplement is no surprise.
• Stay in your lane. Discuss conditions and the cost to restore correctly. Leave coverage decisions to the adjuster and the carrier.

If the adjuster disagrees on an item, do not argue it on the roof. Note the disagreement, keep your documentation, and address it through the proper supplement and reinspection process with the evidence in hand. A calm, documented contractor is more persuasive than a loud one, and the relationship you build across many claims with the same carrier compounds over time.

A worked example: 28-square hip roof, recent hail

Make it concrete. A two-story home, 28 squares of architectural shingle, predominantly hip with several valleys, a 7/12 main pitch with a 10/12 entry gable, gutters on all eaves, one chimney, two plumbing stacks, a kitchen vent, and a satellite dish. Recent hail event. You scope it slope by slope, and here is what the disciplined workflow produces.

Measurements. Your aerial report shows 28.4 squares of actual area. The hip-and-valley complexity calculates a waste factor higher than a simple gable would. Pitch is documented per slope, including the 10/12 gable. Story height is documented as two stories.

Damage. You chalk a test square on all six slopes. The north and west slopes, facing the storm, show eight and seven hits respectively; the south and east show two and three. The gutters on the north and west elevations are dented, and the AC condenser fins on the north side are bruised. You shoot overview, detail, and proof on every hit cluster, and you photograph the dented soft metals and the condenser collateral on the ground.

Line items. Field shingles at 28.4 squares plus geometry-based waste. Starter at eave plus rake. Ridge and hip cap at measured length, broken out from field. Drip edge at eave plus rake. Valley metal at valley length. Step and counter flashing at the chimney, photographed deteriorated. Two pipe boots and the kitchen vent, replaced. Detach and reset for the satellite dish. Steep charge on the 10/12 gable and high-roof labor across the two-story roof.

Code items. The jurisdiction's code requires drip edge at all edges and an ice barrier at eaves. The existing roof has neither. With ordinance-or-law coverage in play, both are code-driven lines, each with its section cited in the package.

Flagged for tear-off. From the attic you spotted staining near the chimney and one soft area underfoot on the north slope. You note decking replacement as a probable item to confirm at tear-off, and you photograph the attic staining now.

Now lay the scope next to a thin carrier estimate, and the structure reads as a reconciliation rather than an argument:

None of this is padding. Every line is a real cost to restore the roof correctly, every quantity is measured, and every condition is photographed or flagged. A reviewer reading this is not reading an argument; they are reading a reconciliation where each row points to a document or photo that already exists. Reviewers approve reconciliations far faster than they approve arguments, because there is nothing to dispute except the documents, and the documents are sound.

Why the order of operations matters

Notice the sequence that made this work. The measurements came before the scope. The damage documentation happened on the same visit as the measurements, not from memory later. The code research happened before the climb. The carrier comparison came last, after a complete scope existed. Reverse any of those and the estimate weakens. Try to add photos after tear-off and the conditions are gone. Build the scope from the carrier's numbers and the quantity gaps vanish. Skip the code research and the strongest line items never make the list. Order of operations is not a nicety here; it is the difference between an estimate that holds and one that collapses.

What pros get wrong

Even experienced estimators leak money in predictable places. Watch for these.

Working off the carrier's measurements

If your quantities come from the carrier's estimate, you have already conceded the biggest category of difference. Always carry your own independent measurement report. It costs a little and it is the highest-return document in the process.

Treating code items as optional

Drip edge, ice barrier, and ventilation get miscategorized as upgrades the homeowner can decline. Where code requires them and the policy carries ordinance-or-law coverage, they are required. Cite the section and stop calling them upgrades.

Skipping the undamaged slopes

Reps photograph the slope that looks hammered and skip the rest. Then the carrier approves a partial repair and you cannot prove the others. Chalk a test square on every slope, every time, even the ones that look clean. Slope-by-slope coverage is what supports a full replacement where the damage warrants it.

Vague photos with no scale or context

A close-up of a bruise with nothing for scale and no indication of which slope it is on is nearly useless to a desk reviewer. Overview, detail, proof, every time. Chalk the hits and put a tape in the frame for quantities.

Forgetting collateral and soft metals

The dents in the gutters, the AC fins, the mailbox, and the window screens corroborate the storm and its direction. Crews focused only on shingles leave this evidence on the ground.

Overreaching on the damage

Calling foot traffic, blistering, or normal granule loss "hail" to inflate a count does the opposite of what the rep hopes. A reviewer who catches one bad call discounts the entire package, including the slopes where the damage is real. Document honestly. The credible scope is the persuasive one.

No tear-off documentation plan

The decking item is the most common second-round addition and the easiest to lose. If nobody photographs the rotted deck before the new wood goes down, there is no basis for it. Build the tear-off photo step into production so it happens every time, not only when someone remembers.

Confusing storm odds with damage proof

Storm models and hail maps point you at likely damage. They do not prove damage on a specific roof. The proof is always the physical documentation: the marked test square, the dented metals, the photographed conditions. Lead with the physical evidence and let the storm context support it, never the reverse.

Letting the scope and the photos drift apart

A scope listing thirty line items with a photo set covering twelve of them is a credibility problem. The reviewer notices the eighteen items with no visual support and discounts the whole package. Keep them aligned: if a line is on the scope, there should be a photo, a measurement, or a code citation behind it. If you cannot back it, either you have not finished documenting or it does not belong.

Edge cases worth planning for

Layered roofs

Two or three layers change the tear-off line and sometimes the decking beneath. Photograph the layers at a cut edge before tear-off. Multiple layers are a legitimate labor line and easy to prove with one clear photo.

Discontinued or unavailable shingles

If the existing shingle is discontinued and a repair cannot reasonably match, that supports replacement of the affected slopes rather than a spot repair, depending on the situation and the policy. Document the existing product and note its availability.

Solar arrays

A roof with solar needs detach and reset by a qualified installer, which is a real and often significant line. Document the array, the panel count, and the requirement for specialized labor. Do not let it be assumed away.

Steep and complex architecture

Turrets, multiple dormers, and very steep sections carry labor that a flat per-square number ignores. Photograph and measure these features specifically; the labor modifiers exist in the platforms for a reason.

Multiple roof systems on one property

A home with an attached low-slope porch or addition needs a different system on that section, with its own line items. Do not let a low-slope section get scoped as if it were the same shingle field as the steep sections.

Recent prior repairs

Mismatched patches or recent partial work affect how pre-loss condition is assessed. Document them up front so they do not complicate the estimate later.

Detached structures

Garages, sheds, and gazebos with their own roofs are easy to forget when the focus is the main house. If they took the same storm, scope them with the same discipline and document them separately.

A repeatable field checklist

Reduce all of it to a checklist your team runs every time. Consistency is what makes the estimate predictable across different inspectors.

Before you climb:

• Order the aerial measurement report
• Pull the local code edition and reroof requirements
• Review the storm context and roof-age range for the address
• Confirm the structures, prior repairs, and intent with the homeowner
• Set up the ladder and fall protection properly

On the roof:

• Verify measurements against the report; note discrepancies
• Document pitch by slope and number of stories
• Chalk and photograph a test square on every slope with hit counts
• Distinguish hail from mechanical and age-related marks honestly
• Document wind damage separately: creases, tears, missing shingles
• Photograph every penetration, wall flashing, and valley
• Photograph all soft-metal and ground collateral
• Note and photograph layers, sags, soft spots, and staining
• Check the attic if accessible for staining and ventilation

Building the scope:

• List every component with measured quantity and reason
• Break out all accessories the carrier tends to bundle
• Add steep and high labor where pitch and stories warrant
• Cite the code section for every code-driven item
• List detach-and-reset items
• Flag conditions to confirm at tear-off
• Format the estimate to match the carrier's platform

The package:

• Measurement report plus verification notes
• Complete line-item scope
• Organized, captioned photo set by slope and component
• Code references with one-line justifications
• Tear-off confirmation list, pre-framed with the adjuster

At tear-off and after:

• Photograph decking and hidden conditions before covering
• Document any new unforeseen condition with overview, detail, proof
• Submit any supplement as a structured comparison to the carrier estimate

Staying inside your lane

A closing note on professionalism, because it is what protects your business over the long run. Your role is to document conditions accurately and produce a correct estimate of the work required. You do not handle the claim, you do not decide coverage, and you do not promise the homeowner any particular financial outcome. The homeowner files the claim and owns the decisions about it; the insurer assesses coverage. That division is not a technicality. In many states, a contractor who negotiates or adjusts a claim for a fee, interprets the homeowner's policy, or represents the homeowner against the carrier is engaged in unlicensed public adjusting, which carries real legal exposure.

Keep the language clean. Talk about conditions, measurements, code requirements, and the cost to restore the roof correctly. The things to avoid saying are specific and worth learning as a list:

• Do not promise a claim will be approved or that a carrier will pay a particular amount.
• Do not say you will handle, manage, negotiate, or fight the claim, or beat the adjuster.
• Do not interpret the homeowner's policy or tell them what their coverage means.
• Do not say anything about waiving, absorbing, covering, or eliminating the deductible.
• Do not advertise or imply a "free roof."
• Do not present a storm model or hail map as proof of damage on a specific roof.

None of that restricts the actual work. You can inspect thoroughly, document every condition, write an accurate estimate aligned to the carrier's pricing, state the facts about your own scope to the carrier, and hand the homeowner a clean package they can file with. That is the entire job, and it is plenty.

The roof tells the truth if you document it properly. Scope it like an estimator, photograph it like the reviewer will never see it any other way, tie every line to a measurement or a code section, and the insurance estimate stops being a battle. It becomes a statement of fact that holds up on its own.

FAQ

What is the difference between scoping a roof and just inspecting it for a sale?

A sales inspection decides whether there is a claimable event and signs the homeowner. A scope is a complete, quantified description of everything required to restore the roof to pre-loss condition, built as if you had to hand a cash customer an exact line-by-line number. The scope produces the insurance estimate; the sales walk only gets the contract. Conflating them is how line items get lost, because the rep never measures or documents at the level the estimate needs.

What measurements do I need before I scope a roof for an insurance estimate?

Total roof area in squares, slope-by-slope area, pitch of every slope, number of stories, and linear footage of ridge, hip, valley, eave, and rake. A third-party aerial measurement report supplies most of this, and you verify the key numbers by hand. Almost every line item is a function of one of those measurements, so accuracy here is what makes your quantities defensible against a thin carrier estimate.

How do I document hail damage so it holds up in a desk review?

Chalk a test square, typically ten feet by ten feet, on every slope, circle and count the hits inside it, and photograph the marked square with the count. Shoot three layers per condition: an overview showing where it is, a detail showing it clearly, and a proof shot with scale or markup. Document the undamaged slopes too, photograph soft-metal and ground collateral, and use a timestamped, geotagged camera so the metadata corroborates the inspection.

Which line items get bundled away or forgotten in roof estimates?

Starter strip, ridge and hip cap counted separately from field shingles, drip edge, ice-and-water barrier, step and counter flashing, valley metal, pipe boots and vents, ventilation, detach-and-reset of solar or satellite, and steep and high labor charges. Build your own complete component scope so each appears with a measured quantity and a reason rather than folded into the field shingle number.

How do code upgrades become line items on an insurance estimate?

When the carrier's policy includes ordinance-or-law coverage, code-required upgrades triggered by the reroof are owed. Common examples are ice barrier at eaves, drip edge at all edges, ventilation brought to minimum net free area, and decking re-fastening or replacement to current code. Identify the local code edition and cite the specific section next to each code-driven item. A citation turns a maybe into a requirement and ends the argument.

How is wind damage documented differently from hail damage?

Wind damage shows up as creased shingles, torn or missing shingles, and unsealed tabs, concentrated on the windward slopes and along edges and ridges where uplift is strongest. A creased shingle was lifted and folded by wind and will not reseal, so photograph the crease line clearly, and shoot missing-shingle areas with an overview that shows the pattern rather than one gap. Reference the storm date and reported wind direction so the damage pattern lines up with the event.

How do I handle decking damage I cannot see until tear-off?

Flag it during the first inspection and pre-frame it with the adjuster by saying you expect to find decking damage under the felt and will document it at tear-off. Then build a tear-off photo step into production so the rotted or soft decking is photographed with overview, detail, and proof shots before the new wood covers it. A decking item with clear pre-cover photos is routine; one with no photos has no basis.

Should I use the carrier's measurements to save time?

No. Working from the carrier's measurements concedes the largest category of difference, which is quantity error. Always carry your own independent measurement report. When your quantities come from a third-party document, a dispute becomes a comparison of two documents rather than your word against the adjuster's, and the more detailed document usually prevails.

Where do roof-age and storm data fit into scoping?

Knowing the roof-age range and the modeled storm exposure for a specific address before you climb tells you which code-driven items to look for and which slopes to scrutinize first. Age is a range, not a manufacture date, and a storm model is odds, not proof. You still confirm actual condition on the roof and document damage with chalked test squares and photos. The data focuses the inspection; the physical evidence proves it.

What language should I avoid so I stay compliant when scoping insurance work?

Stick to documenting conditions and estimating the cost to restore the roof correctly. Do not promise a claim will be approved or that a carrier will pay a specific amount, do not say you will handle or negotiate the claim, do not interpret the homeowner's policy, do not say anything about the deductible, do not advertise a free roof, and do not present a storm model as proof of damage. The homeowner files and owns the claim; the insurer decides coverage. Clean, condition-focused language keeps you out of unlicensed public adjusting territory.