A subcontractor's welder falls from scaffolding at a forward operating base in Iraq. The claim gets filed. Then the fight starts. The subcontractor points up the chain and says the prime carried the insurance. The prime points down and says the sub was required to secure its own Defense Base Act coverage. Neither party wants to be the insured of record. Your client waits while two federal contractors argue about privity.
This is one of the most common and least understood problems in DBA practice. The Defense Base Act, 42 U.S.C. § 1651, requires overseas government contractors to secure workers' compensation coverage. But the Act does not care about corporate org charts. It cares about who employed the worker and who was obligated to insure that employment.
Privity is the hinge. A prime contracts with the government. A subcontractor contracts with the prime. The insurance obligation travels down that contractual chain, not sideways. When a sub's employee is hurt, the question of who was supposed to carry the policy turns on where that worker sat in the contract structure.
ClaimTrove's data holds 43,298 overseas prime contract awards and 4,315 sub-award records across 193 countries. Those records expose the contract vehicles that govern insured status. This article explains how privity decides who owed DBA coverage, why primes and subs fight over it, and what records actually settle the dispute.
What Does Privity Have to Do With DBA Insured Status?
Privity means a direct contractual relationship between two parties. In federal contracting, that relationship forms a chain. The government awards a prime contract to the prime. The prime awards a subcontract to the sub. The sub may award a lower-tier subcontract below that.
The government has privity with the prime. The prime has privity with the sub. The government has no privity with the sub. That gap matters for insured status. The Defense Base Act borrows its machinery from the Longshore and Harbor Workers' Compensation Act, 33 U.S.C. § 901 and following.
Under that machinery, every employer must secure compensation for its own employees. A subcontractor is an employer. Its DBA coverage obligation runs to its own workforce, not the prime's. So when a sub's employee is injured, the sub is the first party expected to have a policy in force.
The confusion starts because a prime and a sub often share a job site. Workers wear similar badges. They answer to overlapping supervisors. A claimant frequently does not know which entity signed his paycheck. The insured of record is a legal question, not a question of who ran the site.
This is why the contract structure controls. Privity tells you which employer was obligated to insure which worker. It also tells you which carrier's policy should respond first. Get the privity wrong and you chase the wrong carrier for months.
How Does a Subcontractor Become Obligated to Carry DBA Insurance?
A subcontractor's DBA obligation does not come from the government directly. It comes from a clause that flows down through the contract chain. The governing clause is FAR 52.228-3, Workers' Compensation Insurance (Defense Base Act).
FAR 28.309 prescribes that clause for covered overseas contracts. The clause requires the contractor to provide DBA insurance for its employees. It also requires the contractor to insert the substance of the clause in every subcontract to which the Act applies. That flow-down language is the mechanism that binds each tier down the chain. For the full text and how it operates, see our breakdown of the FAR 52.228-3 Defense Base Act insurance clause.
When the prime inserts the clause into the subcontract, the sub inherits the duty. The sub must then secure its own DBA policy. The obligation is contractual at the sub level and statutory under the Act. Both sources point to the sub as the insured for its own workers.
Coverage gaps open when the clause is not passed down cleanly. A prime may forget it. A sub may ignore it. We cover that failure mode in detail in how flow-down clauses create coverage gaps at every tier.
A missing flow-down clause does not erase the sub's statutory duty to secure coverage. But it changes the evidence. It also changes who a claimant attorney should pressure first. The paper trail behind the flow-down is where insured status is proven or lost.
Who Pays When a Subcontractor Fails to Secure DBA Coverage?
Sometimes the sub never bought a policy. Sometimes the policy lapsed. The Act anticipates this. Section 4(a) of the LHWCA, 33 U.S.C. § 904(a), places backup liability on the contractor above an uninsured subcontractor.
The rule is direct. If a subcontractor fails to secure payment of compensation, the contractor becomes liable and must secure that payment. This is statutory up-the-chain liability. It exists precisely so an injured worker is not left with no insured employer.
That does not mean the prime volunteers. Primes contest whether the entity below them was truly a subcontractor. They contest whether that sub was actually uninsured at the injury date. They contest whether the worker was even the sub's employee. Each contest is a privity argument in disguise.
Section 5(a), 33 U.S.C. § 905(a), adds another layer. Compensation is normally the exclusive remedy against an employer. But when an employer fails to secure DBA coverage, the injured worker may elect to sue that employer at law. That threat reshapes the negotiation.
When no insured employer exists anywhere in the chain, the analysis shifts to the DOL Special Fund. We walk through that scenario in what happens when a DBA employer was uninsured.
For a claimant attorney, the sequence is clear. Identify the sub's carrier first. If the sub was uninsured, move up to the prime under Section 4(a). If the whole chain fails, look to the Special Fund. Privity determines every step of that ladder.
Why Do Prime and Sub Fight Over Who Was the Real Employer?
The most contested privity disputes are not really about contracts. They are about employment. Two contractors can both plausibly claim or disclaim the same worker. The carrier that insures the losing party pays.
Overseas staffing blurs the line. A sub loans workers to a prime. A prime directs a sub's crew day to day. A worker rotates across task orders under different entities. Federal labor arrangements rarely match the clean boxes on an org chart.
Courts resolve these fights with doctrines like the borrowed servant rule. That doctrine can shift the employment relationship from the sub to the prime for a given task. We explain how it assigns liability in which carrier pays when a worker serves two employers.
The stakes are financial. If the worker is the sub's employee, the sub's carrier responds. If the worker was borrowed by the prime, the prime's carrier may respond instead. The same injury produces two different carrier answers depending on the finding.
This is why tracing a sub's coverage is so much harder than tracing a prime's. The sub sits lower in the records and files under names that shift. We break down that difficulty in why tracing subcontractor insurance is so hard.
Contract vehicles are the tiebreaker. The subcontract, the task order, and the flow-down clause show who employed whom. They show which entity carried the insurance obligation on the injury date. Without those documents, the privity fight is just competing assertions.
How Does the Contract Vehicle Determine Which Party Insured the Worker?
A contract vehicle is the specific instrument that governs a piece of work. It might be a prime contract, a task order under an IDIQ, or a subcontract. Each vehicle carries its own insurance terms and its own dates.
Insured status attaches to the vehicle, not to the company name. The same contractor can be the insured on one task order and a subcontractor on another. Its carrier can differ across those vehicles. The injury date decides which vehicle controls.
Federal award data exposes these vehicles. ClaimTrove holds 43,298 overseas prime awards and 4,315 sub-award records. Those awards name 739 distinct prime contractors and 918 distinct sub-awardees across 193 countries. Each record ties an employer to a specific contract structure.
Sub-award records are the key. They link a prime to the subs working beneath it on a given vehicle. That link is the documentary proof of privity. It shows who sat above and below the injured worker's employer at the time of the injury.
The vehicle also anchors the timeline. Contract periods, task order dates, and re-competition events all shift who held the insurance duty. A worker hurt in one contract period may fall under a different insured than the same worker a year later.
This is where a name-only search fails. Searching an employer name returns a pile of records with no structure. You need the vehicle that governed the specific injury, tied to the specific date, at the specific location. That is the difference between a guess and an answer.
What Records Actually Resolve a Prime-Versus-Sub Privity Dispute?
No single document settles a privity dispute. The answer is assembled from layered federal records. Each source confirms one piece of the chain.
Prime award records show what the government bought and from whom. Sub-award records show who worked beneath the prime. Federal registration records confirm the legal identity behind each contractor name. FOIA database results add insurance filing evidence tied to specific employers and dates.
The work is correlation. You match the employer name to its aliases. You match the alias to the contract vehicle. You match the vehicle to the injury date and location. Then you match that structure to a carrier. Miss one link and the answer collapses.
Manual assembly is slow and error prone. Contractor names change. Subsidiaries file under different entities. A single prime can appear under a dozen variations. A sub can be buried three tiers down a task order most attorneys never see.
ClaimTrove automates that correlation. Enter an employer or a contract vehicle. The engine resolves aliases, traces the prime and sub relationships, and surfaces the carrier evidence tied to that structure and date. Run a privity-aware carrier investigation and see the full contract chain in one report.
The privity question is not academic. It decides which carrier your client pursues and which one pays. The contract vehicle holds the answer, and the records that prove it are public. Stop guessing which contractor owed the coverage. Trace the employer and carrier tied to any contract vehicle and turn a privity standoff into a documented answer.