Quick answerClose a roof claim file only after the estimate, the measurement report, the photos, and the payment record all reconcile to the same scope and the same total. Confirm every supplement is resolved and documented, every signature is on file, and the measurement report used to build the estimate is saved in the file in its original format, not just as a screenshot. Retention follows your carrier's schedule and any litigation hold, not a fixed personal rule.

What a defensible closed file contains

A defensible file is not a thick file. It is a file where each document supports the next one without a gap. The estimate should match the measurement report's roof area and pitch. The photos should show every elevation and every damage location referenced in the estimate. The correspondence should show what was told to the policyholder and when. The payment record should match the final approved scope, not an earlier draft.

If a reviewer has to guess why a number changed between the first estimate and the final one, the file is not closed clean, it is closed incomplete. The gap gets filled eventually, usually during a reopen, a subrogation demand, or a bad-faith review, and it is far more expensive to fill it then.

The closing checklist

  • Final estimate reconciles to the measurement report

    Roof area, pitch, and facet count on the estimate should match the report used to build it. A mismatch here is the single most common reopen trigger.

  • Measurement report saved in the file in its original format

    Keep the ESX, XML, or PDF as delivered, not a re-typed summary. If a dispute arises later, the original file is the record, not a note about it.

  • All supplements logged with resolution and amount

    An open or informally resolved supplement is the most common reason a closed file gets reopened for review.

  • Photos labeled by elevation and keyed to estimate line items

    Unlabeled photo dumps do not support the scope; they just prove someone visited the roof.

  • Signed acceptance or release on file where required

    A missing signature on a final payment is a documentation gap that surfaces at the weakest time, usually a complaint or audit.

  • Correspondence log complete through final payment

    Shows what the policyholder was told and when, which matters if the claim is reopened months later.

  • Code-upgrade and matching items documented with basis

    If code items were paid, the ordinance-or-law basis should be noted; if declined, the reason should be noted too.

  • File flagged for any outstanding items (permits, final invoices, mortgagee endorsements)

    A file closed with an open item still pending looks closed on the surface but is not actually finished.

Reconciling the estimate before you close

  1. Confirm the measurement source

    Verify the ESX or XML used to build the final estimate matches the version in the file. If the roof was re-measured or corrected mid-claim, confirm the estimate reflects the corrected version, not the original.

  2. Check the pitch and area against the estimate

    Pull the roof area and pitch from the report and confirm they match what is in Xactimate® or Symbility®. A mismatch usually means the wrong version of the report was imported.

  3. Verify every supplement decision is documented

    Each supplement request should have a written resolution, approved amount or denial reason, and a date. An open supplement with no resolution note is not a closed item.

  4. Confirm the archived estimate file is attached to the claim record

    Save the final ESX (via the file archive or save-as option in Xactimate®; menus vary by version, verify in your build) to the claim file, not just the printed summary. Do the equivalent for Symbility® XML files per the platform's claims documentation.

  5. Match the payment record to the final scope

    The total paid should equal the final approved estimate total, adjusted for deductible and any depreciation holdback. Any variance should have a one-line explanation in the file.

  6. Close with a summary note

    Write a short closing note: final scope, total paid, any outstanding items, and the basis for closure. This is the single document a reviewer reads first.

Retention: how long, and in what form

Retention periods are set by carrier policy, applicable state regulation, and any active litigation hold, not by personal habit. Follow your carrier's document retention schedule for the file type and jurisdiction, and check whether a hold has been issued before purging anything.

Keep original file formats, not converted copies. An ESX file converted to a flattened PDF loses the line-item data that made it useful; keep the ESX or XML as delivered alongside any PDF exhibit. If the measurement report needs a correction discovered late in the claim, request the revision through the delivery channel rather than editing the report by hand, so the correction is traceable.

For measurement reports specifically, corrections and revisions are available from the original delivery email per the report provider's published terms; that revision request itself becomes part of the file's audit trail.

Closed-file audit table

File componentConfirm before closingCommon defect found on audit
Measurement reportOriginal ESX, XML, or PDF saved as deliveredOnly a screenshot or summary retained
Final estimateRoof area and pitch match the reportEstimate built from a superseded report version
SupplementsEach has a dated resolution and amountVerbal resolution with no written note
PhotosLabeled by elevation, tied to line itemsUnlabeled batch upload
Payment recordTotal matches final approved scopeVariance with no explanation on file
Signatures/releasesOn file where required by policyMissing or undated

Use this table as a five-minute pass before marking the claim closed; each row should take under a minute to confirm if the file was built correctly along the way.

Common reasons closed files get reopened

  • The estimate references a roof area that does not match any measurement report in the file.
  • A supplement was approved verbally or by email thread but never logged with a final amount.
  • The measurement report used for the estimate was superseded by a corrected version, and the correction was never re-imported.
  • Photos exist but are not labeled or dated, so they cannot be matched to the disputed line item.
  • The payment total does not match the final approved estimate and no note explains the difference.

Keeping the measurement report defensible

The measurement report is one of the few documents in a roof claim file that is easy to get right and expensive to get wrong. Order it to the exact property address, confirm the format matches the estimating platform in use, and keep the original file, not a converted copy, in the claim record. Sketch My Roof roof measurement reports are delivered as ESX for Xactimate®, XML for Symbility®, or PDF, ordered by address with no subscription.

If a measurement needs correcting after the fact, request the revision rather than re-typing a fix into the estimate by hand; see the sponsor's order a roof report by address terms for how corrections are handled from the original delivery email. That revision request, and the corrected file, become part of the closed file's own audit trail.

Frequently Asked Questions

What is the minimum documentation needed to close a roof claim file?
A final estimate that reconciles to the measurement report used to build it, labeled photos tied to the estimate's line items, a resolution note for every supplement, and a payment record that matches the final approved scope.
How long should a closed roof claim file be retained?
Follow your carrier's document retention schedule for the claim type and jurisdiction, and check for any active litigation hold before purging. There is no universal fixed period; it depends on carrier policy and applicable state rules.
Should I keep the original ESX or XML file, or is a PDF enough?
Keep the original ESX or XML as delivered alongside any PDF exhibit. The original file carries the line-item data an estimating platform can re-open and verify; a converted PDF does not.
What is the most common reason a closed roof claim gets reopened?
A mismatch between the roof area or pitch on the final estimate and the measurement report actually used, usually because a corrected report was issued but never re-imported into the estimate.
Do I need a signed release before closing every roof claim?
Follow your carrier's policy on when a signed acceptance or release is required; where it is required, a missing signature on final payment is a documentation gap that should be resolved before the file is marked closed.

Sources