Borrowed Servant Doctrine in DBA Claims: Which Carrier Pays When a Worker Serves Two Employers?

A logistics worker is hurt loading cargo at a forward operating base in Kuwait. His paycheck comes from a staffing firm in Dubai. But every order he followed that day came from a prime contractor's site supervisor. When the DBA claim lands, two carriers point at each other. The staffing firm's carrier says the prime controlled the work. The prime's carrier says the man was never its employee. Both are partly right, and that is exactly the problem.

This is the borrowed-servant scenario, and it sits at the center of some of the hardest carrier-allocation fights in the Defense Base Act system. The doctrine asks a deceptively simple question: when a worker serves two masters, which employer's DBA carrier actually pays the claim? The answer is rarely obvious from the paystub alone.

Overseas contracting multiplies the confusion. Staffing chains run three and four tiers deep. A single worker can be nominally employed by one entity, directed by another, and insured by a carrier neither party expected. When liability turns on who controlled the work rather than who signed the check, the carrier you need to name is the one buried in the operational relationship, not the payroll record.

If you handle a dual-employer DBA claim and you cannot answer the borrowed servant doctrine dual employer which carrier liable question early, you risk filing against the wrong responsible carrier and burning months on a coverage fight that never reaches the merits. This article explains how the doctrine allocates liability, why the carrier answer hides inside the contracting structure, and how to map the relationship before you file.

What Is the Borrowed-Servant Doctrine in DBA Claims?

The borrowed-servant doctrine treats a worker as the employee of whichever entity actually controls the work, even if a different company issues the paycheck. The general employer lends the worker. The special employer borrows and directs him. Under longshore law, which the DBA incorporates, the special employer can become liable for compensation because it stepped into the role of employer in fact.

Courts have applied this principle in maritime and longshore settings for over a century. The Supreme Court's reasoning in Standard Oil Co. v. Anderson framed the test: who has the power to control and direct the servants in the performance of their work, not the source of wages, defines the employment relationship. The DBA, by adopting the Longshore and Harbor Workers' Compensation Act, pulls that test directly into overseas contractor claims.

For a DBA claim, the doctrine matters because each employer carries its own DBA insurance. The general employer has a carrier. The special employer has a carrier. If the special employer borrowed the servant, its carrier may shoulder the compensation obligation, even though that carrier never appears on the worker's W-2 or foreign-equivalent pay record.

Three factors drive most borrowed-servant findings:

• Control over the work. Who directed the daily tasks, set the schedule, and supervised performance on site?
• Consent of the worker. Did the worker understand he was now serving the special employer, even informally?
• Whose work was being done. Did the task advance the special employer's contract obligations or the general employer's?

None of these factors live in a public database as a clean field. They live in deposition testimony, site logs, and contract scopes. But the carrier identity that flows from the finding does leave a trail, and that trail is what you can trace before discovery even opens.

How Does the Doctrine Differ From Concurrent and Dual Employment?

Attorneys often blur three distinct concepts. The borrowed-servant doctrine, dual employment, and concurrent employment each allocate liability differently, and naming the wrong one steers you toward the wrong carrier.

Borrowed servant is sequential control. One employer lends the worker to another for a specific task or period. Liability tends to shift to the special employer who directed the work at the moment of injury.

Dual employment, sometimes called joint employment, means two employers share simultaneous control. Both may be liable. Under longshore principles, a borrowing employer and a lending employer can both be responsible, and the carriers may end up sharing the obligation rather than one escaping entirely.

Concurrent employment is different again. The worker holds two separate jobs and the question becomes how to calculate average weekly wage across both, not which carrier pays. We cover that wage-stacking problem in our breakdown of concurrent employment and multiple overseas employers, and it is worth keeping the distinction crisp because the analysis diverges immediately.

The reason this matters for carrier identification is simple. Each doctrine points at a different set of responsible parties, and therefore a different set of carriers to chase. A borrowed-servant finding can move the entire obligation to a carrier the claimant never knew existed. A dual-employment finding can pull two carriers into the same claim. Get the doctrine wrong and your carrier search aims at the wrong target from day one.

This is also where the prime-versus-sub structure collides with the doctrine. A subcontractor's worker directed by the prime's site managers can look like a borrowed servant of the prime. We unpack that tracing challenge in detail in our guide to subcontractor DBA coverage and responsibility for an injured sub employee, because the contracting tier and the control finding frequently move together.

Why Does the Carrier Answer Hide Inside the Contracting Structure?

Here is the core difficulty. The borrowed-servant finding is a legal conclusion about control. But the carrier obligation that follows it is buried in federal contracting records that almost never name the carrier directly next to the worker.

Consider the data reality. ClaimTrove indexes 43,298 prime contract awards and 4,315 subcontract awards across federal databases. A worker injured on a prime's site may be employed by a sub three tiers down. The prime appears in the award record. The sub may appear in a subcontract record, or only in FOIA-sourced filings. The carrier appears in none of those award records by default.

To connect a worker to the right carrier under a borrowed-servant theory, you have to assemble several layers at once:

• The general employer (the staffing or payroll entity) and its carrier history.
• The special employer (the controlling prime or higher-tier sub) and its carrier history.
• The contract or task order under which the work was performed.
• The time window, because carriers change every few years even on stable contracts.

Each layer is a separate research problem. Employer names are inconsistent across sources. A single contractor can appear under twenty spelling and entity variations, so alias resolution across employer name variations is the unglamorous first step in almost every dual-employer investigation. Skip it and you miss half the carrier evidence.

Then there is the flow-down problem. DBA insurance obligations cascade through subcontract clauses, and gaps open at every tier. Our analysis of flow-down clauses and the coverage gaps they create shows how a sub can carry a different carrier than the prime assumed, which is precisely the scenario a borrowed-servant claim exposes. The doctrine forces the question the flow-down clause was supposed to answer and often did not.

