Where Your TPA Fits in a Direct Contracting Program

Direct contracting conversations often start with providers and end with plan design.

The missing piece in the middle is the TPA.

If your administrator is not wired into the model, even a beautifully structured direct contract will feel like a one-off exception that breaks claims flow, member experience, and reporting.

The good news: most TPAs already have enough flexibility to support direct contracts. The work is in defining exactly what you need from them.

Three roles your TPA can play

A TPA can sit in three basic positions in a direct contracting program:

1. Pure claims engine.

   • Pays claims at the rates and rules you define.
   • Minimal involvement in steerage or provider onboarding.
   • Works best when you have a separate navigation or COE vendor.

2. Operational hub.

   • Handles eligibility checks, pre-cert, and coordination with the direct contract partner.
   • Runs custom accumulators and benefit designs tied to the program.
   • Surfaces data back to you and the provider.

3. Strategic partner.

   • Helps identify high-opportunity service lines and markets.
   • Brings experience from other employers’ direct contracts.
   • May help negotiate or template contract language.

You do not have to jump to option three on day one. But you cannot treat your TPA as an afterthought.

Questions to ask your TPA before you sign anything

Before you finalize a direct contract, sit down with your TPA and walk through a concrete use case.

Ask:

• Adjudication: How will you distinguish direct contract claims from standard network claims in the system?
• Pricing: Where will the direct contract fee schedule or case rates live, and who maintains them?
• Eligibility: How will we flag eligible members and service types at the point of prior auth or scheduling?
• Benefits: Can we support a different cost-share structure (e.g., waived deductible) without breaking accumulators?
• Data: What fields will we capture to track steerage, savings, and exceptions during the pilot?
• Exceptions: How will medical exceptions or out-of-area cases be handled in practice?

If your TPA cannot answer these questions at all, you probably have the wrong partner for a direct contract strategy.

Getting the contract plumbing right

Your TPA contract is just as important as your provider contract.

Consider adding:

• Direct contract support language. A clear description of how custom fee schedules, case rates, and benefit designs will be implemented.
• Service levels. SLAs around pricing accuracy, turnaround time on configuration changes, and responsiveness during the pilot.
• Data rights. Your right to receive line-level claims, steerage metrics, and exception logs tied to the direct contract.
• Fees. Transparent pricing for any incremental configuration or ongoing administration tied to the program.

The goal is not to nickel-and-dime your TPA. It is to remove ambiguity about who does what when the first case goes sideways.

Aligning incentives

A TPA that is paid purely on PEPM administrative fees may not feel any direct upside from a successful direct contracting program.

That does not mean they will block it—but it does mean you may need to be explicit about:

• How you will measure their success in supporting the program.
• How they will be recognized (or compensated) if the program hits its savings and experience targets.
• How the program could help them win or retain your business over the next contract cycle.

Sometimes the cleanest move is to treat direct contracting support as a defined project with a one-time configuration fee and a small performance kicker tied to accurate execution.

When you might need a different TPA

In some cases, the answer is that your current administrator is simply not built for this.

Signals:

• They cannot load custom fee schedules or case rates without routing everything through a carrier network contract.
• They refuse to treat direct contract claims differently for accumulators or member cost share.
• They cannot generate even basic reporting on steerage or savings.

If that is the case, you face a choice:

• Run a very constrained pilot that works around the TPA, or
• Use the pilot as a forcing function to move to an administrator that can support the model.

Neither option is painless, but pretending the TPA is neutral is worse.

Direct contracting is not just a provider strategy. It is an administration strategy.

The sooner your TPA is in the room, the more likely it is that your first pilot will feel like a real program instead of a bespoke workaround.