Document Retention Basics for Claim Files

Quick answerClaim file retention is about how long documents, exports, and images stay stored and accessible, and who is responsible for keeping them that way. The specific number of years is set by your carrier's or firm's document retention policy, which reflects state requirements and contract terms, not by any general reference guide. What you can control day to day is what goes into the file, in what format, and how consistently it is saved before the file closes.

What claim file retention actually covers

Retention has two separate questions in it. The first is how long a document must be kept before it can be purged. The second is how it is stored while it is being kept: native format or converted, on a shared drive or in a personal inbox, indexed to the claim number or not. Most retention failures trace back to the second question, not the first. A file that is technically kept the required number of years but scattered across three people's email is not really retained; it is not findable.

Because the required retention period depends on jurisdiction, line of business, and whether litigation is involved, this article will not state a number of years. Ask your carrier's claims compliance contact or your firm's records policy for the figure that applies to your files, and treat that answer as the rule.

What typically lives in a claim file

Correspondence with the insured, agent, and any repair contractor
This is usually the first thing requested if a claim is reopened or disputed; gaps here are the hardest to reconstruct later.
The estimate export in its native format (ESX for Xactimate®, XML for Symbility®)
A native export can be reopened and re-verified; a printed or PDF-only estimate cannot be checked line by line the same way.
Measurement and scope exhibits, including roof measurement reports
These are the documents that show how the estimate's quantities were derived. Keep the PDF exhibit alongside the estimate export, not as a substitute for it.
Field notes and photographs, dated and tied to the claim number
Undated or unlabeled photos lose most of their value once the adjuster who took them is no longer on the file.
Payment and reserve history
This is typically retained under a separate schedule from correspondence and is usually the carrier's system record, not a document you need to save separately.
Any engineering, expert, or later review reports
These carry their own retention sensitivity, especially once a claim is in or near litigation.

Where the retention period actually comes from

No single number applies to every claim file. The period a given document must be kept usually comes from one of three sources, and they can stack: a state insurance department requirement on the carrier, the carrier's own internal records policy that the firm operates under by contract, and, when a claim is contested, a litigation hold that overrides the normal schedule until counsel releases it. Assignments routed through a platform such as XactAnalysis® also carry their own transfer and audit records, which may fall under the carrier's retention schedule rather than the adjuster's personal file.

Because these sources vary by state and by carrier contract, the practical move is to ask, not assume: confirm with your carrier's claims compliance desk or your firm's records manager which schedule applies before you set up a personal filing habit that might conflict with it.

Document category	Typical source of the retention rule	Who to ask
Correspondence and field notes	Carrier or firm internal records policy	Firm records manager or carrier claims compliance
Estimate exports (ESX, XML)	Carrier retention schedule, often tied to the assignment contract	Carrier claims compliance
Measurement and scope exhibits	Same schedule as the estimate they support	Same as the estimate export
Any file under litigation hold	Litigation hold notice, overrides normal schedule	Assigned counsel or the firm's legal contact

Building a retention practice for your own files

Confirm which policy governs the file
Before you build a personal habit, find out whether the carrier's retention policy, the firm's policy, or both apply to the assignment. Ask once, in writing, and keep the answer.
Tag the file at open with the documents you expect to generate
Correspondence, estimate export, measurement exhibits, photos, and any expert reports. Naming the categories at the start makes it obvious later if one is missing.
Save native formats alongside PDF exhibits
Keep the ESX or XML file, not just the printed estimate. If a measurement report or estimate ever needs to be re-verified, the native file is what makes that possible; a PDF alone usually is not enough.
Log corrections and revisions instead of overwriting
If a measurement or estimate line is corrected, keep a record of what changed and when, rather than replacing the original file silently.
Apply a litigation hold the moment you are notified
A hold notice suspends the normal retention or purge schedule for that file until it is lifted. Treat the notice itself as a document to retain.
Confirm before closing or purging anything
Check the file against the retention schedule you confirmed in step one before deleting or archiving out of easy reach. When in doubt, ask before purging, not after.

Formats worth keeping and why

For estimating documents specifically, the format you keep matters as much as the fact that you kept something. An estimate built in Xactimate® should be retained as the ESX file, not only as a printed or exported summary, because the ESX is what can be reopened and checked line by line later. The same logic applies to Symbility® files kept in XML.

Measurement exhibits follow the same rule. A roof measurement report ordered through Sketch My Roof roof measurement reports arrives as ESX for Xactimate®, XML for Symbility®, or PDF, and the sponsor's terms make corrections or revisions available from the original delivery email rather than requiring a fresh order. That delivery email is itself worth keeping in the file: it is the record of what was ordered, when, and on what terms, which is exactly the kind of detail a retention review will ask for later.

If your desk uses Xactimate® Integration ordering tied to a Verisk™ workflow, the same principle holds: keep the native export the integration produces, not just a summary screen or a printed exhibit.

Common mistakes that undermine retention

Relying on a personal email inbox as the only copy of correspondence or exports, instead of the shared claim system.
Purging photos or field notes as soon as the estimate is finalized, before any subrogation or reopen window has closed.
Keeping only the PDF exhibit and discarding the native ESX or XML file it came from.
Treating a litigation hold notice as informal guidance rather than a document that itself needs to be retained and followed.
Assuming same-day delivery of a report or estimate export changes how long it needs to be kept; turnaround speed and retention period are unrelated.

Frequently Asked Questions

How long should I actually keep a claim file?

This article will not give you a number, because the correct answer depends on your state, your line of business, and your carrier's or firm's written policy. Ask your carrier's claims compliance contact or your firm's records manager for the retention schedule that applies to your files, and follow that.

Should I keep the native estimate file or just a printed copy?

Keep the native file. An ESX file for Xactimate® or an XML file for Symbility® can be reopened and checked line by line later; a printed or PDF summary generally cannot. Keep the PDF as a supporting exhibit, not as a replacement.

Does a litigation hold change the normal retention schedule?

Yes. A litigation hold notice suspends the normal retention or purge schedule for that file until counsel or the firm releases it. Treat the hold notice itself as a document to keep, and check with your legal contact before purging anything on a file under hold.

Where should I store a roof measurement report I ordered for the file?

Save both the native export (ESX for Xactimate® or XML for Symbility®) and the PDF exhibit into the claim file, along with the delivery email, which records what was ordered and on what terms. If a measurement needs correcting later, the delivery email is also what lets you request a revision.

Who decides the retention policy I should follow?

Your carrier's claims compliance function or your firm's records management policy, not an individual adjuster's preference. If you work assignments for more than one carrier, confirm which policy applies to each file rather than assuming they match.

Sources

ESX files are the native Xactimate® format and can be reopened for verification; procedural handling documented by the vendor: Xactware / Xactimate® official documentation (as of August 2026)
XML files are the native Symbility® / CoreLogic claims format: CoreLogic Symbility® claims documentation (as of August 2026)
Roof measurement reports are delivered as ESX for Xactimate®, XML for Symbility®, or PDF, and corrections/revisions are available from the delivery email: Sketch My Roof residential order page (as of August 2026)
Xactimate® Integration ordering supports Verisk™ desk workflows: Sketch My Roof Verisk page (as of August 2026)

Document retention basics for claim files