An insurance estimate and a retail bid serve different masters. The insurance scope is priced to the carrier's RCV number with overhead and profit; the retail bid is what a customer pays when they are writing the check. When a contractor runs both from one Xactimate project, the practical problem is keeping them honest: the retail number must not leak back into the insurance estimate, and the insurance lines must not inflate the customer price. That is what cash-bid isolation is for.
The split problem, concretely
Say the insurance scope covers a full roof replacement on a hail claim. The customer also wants the back patio cover rebuilt, which is outside the claim. Add the patio lines inside the insurance file and the RCV teases up; delete the deductibles, and the copy of the original file is no longer the original. Every manual approach either duplicates the project or edits it in place. ESXPress handles the split with a dedicated toggle per line group: insurance lines stay put, the cash-bid lines move into an isolated section of the estimate, and no line values are rewritten anywhere.
Cash-Bid Mode and the Budget Board
The Budget Board is the view that makes the split visible. Insurance line items sit in claim-scope groups; the toggled cash-bid groups sit apart, with their own subtotals. The original insurance lines are untouched, the isolation is a view and export control, not an arithmetic patch. When you export, the cash-bid lines can be kept in a separate ESX file and the insurance ESX file left exactly as converted.
Why this matters to the settlement
Carriers pay on the scope of the loss. If a retail item rides along in the same project, the carrier's review sees a mismatch between the scope and the total. That mismatch creates support questions on the whole file, not just the extra line. Isolation keeps the claims file clean for the adjuster and the retail file clean for the customer, and it keeps the contractor from running two contradictory copies of the truth. The flat conversion of 1,000+ lines also means the split does not trigger a per-line penalty, a 450-line insurance scope plus a 60-line cash-bid addendum stays inside the included line cap with no overage cost.
Keeping the numbers straight after the split
Once the two files are separated, run both through the free ESX validator: one file for the claim, one for the job. The validator checks the structural XML on both, so a hand-edited field in either file is caught before it reaches Xactimate or the customer. The Xactimate pricing explainer is worth a read before you compare line prices across files, because regional price lists produce different printed values for the same SEL code, a difference that is not your margin leak.
The simplest mental model
Insurance lines are the claim. Cash lines are the job. Keep them in the same project only long enough to build them, then export them apart, one file for the adjuster, one for the customer, and the original scope untouched throughout. That is the whole discipline, and it is exactly what ESXPress automates.
Related: split insurance scope into an ESX file.