A new file lands on your desk. A logistics worker fractured his leg loading pallets at an airbase in Kuwait. The intake sheet lists his employer as a staffing company that flowed down from a prime under a federal service contract. His prior attorney scribbled three acronyms in the margin: DBA, FECA, and SCA. All three touch overseas federal work. Only one of them will actually pay this man's medical bills and wage loss.
This scenario plays out constantly in DBA practice. The worker knows he was hurt on a U.S. government job overseas. He does not know which federal statute governs his claim. Neither does the referring attorney half the time.
Picking wrong is not harmless. File the injury under a statute that does not apply, and you burn weeks waiting for a denial. Meanwhile the clock on the correct statute keeps running. The three laws look similar from a distance because they all orbit federal contracting. Up close, they answer completely different questions.
The Defense Base Act (DBA) and the Federal Employees' Compensation Act (FECA) are both workers' compensation statutes. The Service Contract Act (SCA) is not a workers' compensation statute at all. Sorting these three apart comes down to one thing: who signed the worker's paycheck and under what kind of contract. This guide walks the distinctions and gives you a decision tree you can run at intake.
What Is the Core Difference Between DBA, FECA, and SCA?
Start with the paycheck. That single fact resolves most of the confusion.
The DBA covers employees of government contractors and subcontractors. If a private company hired the worker to perform on an overseas military base or public works contract, you are almost certainly in DBA territory. The employer is a business, not the government itself.
FECA covers direct federal civilian employees. If the worker's W-2 came from a federal agency, if he was a GS-scale civil servant or a wage-grade federal employee, FECA governs. The government is the employer, not a contractor.
The SCA is different in kind. It is a labor standards statute, not an injury statute. It sets prevailing wages and fringe benefits for service workers on federal contracts. It does not pay for a broken leg. It never has.
So the question is not really "which of these three benefit systems pays." Two of them are benefit systems and one is a wage law. The real question at intake is whether your client was a contractor's employee, a federal employee, or someone whose contract merely happened to fall under SCA wage rules.
Get the employment relationship right and the statute follows. The rest of this guide unpacks each one so you can defend that call.
One caution before you start. Clients rarely describe their own status accurately. A worker who says he "worked for the base" may have been employed by a fourth-tier subcontractor whose name never came up. Another who insists he was "government" may have been a contractor the whole time. Treat the client's label as a lead, not a conclusion. Pull the W-2, the badge, and the contract before you commit to a forum.
When Does the DBA Cover Your Overseas Worker?
The Defense Base Act lives at 42 U.S.C. § 1651. It extends the benefit framework of the Longshore and Harbor Workers' Compensation Act (LHWCA), found at 33 U.S.C. § 901 and following, to civilian contractor employees working outside the United States.
Coverage generally reaches several categories of overseas contract work. These include employment on U.S. military bases abroad, public works contracts performed outside the country, and work under contracts funded through certain foreign assistance programs. If your client was a contractor employee on that kind of job, the DBA is the likely answer.
The DBA is administered through the Department of Labor's Office of Workers' Compensation Programs, specifically the Division of Longshore and Harbor Workers' Compensation (DLHWC). Because the DBA borrows the LHWCA machinery, the claim procedures, the compensation formulas, and the appeals path all track longshore practice.
Benefits under the DBA generally run to two-thirds of the worker's average weekly wage for disability, subject to the LHWCA maximum, which is tied to the National Average Weekly Wage. That cap matters. A high earner injured overseas may find his compensation limited by a ceiling that has nothing to do with his actual salary. When you are running the numbers, the mechanics of how average weekly wage is calculated for overseas contractors often decide whether a case is worth six figures or far less.
The DBA is also an exclusive remedy against the employer. When it applies, the injured worker generally cannot sue the employer in tort and cannot claim state workers' compensation for the same injury. The trade-off is the classic workers' comp bargain: no-fault benefits in exchange for giving up the lawsuit. That bar has limits, though. Before advising a client that litigation is fully foreclosed, review how courts treat the DBA exclusive remedy and its narrow exceptions.
Coverage under the DBA can also reach up and down the contract chain. A prime contractor's employee and a lower-tier subcontractor's employee can both be covered, even when only the prime appears on the public contract record. When a subcontractor fails to carry the required insurance, the prime can become statutorily liable for the sub's DBA obligations. That liability chain is a feature of the statute, not an accident, and it can matter when the direct employer has vanished or gone bankrupt.
One more DBA reality: the benefits come from a private insurance carrier, not the government. The contractor buys a DBA policy, and that carrier pays the claim. Identifying the correct carrier for a given employer, base, and injury date is its own investigation, and it is often the hardest part of the file.
ClaimTrove was built for exactly that step. Run the employer or the location through the investigation engine and it traces the contract chain to the DBA carrier that was on risk when your client was hurt. That is the difference between filing your LS-203 against the right insurer and chasing a policy that lapsed two rebids ago.
When Does FECA Apply Instead of the DBA?
FECA sits at 5 U.S.C. § 8101 and following. It covers civilian employees of the federal government who are injured in the performance of duty. The key word is employees. Not contractors. Not subcontractors. Direct hires of a federal agency.
This is where practitioners stumble. A worker can be standing on the same overseas base as a DBA-covered contractor and still fall under FECA. The reason is that he is a federal civil servant rather than a contractor's employee. The location does not decide the statute. The employment relationship does.
FECA is administered by a different arm of OWCP: the Division of Federal Employees' Compensation (DFEC). So both DBA and FECA claims flow through OWCP, but through separate divisions, with separate procedures and separate adjudicators. Sending a FECA-type injury to the longshore division wastes time it cannot fix.
The benefit math also differs, and often in the worker's favor. FECA generally pays 66.67 percent of salary for a disabled employee with no dependents and 75 percent for an employee with at least one dependent. Critically, FECA is not subject to the LHWCA National Average Weekly Wage cap. It has its own maximum, but a federal employee's compensation is not squeezed by the longshore ceiling that constrains DBA awards.
Can a worker be covered by both? No. The DBA and FECA are mutually exclusive based on the employment relationship. A person is either a contractor's employee or a direct federal employee for a given job. He does not get to pick the more generous statute. The facts of who employed him control, and part of your intake job is nailing that fact down with pay records, not the client's memory.
When the employment relationship is genuinely murky, treat it as a factual dispute to be developed, not a coin flip. The same care that goes into resolving overseas injury location and jurisdiction disputes applies here: build the record before you commit the client to a forum.
Why the SCA Is Not a Workers' Compensation Statute
The McNamara-O'Hara Service Contract Act lives at 41 U.S.C. § 6701 and following. It is a prevailing wage law. It requires contractors and subcontractors on covered federal service contracts to pay their service employees at least the locally prevailing wages and fringe benefits. That is its entire job.
The SCA does not compensate injuries. It does not pay medical bills. It does not replace lost wages after a workplace accident. If you file an injury "under the SCA," there is nothing there to file. The statute has no claim mechanism for a broken leg.
The SCA is enforced by the Department of Labor's Wage and Hour Division, not by OWCP. That alone tells you it lives in a different world from DBA and FECA. Wage and Hour polices paychecks. OWCP adjudicates injury claims. Different agency, different purpose.
So why does the SCA keep showing up in DBA files? Because the two statutes ride the same overseas service contracts. A service contract performed abroad is often covered by the SCA for wage and fringe purposes, and the same contract will frequently require the contractor to carry DBA insurance under the Defense Base Act and its implementing contract clause. The two obligations travel together, which is why the acronyms land in the same file. One caution for the file: DBA premiums do not count toward the contractor's SCA health and welfare fringe obligation. Under the SCA rules, a benefit the contractor is required to furnish by another federal law, which includes DBA workers' compensation coverage, is not a creditable bona fide fringe benefit. The SCA sets the wage floor; the DBA policy is what actually responds when an injury occurs.
This overlap is worth understanding in detail, because SCA obligations can help you prove that DBA coverage should have been in place even when the contractor claims otherwise. The relationship is spelled out further in this breakdown of how the Defense Base Act and Service Contract Act overlap on the same overseas contract. For claim purposes, though, keep the lanes clean: the SCA sets wages, the DBA pays for injuries.
How Do You Decide Which Statute Applies? (Decision Tree)
At intake, you can resolve most files in under a minute by walking three questions in order. Run them top to bottom and stop at the first match.
| Question | If yes | Governing law |
|---|---|---|
| Was the worker a direct civilian employee of a federal agency (a federal paycheck, GS or wage-grade)? | FECA applies. Route to OWCP's DFEC division. | FECA (5 U.S.C. § 8101) |
| Was the worker an employee of a government contractor or subcontractor performing overseas on a military base, public works, or covered assistance contract? | DBA applies. Identify the carrier and file with OWCP's DLHWC division. | DBA (42 U.S.C. § 1651) |
| Is the only federal statute in play a wage or fringe-benefit requirement on the service contract? | The SCA governs pay, not injuries. Look to the DBA policy the SCA required for the actual injury claim. | SCA (41 U.S.C. § 6701) plus DBA for the injury |
Read the tree as a filter. The first question separates federal employees from everyone else. The second question captures the overseas contractor workforce, which is the bulk of DBA practice. The third question reframes any "SCA injury" as what it really is: a DBA claim on a contract that SCA rules helped create.
The tree resolves the common files fast. It does not eliminate every hard case. Local nationals and third-country nationals raise coverage questions the tree glosses over. So do injuries that straddle a base perimeter or a contract transition. When the facts sit on a line, do not force them. Develop the record, document the employment relationship, and let the evidence pick the statute. The goal is a defensible call, not a fast one.
A few traps deserve a flag. A prime contractor's employee and a fourth-tier subcontractor's employee can both be DBA-covered, even though the paperwork trail looks nothing alike. The location of the base, whether CONUS or OCONUS, changes the analysis, and the line is not always where attorneys assume it is. It is worth confirming how DBA coverage differs on CONUS versus OCONUS military bases before you rule the statute in or out on geography alone.
The decision tree tells you which statute. It does not tell you which insurance carrier stands behind a DBA claim. That answer requires tracing the employer through aliases, subcontract chains, and coverage records to the carrier that was actually on the policy at the time of injury. Employers change names, get acquired, and rebid contracts, so the carrier that was on risk in 2011 may be nowhere on the current paperwork. Statute is the first question. Carrier is the harder one, and it is where most DBA files stall.
What Happens If You File Under the Wrong Statute?
The cost of guessing wrong is measured in months, not minutes.
File a contractor's injury with the FECA division and it does not get quietly redirected. It gets developed under the wrong rules, questioned, and eventually rejected for lack of jurisdiction. Every day of that detour is a day your client goes without benefits.
The deeper danger is the deadline. Each statute carries its own notice and filing timelines. Time spent chasing the wrong forum does not pause the clock on the correct one. A DBA claim carries a limitations period under the incorporated LHWCA provisions. Blowing it because you spent three months in the FECA queue is a malpractice-grade error. Those deadlines have contours, and some exceptions can save a late filing. This discussion of the DBA statute of limitations and its occupational disease exceptions lays them out.
There is also a credibility cost. When you file against the wrong party or the wrong carrier, opposing counsel and the adjudicator both notice. It signals that the file was not investigated. In a system where the Section 20(a) presumption and careful development can carry a close case, giving the other side a free shot at your competence is a bad trade.
The fix is not complicated. Confirm the employment relationship first. Confirm the contract type second. Then, for any DBA claim, identify the carrier before you file rather than hoping a name on an old form is still good. Statute, employer, carrier: get those three right at intake and the rest of the claim runs on solid ground.
ClaimTrove closes the loop on the hardest of those three. Once your decision tree lands you in the DBA, sign up and run the employer or the base through the investigation engine. It returns the carrier, the contract chain, and the source records behind the answer, so your first filing is your correct filing.