How To Read Xactimate Estimates: A Contractor Field Guide

Read an Xactimate estimate in eight passes: verify the estimate identity, check the price list and parameters, read the RCV/ACV/depreciation totals, map the scope, inspect line-item anatomy, reconcile the roof sketch and quantities, compare pricing assumptions to job conditions, then build a neutral evidence packet with photos, notes, documents, and specific review questions. That order keeps the review grounded in facts instead of drifting into line-item folklore or payment promises.

Verisk describes Xactimate as property claims estimating software. That makes it a useful structure for reading an estimate, but it does not make the estimate a public price list, legal opinion, coverage decision, or guarantee of payment. A contractor-safe review says what the estimate shows, what the roof and job conditions show, what evidence is attached, and what should be reviewed. It does not tell a homeowner that an item is automatically owed because it appears in Xactimate.

For RoofPredict, the best product lane is evidence organization. Roof age, storm context, inspection photos, measurement notes, estimate references, and review questions can be assembled into a cleaner packet. RoofPredict should not be framed as replacing Xactimate, publishing proprietary price tables, practicing public adjusting, or deciding claim outcomes.

What An Xactimate Estimate Is And Is Not

An Xactimate estimate is a structured estimating document. For roof work, it usually includes project information, estimate dates, price-list context, parameters, scope sections, sketch or measurement references, line items, quantities, unit prices, depreciation, notes, attachments, and totals. A good reader moves through that structure deliberately.

That structure is useful because it creates places to check the work. A scope item can be missing. A quantity can be linked to a sketch that needs review. A line item can lack a note. A price-list date or location can differ from a prior version. A depreciation setting can change the number a homeowner sees. A photo can exist but not be tied to the item that needs support.

The same structure has limits. An estimate can be incomplete or disputed. It can also include items that still depend on policy terms, contract terms, reviewer decisions, deductibles, limits, exclusions, depreciation rules, or documentation. NAIC homeowner claim-settlement guidance describes adjuster review, policy terms, deductibles, coverage limits, and the possibility of multiple payments. That is why a contractor should keep the conversation evidence-based: what was inspected, what was measured, what is documented, and what needs review.

The safe sentence is: "Here is what the estimate says, here is what the roof evidence shows, and here is the specific review question." That is stronger than "the estimate is wrong" and much safer than "this has to be paid."

Pass 1: Estimate Identity And Version Control

Start at the top of the estimate. Confirm the property address, project or claim reference, estimate version, estimate date, estimator or file label if visible, and whether you are looking at a first estimate, revised estimate, supplement, or comparison copy. Do this before reading totals.

Version control matters because a contractor can lose a review before the facts are discussed. If the homeowner has one PDF, the office has another PDF, and the field rep is looking at screenshots from a third version, the team may be arguing from different documents. Create a simple version note:

This first pass often prevents wasted work. If the version changed, the roof scope may not be the only thing that changed. The price list, parameters, depreciation view, tax settings, or attachments may have changed too.

Pass 2: Price List, Date, Location, And Parameters

Next, read the price-list and parameter context. The Xactware glossary entry for price list and the Xactware pricing-parameter help support a practical review question: which price-list context and manual assumptions are being used?

Then check the estimate parameters. Xactimate parameter help, linked in the source table, shows that parameters can include price-list information and add-ons such as labor burdens, market conditions, permits, sales tax, depreciation, and overhead and profit. These fields are not decorative. They can change how the estimate is configured and how totals are displayed.

Do not turn parameter review into a universal entitlement claim. The right questions are narrower:

• Is the visible price-list context consistent with the job location and estimate date?
• Were prices manually edited, overridden, or left as published?
• Are tax, permit, labor burden, market-condition, depreciation, or overhead/profit fields present?
• If an add-on is present, what scope does it apply to?
• If an add-on is absent, what documented job condition makes it worth asking about?
• Are the same settings used across the versions being compared?

This pass keeps the review from becoming a random line-item hunt. Sometimes the issue is not one item. Sometimes the issue is that two estimates were built under different assumptions.

Pass 3: RCV, ACV, Depreciation, And Add-Ons

