Privacy choices

Choose what we may use.

The site works without optional tracking. Your choice is saved on this device and can be changed here anytime.

Necessary

Runs the site, protects forms, and remembers this privacy choice.

Always on

Claims & supplements

Roofing Insurance Claims and Supplements: A Lawful Operations Playbook

Build a roofing supplement around the work your crew documented. Reconcile measurements and estimate versions, give every disputed item its evidence, and put the next decision with the person authorized to make it.

The short answer

A roofing supplement requests review of documented scope or price differences from the current estimate. Compare the current versions line by line, reconcile measurements, and attach dated photos and applicable technical sources to each proposed change. The contractor explains its own work and bid; coverage and settlement questions go to authorized parties. Track the submitted version, receipt, item-level response and next action so the file keeps moving.

Find roofs that fit

What matters most

  • Compare the 2 current estimate versions item by item before proposing additions.
  • Give every disputed item 1 evidence trail that connects its location and quantity to dated records.
  • Texas and Florida distinguish explaining a contractor's bid from acting as a public adjuster for the policyholder.
  • Track 4 operating measures alongside collected job economics: file quality, cycle time, information requests and revisions.

A finished roof can leave an unfinished payment file: photos in three places, an estimate that differs from the carrier’s version, and no record of who owes the next answer. The office needs to show what changed and where the evidence sits.

This guide covers the office side of claims: how to build a file that answers questions before they’re asked, stay inside what a contractor is allowed to do, and keep the money moving.

Ground Control by PorchRocket serves the earlier prospecting step: finding homes and commercial buildings that fit your work. Carry the property identity into your inspection and estimating records so the office can trace each document to the right roof.

What is a roofing supplement?

A contractor requests further review by submitting evidence of work or pricing that differs from the current estimate, with each proposed change tied to the property record.

Classify the difference before drafting anything:

Difference type Example Primary evidence Normal owner
Measurement/quantity Ridge, valley, eave, facet, area, layer, waste differs Field/aerial measurement, diagram, calculation Contractor estimator
Omitted operation/component Scope contains an operation absent from comparison estimate Labeled photos, scope note, estimate line item Contractor estimator
Code/technical requirement Adopted rule or manufacturer instruction affects work Exact source/version/jurisdiction/applicability Qualified technical/permit owner
Price/labor Contractor price or required labor differs Contractor bid, current support, job facts Contractor/estimator
Hidden condition/change Decking or other condition becomes observable during work Before/during photos, quantity, change record Production + estimator
Duplicate/unsupported Same work already included or not observed Reconciliation review Internal QA: remove/correct
Policy/coverage dispute Whether the policy covers an item, cause, limit, exclusion, or settlement Policy and legal/adjusting analysis Insured, carrier, licensed public adjuster, counsel as applicable

This taxonomy prevents one “supplement team” from treating every discrepancy as the same job. The contractor should document its own work and price. Start with dated observations, then show the quantity calculation and proposed construction method. Policy interpretation, representing an insured, or negotiating a settlement can be regulated activity.

The phrase “maximize every claim” is a poor operating objective. It rewards submitted dollars before anyone checks the evidence. A better objective is: submit an accurate contractor record once, respond to the question, and preserve the path to resolution.

Assign each claims task to a named person with the authority to perform it, then record the evidence that person needs. An estimator can explain a quantity calculation. A coverage decision belongs elsewhere. Record the handoff instead of giving every question to a general “claims specialist.”

The exact legal boundary depends on the state and facts, but a conservative operating map is:

Work Contractor operations role Route outside contractor authority when
Observe and photograph accessible conditions Record observations, locations, limitations, and dates Engineering/cause/safety determination requires another qualification
Measure and scope contractor work Prepare dimensions, quantities, operations, construction method, and price Question is what policy covers or what settlement should be
Explain contractor bid Explain line items, quantities, method, and supporting sources Communication becomes representation/negotiation for the insured
Organize homeowner-provided claim identifiers/documents Index and route under authorized process Identity, privacy, or authority is unclear
Compare contractor scope to another estimate Identify factual differences and provide contractor support Difference is purely policy interpretation
Respond to a request for more contractor evidence Supply accurate property-specific contractor records Request asks for legal/coverage position or insured representation
Decide whether/how to file a claim Do not decide for the homeowner Homeowner should consult insurer and authorized adviser
Negotiate settlement or coverage Outside ordinary contractor scope absent proper authority/licensing Route to insured, insurer, licensed public adjuster, or counsel

Create a file-level authority record

Before outbound communication, record:

  • homeowner/customer and property identity;
  • contractor agreement and work scope;
  • insurer/claim identifiers only when appropriately provided;
  • who authorized the contractor to send which documents;
  • approved sender/recipient/channel;
  • states/jurisdictions implicated and the policy owner for role review;
  • whether a public adjuster, attorney, engineer, or other adviser is involved;
  • communication boundaries and required routing;
  • expiration or event that requires renewed authority review.

Do not assume a signed construction agreement appoints the contractor to represent the homeowner in an insurance settlement. Do not let a CRM checkbox called claim=yes trigger communications before the authority record passes.

Separate the contractor fact record from the coverage record

Keep observations and measurements beside the contractor scope. Attach the proposed construction sequence and priced material specification. Add the invoice and completion evidence as work progresses. Store policy documents with the claim correspondence and payment record. Give each record a named owner.

Apply different access. Field crews may need the approved scope and capture checklist, not policy documents or payment details. Estimators may need comparison estimates and property evidence, not every free-text customer note. A receptionist should route a coverage question, not read an inferred answer from the job record.

Use a communication boundary label

These illustrative statements show how to label a draft:

  • observed contractor fact: “Photo F2 shows the pipe boot at the rear slope on the inspection date.”
  • contractor calculation: “The diagram totals 246 linear feet under the stated measurement method.”
  • contractor bid/position: “Our proposal includes removal and replacement of three boots at the listed price.”
  • external source/application: “The cited document is [version]; applicability was reviewed by [qualified role].”
  • homeowner/carrier statement: attributed, dated, and not converted into contractor fact;
  • coverage/legal/settlement question: routed to the authorized party.

This classification helps a drafting system stay within the contractor’s record and makes human review faster.

How can a roofer get more out of claims without crossing the line?

