Choosing the best TPA for self insured employers is not simply a matter of comparing administrative fees. For a Washington employer, the right third-party administrator should fit the plan’s design, handle claims reliably, coordinate effectively with the network and other vendors, and give the employer usable information for decisions. A disciplined evaluation helps you compare what each proposal actually includes before you make a commitment.
Talk with a benefits advisor about your plan
What Should a TPA Do for a Self-Insured Employer?
A third-party administrator (TPA) performs administrative functions for a health plan. Depending on the agreement, those functions may include processing and paying claims, maintaining eligibility records, answering participant questions, issuing plan communications, coordinating with a provider network, and producing reports. The employer sponsors the plan; the TPA provides contracted services. Those are related roles, but they are not interchangeable.
Start by writing down what your organization expects the TPA to own, what it will share with other vendors, and what remains an employer responsibility. One proposal may include a broad service package. Another may price claims administration separately from member support, reporting, or network access. A low headline fee can be misleading if essential services are excluded or charged as add-ons.
Do not assume every TPA offers the same capabilities or accepts the same decision-making authority. Read the service description alongside the proposed plan structure and contracts. For context on how these firms fit into self-funded arrangements, Georgetown’s Center on Health Insurance Reforms describes TPAs as intermediaries in its overview of TPAs and self-funded health insurance. The practical lesson for a buyer is to identify who does each job, who has authority to act, and how the work is monitored.
How Do You Define Your Requirements Before Comparing TPAs?
Before inviting proposals, create a short requirements document. It should describe your workforce, plan priorities, current pain points, vendor relationships, and service expectations. This makes it easier to compare like with like instead of allowing each bidder to define the problem in its own way.
- Plan profile: Summarize employee count, locations, eligibility rules, plan options, and any populations with distinct support needs. Do not send unnecessary personal health information during vendor selection.
- Current operational issues: List recurring billing or eligibility errors, slow claim resolutions, member confusion, reporting gaps, and handoff failures. Use examples with identifying information removed.
- Required functions: Mark which services are essential, desirable, or already provided by another partner. Include claims, enrollment feeds, member service, appeals coordination, reporting, and network arrangements where relevant.
- Service expectations: Define expected response channels, escalation paths, named points of contact, and the information you need to resolve urgent cases.
- Implementation constraints: Note renewal timing, payroll and enrollment systems, communications needs, and the time your internal team can devote to transition work.
Keep the scope grounded in your actual requirements. For example, an employer with a distributed workforce may place a high value on clear network access and remote member support. An organization with a small HR team may need dependable eligibility feeds and a clear escalation process more than a complex dashboard. Employers comparing plan structures can also review the basics of common group health plan examples to help clarify which administrative needs apply.
Which TPA Capabilities Should You Compare?
Use a consistent scorecard to compare each bidder’s evidence, not just its presentation. Ask for a demonstration or sample deliverable when a capability is important. Score each category using the same scale, and record any assumption that needs to be confirmed in the final contract.
| Evaluation area | What to examine | Evidence to request |
|---|---|---|
| Claims operations | Intake, adjudication workflow, exception handling, corrections, and payment controls | Process map, service commitments, sample anonymized report, and escalation steps |
| Member service | Contact channels, hours, language support, case follow-up, and access to knowledgeable staff | Service description, sample call or case workflow, and performance definitions |
| Network coordination | Network availability, contracting relationship, provider-directory process, and out-of-network handling | Network documentation, directory maintenance process, and written allocation of responsibilities |
| Reporting and data | Regularity, detail, privacy safeguards, data access, and ability to answer plan questions | Sample reports, data dictionary, delivery calendar, and data-export terms |
| Implementation | Eligibility, payroll and vendor integrations, testing, employee communications, and transition ownership | Timeline, responsibility matrix, test plan, and contingency plan |
| Fees and contract | Included services, pass-through charges, renewal terms, termination, and data return | Itemized fee schedule, complete contract, and written assumptions |
Ask each bidder to explain how it would handle a routine claim inquiry, an eligibility mismatch, and a case that requires coordination among the plan, network, and another service provider. The answers reveal whether the vendor can explain its actual workflow or is relying on broad assurances. Ask who receives the issue first, who owns it through resolution, and how the employer learns that it is closed.
How Should You Evaluate Claims Handling and Member Support?
Claims administration is central to the participant experience, but “we process claims” is not enough detail to evaluate service. Ask the TPA to describe the steps from receiving a claim through adjudication, payment or denial, explanation to the member, correction, and appeal-related handoff. Clarify which decisions are made under plan rules, who can correct an administrative error, and how questions are escalated.
Request service standards stated in measurable terms. “Prompt response” is hard to verify. A stronger commitment identifies the type of request, the response or resolution measure, how exceptions are counted, and how performance is reported. Be precise about the difference between acknowledging a question and resolving it. A ticket may be closed in a system while the employee still lacks an answer.
Ask what participants can do when an initial answer does not solve the problem. Is there a named escalation route? Can HR see the status of an authorized case? How does the TPA coordinate with a provider or network without requiring the employee to repeat the story? The TPA should explain how it protects sensitive information while giving authorized employer representatives enough information to manage plan operations.
Request examples of how the TPA handles peak periods, complex inquiries, and corrected eligibility records. Find out whether member support is delivered by the TPA or a subcontractor, and whether the same service commitments apply. A vendor’s operating model matters as much as its technology. Ask for references from employers with a similar level of administrative complexity, and ask those references about unresolved issues, not only initial implementation.
What Should You Ask About Networks and Other Vendors?
A TPA, a provider network, a pharmacy benefit manager, a stop-loss carrier, and other vendors may be separate organizations with different contracts. A proposal should explain how those relationships work in practice. Do not infer that a TPA owns or controls a network simply because the proposal names a network option.
For network coordination, verify which network is available to your plan, how provider-directory information is maintained, and who handles questions about network status. Ask how the TPA routes a claim that appears inconsistent with the network information available to a participant. Confirm whether network access fees, implementation charges, or other costs are included in the proposal or billed separately.
Map the handoffs among vendors. For example, if a participant has a claim question that touches both administration and network status, establish which party is responsible for a complete response. If a separate pharmacy or stop-loss partner is involved, ask who sends each data file, what happens when a file is late or rejected, and who notifies the employer of a problem.
Stop-loss terms and plan administration are distinct, but their coordination can affect operations. A research article on employer self-insurance decisions examines different stop-loss options; it is useful background for recognizing that these arrangements can vary, not a substitute for comparing the actual terms in your own proposals. See the study on employer self-insurance decisions and stop-loss options. Ask bidders to identify any assumptions they make about stop-loss reporting, claim submissions, and reimbursements, and confirm those points with the relevant parties.
Which Reports and Data Should an Employer Expect?
Useful reporting should help the employer understand how the plan is operating and where follow-up may be needed. Ask to see sample reports before choosing a provider. Check that the report has definitions, a clear time period, and enough context to avoid misreading a number. A chart that cannot be reconciled to its source data may create work rather than insight.
Discuss reporting cadence and delivery ownership. What arrives monthly, quarterly, and at renewal? Can the TPA explain material changes in the reporting format? Which employer roles can access reports, and how are access permissions updated? Ask whether the employer can export its data in a usable format during the contract and at termination, not only view it through a portal.
Data terms deserve close review. Clarify what information the TPA collects, how it uses and safeguards it, which subprocessors receive it, and what the contract says about retention, incident notification, and return or deletion at the end of service. Your legal and compliance advisers should review terms that affect plan administration and privacy obligations. Avoid requesting identifiable health details when a de-identified or aggregate view is sufficient for the decision at hand.
Ask whether reports can help answer specific operational questions, such as whether eligibility changes are being processed as expected, whether claim inquiries are being resolved, or whether recurring issues need a plan communication. Avoid selecting a vendor on a promise of “analytics” unless it can show what is delivered, when it is delivered, and what action the employer can reasonably take from it.
How Do Fiduciary Roles and Contract Terms Affect the Choice?
Do not assume that assigning work to a TPA automatically transfers every plan responsibility. The duties and decision-making authority depend on the plan, the contract, and the functions the administrator performs. Ask your benefits counsel to review the arrangement and identify which responsibilities remain with the employer, which functions the TPA accepts, and how each party documents its work.
The Health Affairs discussion of fiduciary duties and third-party administrators underscores why employers should look beyond a service label. Ask whether the contract describes the TPA’s role as administrative, discretionary, or both, and whether the actual services match that description. Do not rely on a sales conversation to answer a legal question; have qualified counsel review the plan documents and contract.
Read the full contract, not just a proposal or summary. Pay particular attention to:
- Exactly which functions and deliverables are included in the base fee.
- Service standards, reporting frequency, exclusions, and remedies when obligations are missed.
- Any delegated authority, approval process, and recordkeeping requirements.
- Subcontractors, data use, security obligations, and incident notifications.
- Fee changes, pass-through costs, automatic renewal, and termination notice periods.
- Transition assistance, data portability, and the timing and format of records returned at exit.
Ask how the TPA documents claims decisions and operational exceptions, and what information it will provide for the employer’s oversight. A contract should make accountability visible: who performs a task, who reviews it, how an error is reported, and how it is corrected. Employers should not treat a general indemnity clause as a substitute for understanding the services and responsibilities being purchased.
How Can You Compare Total Cost Without Missing Hidden Fees?
Compare costs across the same population, service scope, and contract period. Build a single worksheet that separates recurring administration fees from one-time implementation fees, optional services, network costs, transaction charges, and other pass-through expenses. Record whether fees are per employee, per participant, per claim, or fixed, and identify any minimums or volume assumptions.
Then compare the total expected cost under a common set of assumptions. Ask each TPA to state what is excluded and to show how charges change if enrollment rises or falls. A quote may look lower because member support, reporting, data conversions, or implementation work sits outside the base fee. Another may have a higher fixed fee but include services you would otherwise purchase separately.
Cost is only one scorecard category. A modest fee difference may not justify weak reporting, unclear ownership, or a difficult exit process. Conversely, a polished demonstration does not prove a vendor is worth a higher price. Document what evidence supports each score, and note unresolved assumptions for clarification before final selection.
What Is a Practical TPA Selection Process for Washington Employers?
A simple process can keep the decision organized without turning it into a paperwork exercise. Employers of different sizes may need different levels of support, but the core steps are similar. Organizations can also review WHIA’s information for Washington small groups or larger employer groups to understand the kinds of group-market considerations that may shape their requirements.
- Document the current state. List vendors, responsibilities, known service problems, contract end dates, reporting needs, and transition constraints.
- Set the scope. Separate must-have TPA functions from functions handled elsewhere. Decide which items are non-negotiable and which can be evaluated as options.
- Issue consistent questions. Give each bidder the same plan profile, service scenarios, data questions, and fee worksheet. Protect confidential information and avoid providing personal health data unnecessarily.
- Evaluate evidence. Score written answers, demonstrations, sample reports, contract language, and references using one rubric. Ask bidders to resolve gaps in writing.
- Map the transition. Identify who owns each implementation task, the testing schedule, employee communications, and contingency steps if a file or process is not ready.
- Confirm the agreement. Reconcile the final contract to the proposal, document service levels and fees, and have appropriate legal and compliance advisers review relevant terms.
- Monitor after launch. Set regular reviews for service performance, reporting quality, open issues, and contract obligations. Assign an internal owner for follow-up.
Give each bidder a realistic scenario rather than asking only general questions. For example: an employee’s eligibility record is wrong, a provider-directory question affects a scheduled appointment, and HR needs to know whether the issue has been corrected. Ask the TPA to walk through the handoffs, communications, timeframes, and documentation. Then compare the answers against the written proposal and service commitments.
A reliable transition plan matters as much as the selection. Establish enrollment-file formats, testing dates, responsibility for employee notices, and a process to track unresolved setup issues. Ask what can be tested before the effective date and what the employer should do if a file fails validation or an employee cannot access support. A smooth implementation depends on clear owners and early issue escalation, not just the vendor’s go-live date.
Frequently Asked Questions
Is the lowest-cost TPA the best choice?
Not necessarily. Compare the complete fee schedule, included services, service evidence, contract obligations, reporting, and transition support. A low base fee may exclude functions your employer will need to buy elsewhere.
Can a TPA choose the employer’s health plan network?
That depends on the specific arrangement. Confirm which networks are available, who contracts for or provides access to them, what fees apply, and who handles directory and network-related questions. Do not assume a network is included because it appears in a proposal.
What should an employer ask for during a TPA demonstration?
Request a walkthrough of routine and difficult workflows: a claim inquiry, an eligibility correction, an escalation, and a report used to monitor operations. Ask who owns each step, what the participant and employer can see, and how completion is documented.
How often should an employer review TPA performance?
Agree on a regular review cadence in advance, such as recurring operational check-ins and a broader review at key plan or renewal milestones. Use the contract’s service measures, open issue logs, reports, and feedback from authorized internal contacts to guide the discussion.
Should counsel review a TPA contract?
Employers should consider having qualified benefits counsel review the agreement, plan documents, delegated functions, and data terms. A general explanation from a vendor is not a substitute for advice about the employer’s specific obligations.
Ready to Review Your Employer Health Plan Administration?
Comparing TPAs is easier when you define responsibilities, service expectations, reporting needs, and contract requirements before reviewing proposals. Washington Health Insurance Agency (WHIA) works with Washington employers on benefits strategy and can help you frame the questions to bring to a TPA conversation. You can also explore the agency’s overview of level-funded plans as part of a broader review of plan administration and funding arrangements.
Schedule a conversation about your benefits strategy
A clear scorecard, complete contract review, and defined transition plan can help your organization choose a TPA that fits its needs and supports consistent plan administration.