None of this is solvable by reading a single record. It requires cross-referencing prime awards, subcontract awards, FOIA database results, and OALJ party data, then resolving the time window. That is the work ClaimTrove was built to compress from weeks into minutes.

What Does the OALJ Record Show About Dual-Employer Carrier Disputes?

Borrowed-servant and dual-employer arguments surface repeatedly in DBA litigation, and the decisional record is the best window into how administrative law judges actually resolve them. ClaimTrove indexes 5,022 OALJ decisions, and the parties to each decision are mined into a structured employer-carrier knowledge base now holding 2,454 confirmed mappings.

That mining matters for dual-employer claims specifically. When an ALJ decides which employer controlled the work, the decision caption names the responsible employer and its carrier. Over thousands of decisions, those captions reveal which carriers tend to appear behind which employers, and how those pairings shift across time and contract.

What the pattern shows, without revealing any single answer, is that the responsible carrier in a borrowed-servant fight is frequently not the carrier the claimant first identified. The general employer's carrier is the obvious one. The special employer's carrier is the one that ends up paying when control shifts. Finding the second carrier requires tracing the contracting relationship, not the payroll.

The OALJ corpus also confirms how often these disputes turn on timing. A contractor's carrier in 2011 is frequently not its carrier in 2015. If your borrowed-servant theory targets the special employer, you need that employer's carrier for the exact injury date, not its current or historical default. Reading the decisions teaches the analysis, but it will not hand you the live carrier answer.

One caution. The OALJ record tells you how judges reasoned in decided cases. It does not hand you the carrier for your live claim. The doctrine is public; the specific prime-sub-carrier mapping that controls your client's injury is not something you can read off a decision caption. That mapping is reconstructed from the contracting structure, the time window, and cross-source corroboration.

How Do You Map a Borrowed-Servant Relationship to the Right Carrier?

A disciplined workflow keeps a dual-employer claim from collapsing into a carrier guessing game. The goal is to identify every employer with a plausible claim of control, then resolve each to its carrier for the injury date, and let the legal analysis decide which one you pursue.

Start with both employers, not one. Identify the payroll employer from the LS-203 and pay records. Then identify the on-site controlling entity from the worker's account, the contract scope, and the chain of command at the job site. Treat both as targets from the outset.

Next, resolve aliases for each employer. Run every spelling, abbreviation, and successor entity name. A borrowed-servant claim that misses the special employer's alias will miss the special employer's carrier, which defeats the entire theory.

Then pin the contract and the time window. Determine which prime contract or task order the work fell under, and the exact injury date. The carrier behind any contractor is a moving target, so the date is not a detail; it is the whole analysis. Our walkthrough of the five-step DBA carrier investigation workflow lays out the sequence that keeps these moving parts in order.

Finally, corroborate across sources. A carrier name that appears in one record and nowhere else is a lead, not a conclusion. The strongest carrier identification stacks an award record, a subcontract record, FOIA database results, and OALJ party data into a single consistent answer. When those sources agree on a carrier for the right employer on the right date, you have something you can file against.

The trap to avoid is settling for the easy carrier. The payroll employer's carrier is the one you find first and the one opposing counsel will happily concede, because conceding it can shift the loss onto the wrong party. Under a borrowed-servant theory the carrier that actually pays is often the harder one to find, sitting behind the special employer and the controlling contract.

What Happens When Both Carriers Deny Responsibility?

The most common borrowed-servant outcome is a standoff. The general employer's carrier argues the worker was borrowed and the special employer controlled the work. The special employer's carrier argues no borrowing occurred and the worker remained the general employer's. The claimant sits between two denials.

This is where Section 20(a) of the LHWCA helps the claimant. The statutory presumption of compensability does not vanish because two carriers are fighting; the claim is presumed covered, and the burden falls on the carriers to sort out which one bears it. The fight over allocation should not delay benefits to an injured worker, though in practice it often does.

Strategically, naming both responsible employers and both carriers in the claim protects your client. If you file against only the payroll carrier and the ALJ finds a borrowed-servant relationship, you may face a defense that the truly responsible carrier was never joined. Joining both forces the allocation fight into the proceeding rather than into a later collateral dispute.

Carriers also use the dual-employer ambiguity as a delay tactic, the same way they leverage other coverage questions. Understanding how that prime-versus-sub tracing breaks down helps you anticipate the denial; our piece on why tracing subcontractor insurance is so hard explains why the structure itself invites these standoffs and how to cut through them with documented carrier identification.

The cleanest way to end a two-carrier standoff is evidence. When you can show, before the hearing, that a specific carrier covered the controlling employer on the injury date, the allocation argument loses much of its fog. The doctrine tells the ALJ which employer is liable. The carrier mapping tells everyone which insurer writes the check.

Map the Borrowed-Servant Relationship to a Carrier

The borrowed-servant doctrine decides which employer is liable. But a liable employer with an unidentified carrier still leaves your client waiting. The hard part is not the doctrine; it is connecting the controlling employer to the carrier that covered it on the day your client was hurt, across thousands of contracts, aliases, and shifting coverage windows.

ClaimTrove does that connection work. It resolves both employers, traces the contract and task order, fixes the time window, and corroborates the carrier across prime awards, subcontract records, FOIA database results, and OALJ party data. Instead of guessing which of two carriers pays, you walk into the informal conference with a documented answer. Start a borrowed-servant carrier investigation in ClaimTrove and stop letting two carriers point at each other while your client's benefits stall.

This tool provides information from public DOL records. It is not legal advice. Always verify with primary sources.