Why does Sedgwick's name appear on a DBA claim when it never wrote the policy?
A death benefits claim lands on your desk. The overseas contractor employed your client's husband on a logistics contract in Kuwait. The first piece of paper you receive is a letter on Sedgwick letterhead. It lists an adjuster, a claim number, and a phone number. It does not list a policy number. It does not name an insurance company.
So who do you serve? Who bears the compensation liability under the Defense Base Act? If the employer went bankrupt, who still has to pay? The letter answers none of these questions. That is not an accident. It is how claims administration works.
Sedgwick is one of the largest claims administrators in the world. When its name shows up on a Defense Base Act file, it is acting as an agent. It is handling the mechanics of the claim on behalf of the party that actually carries the risk. That party may be an insurance carrier. It may be a self-insured employer. The letter rarely tells you which.
Understanding the Sedgwick claims management third party administrator DBA role starts with one distinction. Administration is not risk. The company adjusting your claim is not automatically the company on the hook to pay it. Confuse the two and you can serve the wrong party, miss the real carrier, and weaken your leverage on penalties.
This article explains what the name on the letterhead actually signals. You will learn how a TPA fits into the DBA claim structure. You will see why the statute puts liability on the carrier. And you will learn to trace the correspondence back to the insurer that underwrote the policy.
What is a third-party administrator in a DBA claim?
A third-party administrator is a company hired to run the day-to-day operations of a claim. It takes the first report of injury. It assigns an adjuster. It reviews medical bills, issues payments, and sends correspondence. It does all of this in someone else's name and with someone else's money.
The TPA does not bear the risk. It never signed a policy that promises to pay compensation. Its contract is a service agreement with the carrier or the self-insured employer. The Sedgwick claims management third party administrator DBA role is defined by delegation, not by underwriting.
Insurers use TPAs to control cost and scale. Rather than staff a national adjusting operation, a carrier outsources file handling to a specialist. Self-insured employers use TPAs for the same reason. A large defense contractor that funds its own claims still needs professionals to administer them.
This creates a recurring problem for claimant attorneys. The name you see most often is the name of the administrator, not the risk-bearer. Adjusters correspond on TPA letterhead. Checks may issue from TPA accounts. The underwriting carrier can stay invisible for months.
Sedgwick is not the only company in this position. The same pattern runs through every major TPA in the DBA space. Want the full map of who administers versus who insures? Our breakdown of the major DBA third-party administrators and the carriers behind them shows how the largest administrators line up.
The distinction matters because the DBA borrows its entire machinery from the Longshore and Harbor Workers' Compensation Act. Under that structure, compensation is owed by the employer and secured by an insurance carrier or an approved self-insurance program. A TPA is nowhere in that chain of liability. It is a vendor.
Reading the administrator as the carrier is one of the most common errors in early file review. It leads attorneys to name the wrong entity and to misjudge who controls settlement authority. Our guide to spotting a TPA versus an actual DBA carrier walks through the tells on the first letter.
How is Sedgwick different from the underwriting carrier of record?
The carrier of record is the entity that issued the DBA policy. It is authorized by the Department of Labor to write Defense Base Act coverage. It bears the financial obligation to pay compensation and medical benefits. Its name belongs on the claim, in the answer, and in any settlement.
Sedgwick is none of those things. It does not appear on the DOL list of authorized DBA carriers as an insurer. ClaimTrove tracks 637 DOL-authorized carriers, and a pure claims administrator does not sit among them as a risk-bearer. When you need the party legally responsible for benefits, the administrator's name is a dead end.
Here is the practical difference. If you file against Sedgwick, you have named a servicing agent. If the employer's coverage lapses or the carrier disputes the claim, the administrator has no independent duty to pay. The obligation sits with the carrier or the self-insured employer standing behind it.
There is a second complication. A single administrator can service many carriers. Sedgwick may handle a file for one insurer on a 2011 injury and a different insurer on a 2016 injury. The letterhead looks identical. The underwriting carrier behind it is not.
This is why coverage shifts over time trip up so many investigations. The administrator can remain constant while the carrier of record changes between policy periods. We cover this moving-target problem in depth in our analysis of why DBA carriers change across policy periods.
The declarations page settles the question. It names the insurer, the policy number, and the effective dates. The TPA may administer the file, but the declarations page tells you who wrote the risk. Knowing how to read one is a core skill. Our field guide to reading a DBA policy declarations page separates the carrier from the broker and the TPA line by line.
How does a TPA differ from the broker and the adjuster on a DBA file?
Attorneys often lump three roles together: the broker, the administrator, and the adjuster. They are not the same. Each sits in a different place in the claim.
The broker sells the policy. It is an intermediary between the contractor and the insurer. Once coverage is bound, the broker's job is largely done. Its name may appear in procurement records, but it does not pay your client's benefits.
The administrator runs the claim after an injury. Sedgwick sits here. It receives the notice of injury, opens the file, and manages the daily flow of payments and correspondence. It acts for the carrier or the self-insured employer, within the authority they grant.
The adjuster is a person inside the administrator or the carrier. This is the individual who signs the letters and returns your calls. An adjuster at a TPA is not a decision-maker with unlimited authority. The reserve and the settlement range are usually set above them.
Why does the layering matter? Because each role points to a different record. The broker shows up in contract and procurement data. The carrier shows up in DOL authorization records and coverage filings. The administrator shows up only on the correspondence. Read all three as one and you lose the thread that leads to the risk-bearer.
There is a further wrinkle with large TPAs. Some offer bundled services like bill review, nurse case management, and investigation. Sedgwick may coordinate all of these on a single file. None of them change the core fact. Managing a claim is not the same as insuring it.
This sorting exercise pays off at every stage. It tells you who to name, who to depose, and whose authority governs a settlement. It also tells you which government records will confirm the answer. Sort the names by function before you act, and the entity that carries the risk stops hiding.
Why does the DBA statute make the carrier, not the TPA, legally liable?
The Defense Base Act appears at 42 U.S.C. 1651 through 1654. It does not create a standalone benefits system. Instead it extends the Longshore and Harbor Workers' Compensation Act, found at 33 U.S.C. 901 through 950, to overseas contract workers.
Under that borrowed framework, the employer owes compensation. The Act requires the employer to secure that obligation. It does so by buying insurance from an authorized carrier or by qualifying as a self-insurer with the Department of Labor. The implementing regulations sit at 20 CFR Parts 701 through 704.
Notice who is absent from that structure. A third-party administrator has no statutory duty to pay compensation. It is not the employer. It is not the carrier. It is not a self-insurer. It is a contractor hired to process the paperwork.
The contract requirement reinforces the point. FAR 52.228-3 is the clause that forces most government contractors to carry DBA insurance. The clause obligates the contractor to provide coverage through an insurer. It says nothing about the administrator who later touches the file.
This is why service matters. When you file a claim or seek a penalty for late payment, the responsible party is the carrier or self-insured employer. Directing your demand at the administrator alone can leave the actual risk-bearer untouched. The liability chain runs through the policy, not the letterhead.
The stakes rise when the employer is defunct. A DBA policy survives the bankruptcy of the employer that bought it. The carrier remains obligated. The administrator does not step into that role. If you have chased only the TPA, you may have never identified the entity that still has to pay.
ClaimTrove was built to close this gap. It maps the administrator on your letter to the underwriting carrier and the policy periods behind it, using federal contract records and DOL coverage filings. Run the employer name and see who actually carried the risk, not just who processed the mail.
How do you trace past Sedgwick to the actual DBA carrier?
Tracing starts with the injury date. DBA coverage is period-specific, so you need the carrier that wrote the policy on the date of injury. The administrator's current involvement tells you nothing about which insurer was on the risk years earlier.
Next, resolve the employer's real name. Overseas contractors operate under subsidiaries, joint ventures, and renamed entities. A claim filed under one corporate name may trace to a parent that bought coverage under another. Getting the Sedgwick claims management third party administrator DBA role right means tracing correspondence back to the policy behind it, and that requires the correct legal employer first.
Then work the federal record. DOL coverage filings, FOIA database results, and industry performance reports connect employers to carriers by period. ClaimTrove data includes more than 150,000 coverage filings spanning 1944 to 2022, plus more than 2,400 employer-to-carrier mappings. These records name the insurer the administrator will not.
Contract data adds another layer. Federal award records show the awarding agency, the contract vehicle, and the period of performance. Some agencies mandated a specific DBA carrier for defined periods, which can resolve the carrier deterministically. A structured workflow keeps these steps in order.
For a repeatable process, our five-step DBA carrier investigation workflow lays out the sequence from employer name to confirmed carrier. It treats the TPA as a clue, not an answer.
The goal is always the same. You want the insurer of record for the date of injury, the policy number if it is discoverable, and the DOL authorization status of that carrier. The administrator's letterhead is where the trail begins, not where it ends.
What mistakes happen when attorneys treat the TPA as the carrier?
The first mistake is naming the wrong party. When the claim names the administrator instead of the carrier, you can spend weeks corresponding with an entity that has no duty to pay. The real carrier stays out of the fight.
The second mistake is misreading settlement authority. A TPA adjuster negotiates within limits set by the carrier or self-insured employer. If you do not know who sets those limits, you cannot tell whether the adjuster can actually close the file.
The third mistake is missing a self-insured employer. Sometimes there is no separate carrier at all. A large contractor may fund its own DBA liability and hire an administrator to run the claims. In that case the employer is the risk-bearer, and the administrator's name hides that fact.
The fourth mistake is losing the bankruptcy safety net. If you never identify the carrier, you lose the argument that the policy survives the employer's insolvency. That is often the difference between a paid claim and an uncollectible one.
Each of these errors traces back to the same root. The name on the letter is the administrator, and the administrator is not the risk. Reading the Sedgwick claims management third party administrator DBA role correctly means always asking who stands behind the file.
You do not have to reconstruct that chain by hand. ClaimTrove maps this carrier's administered employers and the policy periods behind them from the federal record. Start an investigation with the employer name, and let the data name the carrier the letterhead never will.