Reduce avoidable rework by giving each requested change its supporting record and routing each decision to the person authorized to make it. Track missing evidence and staff hours alongside collected job profit. A larger submitted amount alone does not show that the operation improved.

I would start with the waiting files. For each one, identify the missing document or decision and who must supply it. Lock the estimate version and record the next due date. Otherwise an experienced estimator can spend another afternoon reviewing a packet that has not changed.

Match the operating model to claim volume and complexity

Contractor situation Right first control Economic outcome Main risk
Occasional insurance-related roof One file checklist, named estimator, outside authority path Checked first packet and avoided reinspection/rework Building a claims department around rare files
Growing mixed retail/restoration roofer Standard chronology, evidence QA, item comparison, status queue Contractor-controlled cycle time and collected job gross profit One general office queue hides specialized review
Restoration-heavy contractor Dedicated estimator/document team with authorized communication review First-pass completeness, supported discrepancy resolution, cash timing Incentives tied only to submitted or “approved” dollars
Multi-branch restoration operator Common file states, version rules, source standards, jurisdiction matrix, branch accountability Comparable quality/aging/economics by branch and case mix Central team applies one state/process rule everywhere
Contractor seeking a supplement vendor Closed-file replay, role/licensing diligence, export/exit test Quality-adjusted cost per mature file Vendor behaves as an unauthorized representative or owns the file history

An occasional-claim roofer may need disciplined field capture and a qualified reviewer, not software that promises to “find money.” A restoration-heavy company may justify a dedicated queue, but specialization does not widen authority. As volume grows, assign separate drafting and approval duties. Keep the jurisdiction review and version history with the file. Count every eligible file in the performance report.

Measure economics without calling estimate delta revenue

Suppose a 100-file mature cohort previously required 280 avoidable staff hours of rework and 20 reinspections. A redesigned workflow uses 120 avoidable rework hours and 8 reinspections. Assume $42 per fully loaded rework hour and $165 per incremental reinspection. The reinspection allowance includes its labor and travel, with that labor excluded from rework hours so no cost is counted twice. The avoided operating cost is:

(280 − 120) × $42 + (20 − 8) × $165 = $8,700

Assume setup and software cost $2,000, with another $3,000 for review of those 100 files. Total workflow cost is $5,000. The remaining operating contribution is $8,700 minus $5,000, or $3,700. Break-even requires $5,000 in avoided costs. Replace the assumed rates with your loaded costs and count only avoidable events; one avoided reinspection does not earn credit for the entire job.

Any supported additional work needs a longer bridge:

supported discrepancy → resolved item → customer-authorized scope → produced work → invoice → collection → realized gross profit

Only the realized gross profit reasonably changed by the documentation workflow belongs in incremental contribution. Compare fixed or staged cohorts with similar case mix where possible. Show files still open and amounts not mature. A company can improve quality and cash timing even when raw “approval rate” falls because it stopped submitting unsupported items.

The value of one well-matched commercial account

Say a commercial roofer targets 120 warehouse roofs. Assume a Ground Control price of $12 per building, or $1,440, plus $1,560 covering all campaign labor and travel, including proposal preparation. Total customer acquisition cost is $3,000 if one account signs. The funnel assumes 30 conversations from 120 properties (25%), 10 site meetings from those conversations (one-third), 5 proposals from those meetings (50%), and 1 signed account from those proposals (20%). That is 1 signed account per 120 properties.

Assume the signed project covers a 40,000-square-foot roof at the roofer’s quoted $6.15 per square foot: $246,000 of revenue. A 30% job gross margin after all production costs yields $73,800. Assume the account also buys a separate $3,200 inspection and maintenance agreement in each of the following 5 years, with 35% gross margin and no churn. That adds $5,600 in gross profit ($3,200 × 35% × 5). No other work, residual value or discounting is included.

Customer lifetime value here means the account’s gross profit over the initial project and those 5 service years: $73,800 + $5,600 = $79,400. Lead-list ROI subtracts acquisition spending before dividing by that spending: ($79,400 − $3,000) ÷ $3,000 = 2,546.67%, rounded. The gross-profit-to-acquisition-cost ratio is 26.47:1, rounded.

Case Assumptions changed from the base Account gross profit Acquisition spend Net return after acquisition spend ROI
Low Project margin falls to 20%; no follow-on agreement $49,200 $3,000 $46,200 1,540%
Base 30% project margin; 5 service years at 35% margin $79,400 $3,000 $76,400 2,546.67%
High Project margin rises to 35%; same service agreement $91,700 $3,000 $88,700 2,956.67%

Each case holds the funnel at one signed account. With no signed work, the campaign loses $3,000. I would start with a territory the estimator can inspect promptly, then compare signed account gross profit with the full outreach bill before expanding. Use the lead-list ROI calculator to substitute your own job values and margins.

What documentation belongs in a roofing claim or supplement packet?

Give the reviewer a one-page index and item-level evidence links, backed by reconciled measurements, an itemized estimate and the history of what was sent.

The NAIC’s homeowners claim guidance tells consumers to notify their insurer promptly after deciding to file. It recommends photos or video and a damaged-property list. Retain receipts too. Keep those records available for the person reviewing the repair scope.

Packet index

  1. Cover/index with property, insured/customer, claim/reference (when appropriately provided), contractor job ID, date of loss as reported, not inferred, and packet version.
  2. One-paragraph contractor purpose: what document or scope difference is being presented.
  3. Discrepancy table with item, location, compared values, contractor position, and evidence link.
  4. Inspection/observation record with date, inspector, access method, limitations, weather/site conditions as relevant.
  5. Photo report in a consistent sequence.
  6. Measurement report/diagram and quantity calculations.
  7. Current contractor scope and itemized estimate.
  8. Targeted code, manufacturer, permit, technical, invoice, quote, or other support.
  9. Prior estimate/response only where needed for comparison.
  10. Communication/version log and requested next action.

Keep generic manufacturer literature and code excerpts out of the review packet unless they support a specific item. Put the applicable excerpt beside the item and identify its source. Preserve the full document separately.

Photo discipline: context to detail

The IBHS/RICOWI roof survey practices call for preparation using roof records and storm information. They recommend documenting observed conditions and comparing earlier records when available. For your packet, use a repeatable photo sequence:

  • property and all relevant elevations for orientation;
  • full roof planes/facets and access/inspection limitations;
  • mid-range view locating the component within the facet/elevation;
  • close view of the observed condition;
  • scale/measurement reference when size or quantity matters;
  • component label and direction/facet reference;
  • temporary work before/after, where applicable;
  • tear-off/hidden condition before it is covered;
  • installation stages and completed work;
  • metadata/source preserved, with any edit/annotation distinguishable from the original.

