A paralegal pulls a contract file for an injured cook who worked a dining facility at a base in Kuwait. The wage determination is right there in the contract documents, complete with fringe rates and a "health and welfare" line item. The attorney assumes that fringe benefit line proves DBA coverage was in place. It does not. The wage determination is a Service Contract Act document. The DBA insurance obligation lives somewhere else entirely, governed by a different statute, enforced by a different agency, and proven by a different record.
This mistake happens constantly. The Defense Base Act and the Service Contract Act both attach to the same category of work: people performing services for the federal government overseas. They appear together in the same solicitations, the same contract clauses, and the same audit findings. Attorneys and paralegals new to DBA work routinely treat the two as one compliance regime. They are not.
One governs wages and benefits. The other governs workers' compensation for injury and death. One is enforced by the DOL Wage and Hour Division. The other runs through the Office of Workers' Compensation Programs and the Office of Administrative Law Judges. The "interplay" between the Defense Base Act and the Service Contract Act on overseas labor matters because the documents that prove one say almost nothing about the other. If you cannot keep them straight, you will misread the file and chase the wrong carrier.
This guide walks through how the two statutes overlap on a single overseas contract, where they split apart, and what each one actually proves when you are trying to identify an insurance carrier from a public record.
What is the Service Contract Act and how does it differ from the Defense Base Act?
The Service Contract Act of 1965 (41 U.S.C. 6701 et seq.) is a labor standards statute. It requires contractors and subcontractors performing services on prime contracts over $2,500 to pay service employees no less than the wage rates and fringe benefits prevailing in the locality, as determined by the Secretary of Labor. The SCA is about money in the worker's pocket: minimum hourly wages, health and welfare fringe payments, paid leave, and holiday pay.
The Defense Base Act (42 U.S.C. 1651) is a workers' compensation statute. It extends the Longshore and Harbor Workers' Compensation Act to civilian employees working on overseas military bases and under government service or construction contracts performed abroad. The DBA is about what happens when someone gets hurt or killed: medical care, disability payments, and death benefits, paid through a mandatory insurance policy the employer must carry.
Here is the core divergence. The SCA polices the paycheck. The DBA polices the consequences of injury. A contractor can be in perfect SCA compliance, paying every penny of the prevailing wage and the full health and welfare fringe, and still have zero compliant DBA coverage. The reverse is also true. The two obligations run on parallel tracks under the same overseas contract, and neither one guarantees the other.
The enforcement structure underscores the split. SCA violations go to the Wage and Hour Division and can result in withheld contract payments and debarment. DBA disputes go through OWCP and, when contested, to administrative law judges and the Benefits Review Board. ClaimTrove holds 5,022 OALJ decisions and a body of DOL case summary records, and those are DBA proceedings. You will not find your SCA wage dispute resolved in that corpus. If you are still building a foundation on the compensation side, our explainer on what the Defense Base Act is and who it covers lays out the coverage triggers in detail.
Where do the DBA and SCA overlap on the same overseas contract?
The overlap is the entire population of overseas service contracts. When the federal government hires a company to run dining facilities, provide base operations support, perform vehicle maintenance, or staff logistics at an overseas installation, both statutes typically attach at once.
The SCA attaches because the work is services performed under a federal prime contract above the threshold. The DBA attaches because the work is performed outside the United States under a government contract, or on a U.S. military base abroad. The same cook, the same mechanic, the same security guard sits inside both regimes simultaneously.
You see this overlap structurally in the contract paperwork. A single solicitation will carry both an SCA wage determination and the FAR clause requiring DBA insurance (FAR 52.228-3). The same NAICS code and place-of-performance country that flag a contract as overseas service work flag it for both statutes. In ClaimTrove's 43,298 prime contract awards, the records that carry a foreign place of performance and a service NAICS code are exactly the records where both obligations live. The "labor standards" flag on a USAspending award signals the contract sits in this dual-obligation zone.
The overlap also shows up in how money flows down a subcontract chain. The prime passes both obligations to its subs. Across 4,315 subcontract awards in our data, a sub running a dining facility owes its workers SCA wages and owes them DBA coverage, even though the sub never signed the prime contract with the government. This is why the hardest carrier questions arise on layered overseas service work, where the actual employer is three tiers down from the named prime.
For construction work specifically, the overlap gets a third layer: the Davis-Bacon Act sits in the SCA's place for construction labor, while the DBA still governs injury. We covered why building abroad creates the worst tracing problems in our piece on overseas construction contracts and DBA insurance requirements.
Why does an SCA wage determination not prove DBA coverage?
This is the practical heart of the problem. The documents that establish SCA compliance are not the documents that establish DBA coverage. They are generated by different processes and they prove different facts.
An SCA wage determination is a Department of Labor document attached to the solicitation. It lists job classifications and the minimum wage plus fringe rate for each, tied to the locality of performance. It tells you what the worker was supposed to be paid. It says nothing about whether the employer purchased a DBA insurance policy, which carrier wrote it, or whether the policy was in force on the date of injury.
A health and welfare fringe payment under the SCA is also not DBA coverage. The fringe is a cash-equivalent benefit the contractor must provide, often satisfied through health insurance or a cash payment. Attorneys sometimes see the fringe and assume injury coverage is baked in. It is not. The DBA requires a separate, specific workers' compensation policy written by a carrier authorized by the DOL. ClaimTrove tracks 637 such authorized carriers, and a contractor's SCA compliance tells you nothing about which of them, if any, covered the work.
The proof of DBA coverage is a different artifact: a filed coverage record, an OALJ decision naming the carrier as a party, an industry performance report mapping the prime to its carrier, or an SME-confirmed mapping. ClaimTrove's 2,454 employer-carrier mappings come from those sources, not from wage determinations. This is the same separation that makes tracing carriers through mergers and joint ventures so difficult: the labor-standards paperwork and the insurance paperwork live in different filing systems and shift on different schedules.
So when a file hands you a clean wage determination, treat it as evidence of SCA status and nothing more. The carrier question stays open.
How does coverage scope differ between the two statutes?
Even where both statutes apply, they do not cover the same set of workers or the same set of circumstances. The boundaries diverge in ways that matter for both a wage claim and an injury claim.
The SCA covers "service employees," a category that excludes bona fide executive, administrative, and professional employees. A program manager or a contract specialist may fall outside SCA protection while a cook, a guard, or a mechanic falls squarely inside it. The DBA draws its line differently. It reaches employees regardless of white-collar or blue-collar status, as long as the employment connection to the overseas government contract is satisfied. A salaried logistics coordinator excluded from the SCA can still be fully covered by the DBA.
Geographic and situational scope also diverge. The DBA famously reaches injuries that occur during off-duty recreation in the "zone of special danger" surrounding overseas deployment, a doctrine with no SCA analog. The SCA does not care where or how an injury happened; it only cares about hours worked and wages paid. We explored the off-duty coverage question in our analysis of recreational injuries and DBA coverage, and that body of case law has no equivalent on the wage-and-hour side.
Then there are waivers. The DOL can waive DBA coverage for a country or a class of employees, usually local nationals, leaving those workers to a host-country compensation scheme instead. The SCA has its own exemptions, but a DBA country waiver does not waive SCA obligations and vice versa. We broke down the waiver mechanism in our guide to DOL country and class waivers. The takeaway: a worker can be inside one regime and outside the other on the very same contract.
What does each statute mean for remedy and litigation strategy?
The remedy structures are not just different; they point in opposite directions, and that shapes how you build a case.
The DBA, through its incorporation of the Longshore Act, is an exclusive-remedy compensation system. An injured worker generally cannot sue the employer in tort; the trade-off for guaranteed no-fault benefits is the loss of the negligence lawsuit. That exclusivity is the central feature of the compensation regime, and it has important exceptions and pressure points. We unpacked them in our explainer on suing your employer under the DBA.
The SCA carries no individual private right of action at all in the same sense. A service employee who was underpaid does not file an SCA lawsuit the way a DBA claimant files for benefits. Enforcement runs through the Wage and Hour Division, which can recover back wages and bar the contractor from future awards. The worker's leverage is administrative, not a personal injury claim.
For litigation strategy, this means the two statutes generate different evidence and different opposing parties. A DBA claim puts you across from an insurance carrier and its third-party administrator, and your first job is identifying which carrier actually held the risk on the injury date. An SCA matter puts you in front of a federal contracting officer and the Wage and Hour Division. The records overlap at the contract level and split everywhere else.
Practically, the SCA contract documents are still useful in a DBA case, just not for the reason people assume. The wage determination, the job classification, and the place of performance help confirm the worker's role and the overseas nexus that triggers DBA jurisdiction. They corroborate coverage applicability. They do not name the carrier.
How do you actually identify the carrier when both statutes apply?
Once you accept that SCA documents will not hand you the carrier, the carrier question becomes its own investigation. On a dual-obligation overseas contract, the answer is buried across many federal data sources that do not talk to each other.
You start with the employer, which on layered service work is rarely the entity named on the prime contract. The actual employer may be a subcontractor, a subsidiary, or a joint-venture vehicle operating under a name that never appears in the headline award. Resolving that name is step one, and it is harder than it looks because the same company files under many spellings and corporate shells.
From there, the carrier signal comes from sources like filed coverage records, OALJ decisions that name carriers as parties, DOL industry performance reports, and mandatory agency assignments where the awarding agency dictated the carrier. Each source has a different confidence level and a different time window. Carriers shift over the life of a contract, so the policy in force when the contract was signed may not be the policy in force on the injury date.
This is precisely the work ClaimTrove was built to compress. Instead of manually cross-referencing wage determinations, USAspending awards, subcontract chains, coverage records, and 5,022 legal decisions, you run one investigation and get the ranked carrier candidates, the contract chain, and the source citations behind each. The platform handles the alias resolution, the prime-to-sub tracing, and the temporal ranking that the raw documents will never do on their own. Run a search on your employer and injury date, and pull the underlying carrier, contract, and decision data in one pass rather than weeks of FOIA and PACER work.
The Service Contract Act will tell you what your client should have been paid. It will not tell you who pays when your client gets hurt. For that, you have to identify the carrier, and that is a separate problem with a separate solution.