Your Client Names an Employer That Does Not Exist
An injured contractor tells you they worked for "Global Defense Services" in Afghanistan. You search DOL records. Nothing. You check USAspending. No matches. The employer name your client provided does not appear in any federal database.
This happens constantly in DBA investigations. Injured workers often know their employer by a trade name, a project nickname, or an outdated corporate identity. The legal entity that holds the federal contract and carries the DBA insurance policy uses a completely different name.
SAM.gov, the System for Award Management, is where you bridge that gap. Every entity that does business with the federal government must register in SAM. That registration contains the legal business name, any "doing business as" names, the physical address, CAGE code, UEI number, and NAICS codes. For DBA practitioners, SAM is the federal government's own directory of contractor identities.
The challenge is knowing what to look for and how to interpret what you find. SAM holds over 865,000 entity registrations. Most of them have nothing to do with defense contracting overseas. The records that matter for DBA cases are buried among domestic small businesses, universities, and municipal governments. This guide shows you exactly how to extract the employer intelligence you need.
What Data Does a SAM.gov Entity Registration Actually Contain?
Every SAM registration captures a standardized set of identity fields. For DBA employer verification, five of these fields matter most.
Legal Business Name is the entity's official registered name. This is the name that appears on federal contracts, and it is often different from the name your client uses. A worker might say "KBR" while the contract is held by "Kellogg Brown & Root Services, Inc." or a subsidiary like "KBR Technical Services, Inc."
DBA Name (Doing Business As) captures trade names. This is critical. If the entity operates under a name different from its legal name, SAM records that relationship. Searching by DBA name can surface the legal entity behind the name your client actually knows.
UEI (Unique Entity Identifier) replaced the old DUNS number in April 2022. Every federal contractor gets a unique UEI from SAM.gov. This identifier links the entity across USAspending contract awards, subcontract records, and other federal databases. When you find an employer's UEI, you can trace their entire federal contracting history in USAspending.
CAGE Code is a five-character identifier assigned by the Defense Logistics Agency. Defense contractors use CAGE codes across procurement systems. The CAGE code is often the fastest way to confirm you are looking at the right entity, especially when multiple subsidiaries share similar names. For a deeper look at how these identifiers connect, see our guide on CAGE Codes and UEI Numbers.
Entity Status tells you whether the registration is active, expired, or excluded. An expired SAM registration means the entity may no longer hold federal contracts. If the injury occurred during a period when the registration was lapsed, that raises questions about whether a valid DBA policy was in place.
How Do You Search SAM.gov for a DBA Employer?
Go to sam.gov and select "Entity Information" from the search menu. You can search by entity name, UEI, CAGE code, or DUNS number (legacy). For DBA work, start with the employer name your client provided.
SAM's search is case-insensitive but exact-match heavy. If your client says they worked for "Dyncorp," try "DynCorp International" and "DynCorp International LLC" as well. Corporate name variations are one of the biggest obstacles in DBA investigations. A single employer can appear under 20 or more name variations across federal records.
When you find a match, click into the entity record. Look at the physical address, state of incorporation, and NAICS codes. Defense and security contractors typically carry NAICS codes starting with 5616 (Investigation and Security Services) or 5612 (Facilities Support Services). Construction contractors overseas often show 2362 (Nonresidential Building Construction).
Check the registration and expiration dates carefully. SAM registrations must be renewed annually. If the registration expired before your client's date of injury, the employer may have been operating without proper federal registration. That does not automatically mean DBA coverage lapsed, but it signals a compliance problem worth investigating.
What Is the Difference Between SAM Entity Registration and SAM Exclusions?
SAM maintains two distinct databases that serve different purposes for DBA investigations.
Entity Registration is the contractor directory. Active registration is required to receive federal contract awards. This database tells you who the entity is, where they are located, and what they do.
SAM Exclusions is the federal government's blacklist. Entities appear here when they have been debarred, suspended, proposed for debarment, or declared ineligible for federal contracts. ClaimTrove tracks 16,735 exclusion records from this database.
For DBA cases, an exclusion record is a red flag. If the employer was debarred or suspended during the period your client was injured, several questions arise. Was the contract still active? Did the prime contractor know about the exclusion? Was DBA insurance maintained despite the exclusion? These questions can affect both the carrier identification and the liability analysis.
Always check both databases. An entity can have an active registration and a simultaneous exclusion record if the exclusion is agency-specific or if the entity is in "proposed for debarment" status while continuing work under existing contracts.
How Does SAM.gov Reveal Parent Companies and Subsidiaries?
SAM entity records sometimes include a "parent" field that identifies the entity's corporate parent. This is essential for DBA work because insurance policies often attach at the parent company level, not the subsidiary level.
Consider a contractor like Amentum. Through acquisitions, Amentum absorbed PAE, V2X, and GIS. A worker injured while employed by PAE in 2018 would need the carrier that covered PAE at that time, not the carrier that covers Amentum today. SAM records can help you trace that corporate lineage by showing which entity was registered, when, and under what parent.
The limitation is that SAM does not provide a complete corporate family tree. It captures the registration as of a point in time. For complex corporate families with mergers and acquisitions, SAM is one piece of the puzzle. You also need contract award records, DOL filings, and a structured investigation workflow to map the full chain from employer to carrier.
This is where the scale of the problem becomes clear. When a single employer has multiple SAM registrations across subsidiaries, each potentially linked to different contracts and different insurance carriers across different time periods, manual cross-referencing becomes impractical. You need a system that connects SAM entity data to contract awards, carrier mappings, and DOL filings simultaneously.
Why Manual SAM.gov Searching Falls Short for DBA Investigations
SAM.gov is a registration system. It was designed to manage vendor eligibility, not to support insurance investigations. Three structural limitations make manual SAM searching inadequate for DBA carrier identification.
First, SAM does not link to insurance carriers. The registration captures what the entity is and what it does, but not who insures it under the DBA. You need to cross-reference the SAM entity against DOL records, contract awards, and FOIA database results to find the carrier.
Second, SAM snapshots are current-state only. The public search shows the entity's current registration. Historical registrations, including old addresses, old CAGE codes, and expired DBA names, require archived data. If your client was injured five years ago, the SAM record you see today may not reflect the entity's status at the time of injury. The distinction between prime and subcontractor relationships can also shift between the date of injury and the date of your investigation.
Third, SAM cannot resolve the alias problem at scale. A search for "Blackwater" will not automatically surface "Xe Services" or "Academi," even though they are the same company. You have to know the aliases before you can search for them.
ClaimTrove integrates 865,232 SAM entity registrations with carrier mappings, contract awards, and 214 employer alias groups. When you search for an employer, the system cross-references SAM data with 18 federal sources to build a complete picture: entity identity, contract history, and insurance carrier, all in one investigation. Run your first employer investigation and see how SAM data connects to the carrier answer you need.