A close-up of a mark without orientation cannot show where it is. An overview without detail cannot show the observed condition. A measurement photo without a readable starting point cannot establish quantity. Captions should state what is visible and where, not infer cause or coverage beyond the observer’s qualifications.

Photo-resolution and metadata requirements

Get the receiving party’s written image requirements and retain them with the packet version. The NAIC and RICOWI sources cited here do not prescribe a single resolution for every supplement. Use a functional export check: the reviewer must be able to locate the component and read its scale. The condition must remain visible at the report’s exported size.

Keep originals separately from annotations. Retain source files when an export strips metadata. Device clocks and location fields can be wrong, so cross-check them against the inspection record and property diagram. A close-up without orientation needs a wider view. If work has already covered the condition, document the evidence gap rather than infer the missing observation.

Measurement and quantity discipline

Put the field measurements beside the aerial or drone report. Reconcile them with the sketch before adopting estimate quantities. Confirm the structure and facet count. Then verify pitch and edge lengths. Match penetrations and flashings to the diagram. Keep measured area separate from layers and material waste; explain any manual adjustment.

Calculate waste for the roof geometry and selected material. Show how the course layout and package rounding affect the order. Keep three quantities separate: measured installed area; material to purchase; the quantity adopted in the estimate.

Line-item notes that can be reviewed

Each disputed/additional contractor item should answer:

  • what: material, operation, labor, equipment, or fee;
  • where: facet/elevation/room/component;
  • quantity/unit: and calculation source;
  • why in contractor scope: observed condition or construction sequence;
  • support: photo/diagram/code/manufacturer/quote/invoice reference;
  • version/date: current estimate and source;
  • relationship: omitted, quantity difference, price difference, duplicate, alternative, or policy question.

“Per code” does not tell the reviewer what to check. Record the jurisdiction and adopted edition, then identify the exact section and the person who confirmed its applicability. For a manufacturer instruction, identify the product and document revision with the relevant page. Check local adoption before using a code reference.

File and version convention

Use stable names such as:

JOBID_document-type_location_YYYY-MM-DD_v03.ext

Keep originals immutable. A packet manifest should record file ID/hash or stable repository ID, source, capture/upload time, author, current/obsolete status, and packet inclusion. Mark superseded estimates instead of deleting the history. Email attachments named IMG_4382 and final-final2 are not a claims system.

A defensible roofing file chronology

Build one event ledger from first report through closeout, with a dated source and responsible person for each entry. Chronology separates what was known at each point from what was discovered later and prevents a revised estimate from masquerading as the original scope.

Use fields such as:

Field Meaning
event ID and timestamp Stable event and when it occurred; distinguish occurrence from entry time
actor and role Homeowner, contractor employee, vendor, carrier representative, adviser, system
event type Call, inspection, photo capture, estimate, document receipt, submission, response, work, payment
source artifact Recording, email, photo ID, report, estimate version, signed document, system log
attributed statement Who said what, without converting it into verified fact
contractor observation/decision Authorized contractor record and owner
related version Scope, packet, estimate, measurement, or communication version
next action/owner/due date Operational consequence
correction/supersession Link to the event that corrected or replaced it

Do not backdate a new observation to the reported date of loss. Keep the homeowner-reported loss date separate from weather records. Record inspection and discovery dates in their own fields. Hidden decking observed during tear-off belongs at the date and stage it became observable, linked to before/during evidence.

Reconcile the chronology before every major submission

Ask:

  1. Do identifiers and parties remain consistent?
  2. Is every estimate compared against the correct prior version?
  3. Did any photo or measurement arrive after the scope assertion it supposedly supports?
  4. Are changes explained by new observation, corrected error, price/version update, or customer decision?
  5. Are carrier/homeowner statements attributed accurately?
  6. Has any outbound promise been superseded or contradicted?
  7. Does the next action follow the latest accepted event?

A chronology defect can be more damaging than a missing page because it makes the reviewer question which record is current.

How do you find missing or mismatched estimate items?

Compare the contractor’s observed scope with the other estimate line by line and classify the difference. Do not begin with a canned list of “commonly missed” items and add everything. A list can prompt inspection; only conditions and applicable requirements support an item.

Worked discrepancy table

For an illustrative shingle reroof, separate quantity corrections from unsupported additions before drafting the request. LF means linear feet.

ID Contractor scope Compared estimate Classification Evidence Action
D-01 246 LF eave flashing 118 LF Quantity difference Diagram A eave totals; photos E1 to E8; local applicability note Review 128 additional LF (246 minus 118)
D-02 Replace 3 pipe boots 1 boot Omitted/quantity Labeled P1 to P3 photos and roof diagram Review 2 additional boots (3 minus 1)
D-03 Generic “code upgrade package” None Unsupported/too broad No exact adopted source or item mapping Remove; research requirements
D-04 Ridge cap Included in another assembly line Potential duplicate Estimate note and line mapping Do not add; clarify inclusion
D-05 Whether wear is covered Not included Policy/coverage question Contractor can document observation only Route to insured/carrier/authorized adviser

A reviewer can accept D-01 while asking for more evidence on D-02. Remove D-03 unless research supports a specific requirement. D-04 needs an inclusion check; D-05 belongs with an authorized adviser.

Treat price, quantity, and coverage as different disagreements

If both scopes include 30 squares but unit prices differ, that is not an omitted-scope dispute. If one uses 30 and another 33 because waste is treated differently, reconcile the calculation. If both agree the work exists but the question is whether the policy pays it, the contractor can explain the bid while the coverage question remains with authorized parties.

Mixing the three produces vague “underpaid” language that does not tell a reviewer what can be resolved.

Version technical support with the job

Identify each technical document by publisher and title. Save the edition or revision and exact section. Record when it was retrieved. Name the reviewer who confirmed that it applies to this jurisdiction or product. Save the full source or stable official link under the document policy. A search snippet or unlabeled screenshot is not enough.

When code adoption or product instructions change, do not overwrite the source attached to an older packet. The file must show what source the contractor used and why it applied at the relevant time. Explain a later correction in a new version.

