May 1, 2026
A restoration company burns an insurance program when it systematically pursues supplements, disputes scope decisions, or escalates claims in ways that increase carrier costs without legitimate basis — or conversely, when it cuts corners on documentation and quality to protect its own margin at the carrier’s expense. Both patterns erode the carrier relationship and ultimately cost the program more than the contractor’s revenue justifies.
I’ve spent 36 years inside restoration companies. I’ve seen operators who managed TPA work with integrity — running tight documentation, staying within scope, communicating clearly — and I’ve seen operators who used program work as a revenue extraction opportunity until the carrier eventually removed them. The difference isn’t always obvious from the outside, especially early. Here’s how to read the signals before a problem contractor becomes a liability.
Program abuse operates on two opposite vectors, both damaging:
Aggressive supplementing: The contractor systematically identifies scope items outside the program pricing structure and pursues supplements at a rate that isn’t justified by claim complexity. Every job has a supplement conversation. Supplement disputes become the norm, not the exception. The carrier’s adjuster team spends disproportionate time managing this contractor’s files.
Quality/documentation shortcuts: The contractor accepts program pricing but cuts corners to protect margin — incomplete drying cycles, insufficient documentation, substandard materials. The program appears to run smoothly because there are no billing disputes, but the carrier is paying for work that wasn’t fully performed, and the substandard outcomes generate downstream claims, mold callbacks, and tenant or policyholder complaints.
Both patterns cost the program — the first in direct claim costs, the second in downstream liability and program integrity. The second is harder to detect and often runs longer before it’s caught.
Supplement disputes are a normal part of restoration — genuine scope gaps exist, pricing schedules don’t cover every scenario, and legitimate disagreements arise. The signal isn’t that a contractor supplements. It’s the rate, the pattern, and the quality of the justification.
A contractor whose supplement dispute rate is significantly above the program average is either working on genuinely more complex jobs (explainable and verifiable) or systematically testing the program’s tolerance for pushback. Track supplement request rate per $1K of initial program billing, and monitor which contractors are outliers.
Adjuster friction is a leading indicator. If a specific contractor generates disproportionate adjuster time — follow-up calls, documentation requests, escalations — the contractor has an operational or behavioral problem. Adjusters generally don’t escalate without reason. Track complaint and escalation volume by contractor and review outliers quarterly.
For programs that conduct quality audits, QA failure rate by contractor is a direct measure of documentation and scope compliance. A contractor with a QA failure rate above the program average is either poorly trained, understaffed, or cutting corners. Any of these is a program management problem. Track QA results by contractor and require corrective action plans for persistent failures.
A contractor whose average job billing suddenly increases — without a corresponding change in job type or scope complexity — has changed something about how they’re coding and billing. This isn’t always abuse; it may reflect legitimate market conditions or legitimate scope changes. But unexplained billing inflation should trigger a review of recent job files to understand the change.
Policyholder complaints are the most direct signal of service failure. A program contractor who generates complaints about work quality, communication, or professionalism is creating liability for the carrier — not just operational friction. Track complaint volume by contractor and take complaints seriously as early warning signals, not as isolated incidents.
This distinction matters because TPAs that over-correct for program abuse end up squeezing out contractors who are legitimately advocating for proper scope. Program abuse is characterized by: routine supplementing on jobs where scope doesn’t justify it, documentation that appears designed to support supplements rather than to accurately capture work performed, and escalation patterns that bypass normal adjuster communication to pressure approvals.
Legitimate advocacy looks like: documented justification for scope items that aren’t in the pricing schedule, clear communication about why a specific job requires additional scope, and a willingness to accept a “no” and complete the job at program pricing when justification doesn’t hold up.
The behavioral tell is consistency — a contractor who advocates legitimately does so on some jobs and not others, based on actual job conditions. A contractor who games the program does so consistently, regardless of job conditions.
Effective program monitoring doesn’t require auditing every file. It requires tracking the right metrics consistently and reviewing outliers on a defined cadence:
Monthly: supplement request rate by contractor, adjuster escalation volume by contractor, policyholder complaint volume by contractor.
Quarterly: QA failure rate by contractor, billing pattern trend analysis, comparative performance review for bottom quartile performers.
Annual: contractor relationship review for any contractor on the program for 12+ months, including performance against all tracked metrics and a forward-looking assessment of program fit.
Removal is appropriate when: performance metrics are consistently below program standards despite documented corrective action requests, a pattern of abuse is confirmed through file review, a quality failure creates material liability for the carrier, or the relationship has deteriorated to the point where the contractor’s participation costs more than it contributes.
Removal should be documented and process-driven — not reactive to a single incident. A contractor who is removed should have a clear record of the performance concerns, the corrective actions requested, and the outcomes that led to removal. This protects the program from claims of unfair treatment and creates a defensible record if the contractor disputes the decision.
Key patterns: supplement request rates significantly above program average, high adjuster escalation volume relative to job count, QA failure rate above program benchmarks, unexplained billing inflation, and policyholder complaints. Any one of these warrants review. Multiple patterns occurring together indicate a systemic problem, not isolated incidents.
Track supplement rate, adjuster escalation volume, QA failure rate, billing trend, and complaint volume by contractor on a monthly basis. Review outliers — contractors in the bottom quartile on any metric — on a quarterly cadence. Don’t wait for a crisis to review performance data; by the time a contractor has become a serious problem, the pattern has usually been visible in the metrics for months.
Legitimate advocacy is job-specific and documentation-driven — the contractor supplements on particular jobs where actual scope conditions warrant it and provides clear justification. Program abuse is pattern-driven — the contractor supplements routinely regardless of job conditions, with documentation designed to justify rather than to accurately capture. The behavioral test is consistency: does this contractor’s supplement behavior correlate with actual job complexity, or does it occur regardless?
Removal is appropriate after documented performance concerns have been communicated, corrective action has been requested, and performance has not improved within a defined timeframe. It’s also appropriate when a single serious failure — confirmed documentation fraud, quality failure generating liability, or professional conduct violation — warrants immediate action. Process-driven removal with a documented record protects the program from disputes.
Poor documentation creates cost in several ways: claims that can’t be properly adjudicated, downstream mold or quality callbacks that generate new claims, adjuster time spent compensating for documentation gaps, and legal exposure when a coverage dispute requires documentation the contractor can’t produce. A contractor who documents poorly is a program liability even when there’s no active dispute — the documentation problem will materialize as cost eventually.
Mike McCabe is a 36-year restoration industry consultant and founder of Profit Detective. He advises restoration companies on operational infrastructure, financial systems, and growth strategy.
Most engagements pay for themselves within the first week.