You Have an Employer Name. Now What?
Your client names their overseas employer. Maybe it is a household name like KBR. Maybe it is a company you have never heard of, operating under a subcontract three layers deep. Either way, your next move is the same: find the DBA insurance carrier responsible for that employer on the date of injury.
The good news is that several free federal databases contain carrier and employer information relevant to Defense Base Act claims. The bad news is that none of them tell the full story. Each database covers a different slice of the DBA ecosystem, uses its own naming conventions, and carries blind spots that can send your investigation sideways.
Here is a practical walkthrough of the four main free tools available, what each one reveals, and where each one falls short. Understanding these gaps is what separates a confident carrier identification from a guess.
What Does the DOL OWCP Database Show for Employer Searches?
The Department of Labor's Office of Workers' Compensation Programs publishes annual DBA case summary reports broken down by carrier, employer, and nation. These reports are publicly available on the DOL website and cover fiscal years 2009 through 2024.
For carrier identification, the employer-sorted reports are the starting point. They show which employers generated DBA claims in a given fiscal year and how many claims fell into categories like lost-time, death, and controverted. Across all fiscal years, ClaimTrove has indexed 4,983 of these case summary records.
The catch: these reports do not directly map employers to carriers. The employer report tells you an employer had claims. The carrier report tells you a carrier handled claims. But connecting the two requires cross-referencing claim volumes and time periods, which is imprecise at best. The DOL also uses inconsistent employer names across fiscal years. "DynCorp International" might appear as "DYNCORP" or "DynCorp International LLC" depending on the reporting period.
Additionally, OWCP case summaries only reflect filed claims. If an employer operated overseas but had zero DBA claims in a given year, they will not appear at all. That is a significant gap for employers with small workforces or strong safety records.
Can USAspending Data Reveal a DBA Carrier?
USAspending.gov is the federal government's public spending database. It tracks prime contract awards and subcontract awards to specific companies, including contract values, awarding agencies, and performance locations. ClaimTrove indexes 43,298 prime contract awards and 4,315 subcontract awards from this source.
USAspending does not list DBA carriers directly. What it does provide is the contracting chain: which agency awarded the contract, which prime contractor won it, and where the work was performed. This matters because certain agencies maintained mandatory DBA insurance contracts during specific periods. If you know the awarding agency and the performance dates, you can sometimes narrow the carrier universe. For a deeper walkthrough, see how to read USAspending data for DBA investigations.
The limitations are substantial. USAspending tracks spending, not insurance. Employer names in contract records frequently differ from the names employees use. A worker might say they worked for "Triple Canopy," but the contract recipient is "Constellis Group" or an earlier corporate parent. Subcontractor data is especially sparse, with only about 10% of subcontracts reported in many overseas programs.
Another gap: USAspending identifies companies by DUNS numbers, UEI numbers, and CAGE codes rather than the informal names your clients provide. Bridging from a colloquial employer name to the correct federal entity record requires understanding how CAGE codes and UEI numbers work in federal records.
What Can You Find in SAM.gov Entity Records?
SAM.gov (System for Award Management) is the federal contractor registration database. Every company doing business with the federal government must register here. ClaimTrove indexes 865,232 SAM.gov entity records, making it one of the largest sources in the system.
SAM.gov is useful for employer verification rather than carrier identification. It confirms that a company exists, shows its legal name versus trade names, and reveals corporate hierarchy through CAGE code relationships. If your client says they worked for "Blackwater," SAM.gov helps you trace that name through Xe Services to Academi to Constellis.
SAM.gov does not contain any DBA insurance information. Zero carrier data. Its value is purely in resolving employer identity, which is a prerequisite for carrier lookup but not the lookup itself. The database also includes SAM exclusion records for debarred contractors. ClaimTrove tracks 16,735 of these, which can be relevant when an employer has been suspended from federal contracting.
Do OALJ Decisions Name Carriers for Specific Employers?
The Benefits Review Board publishes decisions from Administrative Law Judges handling DBA and LHWCA disputes. These legal decisions frequently name the employer, the carrier, and sometimes the TPA involved in a claim. ClaimTrove has indexed 5,022 OALJ decisions spanning 1993 through 2025.
This is often the most direct free source for carrier-employer connections. When a case reaches an ALJ, the decision typically names both parties. You can search the DOL's decision database by party name and find cases where "Employer X" was insured by "Carrier Y" on a specific date.
The problems are threefold. First, only disputed claims reach an ALJ. The vast majority of DBA claims settle or are accepted without a hearing, meaning most employer-carrier relationships never appear in the OALJ database. Second, decisions often name the claims administrator rather than the actual carrier. A decision listing "ESIS" as the insurance entity is really pointing to ACE American or Chubb, but that connection is not always obvious. Understanding how to distinguish a TPA from the actual DBA carrier is critical when reading these decisions.
Third, decisions reflect point-in-time snapshots. A carrier named in a 2014 OALJ decision may no longer cover that employer in 2024. Carriers shift every few years for most large contractors, and corporate acquisitions regularly reshape the carrier landscape. The hidden carrier family problem means the same insurer might appear under three or four different names across decisions from different years.
Why Do These Free Sources Fail When Used Alone?
Each database answers a different question. OWCP shows claim activity. USAspending shows contract relationships. SAM.gov confirms employer identity. OALJ decisions show disputed carrier assignments. No single source answers the question you actually need answered: who is the carrier for this employer on this date?
The fundamental challenge is stitching these sources together. That requires solving three problems simultaneously.
Employer name resolution. Your client says "KBR." Federal records might list "Kellogg Brown & Root Services," "KBR Technical Services," "KBR Inc.," or a subsidiary name. ClaimTrove tracks 214 employer alias mappings to bridge these gaps. Without alias resolution, you will miss records sitting under variant names in every database you search.
Temporal alignment. DBA carriers change. An employer's carrier in 2010 is rarely the same carrier in 2020. Free databases give you snapshots, but you need to build a timeline. That means cross-referencing OWCP fiscal year data with OALJ decision dates and contract performance periods. For a structured approach to this problem, see building an investigation timeline across database sources.
TPA versus carrier confusion. Free databases regularly list third-party administrators instead of actual insurance carriers. Claims administrators like Gallagher Bassett, Broadspire, and ESIS appear throughout OWCP and OALJ records. Treating a TPA as the carrier is one of the most common errors in DBA investigations, and none of the free tools flag this distinction for you.
How Long Does a Manual Multi-Database Search Take?
In practice, a thorough DBA carrier investigation using free tools alone requires searching four to six databases, resolving employer name variations manually, cross-referencing dates, and verifying whether listed entities are carriers or TPAs. Experienced paralegals report this process taking anywhere from several hours to several days per employer, depending on the complexity of the corporate structure.
The free tools are real and they contain real data. They are not useless. But they were never designed to work together, and the gaps between them are exactly where carrier identification errors happen. Missed alias names, outdated carrier assignments, and TPA confusion account for the majority of incorrect carrier identifications in DBA practice.
ClaimTrove was built to eliminate this multi-database search. It combines DOL case summaries, OALJ decisions, USAspending contract data, SAM.gov entity records, FOIA-obtained coverage filings, and SME-verified carrier mappings into a single search across more than 1 million records. A structured investigation workflow that would take days with free tools runs in minutes.
If you are spending hours jumping between federal databases to find a DBA carrier, run a ClaimTrove investigation instead. Enter the employer name, and let the system search 18 federal data sources, resolve aliases, filter out TPAs, and return confidence-scored carrier results in one report.