Run a red-team review before submission

Assign someone other than the primary drafter for higher-risk or material files. The reviewer tries to disprove the packet:

  • Is the property/structure/claim correct?
  • Is any observation inferred rather than shown?
  • Does each quantity reconcile?
  • Is a line duplicated or bundled elsewhere?
  • Is the source applicable to this jurisdiction/product/work?
  • Does any sentence imply cause, coverage, entitlement, or representation beyond authority?
  • Does the requested action match the evidence?
  • Are obsolete versions or irrelevant pages likely to confuse the recipient?
  • Can the contractor answer likely follow-up questions from its own record?

Record the reviewer’s corrections before approving the outbound version.

How should a roofing contractor read an Xactimate estimate?

Start with the property and price-list basis in an Xactimate report, then check the diagram and individual operations before reconciling the totals. Confirm the current version and report options before comparing the contractor’s observed and priced work. Ask for line detail when a summary does not explain the difference.

Ask for the full current report with its version. The official estimate-report documentation lists selectable sections, including line details and saved-version comparisons. Summaries and audit history are separate options; sketches can appear at the end. Check the report selection before concluding that missing information was never entered.

Read the file in this sequence:

Pass What to inspect Question the contractor must answer Common reading error
Identity Insured/customer, property, claim/job ID, estimator, company Is this the correct property, structure, file, and current estimate? Comparing documents from different structures or versions
Time and price basis Estimate date, price-list code/region, loss and inspection dates What dated market basis and job chronology does this estimate use? Treating every price difference as omitted scope
Sketch/grouping Roof facets, elevations, rooms/areas, dimensions, pitch and annotations Do the diagram and area groupings describe the structure? Reading line quantities before checking their geometry
Scope lines Category/selector or description, activity, location, note What exact physical operation is included? Matching by a short line name while ignoring included components
Quantity and unit Squares, square feet, linear feet, each, hours, or another unit Does the quantity reconcile to a named source and calculation? Comparing different units or waste treatments as if they were equal
Unit-price detail Labor, material, equipment, productivity, yield, minimums or supporting events where shown Is this a price-basis question or a scope question? Assuming the unit price contains, or excludes, an operation without checking
Add-ons and summaries Tax, permits where entered, overhead/profit treatment, category and room recap What is included in each subtotal and where is it applied? Adding recaps that exclude items or double-counting an add-on
Depreciation and totals Replacement-cost, depreciation, actual-cash-value and related columns or summaries where present What is estimate math, and what depends on policy or carrier handling? Treating recoverability, deductible, or coverage as a contractor determination
Evidence and history Photos, notes, source documents, saved-version comparison, audit Can every material change be traced to evidence and a reviewer? Working from an obsolete PDF after the live estimate changed

The line-by-line reading unit is:

location + component + operation + quantity + unit + adopted price basis + evidence + version

“Shingles” is not a full comparison. Removal, preparation, installation, accessory/detail, access/protection, and disposal may appear separately, inside an assembly, or in a note. The contractor should map the physical work first and only then map the estimate language. A text-matching tool can suggest pairings, but it cannot determine that two differently worded operations are equivalent.

Check the arithmetic after the scope is understood. A simple line often resembles quantity × unit price, but the final report may also reflect taxes, depreciation, overhead/profit treatment, rounding, minimums, or other configured factors. Use the displayed detail and component information rather than recreating the total from memory. If the math still does not reconcile, identify the page and line in that report version. Record the expected value beside the displayed value and assign a reviewer.

Why can Xactimate pricing differ from a roofer’s cost?

A local price list describes market research; a roofer’s bid also reflects the property’s access, construction method and dated supplier quotes. Identify the source of each price difference and support the adopted amount. Neither a price list nor a contractor invoice automatically decides what a policy covers or what another party must accept.

Verisk’s published pricing methodology describes localized price lists for more than 460 areas in the United States and Canada. Research draws on suppliers and contractors as well as estimates, transactions and other submissions. ZIP Codes are grouped into markets. The publication recognizes that access and job complexity affect costs. Estimators can modify prices for a particular job.

That leads to a disciplined review. Classify the difference before writing a response:

Difference class Example Supporting record Do not say
Wrong basis Wrong ZIP/market, date, or price-list version Estimate cover, property address, dated price-list record “Xactimate is always wrong”
Scope or assembly An operation is absent, duplicated, or assumed included Physical scope map, component detail, line note, field evidence “The total is low, so add lines”
Quantity Area, length, count, layers, or waste calculation differs Measurement report, field diagram, formula, photos “Use our number” without a source
Job condition Access, height, complexity, protection, schedule, staging, or custom work changes cost Property-specific plan, time record, quote, invoice, photos “Every roof needs this charge”
Market movement Supplier or labor conditions changed after the list basis Dated comparable supplier quotes, invoices, wage or equipment support An undated screenshot or one unrelated invoice proves the market
Company bid The contractor prices its scope differently Current signed or proposed bid with inclusions and exclusions The contract price automatically equals covered loss
Coverage/settlement Parties agree on cost but dispute what is payable Route to the insured, carrier, public adjuster, counsel, or other authorized party Recast a policy dispute as a software correction

Use the price-list date and region shown in the estimate. Open line-item or assembly detail where available. Inspect the assembly’s labor and equipment allowances. Check its material yield, waste and supporting events before adding costs. Then compare the contractor operation on the same unit. To support one line with an invoice, identify the relevant quantity and share of cost. Preserve its scope and date.

For job-specific support, preserve:

  • supplier or subcontractor identity and service area;
  • quote or invoice date and validity window;
  • property/job association;
  • product, grade, quantity, unit, freight, tax, and return terms;
  • labor operation, crew composition, hours, equipment, and access condition where relevant;
  • whether the number is a quote, incurred cost, allowance, or final invoice;
  • any rebate, credit, package rounding, minimum, or shared cost;
  • the person who reviewed and adopted it.

Avoid cherry-picking. State when an estimate uses incurred material cost instead of a published price. Check freight and tax separately so the same cost does not appear in both the invoice allocation and another estimate line. If an item is custom or rare, explain why the standard line does not describe it. For a concern that spans multiple jobs, the pricing methodology describes a verification-request process. Preserve the request and response with the pricing record.

