From carrier file to contractor-ready ESX in five controlled steps.
Send the estimate, photos, and what you know about the job. Our team reviews the file, rebuilds the scope in Xactimate, separates supported work from field questions, and returns a native ESX for your approval. You keep the customer, the carrier communication, and every submission decision.
One file. Five accountable handoffs.
Every stage has one job: remove ambiguity before the file reaches your desk. You always know what we received, what we found, what still needs a field answer, and what is ready for review.
-
Upload the carrier estimate, photos, and project notes. We confirm receipt and check that the core file is complete.
-
We identify whether the file needs estimate writing, scope review, or deeper technical management. We confirm the service and price before billable work begins.
-
Our estimating team reconstructs the work in Xactimate around access, assemblies, trade sequencing, finish continuity, and supported repair operations.
-
Every added line receives an F9 note tied to code, manufacturer documentation, construction logic, or file evidence. Open field questions are separated from supported scope.
-
You receive the native ESX and supporting documentation. Your team reviews the package, decides what belongs in the carrier file, and controls every submission.
The 48-hour clock starts with a complete file.
START HERE
Send the carrier estimate as a PDF or ESX, the loss photos, and whatever your team already knows about the job. Verbal notes are fine.
WHAT HAPPENS NEXT
We confirm the service level and price before billable work begins. Once the core file is complete, standard delivery is within 48 hours.
HELPFUL WHEN AVAILABLE
An ESX or sketch, measurements, Matterport, signed contract, prior carrier correspondence, material specifications, manufacturer documents, and moisture logs.
IF SOMETHING IS MISSING
We tell you what we need within four business hours. The 48-hour clock begins when the missing item arrives, so there is no surprise delay on day two.

