Restoration Job Documentation and Estimating: How to Build a File That Supports the Work Performed

Documentation Starts Before the Estimate

Estimating becomes difficult when the estimator is asked to reconstruct a job from incomplete field information.

Before discussing line items, establish the basic project facts:

• Customer and property identity
• Date of loss and date discovered when known
• Reported cause or source
• Date and time of first inspection
• Areas inspected
• Affected and unaffected rooms
• Safety concerns
• Existing conditions or pre-existing damage
• Customer authorization
• Emergency limitations or access restrictions
• Initial photos and measurements

The estimate should grow from the documented scope. It should not be a separate document created later from memory.

Build the File Around Four Questions

A useful file should answer four questions.

1. What happened?

Establish the physical conditions. What was wet, burned, contaminated, broken, stained, or otherwise affected? What was the observed source or reported cause? Which materials and assemblies were involved?

2. Why was this scope selected?

If carpet was removed, explain why. If drywall was dried in place, explain the condition and drying approach. If equipment was added, moved, or removed, make the reason traceable.

3. What did the company actually do?

The file should show labor, equipment, demolition, cleaning, manipulation, containment, contents handling, specialty work, and other performed tasks with enough detail to connect them to the property.

4. What was the final condition?

Completion documentation closes the loop: final readings, final photos, equipment removal, completed scope, remaining exclusions, customer acknowledgment, and final invoice.

If the file answers those four questions, the estimate becomes easier to evaluate.

The Initial Inspection Is the Foundation

The first site visit is when evidence is easiest to capture and easiest to lose.

A restoration company should have a repeatable inspection process that addresses:

• Loss source or suspected source
• Water migration or affected-area boundaries
• Material types and assemblies
• Dimensions and quantities
• Pre-existing damage
• Contents conditions
• Access limitations
• Utilities
• Contamination or environmental concerns
• Structural or electrical hazards
• Customer priorities
• Photographs before demolition or manipulation

Do not let the first photo of a wall be the photo taken after half of it has already been removed.

Photographs Should Prove Context, Not Just Quantity

A folder containing 300 unlabeled close-ups can be less useful than 60 organized photographs.

Use a deliberate sequence:

• Wide view: establishes the room or area
• Medium view: establishes the assembly or affected section
• Close view: documents the specific condition

Room naming should be consistent across photos, sketches, moisture maps, estimates, and daily notes. If the estimator calls a space “Bedroom 2,” the photo log should not call it “back room” while the technician calls it “kid bedroom.”

Photographs should also capture:

• Source condition when visible
• Pre-existing or unrelated damage
• Material interfaces
• Water lines or soot patterns
• Equipment placement
• Containment
• Removed materials before disposal when practical
• Contents condition
• Final condition

A photograph is strongest when the reviewer can answer: Where is this, what am I looking at, and why does it matter?

Water Mitigation Files Need a Drying Story

Water work is especially documentation-dependent because the physical condition changes rapidly.

The ANSI/IICRC S500 framework addresses professional water restoration topics including inspections, instruments, psychrometry, structural restoration, contents evaluation, and project documentation. The point for an owner is not to turn every technician into a standards lawyer. It is to build a field process that records the information needed to manage and explain the drying project.

A water file commonly includes:

• Source and affected-area documentation
• Water category/contamination observations when applicable
• Moisture map
• Material moisture readings
• Meter/instrument identification according to company SOP
• Ambient and affected-area psychrometric conditions
• Equipment type, quantity, and placement
• Monitoring dates and times
• Equipment moves/additions/removals
• Material removal decisions
• Drying progress
• Final readings
• Completion photos

Our supporting article What Should Be Included in a Water Mitigation Documentation File? expands this into a practical checklist when released.

Moisture Maps Need Location, Not Just Numbers

A reading without a location is difficult to interpret.

The moisture map should let another person understand:

• Which rooms were affected
• Which walls, floors, ceilings, or assemblies were tested
• Where readings were taken
• Where water migrated
• Which reference materials or unaffected areas were used
• How the affected area changed over time
• Where final readings were taken

