Why does one signature decide whether your client keeps DBA benefits?
Your client drove a fuel truck for a logistics contractor outside Kandahar. A host-nation civilian ran a checkpoint and T-boned the vehicle. Your client has a Defense Base Act claim against the employer's carrier. He also has a viable negligence claim against the other driver's employer.
You work the third-party case for a year. You negotiate a solid settlement with the tortfeasor's liability insurer. The number is good, the release is drafted, and you are three days from signing. Then a colleague asks a simple question. Did you get the DBA carrier's written approval first?
If the answer is no, you may have just forfeited every future DBA benefit your client is owed. Not reduced. Terminated. That is the reach of Section 33 of the Longshore and Harbor Workers' Compensation Act, which the DBA adopts wholesale.
Section 33 is codified at 33 U.S.C. 933. The DBA incorporates it through 42 U.S.C. 1651. So every rule that governs a longshore worker's third-party recovery governs your overseas contractor's recovery too. The carrier has a lien on the recovery. It also has a credit against future benefits. And it holds a veto over any settlement for less than the full compensation entitlement.
This article walks the coordination sequence step by step. You will learn how the lien and credit actually compute. You will see where the 33(g) written-approval trap sits. And you will learn why the first move is naming the carrier that holds the lien before you sign anything.
What does Section 33 actually do in a DBA case?
Section 33 answers a recurring problem. A contractor gets hurt overseas by someone other than the employer. Two recovery paths open at once. One is the no-fault DBA claim against the employer's carrier. The other is a tort claim against the third party who caused the harm.
Older versions of the statute forced an election between the two. That is gone. Under current law, your client can accept DBA compensation and still pursue the third party. The two recoveries coexist, but they are linked by a set of accounting and consent rules that protect the carrier from paying twice.
The linkage runs through three mechanisms. First, an assignment: accepting compensation under a formal award can transfer the tort claim to the carrier unless your client sues in time. Second, a lien and credit: the carrier gets reimbursed for what it paid and gets a dollar credit against what it owes next. Third, a consent gate: settling for less than the compensation entitlement requires prior written approval.
Miss any one of these and the consequences range from a smaller net recovery to total forfeiture. The tort claim against the third party is separate from the exclusive-remedy bar that blocks suing the employer itself. That distinction controls who you can even name as a defendant, because the employer and its carrier are usually off limits while an outside tortfeasor is fair game. Sort the reachable defendants first, then apply Section 33 to whatever recovery those defendants produce.
Get the framework right and Section 33 becomes a coordination problem, not a landmine. The whole point of DBA third party recovery lien Section 33 coordination practice is to sequence the moving parts so no benefit is lost.
How does the carrier's lien and credit actually work?
Attorneys often use "lien" and "credit" interchangeably. Section 33 treats them as two different things, and the distinction changes your client's net check.
The lien is backward-looking. It reimburses the carrier for compensation and medical benefits it already paid. When the carrier recovers as the assignee of the tort claim, the distribution formula in 33(e) controls. Litigation expenses come out first. The carrier then retains an amount equal to the benefits it paid and the present value of future benefits. Any remaining excess goes to your client. The 1984 amendments struck the old one-fifth share the employer used to keep, so today the carrier retains only its costs and its compensation stake, not a cut of the surplus.
The credit is forward-looking. When your client, not the carrier, brings the third-party suit, 33(f) reduces the carrier's future liability. The carrier owes compensation only for the excess of the entitlement over the net recovery. Net means gross recovery minus your client's attorney fees and litigation costs. So the credit is computed after your fee, but the lien for past payments is not.
That asymmetry is deliberate, and the Supreme Court confirmed it. In Bloomer v. Liberty Mutual Insurance Co., 445 U.S. 74 (1980), the Court held the employer does not have to share the claimant's third-party attorney fees when it recovers compensation it already paid. The common-fund doctrine that reduces liens in many state systems does not apply here. Your client's lawyer funds the recovery, and the carrier rides for free on the reimbursement portion.
This is why lump-sum math matters so much. The credit can wipe out years of future indemnity, which reshapes what a DBA settlement is actually worth. The interaction between third-party credits and the underlying claim value is exactly the kind of variable that drives DBA settlement valuation across factors state comp lawyers rarely see.
Run the numbers before you accept any tort offer. A recovery that looks generous can leave your client with a large carrier credit and thin future benefits. The credit is not a penalty. It is the price of the double recovery Section 33 permits.
What is the Section 33(g) written-approval trap?
Subsection 33(g) is where good third-party lawyers lose entire DBA claims. It has two triggers, and both bite hard.
The first is prior written approval. Under 33(g)(1), the rule turns on the settlement amount. If your client settles with a third party for less than his full compensation entitlement, the employer stays liable only on one condition. Both the employer and the carrier must have given written approval before the settlement was executed. Approval after signing does not count. Approval from the carrier alone, when the employer is separate, may not count either.
The second is notice. Under 33(g)(2), your client must notify the employer of any third-party settlement, regardless of amount. Fail to give notice, or fail to get required approval, and all rights to compensation and medical benefits terminate. The forfeiture applies even if the carrier already acknowledged the claim and made payments.
The Supreme Court read this provision literally in Estate of Cowart v. Nicklos Drilling Co., 505 U.S. 469 (1992). The Court held that a "person entitled to compensation" must obtain approval even when no formal award exists and even when the employer is not currently paying. Cowart settled for less than his entitlement without approval and lost his benefits. The equities did not save him.
The mechanics of forfeiture, and the narrow paths practitioners use to survive a missed signature, deserve close study on their own. The full anatomy of how a third-party settlement without carrier consent can forfeit the entire DBA claim shows how often the trap springs on lawyers who never handle comp.
One practical relief valve exists. If the third-party settlement equals or exceeds the total compensation entitlement, prior approval is generally not required, though notice under 33(g)(2) still is. That is a dangerous distinction to guess at. Value the claim first, then decide whether you are in approval territory.
How do you coordinate the recovery without forfeiting benefits?
Treat coordination as a checklist you run every time, not a memory test. Sound DBA third party recovery lien Section 33 coordination practice follows the same order in every case.
Start by valuing the DBA claim. You cannot know whether 33(g) approval is required until you know the full compensation entitlement, including future indemnity and lifetime medical. Undervalue it and you may skip approval you actually needed.
Next, identify the employer and the carrier of record with certainty. Approval must come from both when the settlement is below entitlement. You cannot get a signature from a carrier you cannot name. This is harder than it sounds when the claim runs through a subcontractor, a self-insured parent, or a third-party administrator that is not the actual underwriter.
Then request written approval in advance and in writing. Send the proposed settlement figure, the release terms, and a demand for signed consent from the employer and the carrier before execution. Document every transmission. Do not sign the release until the approvals are in hand.
Coordinate the DBA settlement itself in parallel. A Section 8(i) compromise of the comp claim must clear the district director or the ALJ under an adequacy standard. The third-party credit is a core input to that review. The way an ALJ tests fairness under the Section 8(i) settlement adequacy standard means your third-party numbers and your comp numbers have to tell one consistent story.
Finally, mind the assignment clock. Under 33(b), accepting compensation under a formal award assigns the tort claim to the carrier unless your client commences the third-party action within six months of the award. File in time or you lose control of the very suit you built.
Why is naming the right carrier the hidden first step?
Every step above assumes you know who holds the lien. In overseas contractor claims, that assumption fails constantly. The employer on the paystub is often a subsidiary, a joint venture, or a staffing entity layered under a prime. The name on the claim correspondence is frequently a third-party administrator, not the carrier that must sign the 33(g) approval.
Send your approval demand to the administrator and you may never reach the entity whose signature the statute requires. Administrators like the major DBA claims handlers adjust files for carriers, but they are not the underwriter of record. Understanding the split between the adjuster and the insurer is foundational, and the roles that third-party administrators play in DBA claims routinely mask who actually holds the pen.
The carrier can also change over the life of a contract. Mandatory agency programs shifted underwriters on fixed dates. Prime contractors re-bid their DBA coverage every few years. So the carrier on the date of injury may differ from the carrier handling the file today. Only the correct carrier on the correct date controls the lien and the approval right.
This is where fast, source-backed research pays for itself. ClaimTrove pulls the employer, the carrier, and the governing decision data from federal contract awards, DOL industry filings, OALJ decisions, FOIA coverage filings, and 637 DOL-authorized carriers in one investigation. Instead of guessing which underwriter must sign, you get the carrier of record, its corporate family, and the citations behind it. Run the investigation on your employer and injury date before you draft a single approval letter.
Naming the right carrier early also protects your fee. When you know the lienholder, you can negotiate the credit and preserve the value of your work. That preserved value feeds directly into a defensible Section 28 attorney fee petition the ALJ will approve.
How does WHCA reimbursement change the lien math in war zones?
War-zone claims add a layer most practitioners miss. When an injury results from a war-risk hazard, the DBA carrier that pays benefits can seek reimbursement from the federal government under the War Hazards Compensation Act, 42 U.S.C. 1701 and following. Treasury, in effect, backstops the carrier.
That backstop changes the carrier's economic incentive on your third-party case. A carrier expecting full WHCA reimbursement may push harder to preserve its lien and credit, because those recoveries reduce what it ultimately claims from the government. The reimbursement mechanism does not erase Section 33; it sits alongside it.
You should account for the interplay when you model net recovery. The WHCA layer affects settlement leverage and the carrier's willingness to compromise its lien. WHCA reimbursement shapes DBA settlement strategy as a genuine variable in high-value war-zone files, not a footnote. Ask the carrier where it stands on reimbursement before you assume it will trade lien value for a quick close.
Confirm war-hazard applicability early. If your client was injured by hostile action, an insurrection, or a zone-of-special-danger event, flag the WHCA posture before you finalize any third-party number. The lien you are negotiating may ultimately be paid back to the carrier by Treasury, and that reality belongs in your strategy.
Coordinate the sequence, not just the signatures
Section 33 rewards lawyers who treat third-party recovery as a coordinated sequence. It punishes those who treat it as a signature at the end. Value the claim, name the carrier, secure written approval before execution, honor the six-month assignment window, and align the comp settlement with the third-party numbers.
Do that in order and your client keeps both recoveries. Skip a step and 33(g) can erase the DBA claim entirely. The single most common failure point is the one you can fix in minutes: not knowing which carrier and employer must approve the deal. Disciplined DBA third party recovery lien Section 33 coordination practice is really just refusing to sign until the approvals, the credit math, and the carrier of record are all confirmed.
Build the habit on your next file. Calendar the six-month assignment date the moment an award issues. Draft the approval demand as soon as a third-party settlement number takes shape. Confirm the carrier of record before either deadline arrives. The lawyers who lose these claims are almost never careless about the tort case. They are careless about the comp claim riding alongside it.
Before you draft your next approval demand, run the employer and injury date through ClaimTrove. Pull the carrier of record, the corporate family, and the source citations in one pass. Coordinate from facts, not assumptions, and Section 33 stops being a trap.