Why Does Carrier Identification Take So Long?
Every DBA attorney has been there. A claimant names their employer. You need to file a claim. But between the employer name on a pay stub and the insurance carrier on risk at the time of injury, there are a dozen things that can go wrong.
The employer might have been acquired. The name on the contract might differ from the name on the DOL filing. The carrier might have changed between fiscal years. A TPA might be listed where the actual underwriter should be.
Most of these problems are avoidable if you follow a structured workflow instead of diving straight into database searches. After analyzing thousands of DBA investigations across 18 federal data sources, we have distilled the process into five steps that consistently produce accurate results.
Step 1: How Do You Identify the Employer's Exact Legal Name?
The first step is the one most investigators rush past. A claimant says they worked for "KBR" or "DynCorp" or "Triple Canopy." That is a trade name, not necessarily the legal entity that held the contract or the DBA policy.
Start by collecting every name variant the claimant provides. The name on their badge. The name on their pay stub. The name on any employment agreement they have. The name they saw on vehicles or signage at the worksite. Each of these might be slightly different, and each one is a potential search key.
Check SAM.gov for the employer's official registration. SAM.gov contains over 865,000 entity registrations, and the legal business name listed there is the name most likely to match federal contract records and DOL filings. Look for the DUNS number or UEI (Unique Entity Identifier) as well. These identifiers follow the entity through mergers and name changes in ways that text names do not.
If the employer is no longer active, SAM.gov still retains historical registrations. An entity that was deactivated in 2019 will still appear in searches with its last known legal name. That historical record is exactly what you need for injuries that occurred during the entity's active period.
Do not skip this step. Every minute spent confirming the legal entity name saves ten minutes of dead-end searching later.
Step 2: How Do You Resolve Employer Aliases and Name Variations?
Defense contractors do not stay still. They acquire subsidiaries, create joint ventures, operate under DBAs, and rebrand after mergers. A single employer can appear under five, ten, or twenty different names across federal databases.
ClaimTrove tracks 214 known employer aliases across the major DBA employers. These are not theoretical variations. Every alias in the database comes from an actual federal record where that name appeared as the employer of record in a contract award, OALJ decision, DOL filing, or FOIA release.
The alias resolution step means taking the legal name from Step 1 and expanding it to include every known variation. A search for just the primary name might return three results. A search that includes all known aliases might return thirty. That difference matters when you are trying to establish a complete picture of an employer's DBA coverage history.
Common alias patterns include former corporate names (before an acquisition), subsidiary names used on specific contracts, joint venture names created for specific theater operations, and shortened trade names that appear in informal filings. Some employers also appear under slightly different spellings or abbreviations depending on which federal agency recorded the name.
If you do not resolve aliases before searching for carrier matches, you will miss data. It is that straightforward. Our dedicated guide to employer alias resolution covers the most common name variation patterns and how to handle them.
Step 3: How Do You Determine the Contracting Chain?
DBA coverage follows the contract, not just the employer. Whether your claimant's employer was a prime contractor or a subcontractor changes where you look for carrier information and how confident you can be in the results.
Prime contractors are visible in USAspending data. Over 43,000 contract awards in ClaimTrove's database link prime contractors to specific agencies, contract periods, and places of performance. If the employer was a prime, you can trace the contract directly to an agency, and in some cases, that agency had a mandatory DBA carrier during the relevant period.
Subcontractors are harder. Subaward data exists in USAspending, but it covers a fraction of the actual subcontracting activity. ClaimTrove indexes over 4,300 subaward records, but many subcontracts, especially lower-tier ones, are not reported in federal spending databases at all.
When the employer is a subcontractor, you need to identify the prime. The prime's contract vehicle often determines which DBA carrier was required. Some prime contracts mandate that all subcontractors use the same DBA carrier as the prime. Others allow subcontractors to procure their own coverage. For a deep dive into this distinction, see our article on mandatory agency carrier contracts.
FOIA database results can fill gaps here. Records from FOIA releases include contractor presence data that sometimes shows subcontractor-prime relationships that do not appear in USAspending. Cross-referencing FOIA presence data with contract award data can confirm whether an employer was operating as a sub under a specific prime during the injury period.
Document the full chain: agency, prime contractor, subcontractor (if applicable), and the contract vehicle or solicitation number. This chain is what connects the employer to the carrier.
Step 4: How Do You Match the Employer to a Carrier Using Temporal Data?
This is the step where most manual investigations go wrong. Matching an employer to a carrier is not a static lookup. It is a temporal query. The carrier on risk in FY2014 may be completely different from the carrier on risk in FY2019 for the same employer.
ClaimTrove's database contains 2,454 employer-carrier mappings. Each mapping is tagged with the time period it covers, the source it came from, and a confidence weight based on the source type. A mapping from an OALJ decision that names both the employer and carrier as parties carries more weight than an inference from contract timing alone.
Start with the date of injury. This is your anchor point. Every data source you consult should be filtered to the period surrounding that date. A coverage filing from three years before the injury is less reliable than one from six months before, unless no closer data exists.
DOL case summary data shows claim volumes by carrier, employer, and fiscal year. If a specific carrier handled 90% of claims for an employer in the fiscal year of your claimant's injury, that is strong circumstantial evidence even if you do not have a direct coverage filing.
OALJ decisions are the gold standard for confirmed employer-carrier pairings. The 5,000+ decisions in ClaimTrove's database name both the employer and the carrier (or TPA) as parties. When you find a decision from the same employer and a similar time period, you have a confirmed data point.
FOIA database results provide filing dates and coverage periods that can bracket the injury date. If a filing shows Carrier A covering the employer from January 2017 through December 2018, and the injury occurred in March 2018, that is a direct temporal match.
Layer these sources. No single source is definitive in every case, but when three or four sources point to the same carrier for the same time period, your confidence should be high.
Step 5: How Do You Verify DBA Authorization on the DOL Carrier List?
The final step is verification. Not every insurance company is authorized to write DBA coverage. The Department of Labor maintains a list of carriers authorized under the Longshore and Harbor Workers' Compensation Act, which governs DBA. If the carrier you identified in Step 4 is not on that list, something is wrong.
ClaimTrove indexes 637 carriers from the DOL authorization list. This includes currently authorized carriers and historically authorized carriers that may have since withdrawn or been deauthorized. Historical authorization matters because the carrier only needed to be authorized at the time the policy was in effect, not necessarily at the time you are conducting the investigation.
Verification catches two common errors. First, it catches TPA misidentification. If the entity you found in Step 4 is a TPA rather than a carrier, it will not appear on the DOL carrier list. That tells you that you need to resolve the TPA to the actual underwriting carrier. Second, it catches corporate entity confusion within carrier groups. A carrier group might have multiple subsidiaries, only some of which are DOL-authorized for DBA.
Check the carrier name exactly as it appears on the DOL list. "ACE American Insurance Company" and "ACE Property and Casualty Insurance Company" are different legal entities within the same group. Filing against the wrong one creates problems that are entirely avoidable with a simple verification step.
Once you have confirmed that the carrier is on the DOL authorized list and the temporal data supports the match, you have a defensible carrier identification backed by federal source data.
How Do These Steps Work Together in Practice?
Consider a claimant who says they worked for a logistics company in Bagram, Afghanistan, and were injured in 2016. Here is how the workflow plays out.
Step 1 identifies the legal entity name through SAM.gov and confirms the employer's UEI. Step 2 expands the search to include three known aliases for that employer, one from a former corporate name and two from subsidiary designations used on specific contracts. Step 3 reveals that the employer was a subcontractor under a major prime, and that prime held a contract with a specific agency during 2016.
Step 4 finds four data points: a DOL case summary showing one carrier handling 85% of that employer's claims in FY2016, an OALJ decision from 2017 naming the employer and carrier as parties, a FOIA filing covering the 2015-2017 period, and a contract record showing the prime's insurance requirements. All four point to the same carrier.
Step 5 confirms the carrier is on the DOL authorized list with active authorization during 2016. Investigation complete. Total time with ClaimTrove: under 30 seconds. Total time manually: anywhere from hours to weeks depending on FOIA response times.
What Are the Most Common Mistakes in This Workflow?
Three errors account for the majority of failed carrier identifications.
First, skipping alias resolution. An investigator searches one name, finds nothing, and concludes there is no data. In reality, the data exists under a different name variant. This happens with acquired companies, companies that operated under joint venture names, and companies that used different legal entities for different contracts.
Second, ignoring temporal data. An investigator finds a carrier match from 2012 and applies it to a 2019 injury without checking whether the carrier changed in the intervening years. Carriers change more often than most attorneys expect. The data shows that large employers switch carriers every three to five years on average.
Third, filing against a TPA instead of the carrier. TPAs appear prominently in DOL records and OALJ decisions. Without a systematic check against the DOL carrier list, it is easy to mistake a claims administrator for the actual underwriter. For a complete breakdown of this issue, see our guide on how to spot a TPA vs. an actual DBA carrier. ClaimTrove flags known TPAs automatically, but manual investigators need to build this check into their workflow.
How Does ClaimTrove Automate This Workflow?
ClaimTrove runs all five steps in parallel across 18 data sources. When you enter an employer name and date of injury, the engine resolves aliases, traces contracting chains, queries temporal carrier data, and verifies DOL authorization in a single pass.
Results are returned with confidence scores based on source quality and temporal proximity. A direct coverage filing from the injury year scores higher than an inference from contract data two years prior. Every match links back to the specific federal record it came from, so you can verify the source yourself.
The database behind this workflow contains over one million records: 43,000+ contract awards, 5,000+ OALJ decisions, 4,900+ DOL case summaries, 2,454 employer-carrier mappings, 214 employer aliases, and 637 DOL-authorized carriers. Try running an investigation to see how it works on your current caseload.
What Should You Do Before Your Next DBA Filing?
Print this workflow. Pin it next to your monitor. The five steps are simple, but following them in order prevents the three most common errors that delay DBA filings.
If you are handling DBA cases regularly, the time savings compound. Each investigation that follows this workflow takes minutes instead of hours. Each carrier identification traces back to verifiable federal records instead of assumptions. And each filing goes to the right carrier the first time.
The data exists. The question is whether you are searching it systematically or hoping to get lucky with a single query. Start your first investigation with ClaimTrove and see what a structured workflow produces.