Ask for review of a specific line. Show the proposed quantity or price beside the current figure and attach dated support. “Our bid is higher” may be true, but it does not explain why.

How do you build a supplemental roofing estimate from documented differences?

Lock both estimate versions, reconcile the roof geometry, and write a separate explanation for each supported change in scope or price. Build the scope from field evidence before selecting estimate lines. Record who approved the version sent.

Use a gated workflow:

  1. Freeze identity and version. Confirm property, structure, job/claim identifiers, estimate received date, comparison version, contractor version, and price-list basis.
  2. Build the contractor scope independently. Use the inspection, measurement, work plan, contract, and production observations. Do not simply copy the other estimate and add familiar lines.
  3. Reconcile geometry first. Area, facets, edges, penetrations, layers, pitch, height, and units affect many later lines.
  4. Normalize operations. Map removal, preparation, installation, accessory/detail, access/protection, disposal, and closeout by component and location.
  5. Classify each difference. Included, partial quantity, omitted, alternative, duplicate, price basis, unsupported, or policy/authority question.
  6. Capture concealed conditions promptly. Before work covers decking, fasteners, layers, flashing interfaces, or another newly visible condition, create context and detail photos, measurements, notes, quantity, time, and owner. Follow safety and the job’s communication requirements.
  7. Attach applicable support. Use field evidence first, then exact measurement, manufacturer, code, permit, supplier, labor, or technical sources where relevant.
  8. Write an item-level explanation. State the observed fact, compared treatment, requested contractor-scope treatment, quantity math, price basis, and attachments.
  9. Remove duplicates and assumptions. Check assemblies, notes, waste, minimums, taxes, add-ons, and prior accepted changes.
  10. Run authority review. Contractor estimators verify work and price. Qualified technical owners verify code or manufacturer applicability. Authorized professionals handle coverage, representation, or legal questions.
  11. Export a full current packet. Include the index, estimate, discrepancy schedule, diagram, evidence map, source pages, communication request, and version history.
  12. Track the response by item. Accepted, partially accepted, more information requested, not accepted with reason, routed elsewhere, withdrawn, or superseded are distinct states.

An item record looks like this:

Field Example structure
Difference ID RF-017
Location/component South slope, pipe penetrations P-1 to P-3
Contractor operation Replace documented pipe boot during reroof scope
Comparison treatment One boot shown; three documented
Classification Quantity difference
Adopted quantity/unit 2 additional each, tied to diagram P-1 through P-3
Price basis Current contractor estimate line and dated list/job support
Evidence Context C-04, detail D-21/D-22, roof diagram, inspection note
Boundary Contractor scope and price; no coverage statement
Reviewer/version Initials, date, contractor estimate v4
Requested next action Review the two-unit quantity difference

Make it possible to decide each item separately. One quantity can be accepted while another awaits a clearer source. Mark a duplicate for removal and send a coverage question to its authorized owner. Broad prose such as “many items were missed” creates extra work for every party.

Compare like roof systems and file types when reviewing performance. A complex metal roof creates a different documentation workload from a simple shingle replacement.

Evidence for roof-specific estimate operations

Give each proposed roof operation a dated location record and a quantity calculation, then add the technical source that explains the construction requirement. Geometry, height, material, access, code, and concealed conditions change what must be documented. They do not create automatic Xactimate additions simply because a prompt appears on a checklist.

Review area Property-specific evidence Reconciliation question Boundary
Pitch, steepness, height Labeled facet diagram, pitch method, elevation/height, access photos, safety/work plan Which facets and operations are affected, and how is the quantity calculated? A pitch or height value does not itself decide a charge or coverage
Roof system and material Wide/detail photos, layers, attachment, manufacturer/product identification where available, proposed method Is the compared line describing the same material and operation? “Metal,” “tile,” or “shake” is too broad for a canned treatment
Tear-off and layers Edge/test-area documentation, safe field observation, layer count by location What was present and what work was performed? Do not infer concealed layers remotely
Waste and package rounding Facet geometry, cut pattern, valleys/hips, material dimensions, order quantities, returns What is field waste, calculation waste, and purchase rounding? An order quantity is not automatically the estimate quantity
Detach/reset or protection Component identity, location, pre-work condition, work sequence, before/during/after record Was the operation necessary and completed? Proximity to the roof is not proof the operation occurred
Decking or concealed condition Immediate context/detail photos, dimensions, marked diagram, change record, material record What became observable, where, when, and in what quantity? Capture before concealment; avoid generalized extrapolation
Flashing, penetrations, ventilation Interface photos, component count, proposed detail, applicable instructions What exact component and operation are in the contractor scope? Do not assume every accessory is separate or reusable
Code, permit, manufacturer Adopted jurisdiction, edition/effective date, exact section, product/instruction revision, applicability reviewer What rule applies to this location, product, and work? A code excerpt does not decide insurance treatment
Access, staging, equipment Property layout, obstruction, distance, protection need, equipment plan, dated job support What job condition changes the normal operation? Company preference alone may not establish necessity

For a steep or high roof, record the measurement method and affected facets. Tie each operation to its quantity calculation. With a specialized roof system, identify the product and assembly before selecting an estimate treatment. Search-result snippets and generic material photographs are not substitutes for property documentation or the full applicable source.

Keep an applicability record for each technical source. Identify the publication and revision. Record the relevant section with its effective date. Add the retrieval date and reviewer. Preserve the full communication when a qualified person makes a property-specific determination. Do not paraphrase a narrow instruction into a universal claim.

This evidence model also prevents a common economic error. An operation can be physically required in the contractor’s work yet still create a separate question about contract responsibility or insurance treatment. Record the physical fact and price accurately, then route the responsibility question without altering the evidence.

Can roofing contractors communicate with insurance adjusters?

Texas and Florida allow contractors to explain their estimates within defined limits; state law controls when the conversation becomes public adjusting. Check the rules where the property sits before assigning outbound claims communications.

The Texas Department of Insurance’s roofing and insurance guidance prohibits a roofer from acting as a public adjuster on a claim while also doing the work. Advertising that combined role is prohibited too. The agency warns against offers to negotiate settlements, file claims for homeowners or represent them on coverage. Its July 2026 bulletin confirms that contractors can provide estimates and discuss those estimates or technical information with an insurer or adjuster.

Texas prohibits deductible waivers, rebates and absorption. Its required deductible notice applies to contracts of $1,000 or more involving an insurance settlement.

