Most government contractors assume their workers’ compensation policy follows their employees wherever they go. It doesn’t. The moment a covered employee crosses onto foreign soil under a U.S. government contract, a separate federal law takes over, and if coverage hasn’t been structured correctly before that deployment, the contractor is holding uninsured liability on an overseas job site. They usually don’t find out until a claim surfaces.
Understanding the Defense Base Act vs. workers’ compensation is the starting point for any GovCon contractor with overseas personnel. State-administered workers’ compensation governs domestic operations. The Defense Base Act (DBA), a federal law extending the Longshore and Harbor Workers’ Compensation Act (LHWCA), governs injury liability for civilian employees working overseas on covered U.S. government contracts. At Risk Reconnaissance LLC, this is one of the most frequent coverage questions we see, and the answer almost always surprises contractors who assumed their existing policy had them covered everywhere.
This article explains which law applies and when, how the benefits actually differ, what FAR 52.228-3 requires you to carry, and what the claims process looks like when something goes wrong overseas.
The Line That Separates DBA from State Workers’ Compensation
The core distinction is jurisdictional, not industry-based. State workers’ compensation laws apply to employees injured while working within U.S. borders. The Defense Base Act extends the LHWCA to civilian employees working overseas on covered U.S. government contracts. When covered employment moves onto foreign soil, DBA is the governing law, not the state policy you’ve been renewing every year.
A contractor with both domestic and overseas employees needs both systems running simultaneously. State workers’ comp covers employees working stateside; DBA insurance covers employees deployed on covered overseas contracts. One policy does not handle both situations, and that gap is exactly the kind of thing a Contracting Officer, a prime contractor’s insurance compliance checklist, or an injured worker’s attorney will eventually surface.
State workers’ comp policies are written to comply with the law of a specific state and carry no authority outside U.S. jurisdiction. They do not respond to an overseas DBA claim. The LHWCA foundation matters here because DBA benefits are calculated using national formulas and averages rather than state-specific schedules, and the claims process runs through the Department of Labor’s Office of Workers’ Compensation Programs (OWCP), not a state workers’ comp board.
One detail that regularly catches contractors off guard: “overseas” under the DBA includes work on U.S. military bases located in foreign countries. Even if the environment feels operationally similar to a domestic installation, the legal geography still triggers DBA coverage obligations.
GovCon Scenarios That Trigger DBA Coverage
The DBA doesn’t apply to all overseas work. It applies to specific categories of covered employment connected to U.S. government contracts, military operations, or foreign assistance programs. Knowing which contract types create the obligation is the practical starting point for any contractor evaluating their coverage structure.
Work performed by private employer employees on U.S. military bases, or on lands used for military purposes outside the U.S., triggers DBA coverage. So do public works contracts with U.S. government agencies tied to national defense or war activities performed on foreign soil. A logistics firm supporting a DoD base in the Middle East, a staffing company providing personnel to a USAID-funded project in sub-Saharan Africa, or a security contractor working in a contingency environment under a DoD task order, all are in covered employment under the DBA.
DBA coverage also flows down to subcontractors on covered prime contracts. Here’s the detail that surprises most small GovCon firms: coverage does not depend on the worker’s nationality. U.S. citizens, third-country nationals, and host-country locals employed on a covered contract are all covered under the DBA. If your company hires local labor to support an overseas contract deliverable, those workers are covered, and your obligation to carry DBA insurance doesn’t change based on their citizenship.
Once you’ve confirmed that DBA coverage applies, the next question is what it actually pays, and how that compares to a standard workers’ comp policy.
How DBA Benefits Compare to Standard Workers’ Compensation
DBA benefits follow a uniform federal formula. State workers’ comp benefits vary by jurisdiction and often come with lower caps, shorter durations, and more procedural friction on treatment authorization. The comparison typically runs in DBA’s favor, particularly for contractors operating in remote or hostile environments.
On the medical side, DBA entitles injured workers to full medical treatment from a physician of their choice. Many state workers’ comp systems impose fee schedules, treatment authorization requirements, or duration limits that DBA does not carry in the same way. For an employee injured at a remote overseas job site where treatment access is already complicated, that distinction is significant.
DBA temporary total disability pays two-thirds of the employee’s average weekly earnings, subject to a federal maximum weekly rate tied to the national average wage and adjusted annually. For the October 2025 through September 2026 period, that federal maximum is $2,082.70 per week. Many state workers’ comp systems use lower caps or shorter payment periods. DBA also covers partial loss of earning capacity and provides lifetime permanent total disability benefits in qualifying cases, a duration that is not standard across state systems.
For death benefits, DBA pays one-half of average weekly earnings to a single surviving dependent, or two-thirds to two or more dependents, subject to the federal maximum. State workers’ comp death benefits vary widely in amount, eligible survivors, and duration. For contractors performing in contingency environments, the consistency of the federal death benefit structure is a meaningful protection for employees and their families.
What FAR 52.228-3 Requires of Contractors
DBA insurance is not optional on covered overseas contracts. It is a contractual and legal requirement built directly into the Federal Acquisition Regulation. FAR 52.228-3 mandates that contractors provide workers’ compensation-type benefits, including disability compensation, medical benefits, and death benefits, to covered employees during contract performance. The Contracting Officer includes this clause in covered contracts. It is not advisory language.
Prime contractors also carry responsibility for ensuring subcontractor compliance. That makes DBA insurance a teaming agreement concern, not just a prime-level issue. If a subcontractor is performing covered work on your overseas contract without DBA insurance, your exposure doesn’t disappear because the obligation technically sat with the sub.
The War Hazards Compensation Act (WHCA) works alongside the DBA as a cost-recovery mechanism, not a replacement. When an injury results from a war-risk hazard, hostile fire, weapons discharge, or detention by a hostile force, the paying employer or carrier can seek reimbursement from the federal government under WHCA after a qualifying DBA claim is paid. WHCA does not eliminate the contractor’s obligation to carry DBA insurance upfront. The coverage obligation comes first; WHCA applies on the back end when the cause of injury meets the war-hazard definition.
Contractors without required DBA coverage face direct liability for all DBA benefits owed, plus potential contract compliance consequences. That includes stop-work orders, withheld progress payments, cure notices, and contract termination for default. Beyond contract consequences, employees or their heirs can sue an uninsured contractor directly under common law, without the usual negligence burden. That is a financial and legal exposure that can outlast the contract itself.
Filing a DBA Claim: Deadlines, Process, and Common Pitfalls
The DBA claims process runs through OWCP, not a state workers’ comp board. The timeline and forms are specific, and missing a deadline creates complications that are difficult to undo.
Key Deadlines
Three deadlines determine whether a DBA claim gets processed cleanly or gets complicated from the start:
- The injured worker generally has 30 days to provide written notice of injury to the employer.
- The employer must file the First Report of Injury (Form LS-202) with OWCP within 10 days if the injury causes the loss of at least one work shift.
- The worker’s formal claim (Form LS-203) must be filed with OWCP within one year of the injury or the last compensation payment, whichever is later.
How the Process Unfolds
Once the claim is filed, the carrier reviews it and either pays or denies. Disputed claims move through OWCP informal procedures and, if unresolved, to a formal hearing before an Administrative Law Judge (ALJ). An ALJ decision can be appealed to the Benefits Review Board and, in some circumstances, to federal court.
Where Claims Go Wrong
The most common mistakes that produce delays or denials are missing the filing deadline, submitting incomplete medical documentation, and providing inconsistent records that don’t clearly tie the condition to covered work. DBA claims are legally and procedurally more complex than most domestic workers’ comp claims. Contractors benefit from having a broker who understands the DBA claims environment and can help coordinate coverage response, documentation, and carrier communication from the moment an incident occurs. Waiting until the claim is disputed to understand the process is waiting too long.
Getting the Right Coverage Mix for Your Contract Portfolio
GovCon contractors performing both domestic and overseas work need two separate systems running in parallel: state workers’ comp for domestic employees and DBA insurance for overseas-deployed personnel. Contractors new to overseas work often assume one policy handles both, or that a standard workers’ comp carrier will extend coverage to an overseas job site without a separate DBA policy in place. That assumption creates the gap.
Coverage gaps typically appear during transitions. A new task order moves work offshore. A subcontractor is added to an overseas deliverable. A contract expands into a new country or adds a new site. Without a structured review process tied to those contract changes, employees in covered employment can find themselves without a DBA policy in place, and the contractor doesn’t know it until something goes wrong.
At Risk Reconnaissance LLC, we work specifically with government and defense contractors to analyze their contract portfolio, identify which employees and work locations trigger DBA obligations, and structure an insurance program that covers both domestic and overseas operations without gaps. Our team carries direct GovCon operational experience, so we review task orders and subcontract chains the way a compliance-minded contractor would, no need to explain what a NAICS code is, what a performance work statement requires, or why a prime contractor’s insurance exhibit matters before a proposal submission.
DBA exposure changes every time a contractor wins a new overseas contract, adds a subcontractor, or expands a task order’s geographic scope. A properly structured program accounts for that variability from the start, so coverage scales with contract performance rather than lagging behind it.
Defense Base Act vs. Workers’ Compensation: What It Means for Your Next Overseas Contract
State workers’ comp governs domestic operations. The Defense Base Act governs civilian employees working overseas on covered U.S. government contracts. The two systems have different benefit structures, different claims processes, and different compliance obligations codified in the FAR. They are not interchangeable, and one does not substitute for the other.
Getting this wrong doesn’t produce a paperwork headache, it produces uninsured liability on an overseas injury claim, a Contracting Officer compliance issue, and a coverage gap that shows up at the worst possible moment: when a task order is already in performance and an employee is already hurt.
If your contract portfolio includes any overseas performance, the next step is a coverage review with a broker who understands what they’re looking at. That conversation is worth having before a task order ships, not after. Reach out to Risk Reconnaissance LLC to walk through your current coverage structure and make sure your DBA obligations are properly addressed.