TPA Documentation Requirements for Restoration Companies

Restoration contractors often ask for a single checklist of “TPA documentation requirements.” The problem is that there is no universal checklist that applies to every TPA, managed repair program, carrier, service line, and loss.

A strong restoration file has two layers.

The first layer is project documentation that supports what happened at the property, what the contractor observed, why the scope was selected, what work was performed, and what the final condition was.

The second layer is program-specific administration: deadlines, required forms, estimating rules, photo naming, communication steps, software, service-level agreements, carrier guidelines, warranty forms, completion documents, and other requirements created by the controlling agreement or assignment.

A contractor needs both. Excellent field documentation does not excuse a missed contractual deadline, and perfect portal compliance does not make an unsupported restoration scope defensible.

Start With the Controlling Documents

Before building a TPA documentation SOP, identify what actually governs the assignment.

Depending on the program, that may include:

• The contractor network agreement
• Carrier-specific guidelines
• A program manual
• Assignment instructions
• Service-level agreements
• Estimating guidelines
• Scope or price agreements reached with an adjuster
• State or local requirements
• The contractor’s agreement with the customer
• Applicable professional standards

The Restoration Industry Association has published position statements addressing situations where TPA file reviewers request changes that they believe are required by controlling documents. RIA’s position is that when a requested scope change is said to be required by a program agreement, the controlling provision should be identified rather than treated as an unwritten rule.

That distinction matters. A contractor should not label a preference, reviewer habit, or verbal request as a universal TPA requirement if it is not supported by the agreement or applicable program document.

1. Work Authorization and Project Identity

A defensible file starts by showing who hired the contractor, where the work occurred, and what the contractor was authorized to do.

Capture, as applicable:

• Property address
• Customer and contact information
• Claim or assignment number
• Carrier and program information
• Date of loss and date discovered when known
• Date and time of first contact
• Date and time of inspection
• Cause or reported source of loss
• Signed work authorization
• Scope authorization and any limitations
• Required disclosures
• Assignment-specific instructions

If the authorization changes, document that change rather than relying on a phone conversation that never makes it into the file.

2. Initial Condition and Pre-Existing Damage

Photographs should establish what the property looked like before work changed it.

A useful initial photo set commonly includes:

• Exterior or property-identification photo
• Source or suspected source of loss
• Wide photos of affected rooms
• Medium-range photos showing affected assemblies
• Close photos of specific damage
• Pre-existing damage
• Visible microbial growth when present and appropriate to document
• Contents affected by the loss
• Conditions that limit access or drying
• Safety hazards
• Existing repairs or unrelated damage that could later be confused with the current loss

Accuserve’s current water-mitigation guidance specifically emphasizes documenting and photographing pre-existing damage. That is a good practice even when a different TPA or no TPA is involved.

3. Moisture Map and Moisture Readings

For water mitigation, a list of random meter readings is less useful than a record that shows where each reading was taken.

A moisture map should make it possible to understand:

• Rooms and affected areas
• Water migration
• Materials tested
• Reading locations
• Initial equipment placement when relevant
• Containment or drying chambers
• Areas believed to be unaffected
• Final reading locations

Initial and final readings should be traceable to locations. Record the meter type and other information required by the applicable program or your SOP.

Accuserve’s current educational material repeatedly emphasizes the relationship among a moisture map, moisture-content records, photos, and drying logs. The value is not the form itself; the value is being able to reconstruct the drying story later.

4. Psychrometric and Daily Drying Records

When drying continues over multiple visits, the file should show what changed over time.

Common documentation includes:

• Date and time of monitoring visit
• Ambient temperature and relative humidity
• Affected-area or drying-chamber conditions
• Dehumidifier readings when applicable
• Material moisture readings
• Equipment count and placement
• Equipment added, moved, or removed
• Containment changes
• Drying progress
• Conditions slowing the project
• Customer access or scheduling issues
• Technician notes