Florida’s Department of Financial Services explains on its adjuster compliance page that a licensed contractor may explain its construction or repair bid to the residential owner or insurer for the usual and customary fee for its contracted work. Adjusting for the insured requires public-adjuster licensing and compliance. Even with that license, a contractor cannot contract to adjust the claim and perform construction on the same property.

Use language centered on the contractor’s own work:

Attached is Contractor Estimate v3 for the repair scope at [property]. The discrepancy table compares it with Estimate v2 and links each requested change to field documentation. We can explain our measurements and construction bid. Please identify any item requiring additional contractor documentation.

Have the company’s authorized reviewer approve the template for its jurisdiction. Keep advertising centered on construction work. The Texas and Florida pages flag offers to negotiate claims or represent policyholders; Texas also prohibits deductible-avoidance offers.

How should a roofing supplement queue operate?

Make one coordinator responsible for moving each file, with a verified status and a dated next action attached to the current packet version. “With insurance” is not a status because it does not say who received what, when, or what should happen next.

Use a controlled state model:

  1. Scope/document intake: required source files received and identifiers verified.
  2. Draft: reconciliation and packet in progress.
  3. Internal QA: technical, evidence, estimate, role/language, and duplicate review.
  4. Authorized for submission: correct contractor/customer/authorized party has approved the current version.
  5. Submitted/received: delivery channel, date/time, recipient, and receipt recorded.
  6. Information requested: exact request split into owned tasks.
  7. Under review: verified status and next follow-up date.
  8. Response received: item-level outcome and reason captured.
  9. Revision: changed facts/evidence/estimate; new version.
  10. Resolved/escalated/closed: commercial/document outcome, remaining owner, and close reason.

Do not repeatedly send the same packet because the status is unknown. Duplicate submissions create version confusion. Follow the recipient’s submission process and confirm receipt. Record the next follow-up date. Escalate internally when that agreed date passes without a response.

Reason codes should distinguish accepted as submitted, accepted with quantity/price change, alternative method, duplicate/included, insufficient documentation, applicability disputed, policy/coverage question, wrong version/identifier, pending inspection/info, and no response. A single “denied” category cannot improve the process.

Require human approval for every outbound packet. Use automation to assemble documents or compare versions. Require a reviewer to check drafted notes and the intended recipient. The software should not invent an observation, code applicability, price support, policy position, or authorized representation.

Split information requests into item-level work

An inbound request such as “send photos and code support” should create separate tasks with owner and due date:

  • identify exact item/request and current version;
  • find or safely obtain property evidence;
  • validate technical source and applicability;
  • update estimate/reconciliation if facts changed;
  • conduct role/language review;
  • approve and submit one coherent revision;
  • confirm receipt and update customer/job dependencies.

Do not mark the entire file waiting on estimator when only one quantity needs correction. Item-level state allows unaffected work to remain clear and exposes the real constraint.

Control version promotion

Separate drafts from reviewed files. Mark the approved current version explicitly, and preserve its submission record. Give superseded or withdrawn versions their own status. Only an authorized approval promotes a draft to current. Submission creates an immutable snapshot of the packet manifest and estimate version. Later edits create a new version; they do not change what was sent.

Record a response to an older version against that version. Send a clarification through the approved process when needed. Avoid attaching multiple estimates without a cover note identifying current and superseded versions.

Connect claims documentation to production and finance without collapsing them

The documentation queue may block a customer decision, scope approval, material order, start, invoice, depreciation document, or collection follow-up. Record the dependency and business impact, but leave the authoritative state with production or finance.

For example, documentation packet submitted should not automatically mean production scope approved or payment expected. A production owner decides readiness; finance recognizes receivable/cash under its rules. Integration should carry evidence, not invent state.

Diagnose a slow or low-quality queue

Pattern Inspect first Likely control
Files wait in draft missing field capture, estimator capacity, unclear scope owner Inspection standard or capacity
High first-pass QA rejection identity, photo, measurement, template, training defects Upstream quality gate
Frequent requests for information missing linkage, vague notes, irrelevant boilerplate Packet/reconciliation design
Multiple revisions with no new facts version confusion, weak internal review, unclear requested action Approval and submission control
Long “under review” age receipt/follow-up rule, response process, wrong owner Status verification/escalation
High submitted amount, low collected result unsupported volume, case mix, coverage questions, accounting lag Item/economic reconciliation
Production delayed documentation dependency not visible or scope unresolved Cross-functional handoff
Customer receives conflicting updates claims, sales, production, and office reading different states One communication owner
AI drafts require heavy correction poor inputs, unlimited note access, unsupported inference Narrow task and evidence constraints

Segment cycle time into contractor-controllable, customer/third-party wait, and disputed/authorized-escalation time. Do not claim the contractor “reduced claim cycle time” by excluding long files or closing them administratively.

Which roofing claims and documentation tools should you evaluate?

Choose tools that let a reviewer trace each estimate item to its measurement and supporting evidence, then export the approved file. Decide which system owns the job record before buying another platform. Test the handoff between systems with one closed file.

Category map

Category Job to be done Acceptance question
Estimating Build itemized contractor scope/price and diagrams Can every line, quantity, price list, note, and version be audited/exported?
Measurement reports Supply a report for quantity reconciliation Does the sample identify the structure, report date, dimensions and any manual changes?
Photos/documents Capture, label, preserve, report Can originals, metadata, annotations, locations, versions, and access be controlled?
CRM/job record Own property, customer, job, stage, task Is there one ID and current owner/next action?
Code/manufacturer Support applicability Does the source include jurisdiction/product/version and exact reference?
Workflow/QA Reconcile, require fields, age, approve, report Can rules assist without auto-asserting unsupported items?
Communication Submit/receive/log Is receipt, version, recipient, consent/authority, and response preserved?

Verisk’s Xactimate is property-claims estimating software. Its product overview describes desktop, online and mobile platforms, along with roof sketching and exterior scoping. It also explains localized pricing research and access to cost components. Test whether the report and export match your reviewer’s workflow before choosing a platform.

When comparing measurement report vendors, request a sample for the roof types you estimate. Check that the report identifies the intended structure and gives the dimensions your estimator needs. Ask how corrections are recorded and whether the report can be exported with its diagram. The IBHS/RICOWI survey guide calls for field verification of aerial roof measurements. Reconcile the report with site observations before adopting quantities for ordering or the final scope.