After parameters, read the totals. Many readers jump straight to the biggest number, but a total only makes sense after the estimate's structure is understood. Separate replacement cost value, actual cash value, depreciation, deductible display, overhead/profit if present, tax if present, and any line or category totals that explain how the number was built.

The practical contractor question is not "Which number helps my argument?" The better question is "Which number is being discussed, and what assumptions feed it?" If the homeowner asks why the payment amount is different from the replacement estimate, explain that an estimate can show multiple values and that payment may depend on policy terms, depreciation handling, deductibles, limits, prior payments, and claim review. Keep that explanation general unless a qualified reviewer has looked at the actual policy and claim file.

For a line-item review memo, capture the displayed total and the exact value being discussed. Do not write "the estimate is short" without saying whether the question is scope, quantity, depreciation, price-list date, tax, permit, overhead/profit, or another parameter. Specificity is what makes the memo reviewable.

Pass 4: Scope Structure, Areas, And Categories

Now read the estimate as a scope document. Xactware's Estimate Items help area and official help for adding a line item in Xactimate X1 support a basic point: estimates are built from items placed into a structure. The item matters, but where it lives in the estimate matters too.

Map the estimate before disputing it:

The goal is not to force every possible roofing item into every estimate. The goal is to compare the estimate's structure to documented job facts. If the roof is simple, the scope should stay simple. If the roof has multiple planes, unusual penetrations, brittle accessories, interior leak damage, or access constraints, those facts should be visible in the review packet.

Pass 5: Line-Item Anatomy

Only after the scope map should you inspect individual line items. Xactware help for modifying an item unit price, attaching notes, images, sound files, or documents, and adjusting pricing parameters supports a basic point: line-item review is about fields, quantities, assumptions, and evidence, not a public price table. XactAnalysis contractor line-item worksheet help also supports worksheet-style review of fields such as category/selector context, calculation, quantity, RCV, ACV, depreciation, overhead/profit, and components.

Use those fields to make the review concrete:

This table is not a price cheat sheet. It is a review discipline. "The estimate is low" is weak. "The line-item quantity appears to exclude the rear lower facet shown in photos 14 through 18; please review the attached measurement note" is stronger because it names the item, the evidence, and the request.

Pass 6: Roof Sketch And Quantity Reconciliation

For roof work, the sketch deserves its own pass. Xactware roof help includes roof sketch functions involving slope, orientation, eave and rake dimensions, truss spacing, framing type, and roof waste. A contractor review should use those sketch concepts to reconcile the estimate to the roof evidence.

Start with the shape. Compare the sketch to field photos, roof reports, aerial imagery if available, measurement notes, and any inspection record in the file. Then check the details that commonly move roof quantities: facets, slope, ridge, hip, valley, eave, rake, wall intersections, penetrations, chimneys, skylights, dormers, transitions, and waste assumptions.

Write quantity issues as reconciliation notes:

Do not instruct homeowners to climb the roof to prove a quantity. OSHA residential fall-protection guidance, linked in the source table, is a reminder that roof work has serious fall hazards. Homeowner-facing instructions should focus on ground-level photos, safe interior photos, documents, and calling qualified professionals for roof access.

Pass 7: Pricing Assumptions And Job Conditions

Pricing review should be disciplined. Verisk's pricing methodology supports a basic point: local and regional costs matter, and actual job cost can vary with job size, complexity, accessibility, location, contractor overhead, and service level. That does not mean a contractor should argue every price in public. It means the review should tie pricing questions to documented job conditions.

For roofing estimates, useful job-condition evidence often includes:

• Access limitations: steepness, height, staging, driveway limits, fencing, landscaping, neighboring property, or material drop constraints.
• Complexity: cut-up roof planes, multiple pitches, dead valleys, custom flashing, brittle surrounding materials, or unusual penetrations.
• Material handling: drop-zone distance, tear-off path, disposal route, weather protection, and protection of finished surfaces.
• Local constraints: permit requirements, tax treatment, local labor assumptions, or market-condition notes.
• Service level: emergency dry-in, temporary protection, after-hours work, or sequencing that changes labor.

Keep the request factual: "Please review whether the documented access constraints are reflected in the estimate." Avoid: "The carrier has to pay more." The first sentence asks for review of a condition. The second sentence makes a claim the article cannot support.