Do not backfill a daily log from memory after the equipment is removed. The file is strongest when it is created as the work happens.

5. Water Category, Contamination, and Safety Decisions

When contamination or environmental conditions affect the restoration plan, document the observations and the basis for the work performed.

Depending on the loss, the file may need to address:

• Water category or contamination condition
• Sewage or floodwater exposure
• Visible mold or suspected microbial conditions
• Containment
• Personal protective equipment
• Material removal decisions
• Cross-contamination controls
• Regulated-material concerns
• Referral to qualified testing or specialty professionals when appropriate

Contractors should stay within their licenses, certifications, contracts, and legal scope. Do not turn a restoration file into an unsupported coverage, medical, or environmental opinion.

6. Restore-vs.-Remove Decisions

If a material is removed, the file should help another reviewer understand why. If a material is dried in place, the file should help show why that approach was reasonable.

Document:

• Material and assembly
• Extent of impact
• Contamination considerations
• Moisture condition
• Access limitations
• Drying feasibility
• Pre-existing condition
• Photos before removal
• Measurements or quantity
• Debris or disposal documentation when relevant

A one-line note such as “drywall removed” is far less useful than a record connecting the observation to the scope.

7. Contents Documentation

Contents work creates its own chain of custody and condition questions.

When relevant, record:

• Room of origin
• Item or carton identifier
• Photos
• Condition
• Cleaning or restoration disposition
• Items sent to specialists
• Unsalvageable items
• Storage location
• Customer instructions
• Disposal authorization
• Pack-back reconciliation

The file should make it possible to answer, “What happened to this item?” without relying on one employee’s memory.

8. Estimate, Measurements, and Scope Support

A TPA file reviewer may be looking at the estimate without having visited the property.

Make the estimate understandable from the file:

• Accurate room dimensions
• Material quantities
• Photos that correlate to line items
• Sketches or diagrams
• Equipment quantities and duration
• Demolition quantities
• Cleaning or treatment areas
• Notes explaining unusual conditions
• Specialty subcontractor documentation when applicable
• Taxes, permits, or other charges when applicable
• Program-required line-item notes

Do not assume the reviewer will infer the reason for a charge. If a line item is unusual or easily misunderstood, document the reason.

9. Communication and Daily Notes

Restoration claims can involve the property owner, contractor, TPA, desk adjuster, field adjuster, consultant, mortgage company, subcontractors, and other parties.

Keep material communication in the file:

• Customer updates
• Access problems
• Approval requests
• Scope questions
• Reviewer requests
• Adjuster discussions
• Schedule changes
• Customer decisions
• Disputed items
• Instructions received from the program

If an important instruction arrives by phone, summarize it in the project record with the date, time, participant, and next action.

10. Supplements and Change Orders

Supplements are easier to review when the reason for the change is obvious.

A supplement package may need:

• Original scope
• Newly discovered condition
• New photos
• Revised measurements
• Explanation of why the original scope could not include the item
• Revised estimate
• Customer or adjuster authorization when required
• Program form or portal submission
• Change-order documentation

Do not let the supplement become a pile of new line items with no narrative.

11. Completion Documentation

The end of the job should close the documentation loop.

Depending on the service, completion records can include:

• Final moisture readings
• Final psychrometric readings
• Final photos
• Equipment removal
• Cleaned or repaired condition
• Customer completion acknowledgment
• Certificate of completion when required
• Final invoice
• Warranty information
• Pack-back reconciliation
• Remaining exclusions or customer-responsibility items
• Required carrier or TPA closeout forms

For water mitigation, final readings should correlate with the same locations used to establish the affected areas.

Photo Documentation: Quality Matters

A large number of poor photos is not the same as a strong photo record.

A useful restoration photo should answer a question. Where is this? What am I looking at? Why does it matter?

Good practices include:

