Getting approved as a preferred restoration vendor is a risk judgment before it is a quality judgment. A carrier or a third-party administrator reviewing your company is mostly asking who pays when a vendor causes a loss on an insured’s property, and whether your company can show it is ready for that.
Approval is a risk question before it is a quality question
Owners tend to read the approval process as a test of how good the work is. Quality matters, and it is not what is being measured first. A carrier or administrator that hands a vendor an assignment is placing someone in an insured’s building with a claim open, which means the first question is what happens if something goes wrong. How the vendor answers that question is largely an insurance question.
We described the structure of insurer-funded work in You Work for the Owner, But the Insurer Writes the Check. This post is the other half of that picture: not how the money moves, but what a reviewer is looking at when deciding whether you are the vendor to send.
One boundary first. Each carrier and program writes its own requirements, and we do not speak for any of them. Treat what follows as the insurance-side pattern we see when contractors bring us their vendor paperwork, and treat the program’s own written requirements as the authority.
Who pays if the vendor causes the loss
Underneath every vendor review is a transfer of risk. The insured has a covered loss, the carrier is funding the repair, and the vendor is doing work that could itself cause damage or injury: a drying job that goes wrong, a mold removal that spreads, a fire that starts from the equipment, a crew member who is hurt on site. The reviewer wants the answer to be that the vendor’s own insurance responds, so the carrier and the insured are not left to absorb it.
That is why the program asks for proof of coverage before the first day. Proof is the beginning of the answer, not the end of it, because what matters is whether the policy answers the work you actually do. The sections below take the common parts of that question in turn.
Coverage that matches the work, not the label
A certificate that lists general liability looks reassuring and often says less than it appears to. Standard general liability carries a pollution exclusion, and the substances a restoration crew is hired to remove are exactly what it excludes. We cover the consequence in Does General Liability Cover Mold Remediation Contractors? and the line built for it is contractors pollution liability. A reviewer who understands the trade looks for that line, and for evidence that its wording fits the processes you perform.
The same logic runs through the rest of the program. General liability is the operations base. Bailees coverage answers the customers’ contents in your care, which matters to any program that sends a vendor into a loss with belongings to protect. Commercial auto answers the response fleet, and workers compensation answers your own crew. A program that shows only some of these tells a reviewer which exposures the company has not addressed.
Limits that match what the agreement requires
Programs and the parties that hire you set a total limit that the vendor has to carry, and that number is part of the agreement rather than a preference. When the requirement is higher than your primary limits reach, the answer is usually an excess liability layer. The detail that catches vendors out is whether that layer follows the pollution and professional wording underneath it, which we explain in The Tower Gap. A layer that reaches over general liability and not over the line carrying your defining exposure can look like higher limits on a certificate and still leave the exposure that matters uncovered.
A loss history you can explain
A reviewer will usually see your loss history, and a claim on it is not an automatic disqualification. What changes the reading is whether you can explain it: what happened, what changed in how you work afterward, and whether the pattern is getting better. A clean history is a strength. A history with an explanation is a different kind of strength, and an unexplained one is the weakest of the three.
The practical step is to keep your own record of incidents and corrective actions as they happen, so the explanation exists before anyone asks. The long-tail exposure that arrives after a rebuild is the subject of Completed Operations.
Documentation and safety habits are part of the file
Reviewers on the claim side care about how a vendor documents the work, because documentation is what supports getting paid and what defends the job when it is questioned. The industry’s water-damage standard, ANSI/IICRC S500, lists project documentation and risk management among the components it describes. Safety practice matters for a related reason: a crew working in respirators and confined spaces is an exposure the reviewer wants to see managed, not only insured.
Real-World Scenario: Two restoration companies apply to the same program in the same month. The first sends a certificate that lists general liability, auto, and workers compensation, and learns later that the pollution exclusion removes the mold work it was hired for. The second sends the same certificate plus evidence of a pollution line, a limit that matches the agreement, and a one-page summary of how it handled and corrected its last claim. Neither company’s work was in question. Only the second had answered the reviewer’s actual question before it was asked.
Why the same file can read differently to different programs
Because each carrier and program writes its own requirements, the same insurance file can look complete to one reviewer and thin to another. One program may weight the limit the agreement names; another may care most about the credentials behind the crew; another may ask first about the loss history and how it was handled. None of that is arbitrary. Each reviewer is protecting a different book of insureds with a different appetite for what a vendor can cause.
The consequence for an owner is that approval is not a single hurdle cleared once. It is a set of reviews, each answered from the same underlying file. A company that keeps that file coherent, with coverage that matches the work, limits that match the contracts, records that explain the history, and documentation that supports the billing, can answer most of the reviews without rebuilding its position each time. A company that assembles a different story for each application tends to find the stories diverging.
It also helps to separate what is yours to prepare from what is the program’s to decide. The coverage, the records, and the habits are yours. The selection rule, the volume of work, and the timing are theirs. Spend your effort where the control is, and ask the program, in writing, for the rest. If a requirement is unclear, ask what it is meant to protect against; the answer usually tells you which part of your file the reviewer will read most closely, and which question you should be ready to answer before it is asked.
What an approved vendor still has to maintain
Approval is not permanent. Programs revisit their vendors, certificates expire, limits change as contracts change, and a claim or a lapse can reopen a file that looked settled. The companies that stay on lists tend to treat the insurance file as a living document: renewals tracked, certificates ready to issue, named parties kept current, and changes in the work reported to the people placing the coverage before they become a gap.
That is also where the program’s structure earns its keep. A vendor who adds a service line, starts hauling contents, or takes on larger accounts has changed the exposure the reviewer approved. We explain how to keep the program current as the business grows in How to Grow a Restoration Company Without Outgrowing Your Insurance.
Before you apply
Ask the program for its requirements in writing, compare them honestly against your credentials and your coverage, and close the gaps before you submit instead of after a decline. If you want the insurance side of that comparison done for you, the restoration contractor insurance page lays out the program we build, and you can ask us for a quote to have it read against a specific set of requirements. Nate Jones reviews these files himself.
Sources
- ANSI/IICRC S500, Standard for Professional Water Damage Restoration — the standard’s published description lists project documentation and risk management among the components it covers. It states nothing about any carrier’s or program’s vendor requirements, and neither does this post. iicrc.org/s500