Pass 8: Evidence Packet And Neutral Review Memo

The final pass turns findings into a packet. Xactimate X1 help says users can attach notes, image notes, sound files, and documents to line items. That makes evidence attachment part of the workflow, not an afterthought.

Use a consistent packet structure:

Example review memo:

That is the line-item review/dispute workflow in its cleanest form: reference, evidence, mismatch, question, limit. It is firm enough to be useful and restrained enough to avoid overclaiming.

A Fictional Walkthrough: Cover Page To Line-Item Memo

Use fictional examples in public training material. Do not publish a customer's claim file, licensed screenshots, current proprietary price tables, line-item code sheets, or private carrier notes. The point is to show the reading process, not to expose a real claim or teach a pricing shortcut.

Scenario: a revised roof estimate for a fictional property at 100 Cedar Court includes a roof replacement section. The homeowner asks whether the estimate accounts for a lower rear porch roof that ties into the main rear slope. The contractor's job is not to announce that payment is owed. The job is to read the estimate, compare it to documented roof facts, and send one clear review question.

Step 1: Cover Page And Version

Start with the cover page or first estimate screen. Record the estimate title, property address, estimate date, revision label, claim or project reference if visible, and the person or organization that exported the document. If the field rep, office coordinator, and homeowner are not using the same version, stop the review and reconcile the document first.

This small table prevents a common failure: sending a supplement note against the wrong estimate. A version mismatch can make a contractor look disorganized even when the underlying roof observation is valid.

Step 2: Price-List And Parameter Screen

Next, capture the visible price-list context and parameters. The memo does not need to quote proprietary prices. It should record whether the team can identify the market/date context, whether taxes or add-ons are visible, and whether any relevant setting differs from a prior version.

For this article, the pricing lesson stops here. The adjacent RoofPredict pricing guide owns detailed price-list and market-variation strategy. This page only needs enough pricing context to read the estimate correctly.

Step 3: Totals Page

Read the totals before arguing about scope. Separate replacement cost, actual cash value, depreciation, deductible display, prior payments if shown, tax if shown, and overhead/profit if shown. The homeowner may call all of these "the estimate," but they are not the same number.

The contractor memo should say, for example: "This review question concerns roof quantity and scope, not the displayed ACV payment amount." That sentence keeps the discussion from sliding into policy interpretation.

Step 4: Scope Tree And Roof Section

Move into the scope tree or roof section. Find the roof area where the rear slope appears. Do not begin with a vague sentence like "the porch is missing." First identify where the estimate appears to account for rear-elevation roof work, related tear-off and replacement activities, accessories, flashing, or notes.

This is the point where a reviewer can follow the issue. The packet is no longer "the estimate missed something." It is "this specific roof area may not be clearly represented in this specific scope section."

Step 5: Sketch And Quantity Trail

Now reconcile the roof sketch or measurement reference. Look for facets, slope, ridge, hip, valley, eave, rake, wall intersection, porch tie-in, waste assumption, and measurement source. The field team should label photos and measurement notes in the same language it uses in the memo.

Do not ask the homeowner to climb the roof for a better angle. Use safe ground-level photos, interior leak photos if relevant, roof reports, measurement notes, and qualified inspection evidence.

Step 6: Line-Item Reading

Finally, inspect the specific line or group that would change if the lower porch facet were included. Do not publish item codes or current prices. Read the description, unit, quantity, calculation, section, note, attachment field, and value type being discussed.

That final row is the whole discipline. A line-item memo should be easy to verify, narrow enough to answer, and honest about its limits.

Final Memo Example

Here is the complete fictional memo in public-safe language:

The same structure works for a line-item detail question. Suppose the estimate includes two pipe flashings, but the roof photos show three pipe penetrations in the replacement area. The packet should not say, "Xactimate proves the third item must be paid." It should say, "The estimate lists two pipe flashings. Photos RP-17, RP-18, and RP-19 show three pipe penetrations in the replacement area. Please review whether the third pipe flashing is included or explain the exclusion."

That phrasing is more useful for a reviewer, easier for a homeowner to understand, and easier for the contractor to support with evidence. It also keeps the team away from claims it cannot prove from the estimate alone.

