PDF vs. ESX: What's the Difference — and What You're Losing

This post is part of the What the PDF Doesn't Tell You series — a look at what gets lost when an Xactimate estimate becomes a PDF, and why it matters.

When an adjuster sends a PDF estimate, every line item, quantity, and total is there. It looks like the whole estimate. But it isn't — it's a flat snapshot of a much richer Xactimate estimate, and most of what makes that file useful gets stripped out in the export. Many firms downstream never see the original, so they don't know what they're missing.

What Is an ESX?

Xactimate is an estimating software platform, not a format. When an estimator builds a claim in Xactimate, the project lives as an ESX file.

The PDF is a formatted export of that ESX file. It's designed for sharing between parties — easy to email, easy to read without Xactimate. But in the export, the file loses most of its structure. What was a rich, navigable project becomes a flat list of descriptions and numbers.

What the ESX Contains That the PDF Doesn't

Here's what lives in the native Xactimate estimate and disappears when an estimate becomes a PDF.

The project tree

In Xactimate, every estimate is organized hierarchically: structure, areas (interior, exterior, general), rooms, and groups within rooms. A large loss might have hundreds of line items distributed across dozens of areas. The project tree makes that navigable — you can jump to a specific room, filter by area, and understand the scope at every level of the project.

The PDF flattens all of this into a sequential list. The hierarchy disappears. Finding a specific line item requires reading through the entire document from top to bottom.

Trade and activity codes

Every line item in Xactimate carries two codes: a category and selector code. The category code identifies the responsible trade — PNT (Painting), DRY (Drywall), FLR (Flooring), WTR (Water Extraction and Remediation). The selector code tells you the repair action or materials required to bring the property back to its pre-loss condition (e.g. Clean the Floor etc,.)

Together these codes tell you who does the work and what kind of work it is. The PDF keeps the description. The codes don't make it through. What's left is often ambiguous — "Apply anti-microbial to floors" could belong to WTR, HMR (Hazardous Material Remediation), or TCR (Trauma/Crime Scene Remediation), with different compliance standards and cost justification depending on which trade owns it. The PDF gives you no way of knowing.

Custom line items

Xactimate uses a visual flag — a green highlight — to mark non-standard line items: prices that were manually entered, overridden from the price list, or customized for the specific project. These custom items are where negotiations happen, where scope disputes originate, and where the most significant RCV discrepancies hide.

In a PDF, the green highlight is gone. Custom items look identical to standard items. The only way to find them is to know what you're looking for and read every line.

Pricing data

The PDF shows line item totals and room subtotals. It doesn't show the pricing logic behind them: sales tax, depreciation calculations, or overhead and profit structure. For anyone reviewing or disputing an estimate — a building consultant evaluating scope, a contractor checking RCV, a reviewer auditing a mitigation bill — the totals tell you the result but not the reasoning. The reasoning lives in the ESX.

Why the Gap Matters

The missing data isn't just inconvenient. It cascades through every workflow that depends on the estimate.

Supplementing and scope review. Without the project tree, navigating a large-loss estimate means reading it sequentially, page by page. Without trade codes, identifying which items belong to which scope requires interpreting every description manually. The ESX lets you filter, sort, and navigate. The PDF requires you to read — carefully, slowly, and without any structural aid.

Budgets and work orders. Insurance estimates are organized by room. Subcontractors work by trade. Mapping a room-based PDF scope to a trade-based work order — line item by line item, description by description — is manual work that compounds with every line item added. Without trade codes, it's also guesswork. Before ClaimsFlow, J&J Remodeling's production managers did this by hand for every approved scope, combing through the PDF and assigning each line item to the correct trade and budget category.

"At the end of the day, ClaimsFlow is really saving the project manager's ass from doing things out of budget."

— William Ledbetter, Head of Estimating, J&J Remodeling

Estimate analysis and review. Building consultants and mitigation reviewers need trade codes and custom item flags to evaluate whether scope and cost are defensible. Without them, reviewers have to look up every ambiguous line item manually — or approve scope they can't fully verify. That bottleneck is documented: the mitigation review conversion problem runs directly through this gap. The data reviewers need most is exactly what the PDF strips out.

Negotiation. When an adjuster returns a revised estimate, the differences are somewhere in the new PDF. Finding them means comparing two flat lists, line by line. An ESX-to-ESX comparison is structural — you see exactly what changed, in what section, at what cost. The PDF makes that structural comparison impossible. The negotiation flow problem follows from this: every round of back-and-forth costs time proportional to the effort required to find the discrepancies, which the PDF maximizes.

Getting from the Blurry Copy to the Full Picture

ClaimsFlow converts PDF estimates to ESX files and restores what the PDF approximated away: the project tree, trade and activity codes, and custom item flags. The ClaimsFlow dashboard lets you review the restored estimate — sort by trade, identify custom items — before you download the ESX and take it into Xactimate.

The PDF is what gets shared. The ESX is what professionals work from. ClaimsFlow gets you from one to the other — and gives back the structure, codes, and context the PDF left behind.

Each data type the PDF strips has its own story. Read the full series:

• What Disappears: The Xactimate Project Tree

• What Disappears: Custom Line Items the PDF Strips Out

• What Disappears: Trade and Activity Data

• What the PDF Doesn't Tell You — The Complete Guide

Upload a PDF estimate and see what comes back. Try for free at claimsflow.io.