What Is USAspending and Why Should DBA Attorneys Care?
USAspending.gov is the federal government's public ledger of all spending, including contracts, grants, and financial assistance. For DBA attorneys, the contract data is the relevant slice. It contains records of every federal contract award above the micro-purchase threshold, including the prime contractor name, contract number, place of performance, and period of performance.
This matters for DBA investigations because the contract is the link between the employer and the government relationship that triggers DBA coverage. If your client worked overseas under a federal contract, the USAspending record for that contract tells you who the prime was, where the work was performed, and when the contract was active. These three facts are the foundation of carrier identification.
ClaimTrove indexes 43,298 contract awards from USAspending that are relevant to DBA investigations. This curated dataset focuses on overseas contracts with defense and national security agencies, filtering out the domestic contracts that are irrelevant to DBA practice. But understanding what the raw USAspending data contains and what it means helps you use it more effectively, whether you are searching through ClaimTrove or querying USAspending directly.
Which USAspending Fields Matter Most for DBA Carrier Identification?
USAspending contract records contain dozens of fields. Most are irrelevant to DBA practice. The fields that matter fall into four categories: contract identification, recipient identification, place of performance, and labor standards.
The PIID (Procurement Instrument Identifier) is the contract number. This is the single most important field for DBA investigators. The PIID uniquely identifies a contract and allows you to trace all modifications, task orders, and subawards associated with it. When a claimant provides a contract number from their employment records, the PIID search connects that number to the full contract record.
The recipient fields identify the prime contractor. The recipient name, UEI (Unique Entity Identifier), and DUNS number (for older contracts) tell you which company received the contract award. For DBA purposes, this is the prime contractor whose DBA insurance covers workers on this contract, unless the work was subcontracted.
Place of performance fields show where the work was done. The country code, state/province, city, and sometimes specific installation name identify the geographic location. For DBA claims, this confirms whether the work was overseas and, if so, in which country. This information is critical for matching the injury location to the contract location.
The labor standards flag is a field that many DBA practitioners overlook. USAspending includes fields related to labor law applicability, including whether the DBA applies to the contract. When this flag indicates DBA applicability, it confirms that the contract triggers DBA coverage requirements. This can be valuable evidence when a carrier or employer disputes whether the DBA applies to the work at all.
What Does the DBA Labor Standard Flag Actually Mean?
The labor standards data in federal contract records includes flags for various labor laws: the Davis-Bacon Act, the Service Contract Act, the Walsh-Healey Act, and the Defense Base Act. When the DBA flag is set to "Y" (yes), it means the contracting officer determined at the time of award that the DBA applies to the contract.
This determination is significant. It means the government recognized that the contract would involve work outside the United States and that the DBA's workers' compensation requirements applied. The contractor was required to obtain DBA insurance as a condition of the contract. The cost of that insurance was presumably factored into the contract price.
For DBA practitioners, a "Y" flag is strong evidence that the contract triggers DBA coverage. It can counter an employer's argument that the work was not covered by the DBA or that the employer did not know DBA insurance was required. The government's own determination, documented in the contract record, speaks for itself.
However, the absence of a "Y" flag does not necessarily mean the DBA does not apply. The flag may not have been set due to administrative oversight. The contract may have been modified to include overseas work after the initial award. Some contract types have the DBA requirement incorporated by reference through FAR clauses (specifically FAR 52.228-3 and 52.228-4) even if the labor standards flag is not explicitly set.
The flag is most useful as confirmatory evidence. When you already believe the DBA applies based on the nature of the contract and the overseas work location, the "Y" flag confirms that assessment. When the flag is absent, you need to look at the contract terms themselves, particularly the incorporated FAR clauses, to determine DBA applicability.
How Do You Search USAspending Effectively for DBA Cases?
USAspending.gov offers both a web interface and a bulk data API. For DBA investigations, the most common search approaches are by recipient (contractor name), by PIID (contract number), and by place of performance (country).
Searching by recipient is the most intuitive but has pitfalls, which is why starting with employer alias resolution is so important. Contractor names in USAspending may not match the name the claimant used. A contractor may be registered under its legal entity name rather than its DBA (doing business as) name. Corporate acquisitions mean the same contract may show different recipient names at different points in time. Searching for "DynCorp" might require also searching for "DI Operations," "DynCorp International," or the current parent company name.
Searching by PIID is more precise when you have a contract number. The PIID search returns the specific contract record, all modifications, and associated data. If the claimant has any paperwork showing a contract number, this is the fastest path to the contract record.
Searching by place of performance is useful when you know the work location but not the contractor. Filtering USAspending by country (e.g., Afghanistan) and agency (e.g., Department of Defense) returns all contracts with that place of performance. This can identify which primes operated in the relevant area, even if the claimant does not remember their employer's name.
One important limitation: USAspending's recipient search performs substring matching. Searching for "Supreme" will return Supreme Foodservice, Supreme Group, and any other contractor with "Supreme" in the name. This can be useful for broad searches but produces false positives for common terms. Narrowing by agency, place of performance, or date range reduces noise.
What Are the Limitations of USAspending for DBA Investigations?
USAspending is valuable but incomplete. Understanding its limitations prevents you from over-relying on it or drawing incorrect conclusions from missing data.
First, not all overseas contracts appear with overseas place-of-performance data. Some contracts are awarded with a domestic place of performance (the contractor's headquarters) even though the work is performed overseas. This is particularly common with service contracts where the contractor mobilizes from a U.S. location. An attorney searching for contracts performed in Afghanistan may miss contracts that list the contractor's Virginia headquarters as the place of performance.
Second, USAspending tracks obligations, not actual performance. A contract may be awarded in one fiscal year, modified in the next, and performed over several years. When contracts get re-competed, the carrier picture can change entirely, as we explain in our article on what happens to DBA coverage when contracts get rebid. The date fields in USAspending reflect when money was obligated, not necessarily when work was performed. For DBA purposes, the period of performance is what matters, and it may differ from the obligation dates.
Third, classified or sensitive contracts may not appear at all. Some defense and intelligence contracts are excluded from public reporting. A worker on a classified contract may not find their employer in USAspending. Similarly, contracts below the reporting threshold (currently $30,000 for subawards) are not included.
Fourth, the data quality varies. Contracting officers enter the data, and human error means some records have incorrect codes, misspelled names, or wrong country codes. Cross-referencing USAspending data with other sources helps catch these errors.
Despite these limitations, USAspending remains the single most comprehensive public source for federal contract data. Its 43,298 DBA-relevant contract records in ClaimTrove's indexed dataset cover the vast majority of significant overseas defense contracts. The limitations mean you should not treat a negative search result as proof that a contract does not exist. It means you may need additional sources to fill the gaps.
How Does ClaimTrove Cross-Reference Contract Data with Carrier Databases?
Raw contract data tells you who had the contract. Carrier databases tell you who insured the contractor. Connecting these two datasets is the core of DBA carrier identification, and it is what ClaimTrove automates.
The cross-referencing works in several steps. When you search for an employer or a contract, ClaimTrove first identifies the employer from the contract data. It then searches its carrier databases, which include 637 authorized DBA carriers, 2,454 employer-carrier mappings, and 4,983 DOL case summaries. Each of these sources may contain carrier information for the employer, potentially from different time periods.
The temporal cross-reference is where the real value lies. A contract record shows that Employer X held a contract from 2012 to 2017. The carrier database shows that Employer X was insured by Carrier A from 2012 to 2014 and Carrier B from 2014 to 2017. An injury in 2013 points to Carrier A. An injury in 2016 points to Carrier B. Without the temporal dimension, you would just know that two carriers have been associated with the employer. With it, you can pinpoint which carrier was on the risk.
ClaimTrove also cross-references across data types. An OALJ decision involving Employer X may identify its carrier at the time of the case. A DOL case summary may identify the carrier from a prior claim. FOIA database results may confirm the carrier during a specific period. By aggregating these sources, ClaimTrove builds a more complete picture than any single source provides.
This cross-referencing approach addresses the fundamental limitation of USAspending: it tracks contracts, not insurance. By connecting contract data to carrier data, DBA attorneys can move from "who had the contract" to "who insured the contractor" in a single investigation.
What Are the Key FAR Clauses That Indicate DBA Coverage?
The Federal Acquisition Regulation (FAR) contains specific clauses that incorporate DBA requirements into federal contracts. When you are reviewing a contract to determine DBA applicability, these clauses are the definitive indicators.
FAR 52.228-3, "Workers' Compensation Insurance (Defense Base Act)," is the primary clause. It requires the contractor to provide workers' compensation insurance as required by the DBA. This clause is mandatory for contracts that involve work outside the United States. Its presence in a contract is conclusive evidence that the DBA applies.
FAR 52.228-4, "Workers' Compensation and War-Hazard Insurance Overseas," extends the requirement by also incorporating the War Hazards Compensation Act. This clause appears in contracts involving work in areas of armed conflict. It requires both DBA coverage and war-hazard insurance, which provides additional benefits for injuries caused by war-risk hazards.
FAR 28.305 prescribes when these clauses must be included. It states that FAR 52.228-3 must be inserted in solicitations and contracts that require or may require work outside the United States. The "may require" language is important. Even if the contract is primarily domestic, if there is a possibility of overseas work, the clause should be included.
For DBA practitioners, the presence of these FAR clauses in the contract confirms DBA applicability. The contract itself, obtained through FOIA or discovery, is the best evidence. But even without the actual contract document, the combination of an overseas place of performance, a defense agency as the contracting office, and a "Y" on the labor standards flag creates a strong inference that these clauses are present.
What Practical Steps Should DBA Attorneys Follow When Using Contract Data?
Using USAspending data effectively requires a structured approach. Follow these steps to extract maximum value from contract data in your DBA investigations.
Step one: Gather all identifying information from the claimant. The employer name, any contract numbers, the work location, the dates of employment, and the name of the military installation or base. Even partial information helps narrow the search.
Step two: Search for the contract. Use the PIID if you have it. Otherwise, search by recipient name, place of performance, and date range. Look for the specific contract that covers the work your client performed. Remember that the claimant's employer may be a sub, so also check subaward data.
Step three: Verify the employer. Confirm that the recipient on the contract record matches the claimant's employer. If it does not, the claimant likely worked for a sub. Identify the prime and then trace the sub relationship.
Step four: Check the DBA labor standards flag. A "Y" confirms DBA applicability. If the flag is not set, check the contracting agency, the place of performance, and the nature of the work to assess DBA applicability independently.
Step five: Cross-reference with carrier data. Take the confirmed employer name and search carrier databases for the carrier on risk during the relevant period. Use case summaries, OALJ decisions, and FOIA database results to identify or confirm the carrier.
Step six: Document the chain. Record the contract number, the prime contractor, the sub (if applicable), the DBA carrier, and the policy period. This documentation becomes the foundation of your claim filing and protects against jurisdictional challenges.
ClaimTrove automates steps two through five by cross-referencing contract data with carrier databases in a single search. Start your investigation with the employer name or contract details, and the platform returns the contract record, associated carriers, and relevant case history in one result set.