When A Review Question Is Not Ready

Some estimate questions should be held until the packet is stronger. Hold the question if the team cannot identify the exact estimate version, cannot find the item or scope section, cannot label the photo, cannot explain the measurement source, or cannot state the question without using payment language. A rushed supplement can make a real issue look vague.

Use a simple readiness test:

If one of those fields is missing, improve the packet before sending it. The best estimate reviewers are not louder. They are easier to verify.

Source Limits

RoofPredict Xactimate Estimate Review Matrix

Use this matrix before sending a supplement request, client explanation, or internal review note.

Homeowner-Friendly Explanation Contractors Can Use

When a homeowner asks what the Xactimate estimate means, keep the explanation simple:

"The estimate is a structured repair estimate. We read it by checking the project details, scope, roof measurements, line items, notes, photos, and documents. If something does not match the roof or the job conditions, we document the difference and ask for review. The estimate does not replace the policy or the review process."

Then add two safety and consumer-protection boundaries. First, do not ask the homeowner to climb the roof for proof. Use ground photos, interior leak photos, documents, and professional inspection evidence. Second, homeowner decisions about coverage, checks, contractor selection, and written contracts should stay in the homeowner lane. The FTC guidance linked in the source table supports verifying coverage, avoiding signing insurance checks over, confirming license and insurance where applicable, getting more than one estimate, and using written contracts.

Common Mistakes When Reading Xactimate Estimates

The first mistake is reading only the total. The total matters, but it is the final output of scope, quantity, price-list context, parameters, depreciation, and add-ons.

The second mistake is comparing two estimates without checking version, date, price-list context, and parameters. A changed setting can create a real difference before any roof fact changes.

The third mistake is treating every missing item as bad faith. Many issues should start as documentation questions: "Was this excluded intentionally?" "Was this facet counted?" "Which photo supports this condition?"

The fourth mistake is sending unlabeled photos. A folder of photos is less useful than a packet that names the estimate item, roof facet, photo number, measurement source, and review question.

The fifth mistake is using public content as a substitute for actual estimating tools, reviewer judgment, licensing, or legal advice. A public guide can teach workflow. It should not publish proprietary price tables or make coverage decisions.

FAQ

What is the fastest way to read an Xactimate estimate?

Use the eight-pass method: identity, price list and parameters, totals, scope, line items, roof sketch, pricing assumptions, and evidence packet. That sequence prevents one line item from hiding a larger version, scope, or quantity issue.

Should contractors start with the line items?

Not usually. Start with the estimate identity, parameters, totals, and scope. If those are wrong or mismatched, line-item review can waste time.

Does an Xactimate line item mean the insurer must pay it?

No. A line item is part of an estimate. Payment, coverage, depreciation, exclusions, deductibles, and review decisions depend on other facts and documents.

Can this article be used as a public Xactimate price list?

No. This guide does not provide proprietary line-item prices. It explains how to read and document an estimate using official product, help, regulator, consumer-protection, and safety-source context.

What should be attached to a review request?

Attach the estimate version, line-item reference, labeled photos, measurements, roof report or sketch note, relevant invoice or material documentation if applicable, and one clear review question.

Where does RoofPredict fit?

RoofPredict fits before the argument. It can organize roof evidence, age context, storm context, inspection photos, measurement notes, estimate references, and review questions so the packet is easier to understand. It should not be presented as a payment decision tool.

Contractor Checklist

Before asking for review, confirm:

• The estimate version, date, address, and price-list context are identified.
• Parameters and add-ons have been reviewed.
• RCV, ACV, depreciation, and deductible conversations are not mixed together.
• Scope sections match the documented roof and related property conditions.
• Line items under review have item references, quantities, calculations, notes, and attachments captured.
• Roof sketch quantities have been reconciled against photos, measurements, and roof reports.
• Pricing questions are tied to documented job conditions, not generic complaints.
• Photos are labeled by roof area, facet, elevation, or estimate item.
• Homeowner instructions avoid unsafe roof access.
• The review memo uses neutral language and asks a specific question.
• No one is promising that Xactimate, RoofPredict, or a supplement request guarantees payment.