A claimant walks in with a letter from Gallagher Bassett. The letterhead looks official. It references the claim number, the injury date, and the overseas base. Your paralegal files the LS-18 and mails the controversion demand straight to Gallagher Bassett. Three weeks pass with no substantive response.
Then the real carrier's counsel appears at the informal conference. Gallagher Bassett was never the insurer. It was the third-party administrator. Your notice went to a claims processor with no authority to pay the benefit. The clock kept running the entire time.
This is not a rare miss. It is the single most common carrier identification error we see, and it costs attorneys weeks on live claims. The name on the correspondence is almost never the name on the policy. The company that hired the claimant is often filed under an entirely different corporate identity.
Carrier identification looks simple from the outside. Find the employer, find the insurer, send the notice. In practice the DBA insurance market is a moving target. Carriers rotate every few years. Employers merge and rename. Agencies mandate specific insurers for fixed windows, then release the market. Miss any one of these shifts and you chase the wrong entity. The mistake rarely announces itself. You only learn you were wrong when the deadline has passed or the real carrier finally speaks up.
We built ClaimTrove after watching these same mistakes repeat across thousands of files. Our database now holds 2,454 confirmed employer-carrier mappings and 637 authorized DBA carriers. The patterns are consistent. Below are the seven errors that derail carrier identification most often, and the correct process for each one.
Mistake 1: Treating the Third-Party Administrator as the Carrier
The TPA processes the claim. The carrier pays the claim. These are different entities, and conflating them is the error that burns the most time.
Companies like Gallagher Bassett, ESIS, Broadspire, and Crawford handle intake, adjusting, and correspondence. They do not underwrite the policy. When you serve a benefit demand on the TPA, you serve a party that cannot bind the insurer.
The confusion is understandable. The TPA's name is on every letter. The carrier's name may appear only on the policy declarations page, which you rarely see early in a claim. Attorneys reasonably assume the entity communicating with them is the entity on the risk.
Each TPA also maps to specific carriers, and those relationships shift over time. ESIS has historically routed to ACE and Chubb, then to Arch for newer policies. Broadspire pairs with Allied World. Knowing the current pairing is half the battle, which is why understanding the difference between a TPA and the actual DBA carrier is a prerequisite skill, not a footnote.
The fix is a discipline, not a guess. Never accept the name on the correspondence as the carrier of record. Trace the TPA back to the underwriter through the policy, the declarations page, or the adjudicated record before you send anything binding.
There is a second cost to this mistake beyond lost time. A demand served on the wrong party can undercut your later argument that the carrier had notice. Serve the insurer of record, and the notice question never becomes a fight.
Mistake 2: Searching Only One Version of the Employer's Name
The claimant says he worked for KBR. The DBA case is filed under Service Employees International, Inc. Those are the same operation, but a name search for one returns nothing on the other.
Large defense contractors operate through dozens of legal entities. Subsidiaries, joint ventures, and post-merger renames all generate distinct filings. Our alias data tracks corporate families with more than a dozen name variations each. Search one variation and you see a fraction of the record.
This is why single-name searches produce false negatives. The absence of records under KBR does not mean the absence of coverage. It usually means the coverage sits under a subsidiary name you have not searched.
The problem compounds with common misspellings and abbreviations. Fluor appears as Flour in some records. DynCorp appears as DynCorp International, DynCorp Technical Services, and a handful of regional entities. Each spelling is a separate search that most attorneys never run.
The discipline of resolving employer name variations before you search separates thorough investigations from incomplete ones. Build the full name set first. Then search every variation against every data source.
Skipping alias resolution is the quiet failure. You get a clean-looking search that says nothing exists, so you stop looking. The record was there the whole time under a name you never queried.
Mistake 3: Assuming the Carrier Never Changed
Carriers are not permanent. For high-volume DBA employers, coverage rotates across successive policy periods. A carrier that was correct in 2012 is often wrong by 2016.
This matters because the carrier on the hook is the carrier at the time of injury. Not the current carrier. Not last year's carrier. The one whose policy period covered the date the claimant got hurt.
Attorneys who find a single verified mapping often stop there. They locate one carrier, confirm it once, and apply it to every claim for that employer. When the injury dates span different policy periods, that shortcut produces wrong answers.
Understanding why DBA carriers shift across coverage periods forces the right habit: match the carrier to the injury date, every time. Pull the coverage history, not just the most recent policy.
Our FOIA database results span coverage records from 1944 through 2022. That long history exists precisely because coverage is temporal. A carrier mapping without a date range is only half an answer.
The temporal error is especially dangerous on older claims. A worker injured in 2009 may not surface a dispute until years later. By the time you investigate, the employer's current carrier is two or three insurers removed from the one that owes the benefit.
Mistake 4: Ignoring Agency Mandatory Carrier Contracts
For certain contracts, the awarding agency picks the carrier. Every contractor under that agency, during that window, carries the same insurer. No exceptions, no shopping the market.
These mandates are deterministic when they apply. If the contract falls inside the mandated period and under the mandated agency, the carrier is fixed by policy, not inferred from patterns. That makes them the highest-confidence answer available.
The trap is that every mandate is time-bounded. Each program has a start and an end. A contract that predates or postdates the mandate window falls into the open market, where the carrier could be anyone. Apply the mandate outside its window and you name the wrong insurer with false confidence.
Checking a mandate requires two facts together: the awarding agency and the exact contract dates. Get either wrong and the mandate no longer applies. An agency match with the wrong dates is as useless as no match at all.
Attorneys who know a mandate exists but forget its end date are as wrong as attorneys who never checked. The mandate is a fact with an expiration. Treat it that way, and confirm the contract period before you rely on it.
Mistake 5: Applying the Prime's Carrier to a Subcontractor's Claim
The prime contractor is easy to find. The subcontractor is often buried three layers down. So attorneys locate the prime's carrier and assume it covers the sub's injured worker. It usually does not.
Under 33 U.S.C. Section 904, each employer must secure its own DBA coverage. The subcontractor carries its own policy with its own carrier. The prime's insurer has no obligation to the sub's employee unless the sub failed to insure.
The prime's carrier becomes relevant only as a fallback. If the sub was uninsured, statutory liability can flow up the chain to the prime. But that is a secondary path, not the starting assumption.
Getting the prime versus subcontractor coverage tracing right means identifying the actual employer first, then finding that employer's carrier. Not the prime's. The worker's direct employer is the party whose policy pays.
Skip this step and you send the demand to a well-capitalized prime insurer that owes nothing. Meanwhile the sub's actual carrier sits unnotified, and the real coverage question stays unanswered.
The tell is a claimant who names a large prime but describes a small crew and a different paycheck source. That gap usually means a subcontractor employer with its own separate policy sitting one layer below the name everyone recognizes.
Mistake 6: Missing Corporate Mergers and Carrier Family Consolidation
Carriers merge, rename, and fold into corporate families. The name on a 2008 policy may belong to a parent group that operates under a completely different name today. Treat them as two carriers and you double-count or lose the thread.
Insurance Company of the State of Pennsylvania is part of the AIG family. ACE American now sits inside the Chubb group. Allied World includes AWAC. A record that names one is really naming the group.
The same problem runs on the employer side. Post-merger, the contractor in your older records and the contractor in your newer records may be the same corporate family under sequential names. Untangling how one company hides behind multiple carrier names is often the difference between a coherent coverage picture and a scattered one.
The correct move is to normalize by family before you compare. Group subsidiaries under their parent. Then the pattern that looked like three different carriers resolves into one continuous relationship.
Attorneys who track raw names instead of families see noise. The signal only appears once you consolidate. A carrier's identity is its corporate group, not the specific subsidiary that happened to write that year's policy.
Consolidation also protects you at settlement. Naming the current group correctly, rather than a defunct subsidiary label, keeps the release enforceable against the entity that still exists to honor it.
Mistake 7: Relying on a Single Data Source
One source is a lead, not an answer. A single case summary, one contract record, or a lone adjudicated decision can point you toward a carrier. It cannot confirm the carrier by itself.
Every source has blind spots. Legal decisions capture only disputed claims. Contract data reveals who held the award, not who insured the workers. Coverage records prove a policy existed but may not cover your exact injury date. Each fills a gap the others leave open.
Confidence comes from convergence. When three or four independent sources covering different time periods and different data types point at the same carrier, you have a defensible answer. When only one does, you have a hypothesis to test.
This is the logic behind a disciplined step-by-step DBA carrier investigation workflow: cross-reference multiple record types before you commit. A verdict from one source is a verdict waiting to be contradicted.
The attorneys who get carrier identification wrong most often are the ones who stopped at the first plausible hit. The attorneys who get it right treat every single source as one vote, and they wait for the count.
Convergence also gives you a defensibility record. When opposing counsel challenges your carrier, you point to four sources across two decades, not one filing that happened to name a name.
How ClaimTrove Prevents All Seven Mistakes at Once
Each mistake above shares a root cause. The answer requires reconciling many records across time, corporate structure, and data type. Doing that by hand invites exactly the errors listed here.
ClaimTrove runs the reconciliation for you. It resolves employer aliases and separates TPAs from carriers. It matches the carrier to the injury date and checks agency mandates against contract windows. It traces prime and sub coverage separately, normalizes carrier families, and cross-references every result across 18 federal data sources. Each layer catches a mistake that a manual search leaves open.
The output is one ranked carrier answer with the confidence level, the source citations, and the reasoning behind the ranking. You see why the carrier is what it is, not just the name. That transparency is what turns a lookup into evidence you can defend.
Stop chasing TPAs and dead employer names. Run your next carrier investigation on ClaimTrove and get a sourced answer in seconds instead of weeks.