The related daily log should show the progression, not merely a repeated form with numbers filled in.

For more detail, see Moisture Maps, Drying Logs, and Photos: What Restoration Companies Should Document when released.

Estimating Software Is a Tool, Not the Scope

Xactimate and other estimating platforms can organize measurements, line items, pricing, calculations, and reports. They do not inspect the building for you.

Verisk's published Xactimate pricing methodology is important context: its price lists are designed around researched market information and assumptions, but Verisk also says a published price cannot be guaranteed to fit every contractor, repair, or structure. Xactimate allows users to inspect price components and modify costs when appropriate to the specific job and company.

Owners should therefore separate three things:

1. The physical scope — what the property needs
2. The estimating method — how quantities and tasks are represented
3. The company's actual cost and pricing decision — what it costs the contractor to perform the work and what price the company determines is appropriate

Do not reverse that order by searching for line items first and letting available line items define what happened at the property.

Our Xactimate for Restoration Companies article goes deeper when released.

Every Estimate Line Should Have a Reason to Exist

The best estimate is not the one with the most line items. It is the one where quantities and tasks correspond to documented conditions.

For each meaningful charge, ask:

• Is the quantity measurable or otherwise supportable?
• Does the file show the affected area?
• Is the activity actually part of the performed or proposed scope?
• Is an unusual condition explained?
• Does the estimate duplicate another task?
• Does the line-item activity match the intended work?
• Are subcontractor or specialty costs supported when applicable?

A reviewer should not have to guess why a task is present.

Scope Notes Should Explain Decisions, Not Repeat Line Items

“Remove drywall — 64 SF” is a quantity. It is not a scope explanation.

A useful note might explain that the lower wall assembly was affected by contaminated water, that the material could not be cleaned in place, or that removal was required to access a wet cavity. The exact explanation depends on the real job and should be based on observed conditions and professional judgment.

The goal is not to write a novel. The goal is to capture the reason a reviewer cannot see from the line item alone.

Equipment Records Should Match the Project Timeline

If equipment billing is part of the project, the file should make the equipment history easy to reconstruct.

Track:

• Equipment identifier when company policy uses one
• Equipment type
• Placement location
• Date/time placed
• Date/time moved
• Date/time removed
• Reason for material equipment changes
• Monitoring data that informed continued use

Do not make the invoice the first place anyone sees the equipment count.

Daily Notes Are the Bridge Between Field and Office

Daily notes should capture material events, not filler.

Useful entries include:

• Who visited
• What was inspected or performed
• Customer access issues
• Moisture progress
• Equipment changes
• Newly discovered conditions
• Scope discussions
• Customer decisions
• Adjuster/TPA communications
• Safety or containment changes
• Work not performed and why
• Next planned action

A note like “monitoring done” does not tell the estimator or reviewer what changed.

Keep Important Communication in the File

Restoration work can involve owners, tenants, adjusters, desk reviewers, TPAs, plumbers, roofers, environmental consultants, subcontractors, mortgage companies, and others.

For material instructions, record:

• Date and time
• Person and organization
• What was discussed
• What was approved, denied, or requested
• What action the restoration company will take next

If an important direction is given by phone, summarize it in the project record. Do not let a disputed scope depend entirely on one employee remembering a call three months later.

Supplements Should Explain What Changed

A supplement is easier to evaluate when it answers a simple question: Why was this not in the original estimate?

Legitimate reasons might include concealed conditions discovered during demolition, revised measurements, a changed repair method, additional authorized work, or material that could not be evaluated during the first inspection.

A strong supplement package can include:

• Original scope/estimate reference
• Newly discovered condition
• New photos
• Revised quantity or measurement
• Explanation of the change
• Updated estimate
• Supporting vendor/subcontractor documents where relevant
• Authorization or communication records where required

Do not send a revised total with no explanation and expect the reviewer to reverse-engineer the change.

See Supplements and Estimate Revisions: Why Restoration Files Get Sent Back when released.

