Why Do DBA Practitioners Confuse TPAs with Carriers?
You receive an LS-203 form listing "ESIS" as the claims handler. You assume ESIS is the insurance carrier and file accordingly. Three months later, you discover ESIS is a third-party administrator that processes claims on behalf of multiple carriers. Your filing is misdirected. The actual carrier is a company you never searched for.
This scenario plays out repeatedly in DBA practice. Third-party administrators occupy a visible role in claims handling. They send correspondence, manage medical authorizations, and issue benefit payments. Their names appear on official documents. But they carry no insurance risk. They have no policy obligations. They are service providers, not insurers.
The distinction matters because the Defense Base Act requires claimants to file against the insurance carrier, not the claims administrator. Filing against a TPA wastes time, delays benefits, and can complicate proceedings before the Office of Administrative Law Judges. Understanding which carriers sit behind each TPA is a critical skill for any DBA practitioner.
ClaimTrove data drawn from 5,022 OALJ decisions and 2,454 employer-carrier mappings reveals consistent patterns in TPA-to-carrier relationships. These relationships are not random. Each major TPA serves a limited set of carrier clients in the DBA space, and those relationships remain relatively stable over multi-year periods.
What Exactly Is a Third-Party Administrator?
A third-party administrator is a company hired by an insurance carrier to manage the administrative side of claims. The TPA receives claims filings, coordinates medical treatment, calculates benefit amounts, and handles day-to-day communication with claimants and their attorneys. The TPA does not underwrite risk. It does not issue insurance policies. It is paid a fee for administrative services.
In the DBA context, three TPAs dominate the market: ESIS (a subsidiary of Chubb Limited), Gallagher Bassett (a subsidiary of Arthur J. Gallagher & Co.), and Broadspire (a subsidiary of Crawford & Company). Each of these handles claims for specific insurance carriers, and those carrier relationships are the key to proper claim filing.
Other TPAs appear occasionally in DBA records. Helmsman Management Services handles certain CNA claims. Crawford & Company (Broadspire's parent) sometimes appears under its own name. But ESIS, Gallagher Bassett, and Broadspire account for the vast majority of TPA appearances in DBA filings.
The confusion arises because DOL forms and correspondence often list the TPA prominently. A claimant who receives a letter from "Gallagher Bassett Services" reasonably assumes that is the insurance company. The actual carrier name may appear in smaller print, in a different section of the document, or not at all in initial correspondence.
Which Carriers Does Each Major TPA Represent?
ESIS is the claims management arm of the Chubb corporate family. In DBA claims, ESIS most frequently administers claims for ACE American Insurance Company and other Chubb-affiliated carriers. Prior to the 2016 ACE-Chubb merger, ESIS handled claims under the ACE brand. Post-merger, the same relationships continued under the Chubb umbrella. When you see ESIS on a DBA filing, the carrier is almost always within the ACE/Chubb group. However, ESIS has also administered claims for ARCH Insurance Company in certain contract periods.
Gallagher Bassett serves a broader range of carrier clients in the DBA space. Our data shows Gallagher Bassett handling claims for Starr Indemnity & Liability Company, AIG-affiliated carriers, and ARCH Insurance Company at various times. The Gallagher Bassett-to-carrier mapping is less predictable than ESIS because Gallagher Bassett operates as an independent TPA that contracts with multiple insurers.
Broadspire, Crawford & Company's TPA division, appears in DBA records primarily in connection with Allied World Assurance Company (AWAC) and related carriers. The Broadspire-AWAC relationship is particularly visible in USAID-funded contract claims, where Allied World has held the mandatory carrier designation since 2010.
These TPA-carrier relationships shift over time. A carrier may switch TPAs when renewing an employer's policy. An employer may change carriers entirely, bringing a new TPA into the picture. The relationships described above represent the most common patterns in ClaimTrove data, not universal rules.
How Do You Trace the Real Carrier Behind a TPA?
Start with the LS-203 form, if available. The form should list both the carrier and the claims handler. When these are different entities, the claims handler is likely a TPA. The carrier field contains the name you need for filing purposes.
If the LS-203 is unavailable or ambiguous, check the employer's contract records. Federal contracts funded by specific agencies may fall under mandatory carrier arrangements. USAID contracts, for example, have required Allied World coverage since 2010, regardless of which TPA handles the claims. Knowing the awarding agency can shortcut the entire TPA identification process.
OALJ decisions provide another path. When a case reaches the administrative law judge, both the carrier and any TPAs are identified in the decision text. ClaimTrove's database of 5,022 OALJ decisions contains thousands of TPA-carrier pairs extracted from case party listings. Searching for the employer name across these decisions often reveals the actual carrier behind the TPA.
FOIA database results from the Department of Labor can also clarify the relationship. Coverage card filings list the carrier of record, not the TPA. Cross-referencing the employer and date range against these filings typically resolves any TPA ambiguity.
The least reliable method is calling the TPA directly. TPAs are generally prohibited from disclosing their carrier clients without authorization. Even when they do provide information, it may reflect current arrangements rather than the arrangement in effect at the time of injury.
What Happens When You File Against a TPA Instead of the Carrier?
Filing a DBA claim naming the TPA rather than the carrier creates several problems. The Department of Labor's Office of Workers' Compensation Programs (OWCP) may reject the filing or require amendment. This delays the case timeline and pushes back the claimant's access to benefits.
Before the OALJ, naming the wrong entity can result in procedural challenges from the employer's legal team. While administrative law judges generally allow amendments to correct carrier identification, the process consumes time and resources that proper identification would have avoided.
There is also a strategic cost. Filing against the wrong entity signals to opposing counsel that the claimant's attorney may not have fully investigated the coverage chain. This can affect settlement dynamics and case management decisions throughout the proceeding.
The most significant risk arises when statute of limitations is a factor. If the filing against the TPA is deemed defective and the limitations period has run, the claimant may face arguments that the claim is time-barred against the actual carrier. While case law generally favors correcting such errors, the argument itself creates unnecessary litigation risk.
How Does the "c/o" Problem Complicate TPA Identification?
Federal records frequently use "c/o" (care of) notation to link carriers with their TPAs. You might see "ACE American Insurance Company c/o ESIS" or "Starr Indemnity c/o Gallagher Bassett Services." This notation is helpful when it appears, but it creates its own set of problems.
Database searches that look for exact carrier names will miss records formatted with "c/o" notation. Searching for "ACE American Insurance Company" will not match a record stored as "ACE American Insurance Company c/o ESIS" in systems that use exact-match logic. Similarly, searching for "ESIS" may return results for multiple carriers, since ESIS handles claims for several insurers.
ClaimTrove's investigation engine handles this through pattern matching that recognizes "c/o" notation and separates the carrier name from the TPA name. The system then scores each entity independently: the carrier gets full weight in the identification waterfall, while the TPA is flagged as a claims handler rather than an insurer.
Some DOL records omit the carrier name entirely and list only "c/o Gallagher Bassett" or "c/o Broadspire." In these cases, the TPA name is the only starting point, and you must trace backward to identify the carrier through other data sources.
How Can You Verify Your Carrier Identification?
Cross-referencing is the most reliable verification method. If your research points to ACE American Insurance Company as the carrier, verify by checking: (1) whether ACE appears in DOL case summaries for this employer during the relevant fiscal year, (2) whether OALJ decisions involving this employer name ACE as the carrier, and (3) whether the employer's federal contracts fall under an agency with a mandatory carrier arrangement.
The DOL's list of authorized DBA carriers provides a baseline check. Any entity identified as a carrier should appear on this list, which currently contains 637 authorized carriers and self-insured employers. If the name on your filing does not appear on this list, you may have identified a TPA rather than a carrier.
ClaimTrove runs this verification automatically, cross-referencing your employer against 18 federal data sources and resolving TPA names to their underlying carriers. The platform flags TPA identifications and presents the actual carrier with supporting evidence from multiple sources.