Show Me the File: How to Vet a Vendor’s Technology

Vendors and subcontractors may own pieces of the work. Your company still owns the outcome and the file that has to support it.

By Clayton Roberts

Most restoration projects take a village. On a commercial water loss, that may include the mitigation contractor, a plumber, an industrial hygienist and laboratory, an abatement subcontractor, an estimator, and a TPA or carrier reviewer. Each party performs a different part of the work. Each also brings its own technology and documentation habits.

That part is normal. The trouble starts when those systems never produce a usable record of the job.

A subcontractor may own the abatement scope. An industrial hygienist may own the sampling and report. A remote estimator may own the Xactimate file. But when the client or carrier asks why equipment ran for seven days, who approved a change, or where the chain-of-custody record is, the restoration company managing the job still has to answer. A weak handoff becomes our delayed invoice, our rework, and our uncomfortable client conversation.

We can delegate pieces of the work. We do not delegate the outcome.

A good tech stack can still produce a weak file

Consider a commercial water loss involving mitigation, environmental testing, and selective abatement. The mitigation contractor records moisture readings and equipment in a mobile app. The environmental consultant uses different room names in the report and laboratory paperwork. The abatement photographs stay on a supervisor's phone. A scope change is discussed onsite but never documented in writing. The estimator receives a summary instead of the original field records.

Weeks later, accounting assembles the billing packet. The equipment dates do not match the drying records. The estimate and environmental report describe the same areas differently. The photographs do not show what was removed. The added scope has no written authorization.

Every party may be able to explain what happened. No one can quickly produce a clean, consistent file that supports the invoice. The client or carrier does not see five different systems and four company org charts. It sees one file with gaps.

That is called a documentation-chain failure. The problem is not that the parties lacked technology. Their process for capturing, reviewing, correcting, and handing off information did not hold.

Change the question

Vendor vetting often starts with, "What software do you use?" The answer may tell us whether a vendor works in Xactimate, has a moisture documentation app, or can submit through a TPA portal. It does not tell us whether the process works on a real job.

The better request is, "Show us how your team uses it."

Show how the field technician records the work. Show who catches a missing photo or an incorrect room name. Show how a correction is made without losing the original record. Show what estimating and accounting receive, and what ultimately reaches the client or carrier.

The parties do not need to use the same software. They do need a shared understanding of what must be produced, when it is due, how it will be named, how changes will be approved, and who is responsible for the complete file. Depending on the assignment, that may include daily notes, photographs, moisture and equipment logs, T&M support, environmental field records, chain-of-custody documents, laboratory results, estimate revisions, written authorizations, and closeout records.

Run the handoff test

Skip the polished feature tour. Ask the vendor for one redacted, completed project from the branch and service line that would actually handle your work.

First, follow the file forward. Watch the assignment enter the vendor's system. See how client requirements reach the field crew, how daily records are captured, who reviews them, how gaps are corrected, and what estimating, accounting, and the client receive.

Then trace the file backward. Choose an equipment charge, a labor entry, and a scope change from the invoice. Ask the vendor to locate the supporting readings, logs, photographs, T&M records, and authorization. Bring in the people who perform those handoffs, not only the salesperson. Operations, project management, estimating, accounting, and IT will see different failure points.

A polished software demonstration shows what a platform can do. A completed project file shows what the vendor actually does.

Take these three questions into your next vendor conversation

1. Show us one redacted project from dispatch through final invoice, from the branch and service line that would handle our work. What did the field team capture, who reviewed it, and what did the client receive?

2. Let us choose an equipment charge, a labor entry, and a scope change from the invoice. Can your team trace each one back to the daily notes, photographs or readings, T&M support, and written authorization?

3. If our client or carrier asks for the complete file six months from now, and the original project manager is no longer there, who can produce it, in what format, and how quickly?

You do not need a 40 question technology assessment to improve the next vendor conversation. These three questions test the live workflow, the support behind the bill, and whether the record survives after the people who worked the job have moved on.

If the answers keep coming back to "our software can do that," the handoff has not been proven. Start with a few assignments, review the files, and do not expand the work until the documentation holds together. The tool matters. The handoff matters more, because even when someone else owns part of the work, we still own the outcome.