Program Requirements Are an Overlay, Not Your Entire SOP

TPA and managed repair assignments can add deadlines, portal rules, file naming, photo requirements, estimating rules, carrier-specific guidelines, warranty forms, and closeout steps.

Your company should still own its underlying documentation standard.

A practical model is:

Company restoration-file SOP + program-specific overlay = assignment workflow.

That prevents technicians from learning 12 completely different field processes while still allowing the office to meet contractual program requirements.

Our existing Restoration TPA Networks guide and TPA Documentation Requirements resource provide additional program context.

Completion Documentation Is Part of the Estimate Story

The job file should not end when the last technician leaves.

Closeout may include:

• Final moisture readings
• Final psychrometric conditions when relevant
• Equipment removal record
• Final photos
• Completed repair photos
• Contents reconciliation
• Certificate or acknowledgment of completion when applicable
• Final invoice
• Warranty or care information
• Remaining exclusions or customer-responsibility items
• Required program closeout documents

The beginning and end of the file should match. If the initial moisture map identified eight affected wall locations, final drying documentation should not leave the reviewer wondering what happened to five of them.

Build the Process So Quality Does Not Depend on One Great Employee

The strongest operational improvement is a repeatable file structure.

Create mandatory project stages with clear ownership:

1. Intake and authorization
2. Initial inspection
3. Scope development
4. Work execution
5. Monitoring/daily documentation
6. Estimating
7. Quality review
8. Supplement/change management
9. Completion
10. Billing and archive

Define the minimum evidence required before a job can move to the next stage. Then audit files for completeness and usefulness, not just whether a checkbox was clicked.

How The Restoration Directory Helps Restoration Companies

The Restoration Directory is building an educational resource library for restoration professionals while helping property owners find restoration companies that serve their area.

For restoration owners, the goal of resources like this is practical: improve the quality of the information you use to run the company, communicate your services accurately, and help property owners understand professional restoration work.

Companies can also review or claim their Directory presence so business information, service areas, and offered restoration services are represented accurately to property owners searching for help.

Frequently Asked Questions

What is the most important part of a restoration job file?

There is no single document that replaces the rest. The strongest file connects initial conditions, scope decisions, work performed, measurements/readings, photographs, estimate quantities, communication, and final condition into one coherent record.

How many photos should a restoration job have?

There is no universal number. Take enough organized photos to establish identity, context, condition, scope, progress, and completion. Program-specific contracts may impose additional requirements.

Does Xactimate determine what work should be performed?

No. Estimating software represents scope and price information. The physical scope should come from inspection, professional judgment, applicable standards, customer authorization, contracts, and job-specific conditions.

Should technicians write the estimate?

Companies organize this differently. Regardless of who estimates, the field team must collect enough accurate information for the estimator to understand the property without guessing.

What makes a good scope note?

A good scope note explains a decision that cannot be understood from the line item alone: why material was removed, why access was needed, why equipment changed, why a specialty process was used, or what unusual condition affected the work.

Do TPA requirements replace IICRC standards or company SOPs?

A program agreement can impose contractual administrative requirements, but restoration companies should understand their applicable professional standards, law, licenses, customer contracts, and program agreements separately. Do not label a reviewer preference as a universal requirement.

Sources and Further Guidance

1. IICRC — ANSI/IICRC S500 Standard for Professional Water Damage Restoration (standard information and 2025 adoption context)

1. Verisk — Xactimate Pricing Research Methodology

1. Verisk — Xactimate Platform Comparison / price-list capabilities

1. Restoration Industry Association — Pricing and TPA Position Statements

1. Accuserve — Water Mitigation Checklist for Restorers

1. Accuserve — Telling Your Story in Water Mitigation

Disclaimer

This article provides general operational and educational information. It is not legal, insurance-coverage, accounting, estimating, engineering, or standards-compliance advice. Requirements vary by project, contract, jurisdiction, insurer, TPA, and professional standard. Restoration companies should follow applicable law, licensing, current standards, customer agreements, program documents, and their own qualified professional judgment.