Quick answerOne roof measurement report, ordered by address and delivered as ESX, XML, and PDF from the same order, can be shared between the carrier desk and the contractor so both estimates start from identical measurements. The risk is not the file itself, it is two people working from two different versions of it. Fix that with a named file convention, a single point of revision requests, and a rule that a corrected report replaces the old one everywhere it lives, not just in one estimate.

Why sharing one file beats ordering two

When the carrier orders a report and the contractor separately orders its own, the two measurements can differ even on the same roof, because footprint interpretation, facet counts, or a missed detached structure can vary between orders. That gap becomes a line-item argument that has nothing to do with the actual damage.

Ordering one report and routing the same file to both sides removes that variable. The measurements are identical because the file is identical. What differs afterward is scope and pricing judgment, which is the argument worth having.

Sketch My Roof, this site's sponsor, delivers a residential order as ESX for Xactimate®, XML for Symbility®, and PDF together from a single request, so one order can supply the format each side's software needs without re-measuring.

What each side actually needs from the file

The carrier desk typically needs ESX for Xactimate® or XML for Symbility® to build or reconcile the estimate line by line, plus the PDF as the documentation exhibit in the claim file.

The contractor typically needs the same PDF to walk the roof and confirm facets against the measurement, and may need the ESX or XML only if they are writing their own estimate in the same platform rather than working from the carrier's Xactimate® or Symbility® estimate directly.

Sending all three formats from one order avoids a second conversation later about which file someone else needs.

Sharing the report, step by step

  1. Order once, at the format set both sides need

    Choose ESX + PDF (or add XML) so the delivery covers the estimate platform and the exhibit copy from a single request rather than ordering twice.

  2. Name the file to the claim, not the vendor

    Rename the delivered file to the claim number before distributing it (for example ClaimNumber_RoofReport_v1.pdf), so everyone downstream is opening the same object regardless of who ordered it.

  3. Distribute from one source

    Send the file from the claim file or a shared claim folder, not by forwarding the original delivery email to multiple people separately. That prevents two people from each holding a copy and later assuming theirs is current.

  4. Import into the estimate platform

    Bring the ESX in via the Sketch import option in Xactimate®, or the equivalent import in Symbility®. Menus vary by version, verify the exact steps in your build against the vendor's help documentation.

  5. Log who has the file

    Note in the claim file which parties received which version and when. This one line saves the reconciliation call later.

Format by recipient

RecipientFormat neededWhat they do with it
Carrier desk (Xactimate®)ESXImport for line-item estimate
Carrier desk (Symbility®)XMLImport for line-item estimate
Claim file / documentationPDFExhibit, no import needed
Contractor field estimatePDF (plus ESX or XML if writing in-platform)Facet confirmation, own estimate build
Homeowner / policyholderPDFReference copy

One order that includes ESX + PDF (or adds XML) covers every row above without a second order.

Version discipline: the part that actually breaks down

  • One file name convention across every copy

    Two files with different names for the same claim invite someone to work from the wrong one without noticing.

  • One person owns revision requests

    If both the carrier and the contractor can independently request a correction, you can end up with two corrected versions that disagree with each other.

  • Corrected reports replace the old file everywhere, not just in the requester's copy

    A revision fixed in the carrier's estimate but never sent to the contractor recreates the exact gap the shared file was meant to prevent.

  • Date stamp or version number visible on the file itself

    When a dispute reaches a supervisor or umpire, the file needs to self-identify as current without a side conversation to confirm it.

  • Keep the original delivery email

    It is the source record for what was ordered, on what address, and when, which matters if a version dispute needs resolving later.

Revision or re-order: which one to use

A revision (correcting a measurement error on the existing report) is the right move when the footprint is wrong, a structure was missed, or a facet was misread on an already-delivered report. Request it from the original delivery email rather than placing a new order, and the correction should be pushed out to every party holding a copy of the old file.

A new order is the right move when the property itself has changed, for example a different structure needs measuring, or the claim covers an address that was never ordered in the first place. Do not use a re-order to fix a measurement error; that creates a second file with a different order date and invites the exact version confusion this workflow is meant to avoid.

Frequently Asked Questions

Can the carrier and the contractor legally use the same measurement report?
Yes. A roof measurement report is ordered by property address for the claim and delivered to whoever the ordering party routes it to. There is no restriction against sharing the delivered file between the carrier desk and the contractor working the same claim.
What if the contractor's field measurement disagrees with the shared report?
That is a scope conversation, not a version problem, as long as both sides are looking at the same report. Document the specific facet or dimension in question and route the correction through a revision request rather than each side ordering a separate report.
Does ordering ESX + PDF instead of ESX-only cost more?
Yes, modestly. Published pricing from the site sponsor is Standard ESX $19, Complex-roof ESX $25, PDF-only $25, and ESX + PDF $29, so getting both formats from one order costs $10 more than ESX alone but avoids a second order later.
Who should hold the master copy of the report in the claim file?
The party managing the claim file, typically the carrier desk or the IA firm handling the claim, should hold the named master copy and be the point of contact for any revision request, even when the contractor is the one who spots the needed correction.

Sources