If you’ve ever asked yourself, “when do I need DBA insurance instead of workers’ comp?”, you’re already ahead of most contractors who discover the answer after an employee is injured overseas. Most contractors who’ve been around federal work for a while carry a quiet confidence about their insurance. They have workers’ comp. Their employees are covered. That confidence is usually well-placed for domestic contracts. The moment those same employees board a plane for a military installation overseas, it becomes a liability.
State workers’ compensation is a state-governed program. It has territorial limits. It was not designed to follow your workforce to a U.S. military base in the Middle East or a USAID-funded infrastructure project in West Africa. The Defense Base Act (DBA) exists specifically for that gap, and it operates as a federal statute, not a state benefit. Under 42 U.S.C. §§ 1651, 1654 and FAR 52.228-3, once the triggers are met, coverage is not discretionary.
This article works like a decision tree. By the end, you’ll know when DBA is required instead of state workers’ comp, which clauses signal the obligation, and what it costs you legally and financially to get this wrong. The contractors who handle this cleanly are the ones who run the question at the proposal stage, not after award when the first employee is already on the ground.
How DBA and Workers’ Comp Actually Differ
The dividing line between these two programs is geography and governing law. State workers’ compensation operates under state jurisdiction, administered by state agencies, and bounded by state borders. The Defense Base Act is a federal statute, codified at 42 U.S.C. §§ 1651, 1654, that extends the Longshore and Harbor Workers’ Compensation Act to overseas government contract work. In covered overseas employment, DBA generally supersedes state workers’ comp, and state boards typically lack jurisdiction over DBA claims. If you have a mixed-employment situation with both domestic and overseas exposures, state coverage may still apply to the domestic portion, but for employees on qualifying overseas contracts, the two programs don’t share the same lane.
The benefit structure is also materially different. DBA provides unlimited lifetime medical benefits with no dollar cap, disability payments at two-thirds of average weekly wage (currently capped at $2,082.70 per week for fiscal year 2025, 2026, per the Department of Labor’s LHWCA benefit schedule), repatriation expenses, and death benefits. State workers’ comp varies widely by jurisdiction and often includes treatment caps and duration limits that DBA doesn’t impose. That difference matters when an employee sustains a serious injury overseas. That’s not a technicality; it’s the difference between what an injured worker can actually recover.
Coverage under DBA also extends further than most contractors expect. Per DOL statutory interpretation, DBA covers all employees on a qualifying contract regardless of nationality. U.S. citizens, third-country nationals, and host-country nationals are all included once the contract qualifies. If you’re running a mixed-nationality team on an overseas project, DBA covers the entire workforce, not just the Americans.
When Is DBA Required Instead of State Workers’ Comp?
The most common trigger is straightforward: if your employees perform work on a U.S. military base, air base, or naval installation outside the United States, or on any land occupied or used by the U.S. for military purposes abroad, DBA is required. The location alone is often sufficient to establish the obligation. You don’t need a war-zone designation, a specific contract type, or any particular funding structure. The military land trigger is independent.
“Public work” under the DBA is broader than most contractors assume. According to DOL guidance, it includes service contracts, logistics support, staffing, and other projects connected to national defense or war activities performed outside the United States under a U.S. government contract. Contractors who associate DBA exclusively with construction crews frequently miss this trigger and find themselves uninsured on service contracts that clearly qualified.
The Foreign Assistance Act trigger catches a different category of contractors entirely. If your contract is approved and funded by the United States under the Foreign Assistance Act, DBA applies to employees performing that work overseas. This includes USAID-funded projects and similar programs, even when the funding reaches workers through cooperative agreements or grants rather than direct contracts. The funding source matters, not just the contract vehicle.
FAR and DFARS Clauses That Activate Your DBA Obligation
FAR 52.228-3: The Primary Trigger
FAR 52.228-3is the clause that converts the DBA statute into a contractual requirement. Per FAR 28.309, contracting officers are required to include this clause in applicable overseas contracts. When FAR 52.228-3 appears in your contract, it requires you to secure DBA coverage before performance begins and maintain it through contract completion. The clause applies to prime contractors and flows down to subcontractors. If you’re a subcontractor on a DBA-covered prime contract, the obligation follows you even if your own subcontract documents don’t explicitly restate the clause.
AIDAR 752.228-3: The USAID Equivalent
Contractors working on USAID-funded international projects encounter AIDAR 752.228-3 instead of the standard FAR clause. This clause similarly requires the contractor to procure DBA insurance unless the Department of Labor has approved self-insurance or a retrospective rating plan. During solicitation review, these clause numbers are the clearest signal that DBA is a requirement. When you see them in the contract documents, the compliance question is answered. The only remaining question is how to obtain the coverage.
DoD components, including Army, Navy, Air Force, DCMA, and DCAA, use FAR 52.228-3 routinely in overseas defense contracting. Civilian agencies like State, USAID, and GSA use it more selectively when they have overseas performance requirements. Regardless of which agency issued the contract, finding FAR 52.228-3 in your documents ends the analysis on whether DBA applies.
Contingency Zones and Elevated-Risk Performance Locations
The DBA obligation exists whether your contract is performed in a stable allied country or a conflict-adjacent environment, take a logistics contractor in the Horn of Africa or a staffing firm supporting base operations in Eastern Europe, for example. What changes in higher-risk locations is how underwriters assess the exposure, what they need in order to quote coverage, and what premiums look like. The legal requirement is identical. Contractors performing work in contingency zones sometimes assume the compliance rules are relaxed or suspended in those environments. They aren’t.
A standard state workers’ comp policy has no mechanism to respond to a DBA-covered injury sustained overseas, particularly in a war-risk or contingency environment. Attempting to rely on a domestic policy for overseas employees on a qualifying contract leaves the employer directly liable for every benefit owed to the injured worker, with no policy to absorb that exposure. In a serious injury or fatality claim, that’s not an administrative problem, it’s a financial one that can end a company.
What’s at Stake When You Skip Required DBA Coverage
Failing to secure required DBA insurance is a federal misdemeanor. The statute authorizes fines up to $10,000, imprisonment up to one year, or both. For corporations, the president, secretary, and treasurer carry personal and several liability for those penalties, alongside joint and several liability with the corporation for any compensation benefits owed to injured workers. This is not an administrative citation from a contracting officer. It is federal criminal exposure with personal consequences for named officers.
The civil exposure compounds the criminal risk. Without coverage in place, the employer loses access to common-law defenses like contributory negligence and assumption of risk in civil suits brought by injured workers or their families. It’s also worth distinguishing between DBA statutory benefit exposure, which follows the LHWCA wage schedule, and separate tort liability, which can arise in certain forums and claim theories and may not be subject to the same limits. A missing DBA policy is also a contract violation that can trigger termination for cause. For a small GovCon firm, absorbing a serious overseas injury claim entirely out of pocket is an existential event.
The contractors who end up in these situations rarely set out to cut corners. They simply assumed their existing workers’ comp coverage was sufficient, or they didn’t read the clause language carefully, or they bought their insurance from a broker who didn’t know to ask the DBA question. None of those explanations change the liability exposure once a claim arrives without a policy behind it.
Securing DBA Coverage Before Your Contract Starts
DBA underwriting centers on a few core data points: total payroll by job classification, countries or regions of performance, employee headcount (broken down by U.S. nationals, third-country nationals, and local nationals), contract duration, and the nature of the work being performed. Unlike some commercial lines, DBA policies are typically guaranteed-cost with no deductibles, so the premium reflects the full exposure without cost-sharing options. Authorized carriers are fewer than in standard commercial markets, major players include ACE-USA, AIG, and CNA, which makes broker relationships with experienced DBA underwriters more valuable than they are in domestic lines.
In practice, most DBA placements through a specialist broker can be bound within one to three business days once the submission is complete. Complex programs with multiple countries or unusual job classifications take longer. Start the placement process during proposal development, not after award.
The contractors who stay compliant don’t figure this out after award. They run contract language through a compliance review at the proposal stage, before they’ve priced the work and committed to a cost structure. At Risk Reconnaissance LLC, that’s exactly how we work with government contractors: identifying DBA triggers during proposal development so the coverage cost is priced into the bid and the policy is in place before the first employee boards a plane. Getting this right at the front end is a straightforward problem. Discovering a compliance gap mid-performance is a different problem entirely.
The Decision Tree, Simplified
When do you need DBA insurance instead of workers’ comp? If your contract involves performance outside the United States on a military installation, a U.S. government public works contract, or a Foreign Assistance Act-funded project, and FAR 52.228-3 or AIDAR 752.228-3 appears in your contract documents, DBA coverage is not optional. State workers’ comp doesn’t travel with your employees to those locations. The penalties for going uncovered include criminal liability and contract termination; civil exposure can extend into tort liability territory beyond the DBA wage schedule, depending on the claim and forum.
The practical move is to review solicitation language before submission, not after award. If you’re uncertain whether your contract triggers the DBA obligation, run it through a broker who understands GovCon contract language before you commit to a performance price that doesn’t account for the coverage cost. Getting DBA insurance in place is a straightforward process once you know the triggers. Knowing the triggers before award is what changes outcomes.