Xactimate Estimating Guide for Restoration Contractors
A useful Xactimate estimate does more than name the damaged finish. It explains the complete repair sequence, documents why each operation belongs, and gives the contractor an editable file that can be reviewed before submission.
This guide explains the process in plain language. It is built for restoration contractors handling roofing, interior repair, and reconstruction scopes.
The short version
A complete estimate should answer five questions:
- What must be protected or accessed before work starts?
- What must be detached, removed, or opened?
- What preparation and assembly layers are required?
- What must be reset, finished, and cleaned?
- What evidence supports each addition?
If the file skips one of those stages, it may be under-scoped even when the visible damage is listed.
What an Xactimate estimate should contain
A contractor-ready estimate connects the observed damage to the operations needed to restore the property. That usually includes:
- Accurate rooms, elevations, dimensions, and quantities
- Labor and material line items that match the actual repair method
- Access, protection, removal, preparation, installation, reset, and cleanup operations
- Trade sequencing and finish continuity
- Clear separation between supported work and items that still need field verification
- F9 notes tied to photos, file evidence, construction logic, code, or manufacturer guidance
- A native ESX file that the contractor can review, revise, archive, and submit
A total by itself is not enough. The value of the estimate comes from the repair logic and the documentation inside the file.
Why carrier estimates often miss work
Many estimates describe the final surface without documenting the work required to reach it. A line for drywall or shingles can leave out connected operations such as protection, access, detach and reset, substrate preparation, flashing, transitions, finish matching, and cleanup.
Common causes include:
- The inspection focused on visible damage instead of the complete assembly
- Photos did not show every affected condition
- Measurements or material details were incomplete
- Connected trades were treated as separate problems
- The estimate named the result but skipped the construction sequence
- Code or manufacturer requirements were not researched
The goal is not to add every possible line item. The goal is to include every operation that is supported by the file and required to perform the repair correctly.
A practical reconstruction process
1. Confirm the file evidence
Review the current estimate, photographs, measurements, reports, material information, and any available field notes. Mark missing information instead of guessing.
2. Rebuild the repair sequence
Work through the project in the order the repair will occur. Start with access and protection. Continue through removal, preparation, assembly, reset, finish, and cleanup.
3. Match each operation to Xactimate
Choose line items that reflect the actual labor, materials, quantities, and conditions. Avoid vague allowances when a specific supported operation is available.
4. Document the support
Use F9 notes to show why an item belongs. A strong note connects the operation to file evidence, construction logic, code, or manufacturer instructions.
5. Separate facts from field questions
Do not present an unverified condition as fact. Put open measurements, hidden conditions, material questions, and site decisions on a field verification list.
6. Deliver an editable file
The contractor should receive a native ESX, not only a flattened PDF. The company can then review the scope, revise the file, and control every submission.
Commonly missed reconstruction operations
The exact scope depends on the loss, but contractors should routinely check for:
- Contents and surface protection
- Access equipment and difficult working conditions
- Detach and reset of fixtures, trim, appliances, or connected components
- Demolition required to expose the damaged assembly
- Debris handling and disposal
- Substrate cleaning, drying, preparation, or replacement
- Underlayment, membranes, flashing, fasteners, sealants, and accessory materials
- Matching, blending, transitions, and finish continuity
- Multiple trade mobilizations or sequencing requirements
- Required testing, permits, code upgrades, or manufacturer procedures
- Final cleaning and jobsite closeout
This is a review framework, not a universal list of billable items. Every addition still needs support.
What makes an F9 note useful
An F9 note should help another reviewer understand the reason for the line item without having to guess. Useful notes are specific, factual, and tied to the file.
A useful F9 note may identify:
- The photo, room, elevation, or measurement that supports the quantity
- The construction step that makes the operation necessary
- The code section or manufacturer instruction that applies
- The connected material or component that must be detached, removed, or restored
- The condition that must be verified before the item is finalized
Avoid unsupported conclusions, emotional language, and claims about what a carrier must approve.
ESX file versus PDF
A PDF is useful for reading, but it is not the working estimate. An ESX preserves the editable Xactimate project data, including line items, notes, quantities, and structure.
For contractor control, the clean handoff is:
- Native ESX file
- Review PDF
- Indexed photo or documentation record when available
- Field verification list
- Clear notes for supported additions
What SaguaroScope does
SaguaroScope provides Xactimate estimate writing, scope reconstruction, and supplement documentation for restoration contractors nationwide. Our estimating teams build files for contractor review and control.
We do not act as a public adjuster. We do not negotiate claims, contact the carrier, communicate with the homeowner, or guarantee approval. The contractor decides what belongs in the file and controls every submission.
See how the process works
Review common scope gaps
Send a file for review
Contractor file checklist
Before sending a file, gather as much of the following as possible:
- Current estimate in PDF and ESX when available
- Loss photos and overview photos
- Measurements, sketches, roof reports, or floor plans
- Material identification or manufacturer information
- Damage reports and relevant field notes
- Known code, permit, access, or sequencing issues
- A clear description of the work your team believes is required
Missing information does not automatically stop the review. We separate open questions so your field team knows what still needs an answer.
Frequently asked questions
Does every estimate need a full reconstruction?
No. Some files only need professional estimate writing from a clear contractor scope. Others need a detailed review because the current estimate misses supported operations. The file should determine the service.
Can SaguaroScope submit the estimate to the carrier?
No. We prepare documentation for the contractor. Your company reviews, approves, and submits the deliverable.
Do you guarantee that added items will be approved?
No. No estimating company can control a carrier decision. We focus on clear repair logic and supportable documentation.
What types of files are a fit?
Our core work is roofing, interior repair, and reconstruction estimating. Mitigation and contents files use different workflows and are outside our core service.
Start with one file
Send the current estimate, photos, and available documentation. Our team will review the file, identify the right path, and confirm the service before billable work begins.