Import vs manual trace: which one to use
An ESX file built for a specific address already contains the roof's facet outlines, pitch per facet, and calculated area. Bringing that file into Xactimate® via the sketch import option reproduces the same geometry inside the estimate, so the roofing-square math ties directly to the source report.
A manual trace means drawing the roof in the Xactimate® sketch tool by hand, facet by facet, using the report's PDF, a diagram, or site notes as reference. It takes longer and depends on the person drawing to set each pitch correctly, but it is the right fallback when there is no ESX for the property, when the structure has changed since the report was produced (an addition, a re-roof section, storm damage that altered the plane count), or when the estimate needs a facet the original report did not scope, such as a detached garage ordered separately.
Most estimates on a standard residential roof are faster and more accurate with the import. Reserve the manual trace for exceptions, and when you do trace by hand, cross-check every pitch against the report legend rather than eyeballing the roof photo.
Importing the report's ESX into the sketch
- Confirm the file type
Make sure the delivered file is an ESX built for Xactimate®, not a Symbility® XML or a PDF. The three formats are not interchangeable at the file level.
- Open the claim in Xactimate®
Start or open the estimate for the correct claim before importing, so the sketch attaches to the right job file.
- Use the sketch import option
Bring the ESX in via the import function in the sketch module. Menus vary by version; verify the exact menu path in your build against the official documentation before you rely on it for a live claim.
- Let the facets and pitches populate
The imported sketch should show each roof facet with its pitch already set and the total area calculated. Do not manually re-enter areas at this point; that is the next check, not a redraw.
- Compare the import to the source report
Open the report's PDF or summary page side by side with the sketch and check facet count, total squares, and pitch per facet before you build line items on top of it.
Checking pitch after import
- Match pitch per facet, not just the average
A roof reported at a blended 7/12 average can still have a low-slope porch facet and a steep dormer facet. Xactimate® prices steep and low-slope roofing differently, so the sketch needs the actual per-facet pitch, not the average.
- Verify the pitch multiplier the sketch applied
Xactimate® converts footprint to sloped area using the same rise-over-run relationship the report used. If the sketch shows a different total area than the report for the same footprint, the pitch value is the first thing to check.
- Flag any facet marked as unknown or default pitch
An import can occasionally leave a facet at a default pitch if the source data for that plane was incomplete. An unflagged default pitch understates or overstates that facet's squares.
- Confirm eave and ridge lengths against the report
Pitch errors often show up first as a mismatch in total ridge or eave footage, which drives ridge cap and starter course quantities separately from the field area.
Checking facet count and total squares
Facet count is the second check. Count the planes shown in the sketch and compare that number directly to the report's facet count. A missing facet, most often a small dormer, a bay window roof, or a porch return, will understate total squares even when every other pitch is correct.
The underlying math is simple and worth knowing rather than trusting blindly: pitch multiplier equals the square root of rise squared plus run squared, divided by run. Area equals footprint multiplied by that multiplier. Multiply by 100 to convert square feet to roofing squares. The table below applies that formula across common pitches to a sample 1,800 square foot footprint, so you can see how much a wrong pitch shifts the final square count.
| Pitch | Multiplier (sqrt(rise^2+run^2)/run) | Area at 1,800 sq ft footprint | Roofing squares |
|---|---|---|---|
| 3/12 | 1.031 | 1,856 sq ft | 18.6 |
| 4/12 | 1.054 | 1,897 sq ft | 19.0 |
| 6/12 | 1.118 | 2,012 sq ft | 20.1 |
| 8/12 | 1.202 | 2,164 sq ft | 21.6 |
| 9/12 | 1.250 | 2,250 sq ft | 22.5 |
| 10/12 | 1.302 | 2,344 sq ft | 23.4 |
| 12/12 | 1.414 | 2,545 sq ft | 25.5 |
Same footprint, one pitch step in either direction, and the square count moves by roughly half a square per 100 square feet of footprint. On a 2,500 square foot footprint that gap is over a full square, enough to change a bundle count.
Common sketch mismatches and how to fix them
| What you see | Likely cause | Fix |
|---|---|---|
| Sketch total squares differ from the report total | A facet imported at the wrong pitch, or a facet missing from the import | Compare facet-by-facet pitch and count against the report before touching line items |
| Ridge or hip length looks short against the roof outline | Facets not fully joined at the ridge line during import or trace | Check that adjoining facet edges snap together in the sketch; a gap under-reports linear ridge and hip footage |
| One facet shows a flat or unusually low pitch | Default pitch applied where source data for that plane was incomplete | Set that facet's pitch manually from the report legend or a site photo before pricing it |
| Detached structure roof missing from the sketch | The report or the order did not include the secondary structure | Order a separate report for the detached structure or add it to the trace; do not estimate it off the main roof's average pitch |
| Total squares match but waste percentage looks off | Waste factor applied in Xactimate® does not match the facet complexity in the report | Adjust the waste factor line item to reflect actual facet count and cut complexity, independent of the raw area |
When to trace by hand instead
Trace manually when the property has no ESX on file, when storm damage has changed the roof plane count since the report was produced, or when you are scoping a structure the original order did not cover. In every manual trace, pull pitch values from the report's legend or from documented site notes rather than estimating pitch by eye; pitch is the single input most likely to be wrong in a hand-drawn sketch, and it is the input that drives both squares and the steep or high-pitch charge.
Reports ordered by address are available as ESX for Xactimate®, XML for Symbility®, and PDF. If your file did not come as ESX, order a roof report by address in the ESX or ESX + PDF format so the next estimate on that property imports directly instead of requiring a trace.
Frequently Asked Questions
Should I always import the ESX instead of tracing the roof by hand?
Why does my Xactimate® sketch show a different total than the measurement report?
Does pitch really change the square count that much?
Can I import a Symbility® XML into Xactimate®?
What if the report has an error in facet count or pitch?
Sources
- Sketch import procedure for bringing an ESX file into the Xactimate® sketch; menu paths vary by version: Xactimate® official documentation (as of August 2026)
- Symbility® XML file handling and claims documentation reference for XML-based estimates: Symbility® / CoreLogic claims documentation (as of August 2026)
- Report formats available: ESX for Xactimate®, XML for Symbility®, PDF; ordered by property address: Sketch My Roof service facts page (as of August 2026)
- Residential report ordering, ESX and ESX + PDF formats available by address: Sketch My Roof residential order page (as of August 2026)
