This is the third article in the Carrier & TPA Strategy cluster under The Restoration Operator’s Playbook. It builds on the strategic asset article and the scope discipline article.
Most contractors do not understand what TPAs actually do
Restoration contractors interact with third-party administrators every day. They submit files through TPA platforms. They follow TPA guidelines on scope and pricing. They receive work assignments from TPA programs. They deal with TPA quality reviews and program management decisions. The TPA is, for many contractors, a constant operational presence that shapes a meaningful portion of their working day.
What most contractors do not have is a clear mental model of what the TPA is actually optimizing for, what the TPA’s relationship with the carrier looks like from the inside, what kinds of contractor behavior the TPA rewards and punishes, and how those incentives shape the TPA’s decisions about programs, panels, and individual contractor placements. Without this mental model, contractors react to TPA decisions without being able to predict or shape them, which puts the contractor in a perpetually defensive posture.
This article is about building that mental model. Not as a critique of TPAs, who are largely doing legitimate work in a complex business, but as a strategic tool for contractors who want to operate the relationship deliberately rather than reactively. Contractors who understand what the TPA is doing and why can position themselves to be the contractors the TPA most wants to work with. Contractors who do not understand it are at the mercy of decisions they cannot anticipate.
What the TPA actually sells
To understand what the TPA optimizes for, start with what the TPA actually sells to the carrier. The TPA is not selling claim adjustment. The carrier already has internal claim adjusters. The TPA is selling something more specific.
The TPA is selling the management of a contractor network at scale. The carrier needs work done in markets across the country, on losses of varying complexity, by contractors of varying capability. Managing this directly requires the carrier to maintain contractor relationships, vet new contractors, monitor performance, handle disputes, and address the operational headaches that come with thousands of contractor interactions per year. The TPA takes this complexity off the carrier’s plate. The carrier pays the TPA to make the contractor problem invisible.
The TPA is also selling consistency. The carrier wants to know that work done in Houston meets the same standards as work done in Hartford, that scope decisions follow the same logic across programs, that documentation arrives in the same format, that quality outcomes are predictable across markets. The TPA produces consistency by imposing uniform processes across the contractor network. The contractors experience the uniformity as bureaucratic constraint. The carrier experiences it as risk management.
The TPA is selling cycle time control. The carrier wants files to close in defensible time. The TPA produces cycle time control through service-level agreements with contractors, through process automation that pushes files along, and through escalation mechanisms that surface delays before they become customer complaints. Contractors who hit the cycle time benchmarks make the TPA look good to the carrier. Contractors who miss the benchmarks make the TPA look bad.
The TPA is selling cost containment. Carriers measure their TPAs in part by the average claim cost on TPA-managed files compared to internally managed files. TPAs that consistently produce lower average costs are valuable to the carrier. The cost pressure flows down to the contractor through pricing guidelines, scope review processes, and program structures that incentivize tighter scopes.
The TPA is also selling defensibility. Files closed through the TPA need to survive subsequent scrutiny — by carrier auditors, by state regulators, by reopening claims, by litigation. Files that include the right documentation, follow the right processes, and resolve cleanly are defensible. Files that have weak documentation, irregular processes, or lingering disputes are not. TPAs reward contractors who produce defensible files and punish contractors who do not.
None of these things are mysterious or sinister. All of them shape what the TPA cares about and how the TPA evaluates contractors. Contractors who understand the value the TPA is selling can position themselves to deliver that value, which positions the contractor to receive favorable treatment in return.
What the TPA’s incentive structure produces
The TPA’s incentive structure, when understood clearly, predicts most of the TPA decisions that contractors otherwise find inexplicable.
The TPA’s preference for low-friction contractors is not personal. The TPA is being measured on cycle time, dispute rate, and customer satisfaction. Contractors who produce friction in any of these areas hurt the TPA’s metrics. The TPA naturally gravitates toward contractors who do not create friction, even when the friction-prone contractor is technically more skilled. This is why contractors who fight every scope reduction get squeezed out even when their underlying work is good.
The TPA’s preference for documentation-disciplined contractors is also not personal. The TPA is being measured on file defensibility. Contractors who produce thin documentation create files that are vulnerable to subsequent challenge, which puts the TPA at risk. The TPA naturally favors contractors whose files always read well, even when the underlying scope might be slightly higher than what a less-disciplined contractor would have written.
The TPA’s preference for cost-disciplined contractors is partly about the cost containment metric and partly about the predictability the TPA needs. Contractors whose pricing falls within expected ranges are easier for the TPA to manage. Contractors whose pricing varies unpredictably create work for the TPA’s review processes. The TPA favors contractors whose pricing is consistent and defensible over contractors whose pricing fluctuates regardless of justification.
The TPA’s preference for cooperative contractors reflects all of the above and adds an additional dimension. The TPA needs contractors who participate constructively in the TPA’s processes, who provide feedback through proper channels, who respond promptly to TPA inquiries, and who treat TPA staff professionally. Contractors who treat the TPA as an adversary make every interaction harder than it needs to be, which over time produces program decisions that the contractor will find unfavorable.
Conversely, the TPA’s lack of patience for certain contractor behaviors reflects what those behaviors do to the TPA’s metrics. Contractors who supplement late hurt cycle time. Contractors who dispute frequently hurt the dispute rate. Contractors who produce customer complaints hurt customer satisfaction. Contractors who deviate from program guidelines without explanation hurt consistency. Each of these behaviors triggers TPA responses that reflect the metric being damaged.
What contractors should and should not negotiate with the TPA
Understanding the TPA’s incentive structure also clarifies which kinds of negotiations are productive and which are not.
Negotiations about specific scope items on specific files are usually productive when the contractor has the documentation to support their position and approaches the conversation in the disciplined way described in the scope discipline article. The TPA’s adjuster has discretion at the file level and can move on items where the contractor has made a defensible case.
Negotiations about the TPA’s published guidelines are usually unproductive at the file level. Adjusters cannot change the guidelines on individual files. Contractors who push for guideline-level changes through file-level disputes frustrate adjusters and damage relationships without producing any benefit. Guideline-level changes are made through program-level conversations, which require a different posture and a different audience.
Negotiations about pricing are usually productive when the contractor can demonstrate that their pricing reflects legitimate market conditions or specialized capabilities. Negotiations about pricing that amount to the contractor wanting more money than the TPA’s pricing structure supports, without supporting reasoning, are usually unproductive and damage credibility.
Negotiations about cycle time exceptions are usually productive when the contractor proactively communicates the reason for an exception in advance and provides supporting documentation. Negotiations about cycle time exceptions that arrive after the fact, without proactive communication, are usually unproductive because the metric has already been damaged.
Negotiations about program standing are usually productive when conducted at the right level — typically the program manager rather than the file-level adjuster — with a defensible case based on performance data and a clear ask. Negotiations about program standing that are conducted as complaints rather than as proposals are usually unproductive.
The general principle is that productive negotiations work within the TPA’s incentive structure rather than against it. Contractors who frame their requests in terms of how granting the request improves the TPA’s metrics — better cycle time, lower dispute rate, higher customer satisfaction, stronger defensibility — are speaking the TPA’s language. Contractors who frame their requests purely in terms of what they want without addressing the TPA’s incentives are speaking a language the TPA cannot easily respond to.
The relationships inside the TPA that matter
The TPA is not a monolith. Different roles inside the TPA have different responsibilities, different discretion, and different perspectives on the contractor relationship. Contractors who understand these distinctions can engage the right people for the right conversations.
The file-level adjuster is the person who reviews scope, approves payments, and handles day-to-day file management. The adjuster has discretion at the file level but limited authority on program-level questions. Most of a contractor’s daily TPA interactions are at this level. Building strong relationships with the adjusters who handle the contractor’s files pays off in faster approvals, more reasonable scope discussions, and smoother file management.
The supervisor or manager above the adjuster is the person who handles escalations, manages adjuster performance, and addresses cross-file issues. Contractors should know who supervises the adjusters they work with most frequently and should engage the supervisor when escalation is needed. Engaging the supervisor for routine file matters is inappropriate and damages the adjuster relationship.
The program manager is the person responsible for the overall contractor program — panel composition, performance evaluation, program policy, contractor recruitment and termination. The program manager is the right audience for program-level conversations about standing, performance recognition, and structural concerns. Most contractors interact with program managers infrequently and should make those interactions count.
The quality team or audit team conducts file reviews and pattern analysis across contractors. Contractors usually do not interact with this team directly but are affected by their findings. Contractors whose files consistently pass quality review build a reputation that supports favorable program decisions. Contractors whose files trigger quality flags build a reputation that supports unfavorable program decisions.
The technology and operations teams build and maintain the platforms contractors use to interact with the TPA. Contractors usually do not engage these teams directly but benefit from understanding that platform problems often have specific causes that can be addressed through proper channels. Filing thoughtful platform feedback through the right mechanisms can produce changes that benefit the entire contractor network.
The senior leadership of the TPA — the directors, vice presidents, and executives — set strategic direction and make the largest decisions about the contractor network. Most contractors do not engage at this level. Contractors who do engage at this level, when appropriate, often find that senior TPA leaders are interested in input from contractors who think strategically about the business.
The contractor’s reputation inside the TPA
Across all of these roles and across years of file-level interactions, each contractor develops a reputation inside the TPA that informs every decision the TPA makes about the contractor. The reputation is not formal. It is the accumulated impression of how the contractor operates, formed through hundreds of interactions and shared informally across the TPA’s staff.
The reputation includes specific dimensions. Whether the contractor’s files are clean and easy to work with. Whether the contractor’s communication is professional. Whether the contractor’s cycle times are reliable. Whether the contractor’s quality outcomes are strong. Whether the contractor escalates appropriately or inappropriately. Whether the contractor’s senior leadership engages constructively when needed. Whether the contractor’s representatives at every level — estimators, project managers, supervisors, owners — represent the contractor consistently or whether the contractor’s behavior varies by who is interacting with the TPA.
The reputation, once established, is durable. Contractors with strong reputations get the benefit of the doubt on close calls. Contractors with weak reputations get scrutiny on situations that would pass without comment for stronger contractors. Changing the reputation requires sustained behavior change over many files, and the change takes longer than the deterioration that produced the bad reputation in the first place.
This is one of the strongest arguments for treating every TPA interaction as part of the relationship rather than as an isolated transaction. The interaction the contractor handles poorly today will inform decisions the TPA makes about the contractor for the next several years. The interaction the contractor handles well today is building credit that will pay back across many subsequent files.
What this means for owners
If you run a restoration company that does meaningful TPA-managed work, the practical implication of this article is that the TPA relationship is shaped by everyone on your team, not just by the senior people who think about it strategically. Estimators who handle file-level interactions, project managers who handle supplemental conversations, supervisors who handle escalations, and the owner who occasionally engages program managers all contribute to the contractor’s reputation inside the TPA.
The training implication is that every team member who interacts with the TPA needs to understand what the TPA is optimizing for and how their interactions affect the relationship. This understanding cannot be assumed. It has to be taught explicitly, reinforced through coaching, and modeled by senior leadership.
The strategic implication is that the contractor’s TPA reputation is a long-term asset that can be deliberately built, just like the customer relationship and the senior team. Owners who treat the TPA reputation as something to be invested in produce reputations that compound. Owners who treat the TPA as a daily friction without considering the reputational dimension produce reputations that erode.
The TPA game is, in the end, a relationship game played at scale across many simultaneous interactions. Contractors who understand the game play it deliberately. Contractors who do not understand it play reactively, and the reactive posture is structurally weaker over time.
Next in this cluster: program standing and how it is actually won — what the published criteria say, what the unpublished criteria really are, and what contractors should be doing across years to build the standing that determines the volume and quality of work they receive.
Leave a Reply