Quick answerA complete supplement package contains the original estimate, the revised estimate with the added line items, a comparison showing only what changed, photos referenced to each added line, and a measurement report matched to the loss address. Attach the measurement report in the format the receiving desk uses: ESX for Xactimate®, XML for Symbility®, or PDF for the file. Name files consistently and confirm the property address on the measurement report matches the claim address exactly before submission.

What goes in the package

  • Original estimate or prior approved scope

    Gives the reviewer a baseline. Every added line in the supplement should trace back to something not present here.

  • Revised estimate with the new line items

    This is the estimate as it should read after the supplement. It should be a complete, current version, not a fragment.

  • Line-item comparison showing only the additions or changes

    A side-by-side reduces back-and-forth by isolating exactly what is new, rather than requiring a full re-read of both estimates.

  • Photos referenced to each added line item

    A quantity or line item without a photo reference is harder to trace back to a specific condition on the roof.

  • Measurement report matched to the claim address

    Backs the area, facet count, and pitch used to build the added quantities. See the section below for format.

  • Manufacturer instruction sheet, only where a specific line item cites it

    Attach it as supporting reference for that line item. Do not attach general manufacturer literature unrelated to a line.

  • Cover sheet listing package contents

    A one-page index of what is attached and in what order saves the reviewer from opening every file to find out.

Measurement backup: what to attach and in what format

The measurement report is the backup for area, facet count, pitch, and any waste factor used to build the added quantities in the estimate. It should show the same property address as the claim, and its area figures should match what the estimate line items actually use.

Match the format to the platform the estimate lives in. An ESX file imports directly into Xactimate® via the sketch import option; menus vary by version, verify the exact steps in your build. An XML file serves the same role for Symbility®. A PDF is the version to attach to the file itself or hand to anyone who does not have estimating software open. You can order a roof report by address in any of these formats from the site sponsor, Sketch My Roof.

For Verisk™-connected desks, the package is often routed through XactAnalysis®. Confirm the desk's required attachment format before you submit, since a wrong format is a common reason a package gets kicked back for resubmission rather than reviewed.

Checking the roof math behind the added quantities

Roof area is footprint multiplied by a pitch multiplier, and one roofing square equals 100 square feet. The pitch multiplier is derived as the square root of rise squared plus run squared, divided by run. Use this to sanity-check that the measurement report's stated area lines up with the pitch and footprint it reports, before that area drives an added quantity in the supplement.

PitchMultiplier1,800 sq ft footprint, area in squares
4/121.05418.97
6/121.11820.12
8/121.20221.64
12/121.41425.45

Area in squares is footprint times multiplier, divided by 100. Recalculate from the measurement report's own stated footprint and pitch rather than assuming these figures apply to a specific roof.

Building the comparison

  1. Open the current approved estimate

    Confirm this is the version the added line items should be compared against, not an older draft.

  2. Create the supplement within the estimating platform

    In Xactimate®, this is typically done through the platform's supplement workflow; in Symbility®, through its comparable revision workflow. Menus vary by version, verify the exact steps in your build and consult the vendor's own documentation for the current click path.

  3. Add the new line items with measurement-backed quantities

    Pull quantities from the measurement report rather than re-deriving them by hand, so the estimate and the backup agree.

  4. Generate a comparison showing added or changed lines only

    Most estimating platforms can output a delta or comparison view. Export this as its own document for the package.

  5. Assemble the package in order

    Cover sheet, comparison, revised estimate, photos, measurement report, then any cited manufacturer sheet, saved as consistently named files.

Formatting and file naming

  • Claim number in every file name

    A supplement package with unlabeled files is harder to match back to the claim once it leaves your outbox.

  • One format per destination, not one of everything

    Send ESX to an Xactimate® desk and XML to a Symbility® desk rather than attaching every format to every submission.

  • Property address on the measurement report matches the loss address exactly

    A mismatched address is one of the more common reasons a measurement report gets questioned on review.

  • Page order matches the cover sheet index

    If the cover sheet lists five attachments in a specific order, the files should arrive in that same order.

Common gaps in a supplement package

  • Revised estimate attached without a comparison, so every line has to be checked against the original by hand.
  • Photos included but not referenced to a specific line item, leaving the connection to be inferred.
  • Measurement report with a footprint or pitch that does not match the quantities actually used in the estimate.
  • No cover sheet, so the reviewer has to open every file to learn what was submitted.
  • PDF exhibit missing when the package needs a document version for the file, not just an ESX or XML file.

Frequently Asked Questions

What counts as measurement backup in a supplement package?
A measurement report matched to the claim address, showing the footprint, pitch, and facet layout that the added quantities are built from. Attach it in the format the receiving platform uses: ESX for Xactimate®, XML for Symbility®, or PDF for the file.
Does the package need a side-by-side comparison, or is the revised estimate enough?
Include both. The revised estimate is the full current scope; the comparison isolates only what changed, which is what a reviewer needs to check quickly.
Should every added line item have its own photo?
Reference each added line to a specific photo where one exists. A quantity without a photo reference is harder to trace back to a condition on the roof.
Which file format should the measurement report be in?
Match it to where the estimate lives: ESX for Xactimate®, XML for Symbility®, or PDF when the package needs a document version rather than an estimating-software file.
What if the measurement report needs a correction after it is already in the package?
Request a revision from the report's delivery email rather than re-ordering, then swap the corrected file into the package before submission.

Sources