Give AI only evidence-bounded jobs

Start with one assisted task, such as comparing two estimate versions or drafting an index from verified records. Let a reviewer check the result before adding another task. Every output should link to source evidence and remain a draft until approved.

Acceptance testing should include wrong-property documents, duplicate/bundled lines, a blurry photo, conflicting quantities, outdated code sources, a pure coverage question, a homeowner statement contradicted by the field record, and prompt text embedded in an uploaded document. Score whether each draft cites its source and uses the right version. Count unsupported assertions and the reviewer time needed to correct them.

Pilot on a closed-file replay before live submissions

Select representative closed files with known versions and outcomes. Give the system only information that would have existed at each historical stage. Check whether the replay preserves chronology and locates known missing evidence. Include a duplicate and a coverage question to test the review path. Withhold later responses so the system cannot use information unavailable at that stage.

Then run a live pilot with reviewed outbound communication. Compare drafting time with correction time. Require an export that preserves original evidence and versions alongside approval records and submission receipts. Set data ownership and retention terms in the contract. Specify any permitted model training before expanding access.

What claims and supplement KPIs matter?

Track packet quality and time in contractor-controlled stages, then compare the avoidable rework cost with the gross profit collected on mature jobs. An approval rate needs a defined set of submitted items and comparable case mix before it can guide a staffing decision.

KPI Definition
First-pass completeness Packets passing internal required-field/evidence QA before submission
Request-for-information rate Submitted packets receiving avoidable missing/clarification request
Revision rate Packets requiring corrected contractor facts/version after submission
Stage cycle time Median and older-percentile days in each controllable state
Aged/unowned backlog Files past SLA or without accountable next action
Supported discrepancy value Contractor scope difference with linked evidence, before policy decision
Resolved contractor value Amount/items resolved and ultimately collected/contracted, clearly defined
Documentation defect Wrong property/version, missing photo/quantity/source, duplicate/unsupported item
Reopen rate Closed files reopened due to missed work or process defect
Production/invoice delay Days attributable to documentation queue, separately coded

An “approval rate” should always state: approvals of what, among which submitted items/files, over what period, with which policies, carriers, states, job types, and decision definition? A conditional approval proportion cannot be applied to all inspected roofs or used to claim influence over a carrier.

Review weekly aging by state, owner, reason, amount at risk (if appropriate), customer promise, and production dependency. Review monthly root causes: missing field observation, estimator training, bad measurement, unsupported template, code-source error, version mismatch, response reason, or integration failure.

Use the company’s roofing operating system to assign the claims queue. Keep its owners and approval rules visible beside production tasks so a scope change does not disappear into a separate office inbox.

Start economic reporting with incremental collected job gross profit attributable to supported contractor work. Subtract documentation and sales costs that have not already been deducted. Keep each cost in one place in the calculation. Do not treat a submitted amount as revenue or an accepted estimate line as collected profit. Avoid attributing amounts the job would have earned anyway.

Build a claims-operations economic bridge

Keep these quantities separate:

  1. contractor estimate total;
  2. compared estimate total;
  3. supported contractor discrepancy submitted;
  4. item/amount accepted or otherwise resolved in the estimate process;
  5. contract/change scope authorized by the customer;
  6. invoiced amount;
  7. collected amount;
  8. realized job gross profit;
  9. incremental gross profit reasonably attributable to the documentation process;
  10. documentation/estimating/service and downstream incremental cost.

A $12,000 submitted difference is not $12,000 revenue. An accepted estimate line can still be outside the customer’s final contract, cancelled, uncollected, or costly to produce. Gross profit, not added revenue, is the starting point for operating return.

For a cohort:

documentation contribution = incremental realized job gross profit − documentation and sales costs not already deducted

Incrementality is difficult because complex files both need more documentation and may have larger outcomes. Use a carefully matched, randomized workflow where appropriate, or a stepped rollout; disclose selection and timing. Compare fixed groups of files with similar case mix. Track evidence quality and controllable time alongside rework costs and collected job economics.

Value avoided failure separately

Some gains are avoided reinspection, expedited material, duplicate submission, customer escalation, delayed invoice, or staff rework. Measure events and cost. Do not count an entire contract as “saved” because one document was corrected unless there is evidence the contract would otherwise have been lost.

Put denominators on every claim

Examples:

  • packets passing first review ÷ packets entering QA;
  • accepted items ÷ supported submitted items;
  • information requests ÷ submitted packets;
  • collected incremental gross profit ÷ mature treated files;
  • documentation cost ÷ mature files or accepted items;
  • critical boundary/version defects ÷ outbound packets;
  • aged files ÷ open files eligible for the SLA.

Publish excluded and not-yet-mature counts. Moving difficult files out of the denominator does not improve operations.

A 30-day claims and supplement playbook in 8 steps

Use the first 30 days to audit closed files, set the evidence standard, and test the next packets with a named reviewer.

  1. Days 1 to 3: sample closed files. Select files across estimators and roof types, including difficult outcomes. Count missing evidence and version errors. Record staff rework hours and reinspections at your own loaded costs.
  2. Days 4 to 7: trace the handoffs. Map the inboxes and systems that touched each file. Identify where a question lost its owner. Have the communication boundaries reviewed for the states where you work.
  3. Days 8 to 10: set the packet standard. Agree on identifiers, a photo sequence and the quantity calculation for each disputed item. Remove any canned addition that lacks property evidence or an applicable source.
  4. Days 11 to 14: assign the queue. Give each file one owner and a next action with a due date. Define the receipt that proves submission and the event that permits closure. Link the queue to your roofing operations plan.
  5. Days 15 to 17: set the next outreach territory in Ground Control. Choose the service area, roof age band and material; add commercial building size where it fits. Homes cost $0.72 to $1.20 each and commercial buildings $10 to $20 each, with the file delivered within 48 hours after payment. Assign the matched properties to your team and carry their identifiers into new inspection files.
  6. Days 18 to 21: train on exceptions. Test a wrong-property upload, a duplicate line and an unsupported code assertion. Include a coverage question that must go to an authorized adviser. Confirm that the reviewer can export the record.
  7. Days 22 to 26: pilot new packets. Keep a human review before each outbound submission. Split information requests into item-level tasks and record each response against the version sent.
  8. Days 27 to 30: compare the work. Review file quality and avoidable rework alongside collected job economics. Keep unresolved files visible. Expand the workflow only after the pilot shows that people can follow the evidence and approval history.

