Why Is DBA Carrier Identification So Difficult?
You have a new DBA client. She was injured in Kabul in 2017 while working for a company she calls "DynCorp." She does not have a copy of her employer's insurance policy. She does not know the carrier name. She barely remembers her supervisor's name. Your job is to identify the insurance carrier so you can file the LS-203 and initiate the claims process. This should be straightforward. It almost never is.
DBA carrier identification is the single most time-consuming step in the early stages of a Defense Base Act claim. The problem is not that the information does not exist. Federal databases contain extensive records of carrier authorizations, contract awards, and claims filings. The problem is that the information is scattered across multiple unconnected systems, buried under employer name variations, and obscured by the distinction between insurance carriers and third-party administrators.
ClaimTrove's database contains 2,454 employer-carrier mappings verified across multiple sources. The patterns in that data reveal why manual identification fails so often: employers change carriers every 3-5 years, corporate acquisitions create new name variants, and the same employer may appear under 10 or more different names across federal records.
What Is the Difference Between a Carrier and a TPA?
The most common error in DBA carrier identification is confusing a third-party administrator (TPA) with the actual insurance carrier. When your client receives correspondence about their claim, the letterhead often shows a TPA name, not the carrier. Gallagher Bassett, ESIS, Broadspire, Crawford, and Helmsman are TPAs. They administer claims on behalf of insurance carriers, but they are not the carrier of record.
This distinction matters for your filing. The LS-203 requires the insurance carrier name, not the TPA. Filing against the TPA creates delays and potential jurisdictional issues. Yet many attorneys list the TPA because that is the only name their client recognizes from claims correspondence.
The TPA-to-carrier mapping is not one-to-one. ESIS administers claims for both ACE/Chubb and ARCH Insurance. Gallagher Bassett works with Starr Indemnity, AIG, and Allied World depending on the policy period. Broadspire typically administers for Allied World/AWAC. Without knowing the specific policy period and employer, knowing the TPA name narrows the carrier to two or three possibilities but does not give you a definitive answer.
ClaimTrove's investigation engine automatically detects TPA names in carrier results and resolves them to the actual insurance carrier using our entity relationship graph. When our system finds "c/o Gallagher Bassett" in a DOL filing, it flags the TPA and applies scoring logic to determine whether the underlying carrier is Starr, AIG, or another insurer for that employer and time period.
How Do Employer Name Changes Complicate Carrier Searches?
Corporate acquisitions, mergers, and rebranding create a trail of name variations that fracture search results across federal databases. Consider Amentum, a major DBA employer formed through a series of acquisitions. Searching DOL records for "Amentum" returns only recent filings. But this same corporate entity previously operated as PAE Incorporated, Vectrus, V2X, AECOM's management services division, and DynCorp International's technical services line, depending on the business unit and acquisition date.
ClaimTrove tracks 214 employer alias mappings that connect these corporate families. Our investigation engine resolves aliases in exactly two database queries: one to find all canonical names associated with the input, and another to retrieve every alias for those canonical names. The result is a complete search term list that catches filings under every known name variation.
Without alias resolution, your carrier search will miss critical records. A carrier that insured "PAE Incorporated" from 2015-2019 will not appear in results for "Amentum" unless you know to search both names. Multiply this problem across the dozens of DBA employers who have undergone acquisitions since 2001, and the scope of the challenge becomes clear.
Name variations go beyond corporate restructuring. Federal databases contain spelling errors, abbreviation differences, and entity type variations. "DynCorp International LLC" and "Dyncorp Technical Services" and "DI Operated Systems" all refer to parts of the same corporate family. SAM.gov registrations may use the legal business name while DOL filings use a DBA (doing business as) name. Contract awards may abbreviate differently than OSHA inspection records.
Why Do Carriers Change Every Few Years?
DBA insurance policies are typically annual contracts. Employers rebid their DBA coverage regularly, and carriers enter and exit the DBA market based on loss experience and premium adequacy. The result is temporal fragmentation: the correct carrier for a 2014 injury may be completely different from the carrier for a 2019 injury at the same employer.
Our data shows that most large DBA employers have used three or more different carriers over the past two decades. Some have cycled through five or six. The carrier that covered a major defense contractor during the Iraq surge (2006-2008) frequently exited the relationship by 2012 as claims matured and losses exceeded projections. A new carrier stepped in, often at higher premium rates, only to face the same cycle.
Agency mandatory contracts add another layer. The State Department mandated CNA as the sole DBA carrier for all State Department contracts from July 2001 through July 2012. After that mandate expired with zero bidders on the re-solicitation, coverage moved to the open market. USAID has mandated Allied World since March 2010 through a series of AAPDs. If your client worked under a USAID contract, the carrier identification is deterministic within the mandate window. Outside it, you are back to multi-source research.
USACE ran a mandatory program with CNA from December 2005 through September 2013. After that program ended, DBA rates for Army Corps contractors roughly doubled on the open market. Knowing these mandate boundaries saves hours of unnecessary research.
What Sources Should You Search for Carrier Information?
Effective DBA carrier identification requires searching at least five categories of federal records. Each source captures different aspects of the employer-carrier relationship, and no single source provides complete coverage.
DOL case summaries report claims activity by employer and carrier across fiscal years. These summaries cover FY2009 through FY2024 and show which carriers appeared in claims data for each employer. However, they reflect claims filed, not policies written. A carrier appearing in FY2016 data may be handling claims from injuries that occurred in 2013 or 2014.
BRB decisions (published and unpublished) name the employer and carrier as parties. ClaimTrove's database contains 5,022 OALJ decisions, and our automated extraction has mined over 1,200 employer-carrier pairs from decision text alone. These pairs are timestamped by case filing date, providing temporal context for the carrier relationship.
Contract award data from USAspending reveals the prime contractor and awarding agency for each overseas contract. While contracts do not directly name the insurance carrier, knowing the awarding agency allows you to check for mandatory carrier requirements. Knowing the prime contractor lets you trace upward from a subcontractor.
FOIA database results contain coverage card filings and contractor records that directly link employers to carriers during specific time periods. ClaimTrove has obtained over 30,000 coverage card records and nearly 30,000 contractor deployment records through FOIA requests, providing granular carrier data that is not available through any public-facing DOL system.
DOL industry performance reports match prime contractors to carriers by fiscal year with performance metrics. These reports cover the largest DBA programs and provide high-confidence mappings, though they are limited to roughly 80 employer-carrier pairs.
How Does ClaimTrove Automate Carrier Identification?
ClaimTrove's investigation engine searches 18 federal data sources in parallel, resolves employer aliases, checks agency mandate periods, and ranks carrier matches using a confidence-weighted scoring system. The entire process takes under 10 seconds.
The engine uses a carrier discovery waterfall that prioritizes high-confidence sources. Agency mandates (deterministic matches) rank first. Direct employer-carrier mappings from verified records rank second. BRB decision party extractions rank third. Prime contractor carrier lookups and statistical co-occurrence provide additional signals when direct matches are unavailable.
Each carrier result includes the source document, a confidence rating, and temporal alignment scoring. Carriers from records closer to the injury date score higher than carriers from records a decade away. The system also deduplicates by corporate family, so you see "AIG" once instead of separate entries for AIG, ICSP, and National Union Fire Insurance Company.
Stop spending hours on manual carrier research. Run your investigation at ClaimTrove.com and get ranked carrier results with source documentation in seconds.