Carrier roof scopes: how to turn the estimate you were sent into Xactimate.

ESXPress is a conversion tool that turns a carrier roof scope, whether it arrives as a PDF or as a scope XML export, into an import-ready Xactimate ESX file in about two minutes. This page answers the question contractors bring here: which carrier scope formats the converter reads, what to check on any roof scope, and what we will not claim about a named carrier.

Which carrier scope formats does ESXPress convert to Xactimate?

ESXPress reads the roof scope formats used by State Farm, Allstate, USAA, Farmers, Progressive, Travelers, Liberty Mutual, and Auto-Owners, whether the scope arrives as a PDF or as a scope XML export. Most carrier scopes run 25 to 50 line items, and structured XML converts with no OCR step in the path.

A scope that arrives as XML (Xactimate's export, or any other system's) converts with no OCR step in the path: line items, rooms, and notes land exactly as written. A carrier scope PDF converts through the same pipeline with extraction and per-line flagging.

Does a carrier omit items from my roof estimate?

We do not publish a per-carrier omission list, because we hold no evidence that a named carrier omits a specific item on your claim. What you can check is your own scope: ESXPress converts it, and dashboard conversions flag what it does or does not carry with a code citation behind each flag. The winning argument is the code section or your measurement, not a generalization about the carrier.

Contractors reach this cluster looking for a specific answer: did this carrier leave something off my estimate? We answer the part we can, and we say so plainly where we stop.

What will ESXPress say about a carrier, and what will it not?

We will tell you which carrier scope formats ESXPress reads, and the aggregate behavior of the scopes we have converted, reported without carrier attribution. We will not tell you that a named carrier omitted a specific item on your claim, or that a named carrier always or systematically does anything, because that is a claim about the carrier on a file and we do not hold that evidence.

The reason is not caution for its own sake. A claim that a carrier left something off is a claim about that carrier on a specific file, and we do not hold that evidence. A supplement that leads with the code section, the manufacturer instruction, or the number you measured from the roof is stronger anyway, because a desk reviewer can check it and does not have to take a pattern on faith.

What should you check on any roof scope?

These four items turn on the code or on plain arithmetic, so you can check them against the scope in front of you regardless of who wrote it. Each one is a requirement you can document with a photo or a measurement, which is why it is harder for a desk reviewer to decline than a preference you have to argue.

Beyond those, a short scope's missing lines cluster in the same eight categories. Read the scope as an assembly list, not as a total:

What does ESXPress measure across carrier scopes?

The one carrier-blocked number we publish is aggregate and unattributed: across 289 real claim files and 7,525 line items, 2,756 lines (36.6%) carried a code the converter recognizes, so 4,769 lines kept the price printed on the scope. The median file moved 17% of its lines when repriced on import, and 39 of the 289 files never moved a line.

The State of Insurance Scope Quality (2026) carries the method and the caveats. It is not broken out by carrier, and we do not present it as if it were.

How do you convert a carrier scope to Xactimate?

Convert the carrier's scope, then compare it line by line: that is where a gap becomes a list instead of a memory test. Dashboard conversions run the 93-rule completeness check on the conversion row with a citation behind every flag; the public structured API returns the ESX and its structured payload and does not run that check. Start with the converter, or request the free Scope Audit first.

Carrier scope walkthroughs

The pages below are the cluster's carrier walkthroughs, some of which still carry an older "What Carriers Omit" title. Read them as workflow guides: where one describes a pattern, it is an industry pattern you can check for yourself on the scope in front of you, not a finding about a named carrier.

The winning argument still rests on the code section or the measurement behind the line. These scopes arrive in waves too: storm season is when a single weather event fills a market's queue at once, and the storm season supplement playbook maps that cycle across the claim year.

Questions contractors ask about carrier scopes

Related: what an Xactimate supplement is, the line-by-line supplement audit, and how PDF to ESX conversion works. Storm claims arrive on these scopes all season, and how those losses present on the roof is worked through on the hail damage claim and wind damage claim pages.

ESXPress is not affiliated with, endorsed by, or sponsored by any insurance carrier. Xactimate is a registered trademark of Verisk Analytics, Inc. This page is a workflow guide for the scope in front of you, not a statement about any carrier's practice.