For the earlier field response after a storm, use the roofing storm-response guide. Carry its property identifiers into this claims queue so the office can find the inspection record.

Source method

The cited sources were checked on November 5, 2026. They support the cited rules and software descriptions; the operating checklists are the workflow I would use.

Texas and Florida provide specific examples of contractor communication boundaries. Apply the rules for the property’s jurisdiction, with a qualified reviewer for questions about authority or coverage. The source notes record what each publication supports.

NAIC guidance addresses consumer records. IBHS/RICOWI supports roof-survey practices, including field verification of aerial measurements. Verisk’s publications explain its estimate reports and pricing methodology.

Starting the next roofing territory with Ground Control

The fastest way to find roofs that fit your crew is Ground Control by PorchRocket: filter homes by area, roof age band and material, or commercial buildings by business type, roof age band, material and building size. Homes cost $0.72 to $1.20 each; commercial buildings cost $10 to $20 each. Files arrive within 48 hours after payment. Each property says why it matched, and wrong matches receive a credit within 30 days. These are prospects for your team to contact. Use older-home roof lists or commercial roof lists to pick the territory.

Set up the Ground Control order around the next inspection route:

  • Choose the geography your crews can serve and the roof materials they install.
  • Add commercial business type and building-size bands when those determine job fit.
  • Add owner information or commercial decision-maker contact research where needed; both are add-ons.
  • Roof trades can add a roof report and storm history to the order.
  • Import the CSV or Excel file into your workflow and preserve the property identity as the job develops.

For the broader acquisition plan, start with the roofing lead-generation guide. Use the roofing software comparison to choose the system that holds the inspection and estimate record. The commercial roofing leads guide covers the owner conversation before a contracted job, and the commercial roofing lead-cost guide helps budget outreach separately from documentation work.

For city, county and school roofing work, Bid Control by PorchRocket brings bid papers, due dates and addenda together. Bid Team works the estimate with you and prepares the forms; you make the final call on your number, sign and send. The government roofing contracts guide covers that separate sales channel.

Select the roofs first. Build the evidence file while the crew can still collect what the estimator needs.

Questions people ask

Quick answers

Is every difference between roofing estimates a supplement?

No. A difference can be a duplicate, a quantity error, an alternative construction method or a coverage question. Compare the current versions first. Submit only supported contractor scope through the authorized process, with each proposed change linked to property evidence and a clear requested action.

Do I need Xactimate for a roofing supplement?

Only if the recipient requires that format. Check submission requirements before buying estimating software, then test an export against them. Preserve the contractor's scope and price basis, reconcile quantities, and attach evidence to each proposed change in the required report.

How many photos does a roofing supplement need?

Use enough photos to locate and explain each disputed item, including a readable scale where quantity matters. Start with the recipient's written requirements. An overview should locate the detail photo, and the caption should identify the observed condition. Review the exported report for legibility before submission.

Does a code requirement automatically mean insurance will pay?

No. Document the adopted code edition and the exact requirement that applies to the work. Ask the qualified reviewer to confirm applicability. Keep the contractor's construction requirement separate from the policyholder's coverage question, which belongs with the insurer or an authorized adviser.

Is roofing overhead and profit automatically owed?

An automatic allowance should not be assumed. Explain how the contractor priced the work and check whether the comparison estimate already includes the disputed cost. Record the remaining difference without adding the same cost twice. Route any question about insurance payment to the authorized party.

Who handles recoverable depreciation on a roof claim?

The policyholder coordinates the payment request with the insurer. Ask what documentation the policy requires. The contractor can supply an accurate invoice and records of finished work when requested. Track the request and delivery date, but keep expected funds separate from collected cash and leave the payment decision with the insurer.

Can a roofer waive the insurance deductible?

No in Texas: the state prohibits contractors from offering to waive, rebate or absorb a property-policy deductible. For contracts of $1,000 or more involving an insurance settlement, Texas requires notice that the policyholder must pay the deductible. Check the rules for the state where the work occurs before writing the contract or advertising an offer.

What should a roofer do when a supplement item is denied?

Record the written reason and compare it with the contractor evidence already sent. Correct a factual or version error through a reviewed revision. If the disagreement concerns coverage or settlement, route it to the policyholder, insurer or qualified adviser. Give the customer a dated next action.

Research file

Sources used in this guide

Sources are linked at the claim they support and collected here for auditability. Vendor features and prices can change; verify them before purchasing.

  1. What you need to know when filing a homeowners claimNational Association of Insurance Commissioners: Consumer guidance on prompt notice, photos/video, damaged-property lists and retained receipts; checked November 5, 2026.
  2. Roofing and insurance: Know the lawTexas Department of Insurance: Texas contractor/public-adjuster boundaries, advertising examples, and deductible rules; checked November 5, 2026.
  3. Commissioner's Bulletin B-0006-26Texas Department of Insurance: July 20, 2026 bulletin permits contractors to provide estimates and discuss estimates and technical information with insurers or adjusters; checked November 5, 2026.
  4. Adjusters: claims communicationsFlorida Department of Financial Services: Florida contractor bid-discussion, public-adjusting boundaries, and same-property conflicts; checked November 5, 2026.
  5. RICOWI best practices guide: survey practicesInsurance Institute for Business & Home Safety: Roof survey preparation and documentation, including field verification of aerial measurements; checked November 5, 2026.
  6. Xactimate property claims estimating softwareVerisk: First-party property-claims estimating product page; checked November 5, 2026.
  7. What information is in Xactimate estimate reports?Verisk Xactware Help: First-party explanation of estimate report sections and saved-version comparisons; checked November 5, 2026.
  8. Pricing research methodologyVerisk: First-party local-market pricing research, component detail, verification requests, and job-specific adjustments; checked November 5, 2026.
  9. Xactimate product and pricing-data overviewVerisk: First-party overview of sketch, roof/exterior scoping, pricing research, component detail, and platforms; checked November 5, 2026.
Your next best move

Start with the roofs your crew serves.

Ground Control selects homes and commercial buildings by area, roof age band and material. Get a target list with each match explained, then build the inspection record on site.

Find roofs that fit