Your Client Was Injured Overseas, But Was DBA Coverage Even Required?
A paralegal calls you with a new referral. The injured worker was employed by a U.S. contractor in Kuwait, doing vehicle maintenance on a military installation. Straightforward DBA case, right? Maybe not. The employer's contract was a supply agreement for replacement parts, not a service contract. The worker was a local national, not a U.S. citizen. And the contract file contains no trace of FAR 52.228-3 or 52.228-4.
These details matter. The Defense Base Act does not blanket every federal contract performed outside the United States. It covers specific categories of work, specific types of workers, and specific contractual arrangements. Miss the distinction, and you spend weeks chasing a carrier that was never required to exist.
Attorneys who handle DBA claims regularly know the frustration. You identify the employer, trace the prime contractor, and begin the carrier investigation, only to discover the underlying contract may not have triggered DBA obligations at all. The contract type determines whether FAR insurance clauses were mandatory, and those clauses determine whether a carrier was ever on risk.
ClaimTrove's database tracks 43,298 prime contract awards across federal agencies. Not all of them carry DBA insurance requirements. Understanding which contract types do, and which do not, saves you from investigating dead ends before you even start.
What Is the Core Legal Test for DBA Coverage on an Overseas Contract?
The Defense Base Act (42 U.S.C. Section 1651) extends the Longshore and Harbor Workers' Compensation Act to specific categories of overseas employment. The statute identifies four covered situations. Each one connects to contract type in a different way.
First, any contract with a U.S. government agency for public works outside the United States. Second, contracts approved or funded under the Foreign Assistance Act. Third, contracts with employers providing services or construction on military bases or lands used by the United States outside the continental U.S. Fourth, contracts where employees work for American employers providing welfare or similar services for armed forces personnel overseas.
The practical test breaks down to three elements: Is there a U.S. government contract or subcontract? Does the work occur outside the United States? Does the contract involve U.S. citizens, residents, or individuals hired within the United States? When all three align, the employer must secure DBA insurance. When any element is missing, the obligation may not exist, and no carrier was ever required to write a policy.
This is where FAR 52.228-3 and the contract clause framework become critical. The Federal Acquisition Regulation translates the statutory requirement into a contract-level obligation. If the contracting officer determined DBA applied and inserted the clause, the contractor was required to obtain coverage. If the clause is absent, the coverage question gets significantly murkier.
How Do Service Contracts Differ From Supply Contracts Under the DBA?
The single most common contract-type confusion in DBA practice involves service contracts versus supply contracts. The distinction is not academic. It determines whether workers performing under the contract were ever covered.
Service contracts involve people performing work. Maintenance, security, logistics, food service, IT support, construction, medical staffing. These contracts almost always trigger DBA requirements when performed overseas on government installations. The Department of Defense alone accounts for the vast majority of OCONUS service contracts, and DOD's 38,582 overseas contracts represent the largest pool of DBA-obligated work in the federal system.
Supply contracts, by contrast, involve delivering goods. A contract to ship 10,000 replacement vehicle batteries to Bagram Airfield is a supply contract. The manufacturer in Ohio does not need DBA coverage for factory workers. But here is where it gets complicated: if that same contract includes installation services, or if the supplier sends technicians overseas to train military personnel on the equipment, those workers may fall under the DBA.
Hybrid contracts blur the line further. A contract classified as "supplies" in the Federal Procurement Data System may contain a significant service component. The FPDS product or service code (PSC) provides a clue. Codes starting with letters A through Z indicate services. Codes starting with numbers indicate supplies. But the PSC classification does not control the legal analysis. A contract coded as a supply contract can still trigger DBA obligations if it involves U.S. workers performing services overseas.
For attorneys investigating a claim, the contract type in USAspending or FPDS is a starting point, not a conclusion. You need the actual contract document, the statement of work, and the FAR clauses incorporated by reference to determine whether DBA coverage was required.
When Do Grants, Cooperative Agreements, and USAID Programs Trigger the DBA?
Federal assistance instruments create a separate category of DBA confusion. Grants and cooperative agreements are not contracts in the FAR sense. They are not subject to the Federal Acquisition Regulation. Yet certain overseas assistance programs still trigger DBA coverage through the Foreign Assistance Act pathway.
USAID is the primary example. When USAID awards a contract for overseas development work, DBA coverage applies under the standard FAR framework. But USAID also funds work through implementing partners under grants and cooperative agreements. These instruments do not contain FAR clauses. Instead, USAID imposes DBA requirements through Agency Acquisition and Assistance Policy Directives (AAPDs).
The practical result: a nonprofit implementing partner running a health program in Sub-Saharan Africa under a USAID cooperative agreement still needs DBA insurance for its U.S. employees. The legal pathway differs from a DOD service contract, but the obligation exists. Understanding how USAID structures its DBA coverage requirements is essential for attorneys handling claims from the development sector.
Other agencies funding overseas work through grants, such as the State Department's Bureau of Democracy, Human Rights, and Labor, may impose similar requirements. The key is whether the grant terms incorporate DBA insurance obligations. Unlike FAR-governed contracts, you cannot rely on a standard clause number. You must review the specific award terms and conditions.
International organizations add another layer. Work funded by the World Bank, the UN, or NATO but performed by a U.S. contractor may or may not trigger DBA coverage depending on whether a U.S. government contract sits somewhere in the funding chain. A U.S. company hired directly by NATO without a U.S. government contract intermediary may fall outside the DBA entirely.
What Role Does FAR 52.228-3 Play in Determining Coverage Obligations?
FAR 52.228-3 (Workers' Compensation Insurance, Defense Base Act) and FAR 52.228-4 (Workers' Compensation and War-Hazard Insurance Overseas) are the regulatory mechanisms that translate statutory DBA requirements into contract-level obligations.
When a contracting officer determines that a contract involves work outside the United States and that DBA coverage applies, they are required to insert FAR 52.228-3 into the contract. This clause obligates the contractor to obtain DBA insurance, maintain it throughout contract performance, and extend the requirement to subcontractors.
FAR 52.228-4 goes further, incorporating the War Hazards Compensation Act (42 U.S.C. Section 1701) for contracts in war-risk zones. This clause matters for carrier investigation because WHCA allows Treasury Department reimbursement of insurance carriers for war-caused injury claims, which affects how carriers price and structure DBA policies in conflict zones.
The absence of these clauses in a contract does not automatically mean DBA coverage was not required. Contracting officers sometimes fail to include mandatory clauses. The DBA statute operates independently of the FAR. If the statutory criteria are met, the employer's obligation to secure DBA insurance exists regardless of whether the contracting officer remembered to insert the clause. However, the absence of the clause makes carrier identification harder because there is no contractual paper trail requiring the contractor to obtain and report coverage.
For attorneys, the FAR clause is the first investigative marker. A contract containing FAR 52.228-3 confirms DBA applied. A contract missing the clause requires deeper statutory analysis to determine whether coverage was nonetheless required.
How Do Personal Services Contracts and Intergovernmental Agreements Affect DBA Coverage?
Personal services contracts (PSCs) are a distinct contract type used primarily by the State Department and USAID to hire individuals, not companies, for overseas work. Under a PSC, the individual is treated essentially as a direct-hire government employee for supervision purposes, but they remain a contractor for benefits purposes.
DBA coverage applies to PSCs when the individual is a U.S. citizen or resident hired to work outside the United States. The contracting agency typically arranges DBA coverage through its mandatory insurance program rather than requiring the individual to obtain their own policy. This is one reason smaller agencies like DOJ sometimes create coverage blind spots: the administrative machinery for ensuring PSC workers have DBA coverage is less developed than at State or DOD.
Intergovernmental agreements (IGAs) present a different problem. When the U.S. government enters an agreement with a foreign government, and that foreign government hires contractors to perform work, the DBA chain may break entirely. The foreign government is not a U.S. employer. The contract is not a U.S. government contract. Unless a U.S. agency has a separate contract with the employer, DBA coverage does not attach through the IGA alone.
Status of Forces Agreements (SOFAs) add jurisdiction complexity without directly creating DBA obligations. A SOFA governs the legal status of U.S. personnel in a host nation. It does not determine whether a contractor's workers are covered under the DBA. That determination still flows from the contract type and the statutory criteria.
Contingency contracts under programs like LOGCAP, AFCAP, and CONCAP are almost always DBA-obligated. These large-scale logistics and construction programs exist specifically to support military operations overseas. The prime contractors, and their subcontractors down the chain, carry DBA insurance as a contract requirement. The challenge for attorneys is not whether coverage exists but which carrier held the policy during the relevant contract period.
Which Contract Types Fall Outside the DBA Requirement?
Several categories of overseas federal work do not trigger DBA coverage. Knowing these exclusions prevents wasted investigation time.
Purely domestic contracts with incidental overseas travel generally do not require DBA coverage. An engineer employed under a contract performed primarily in Virginia who makes a two-week trip to Germany for a site inspection is typically covered by state workers' compensation, not the DBA. The test looks at where the work is "principally" performed, not whether any overseas travel occurred.
Foreign national employees hired in-country, outside the United States, may fall outside the DBA depending on the contract terms and the specific statutory provision invoked. The DBA's coverage of local nationals varies by contract type and agency. Some contracts explicitly extend DBA coverage to local nationals. Others rely on host-nation labor law. This is a frequent source of disputes at the Benefits Review Board.
Contracts with foreign governments or international organizations that do not involve a U.S. government contract or subcontract in the chain typically fall outside the DBA. A U.S. security company hired directly by the Iraqi government, without a U.S. prime contract, would not have DBA obligations, though it might carry commercial workers' compensation or foreign voluntary workers' compensation instead.
Military and civilian government employees are covered by the Federal Employees' Compensation Act (FECA), not the DBA. This seems obvious, but it creates confusion when government personnel and contractor personnel work side by side on the same installation. The employment relationship, not the work location, determines the applicable statute.
Finally, contracts performed in U.S. territories (Guam, Puerto Rico, U.S. Virgin Islands, American Samoa, Northern Mariana Islands) may fall under the LHWCA directly rather than the DBA, depending on the specific territory and the nature of the work. The DBA applies "outside the continental United States," and whether a territory qualifies depends on the statutory definition in play. Understanding who the DBA actually covers requires parsing these geographic boundaries carefully.
How Does ClaimTrove Help You Determine Contract-Type Coverage?
When you receive a new DBA referral, the first question is whether the DBA even applies. The second question is who the carrier was. Both require contract-level data that most attorneys do not have at intake.
ClaimTrove's database contains 43,298 prime contract awards and 4,315 subcontract awards sourced from USAspending, filtered to overseas and OCONUS work relevant to DBA practice. Each record includes the awarding agency, contract type classification, product or service code, performance country, and period of performance. This data lets you quickly determine whether an employer held the type of contract that triggers DBA obligations.
The platform cross-references contract data against 2,454 confirmed employer-carrier mappings, FOIA database results with coverage filing records, and 5,022 OALJ decisions to connect the contract type to an actual insurance carrier. Instead of manually pulling contract documents from FPDS, checking FAR clause inclusion, and tracing the subcontractor chain, you get the coverage determination and carrier identification in a single investigation.
Run your employer through ClaimTrove to see whether their contract type required DBA coverage and which carrier was on risk during the relevant period. Start your investigation now.