You pull the prime contract for an injured logistics worker who was hurt at a forward operating base in Kandahar. The PIID checks out. The place of performance is foreign. The contractor is a name you recognize. Then you scan the clause list and find it: FAR 52.228-3, "Workers' Compensation Insurance (Defense Base Act)." That one incorporated clause is the contractual hook that obligated the prime to carry DBA coverage. But the contract does not name the carrier. It never does.
This is the gap most attorneys hit on day one of a DBA matter. The clause tells you coverage was required. It does not tell you who wrote the policy, whether the prime actually bought it, or whether the obligation flowed down to the sub who actually employed your client. Those answers live in DOL filings, FOIA releases, and litigated decisions, not in the four corners of the award.
FAR 52.228-3 is short. It is also one of the most consequential clauses in federal contracting for anyone working a comp claim overseas. It converts the Defense Base Act from a statute that "might apply" into a contractual command that the contractor "shall" insure. Understanding exactly what it requires, how it cascades down the subcontract chain, and what its absence does and does not mean separates a fast carrier identification from weeks of dead ends.
This article explains the clause itself. It will not tell you whether any specific contract actually carried compliant coverage. That requires tracing the award against insurance evidence, and that is exactly what ClaimTrove was built to do.
What does FAR 52.228-3 actually require?
FAR 52.228-3 is the Federal Acquisition Regulation clause that implements the Defense Base Act inside a government contract. The operative language is blunt. The contractor "shall, before commencing performance under this contract, comply with the provisions of the Defense Base Act" and "provide insurance for liability" under that Act. It then requires the contractor to maintain that coverage for the life of the contract.
The clause does three concrete things. First, it imposes an affirmative duty to obtain DBA insurance before any work begins. Second, it requires the contractor to keep that coverage active. Third, it forces the flow-down obligation: the prime must insert a clause requiring every subcontractor to do the same. That third function is where most coverage disputes originate.
What the clause does not do is name a carrier, set a policy number, or guarantee compliance. It is a command, not a record. A contracting officer incorporates the clause by reference, and the burden shifts entirely to the contractor to act on it. Whether the contractor did is a question of evidence, not contract language.
The clause pairs with FAR 28.305, the procurement policy section on overseas workers' compensation, while FAR 28.309 is the prescription that tells contracting officers when to insert it. As a rule, 52.228-3 belongs in any contract performed outside the United States, including supply, service, and construction contracts. There are carve-outs, which matter enormously and are covered below. But the default for overseas federal work is that the clause is present and DBA applies.
In ClaimTrove's contract data, the practical proxy for this clause is the labor standards flag carried on USAspending award records. A "Y" value signals that labor standards including DBA likely attach to the award. Across 43,298 overseas prime awards in the database, that flag is a starting filter, not a final answer. The clause being required and the policy being purchased are two different facts, and only one of them lives in the contract.
How does FAR 52.228-3 flow down to subcontractors?
The flow-down is the part that creates real-world coverage gaps. FAR 52.228-3 requires the prime to insert a Defense Base Act insurance requirement into every subcontract under which DBA work is performed. In theory this means coverage cascades cleanly from prime to sub to lower-tier sub. In practice, the chain breaks at predictable points.
The most common failure is incomplete insertion. A prime carries its own DBA policy, satisfies the clause on paper, and then either fails to insert the flow-down language into a sub agreement or inserts it without verifying the sub actually bought a policy. The injured worker is employed by the sub. The sub has no coverage. The clause was technically satisfied at the prime level and technically violated at the sub level.
This is why subcontract chain mapping matters so much. ClaimTrove holds 4,315 sub-award records linking primes to subs across 918 distinct sub-awardees. A claimant who says they worked for "ABC Logistics" may have been a sub three tiers below a recognizable prime, and the carrier obligation at their tier may bear no relationship to the prime's named carrier. We cover this mechanism in depth in our analysis of how flow-down clauses create coverage gaps at every tier.
The statutory backstop is what makes the flow-down survivable for claimants. Under 33 U.S.C. §§ 904 and 932, applied to DBA through 42 U.S.C. § 1651, a prime contractor is statutorily liable for benefits if its uninsured subcontractor fails to secure coverage. The clause creates the contractual duty; the Longshore Act provisions create the fallback liability. If the sub's policy does not exist, the claim does not vanish. It climbs the chain.
That climb is rarely automatic. It requires proving who the prime was, that the sub was in fact uninsured, and that the work fell within the contract. The flow-down obligation in 52.228-3 is the thread you pull to establish the first link. Whether a specific sub actually carried compliant coverage at the date of injury is a question ClaimTrove answers by tracing the award against insurance filings, not something you can read off the clause.
When is the clause absent, and what does that mean?
A missing FAR 52.228-3 is not proof that DBA does not apply. This is the single most expensive assumption an attorney can make. The clause governs what the contract requires. The Defense Base Act itself governs what the law requires, and the two do not always match.
Several legitimate reasons explain an absent clause. A contracting officer may have failed to insert it through administrative error. The contract may predate a modification that should have added it. The work may have shifted overseas after award under a task order that controls the coverage terms. Or the contract may genuinely fall outside DBA's scope.
The Christian doctrine matters here. Under federal contract law, a mandatory clause required by regulation can be read into a contract as a matter of law even when the contracting officer omitted it. If DBA coverage was required by FAR 28.305 and the officer left 52.228-3 out, courts and the Department of Labor can treat the obligation as present anyway. The absence of the printed clause does not extinguish a statutory duty that should have been there.
Task-order vehicles complicate this further. On indefinite-delivery contracts, the base contract and the individual task order can carry different clause sets, and the order that sends a worker overseas may be the document that triggers DBA. We unpack which document controls in our piece on how task orders control the carrier on IDIQ contracts. Reading only the base award and concluding "no clause, no coverage" misses the order that actually mattered.
There are also real exclusions. Contracts performed under a foreign government's authority, certain NATO-funded work, and host-nation agreements can change or defeat DBA applicability. A bilateral security agreement can shift jurisdiction over an injured contractor entirely, which we examine in our analysis of how security agreements affect DBA jurisdiction. The lesson is consistent: clause presence is evidence, not the verdict.
How do agencies turn the clause into a mandatory carrier?
FAR 52.228-3 requires DBA insurance. It is silent on which carrier provides it. Some federal agencies close that silence with their own mandate, requiring every contractor under their authority to use one designated carrier through a single-source program. When that happens, the clause and the mandate stack: the contract requires coverage, and the agency requires it from a named insurer.
These programs are the most powerful carrier-identification signal in DBA work because they are deterministic. If you can establish that a worker's employer performed under a covered agency contract during the program's active window, the carrier follows by rule rather than by inference. ClaimTrove treats these agency mandates as the highest-confidence source in its carrier discovery waterfall, ranked above litigated decisions and contract chains.
The critical wrinkle is that every mandate is time-bounded. A program that designated one carrier for a span of years ends, and the market reopens to whatever carrier each contractor chooses. A worker injured one year may have a deterministic answer; a worker injured at the same base three years later may have an open-market answer that requires full investigation. Getting the date window wrong produces a confidently wrong carrier.
Protective-services and embassy-security contracts are a notorious example of how messy this gets even with mandates in play, because the contract vehicles change hands and the carrier history fragments. Our deep dive on the State Department WPPS contract and why carrier tracing is so difficult shows how a single mandate period sits inside a much longer and murkier coverage timeline.
We will not publish which agency mandated which carrier for which years. That mapping is exactly the proprietary, date-sensitive answer ClaimTrove exists to deliver. Knowing a mandate existed is education. Knowing which carrier it named on the date your client was hurt is the deliverable, and getting it wrong by a single program boundary is a malpractice-grade error.
Why doesn't the clause name the carrier?
Attorneys new to DBA expect the contract to name the insurer the way an auto policy names a company. It never does, and the reason is structural. FAR 52.228-3 is a performance obligation imposed on the contractor. The contractor satisfies it by going to the commercial insurance market and buying a policy. The government contract and the insurance policy are two separate documents with two separate parties.
This separation is why carrier identification is a research problem rather than a lookup. The contract tells you a policy was required. The policy itself, the document that names the carrier and the policy number, is held by the contractor and the insurer, not filed with the contract. You reconstruct the connection from secondary evidence.
That evidence comes from several streams. Litigated DBA decisions name the carrier in their party headers. DOL coverage filings record which carrier insured which employer on which dates. Industry performance reports map prime contractors to carriers by fiscal year. Each stream is incomplete on its own, and they frequently disagree, especially when a third-party administrator like ESIS or Gallagher Bassett appears in the file and gets mistaken for the underwriting carrier. Untangling the TPA from the actual carrier is its own discipline, and one our explanation of the exclusive-remedy framework touches on when it discusses who actually pays a claim.
Temporal drift makes it harder. ClaimTrove's data shows that carriers shift over time for most contractors; a company insured by one carrier in 2010 may sit with a different one by 2015. A clause that says "shall provide insurance" tells you nothing about which year's carrier matters. Only the date of injury, matched against dated coverage evidence, resolves it.
This is the core reason the clause is a starting point and not an answer. FAR 52.228-3 proves a duty existed. It cannot prove the duty was met, by whom, or with which policy. Closing that gap means tracing the prime, mapping the subcontract chain, applying any agency mandate for the relevant window, and reconciling the carrier evidence against the injury date. That is the investigation ClaimTrove runs in seconds across 18 federal data sources, and it is the work the clause leaves entirely undone.
Trace the clause to the carrier with ClaimTrove
FAR 52.228-3 is the contractual instruction. The carrier is the answer. ClaimTrove bridges the two by running a contract PIID or an employer name through 43,298 prime awards, 4,315 sub-awards, litigated decisions, DOL coverage filings, and agency-mandate logic to surface the responsible DBA carrier and the prime-sub liability chain behind it. Start an investigation and turn a clause reference into a named carrier with a defensible citation trail.