Why Is Subcontractor Coverage the Hardest Question in DBA Practice?
Your client was injured in Iraq while working for a small security company you have never heard of. The company provided guards for a facility managed by a mid-tier contractor, which held a subcontract under a major LOGCAP prime. Three layers of contractors, potentially three different insurance arrangements, and your client knows only the name of the company that gave them a badge and a paycheck.
Subcontractor DBA coverage sits at the intersection of contract law, insurance regulation, and federal workers' compensation. The Defense Base Act requires that every employer of workers on overseas government contracts carry DBA insurance. But the word "employer" does the heavy lifting in that sentence. In a multi-tier contractor chain, the legal employer may be the subcontractor, the prime contractor, or (in some interpretations) both.
The practical stakes are high. If the subcontractor has its own DBA policy, the claim is filed against that carrier. If the subcontractor lacks coverage, the prime contractor's policy may apply. If neither has appropriate coverage, Section 4(a) of the DBA creates statutory employer liability that can reach up the contractor chain. Getting this wrong means filing against the wrong carrier, which delays benefits and complicates litigation.
ClaimTrove tracks 4,315 subcontract awards in our USAspending database, covering 918 distinct subcontractors linked to overseas prime contracts. These records, combined with OALJ decisions and DOL filings, reveal the patterns that drive subcontractor coverage disputes.
What Does Section 4(a) of the DBA Require?
Section 4(a) of the Defense Base Act extends the LHWCA's coverage provisions to employees working on overseas government contracts. The LHWCA, in turn, requires every employer to secure workers' compensation coverage for its employees. The DBA incorporates this requirement and applies it to the overseas contracting context.
The critical provision is LHWCA Section 4(a), which establishes that a contractor who subcontracts work is liable for compensation to the subcontractor's employees if the subcontractor fails to secure its own coverage. This "statutory employer" doctrine means the prime contractor cannot escape DBA liability simply by subcontracting the work to an entity that lacks insurance.
In practice, Section 4(a) creates a two-tier safety net. The first tier is the subcontractor's own DBA policy, if one exists. The second tier is the prime contractor's liability as statutory employer if the subcontractor is uninsured. This structure protects workers from falling through coverage gaps in the contractor chain.
The statutory employer doctrine does not make the prime contractor the employer for all purposes. It creates liability for workers' compensation purposes only. The prime contractor's carrier must pay benefits if the subcontractor is uninsured, but the employment relationship for other legal purposes remains between the worker and the subcontractor.
How Do You Determine Which Entity Holds the DBA Policy?
Start at the bottom of the contractor chain and work upward. The most direct path to carrier identification begins with the claimant's immediate employer, the entity that hired, paid, and directed the worker's daily activities.
Check whether the subcontractor has its own DBA policy. Search the DOL's authorized carrier list and case summary data for the subcontractor name. Check OALJ decisions for cases involving the subcontractor. If the sub has a history of DBA claims under its own name, it likely carries its own coverage.
If the subcontractor does not appear to have its own DBA coverage, move to the prime contractor. The prime's DBA policy typically covers its direct employees, but it may also extend to subcontractor employees through the Section 4(a) statutory employer mechanism or through contractual flow-down provisions.
Contract terms matter significantly. Many federal prime contracts require the prime to ensure all subcontractors maintain DBA coverage. Some primes satisfy this by requiring subs to purchase their own policies. Others include subcontractor employees under the prime's policy. Still others purchase a blanket policy that covers all workers on the contract regardless of employer. The specific contract language determines which arrangement applies.
Agency mandatory carrier arrangements add another variable. If the prime contract is funded by USAID, Allied World coverage applies regardless of the subcontractor's own insurance arrangements. The mandatory carrier covers all workers on the contract, from the prime down through every subcontractor tier.
What Happens When the Subcontractor Has No DBA Insurance?
When a subcontractor lacks DBA coverage and one of its employees is injured, the consequences flow upward through the contractor chain. Section 4(a) makes the prime contractor liable as statutory employer. The prime's DBA carrier becomes responsible for the claim.
This scenario is more common than practitioners might expect. Small subcontractors, particularly local national firms operating in conflict zones, sometimes lack DBA coverage due to cost, ignorance of the requirement, or difficulty obtaining policies. Foreign subcontractors may not understand U.S. insurance requirements. The DBA market's limited carrier pool makes it difficult for small firms to obtain coverage at affordable rates.
When the prime's carrier pays a claim for an uninsured subcontractor's employee, the carrier typically seeks reimbursement from the subcontractor. Whether the carrier can recover depends on the contract terms between the prime and sub, including indemnification provisions and insurance requirements. In practice, recovery from a small or foreign subcontractor is often difficult or impossible.
For the injured worker, the absence of subcontractor coverage should not affect benefits. The statutory employer mechanism ensures someone is liable. The practical challenge is identifying who that someone is and which carrier backs them. This is where systematic investigation across multiple data sources proves essential.
How Do Multi-Tier Contractor Chains Complicate Claims?
Large overseas operations frequently involve three or more contractor tiers. A prime contractor holds the government contract. Tier-one subcontractors handle major work packages. Tier-two and tier-three subcontractors provide specialized services or local labor. Each tier may have its own DBA coverage arrangements, or coverage may flow from the prime through contractual provisions.
The complexity multiplies when corporate structures change during the contract period. A subcontractor that was independent when hired may be acquired by another firm. The acquiring firm may have different insurance arrangements. The original subcontract may be novated (formally transferred) or may simply continue under the old entity name while the corporate parent changes.
Joint ventures create additional complications. Two or more companies forming a JV for a specific contract may carry separate DBA policies for their respective employees, or the JV entity itself may carry a single policy. Workers deployed to the JV project may not know which JV partner is their legal employer.
ClaimTrove data captures these relationships across multiple data sources. USAspending records link primes to their subcontractors through sub-award filings. OALJ decisions identify the parties in coverage disputes. Contract vehicle records show the hierarchical relationships between parent contracts and task orders. Searching across all these sources simultaneously reveals contractor chain relationships that single-source searches miss.
What Does the Case Law Say About Subcontractor Coverage Disputes?
BRB decisions have addressed subcontractor coverage disputes extensively. Several recurring themes emerge from the case law.
The "borrowed employee" doctrine applies when a worker technically employed by one entity works under the direction and control of another. If a subcontractor's employee works daily under the prime contractor's supervision, the prime may be considered the "borrowing employer" for DBA purposes. This can shift coverage responsibility to the prime's carrier even when the subcontractor has its own policy.
The "dual employment" concept recognizes that a worker can be simultaneously employed by two entities for DBA purposes. A subcontractor's employee who is also treated as a prime contractor employee under the contract terms may be covered by both policies. In practice, the claim is typically filed against one carrier, with the carriers resolving allocation between themselves.
Contract language receives significant weight in coverage disputes. BRB decisions consistently look at the prime-sub contract to determine the parties' intent regarding DBA coverage. Contracts that explicitly require subcontractor employees to be covered under the prime's policy are treated differently from contracts that require subs to maintain independent coverage.
The "integral relationship" test, drawn from LHWCA case law, examines whether the subcontractor's work was integral to the prime contractor's operations. If so, the prime's statutory employer liability is more easily established, strengthening the argument for prime contractor coverage of the sub's employees.
What Steps Should You Take When a Client Was a Subcontractor Employee?
Document the full employment chain from the client's perspective. Get the name of every company the client interacted with: who hired them, who paid them, who supervised them daily, and who they believed they worked for. These may all be different entities.
Identify the prime contractor. If the client knows which military base or facility they worked at, contract award records can identify the prime contractor for that location and time period. USAspending data, which ClaimTrove indexes, links 43,298 overseas prime contract awards to specific locations and time periods.
Search for both the subcontractor and the prime in DBA records. Check whether the subcontractor has its own carrier history. Check the prime's carrier arrangements for the relevant period. If the prime's contract was funded by an agency with a mandatory carrier, that carrier likely covers all workers on the contract including subcontractor employees.
Review the contract terms if accessible. Federal contracts and subcontracts may be available through FOIA requests or through the client's employment records. The DBA insurance provisions in the contract will indicate whether the sub was required to maintain its own coverage or was covered under the prime's policy.
Consider filing against both the subcontractor's carrier and the prime's carrier if the coverage responsibility is genuinely ambiguous. Administrative law judges can sort out the correct responsible party, but only if both carriers are named. Failing to name the correct carrier initially can create jurisdictional and procedural complications later.
ClaimTrove traces contractor chains automatically, linking subcontractors to prime contractors and identifying carrier arrangements at each level. Search once across all 18 data sources to map the full coverage picture for your subcontractor claim.