• Wide, medium, and close views
• Consistent room naming
• Descriptive labels
• Claim or project identifiers where the program requires them
• Date and time information
• GPS or geolocation when required
• Photos that correlate to readings and estimate items
• Retaining original files according to company policy and contractual requirements

Never claim that every TPA requires GPS, a specific filename, or a specific photo count unless the current program document actually says so.

Build One Internal SOP, Then Add Program Overlays

The most efficient approach is not to build a completely different field process for every network.

Create a strong company-wide restoration documentation SOP first. Then create a program overlay for each TPA or managed repair program that adds:

• Required forms
• Required portal steps
• File naming
• Response deadlines
• Inspection deadlines
• Estimate deadlines
• Required software
• Carrier-specific estimating guidelines
• Customer-contact rules
• Escalation contacts
• Warranty forms
• Completion requirements

That gives technicians and project managers a consistent base while allowing administrative staff to meet each program’s contractual requirements.

What If a TPA Reviewer Requests a Scope or Price Change?

Do not turn every disagreement into a confrontation, but do not confuse an unsupported request with a contractual requirement.

If a reviewer says the program agreement requires a change, ask for the applicable provision when the requirement is not already clear in the controlling documents.

RIA’s published position on scope-change requests says that when a TPA requests a change based on a program agreement, the TPA should specifically cite the contract provision that justifies the request. RIA also says that when a requested reduction is not required by the program agreement, the contractor can seek review by the carrier adjuster.

That is industry advocacy guidance, not legal advice. Contractors should understand their own agreements and obtain legal advice when a contractual dispute warrants it.

Frequently Asked Questions

Is there one universal TPA documentation checklist?

No. Documentation requirements vary by TPA, managed repair provider, carrier, service category, state, assignment, and current agreement. Build a strong restoration-file standard, then add the requirements in each program’s controlling documents.

What documentation is most important on a water mitigation file?

A strong file commonly includes initial-condition photos, source information, moisture mapping, material readings, psychrometric and drying logs, equipment records, scope notes, restore-or-remove rationale, work authorization, daily communication, and final readings and photos.

Do TPAs require a moisture map?

Some managed repair programs explicitly emphasize or require moisture mapping for water mitigation. Even when a particular program form is not required, a moisture map can make readings and water migration easier to understand. Follow the current controlling program requirements.

Should every photo be time- and GPS-stamped?

Do not assume every program requires the same metadata. Follow the assignment and program rules. Regardless of the technical requirement, photos should be traceable, clearly labeled, and sufficient to explain the work.

What should I do if a reviewer says my contract requires a scope change?

Review the controlling documents. If the requirement is not clear, ask which provision supports the request. RIA’s published TPA position guidance supports identifying the controlling provision when a requested scope change is said to be contractually required.

Should technicians learn every TPA portal?

Technicians should understand the field documentation the company requires. Many restoration companies are more efficient when administrative staff or dedicated coordinators handle program-specific portal steps, file naming, estimating workflows, deadlines, and closeout requirements.

How long should restoration documentation be retained?

Retention obligations can depend on contracts, state law, licensing rules, insurance requirements, litigation risk, and company policy. Follow the applicable legal and contractual requirements and obtain professional advice for your jurisdiction.

Sources and Further Guidance

1. Restoration Industry Association — TPA Position Statements / Scope Change Requests

1. Restoration Industry Association — Position Paper Summary Guide

1. Restoration Industry Association — Code of Ethics

1. Accuserve — Water Mitigation Checklist for Restorers

1. Accuserve — Job Scope Protocol for the Initial Water Damage Inspection

1. Accuserve — Telling Your Story in Water Mitigation

1. Accuserve — What Is a Moisture Map and Why Is It Critical?

Disclaimer

This article provides general operational information, not legal advice, insurance-coverage advice, or a substitute for a contractor’s current TPA, carrier, customer, or program agreement. Requirements can change. Restoration companies should follow applicable law, professional standards, licenses, current program documents, and their controlling contracts.