Who owns Xactimate estimates: contractor, carrier or software provider?

Why an Xactimate estimate has more than one owner#

An Xactimate estimate has more than one owner because it is built from three sources at once: what your estimator observed and decided, the price and line item data supplied by the software provider, and the insurance claim it was written for. Each source brings its own rights and its own contract.

The question usually comes up at a specific moment: a company is retiring old estimates, selling the business, changing estimating platforms or considering licensing its restoration records. In each case the useful question is not who owns the file but who controls each part of it, and what each party's terms allow you to do with that part.

Layer one: your scope, measurements and notes#

The contractor layer is the scope your team built: the line items chosen, the quantities, the room and roof diagrams, the attached photos and the notes explaining the work. That layer reflects your company's expertise, and it is generally the part you have the strongest claim to, subject to your customer and program agreements.

This layer is also the most useful one for licensing. A sequence of observed damage, chosen repair items and the reasoning behind them shows how an experienced estimator thinks, and the same scope with prices removed still carries most of that signal. The contractor layer usually includes the items below.

• 1Line item selections and quantities for each room, elevation or area.
• 2Diagrams and measurements your team took on site.
• 3Line item notes and the narrative explaining scope decisions.
• 4Photos taken by your crew and attached to the estimate.
• 5Revisions made after reinspection, with dates and reasons.

Layer two: the carrier's claim file#

The carrier layer is the copy of your estimate that enters the carrier's claim file, alongside the carrier's own estimate, coverage decisions and payment records. Once you submit an estimate, the carrier keeps it as part of its record of the claim and controls that record.

Submitting a copy does not usually transfer your rights in your own work, but a program or preferred vendor agreement can change that. Some agreements give the carrier or program administrator ownership of, or broad rights over, documents submitted through the program, and many treat claim information as confidential. An estimate written by a staff or independent adjuster belongs to the carrier side, even if you received it as an editable file to work from.

Layer three: the software provider's price data and terms#

The vendor layer is the content and software the estimating platform supplies under its license: price lists, line item codes and standard descriptions, and the program itself. Your subscription lets you use that content in your work, and the end-user license agreement sets out what else you may and may not do with it.

Software licenses of this kind commonly restrict copying, extracting or redistributing the vendor's data outside the product. Unit prices that came from a vendor price list are therefore best treated as vendor content, even though they appear inside your estimate. Read the current license and your order form, and ask counsel how they apply before any price field leaves the company.

Who controls each part of a typical estimate#

Each element of a typical estimate maps to one of the three layers, and that mapping decides how the element is handled in a licensing review. Treat the table as a starting point for the review, not a conclusion, because program agreements and license terms can move an element from one column to another.

ESX files: what changes when an estimate is exported#

Exporting an estimate, commonly as an ESX file, changes where a copy sits but not who controls its contents. The exported file still holds all three layers, including vendor pricing and claim identifiers, so it is not a clean licensing package on its own.

A vendor-specific file format may also be meant to open only in the vendor's software, and the license may limit tools that read or convert it. The safer route is usually to export through the reports the software is designed to produce, or to rebuild the contractor layer from your own job management system, where scope notes, photos and quantities often live as well.

Whatever route you choose, export before a subscription lapses. Access to old estimates can depend on an active license, and a company that cancels first and asks later may find its own scope history out of reach.

Illustrative: a water mitigation company maps its estimates#

Illustrative: Harbor Line Restoration, a fictional water and fire mitigation company, has written years of estimates in Xactimate and tracks jobs, moisture logs and photos in a separate restoration job management system. The owner wants to know which estimate records could belong in a licensed dataset.

The team maps each estimate element to a layer. Carrier and adjuster estimates received as files are set aside. Counsel reads the estimating software license and advises that unit prices and standard line item descriptions stay out, so the team replaces unit prices with item categories and keeps only the contractor's own selections, quantities, diagrams, scope notes and photos. Jobs from a preferred vendor program are flagged for a separate review of that program's agreement.

The result is a dataset built mostly from the job management system and cross-checked against estimate reports, with a column recording the layer and rights basis for every field. The owner can now explain to any reviewer why each field is included.

How SourceX handles estimate layers#

SourceX separates the three layers during the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check before that uses metadata only, such as which estimating platform you used, which years are available and whether program jobs are flagged.

The SourceX Evidence Packet then records, for each included field, its provenance, the licensing rights relied on, the permitted use, the privacy record and your release authorization. Vendor price data and carrier documents stay out unless counsel confirms a basis to include them, and you approve each step.