You take the call from a new client. Her husband worked overseas for a large defense technology firm, suffered a back injury on a logistics base, and the claim has stalled. You do what you always do first. You go looking for the insurance carrier so you know who you are fighting. You pull federal contract data, you check coverage filings, you run the employer name through every variation you can think of. Nothing lines up. There is no AIG policy, no Starr filing, no ACE American letter of authorization. Hours later you realize the problem is not that you missed the carrier. There is no carrier. The employer is self-insured.
This is one of the most consequential facts you can learn about a Defense Base Act claim, and most attorneys learn it late. A self-insured employer carries its own risk under direct authorization from the Department of Labor. There is no third party underwriter standing between you and the company. The litigation posture changes, the negotiating dynamics change, and the documents you should be requesting change. Spotting self-insurance early is not a technicality. It reshapes your entire strategy from the first week.
The challenge is that self-insured status is not advertised. It hides behind third-party administrators, behind name changes, and behind the same federal records that usually point you to a carrier. Knowing how to identify self-insured DBA employers when there is no carrier to find is a distinct investigative skill. This article explains how DOL self-insurance authorization works, why self-insured employers behave differently in claims, and the signals that tell you to stop hunting for a policy that does not exist.
What Does It Mean for a DBA Employer to Be Self-Insured?
Under the Longshore and Harbor Workers' Compensation Act, which the Defense Base Act extends to overseas federal contractors, an employer has two ways to satisfy its obligation to pay benefits. It can buy a policy from an authorized insurance carrier, or it can become self-insured. Self-insurance is not a loophole. It is a formal status granted by the DOL Office of Workers' Compensation Programs after the employer proves it can pay claims directly.
The DOL authorized carrier list, which underpins much of ClaimTrove's carrier intelligence, actually tracks both categories. Each record carries a type marker that distinguishes an insurer from a self-insured entity. Of the 637 authorized DBA carriers in our data, a subset are not carriers at all in the conventional sense. They are employers that have been cleared to carry their own risk.
To win that authorization, an employer typically posts security. That means a surety bond, a letter of credit, or another financial instrument that the DOL holds to guarantee benefit payments if the company defaults. The bigger the expected exposure, the larger the security. This is why self-insurance is concentrated among the largest, most established defense contractors. A company needs deep balance sheets and a long compliance history before the DOL will let it skip the insurance market entirely.
The practical takeaway is direct. When you investigate a smaller or newer contractor, you should expect a carrier. When you investigate a household-name prime with decades of federal work, self-insurance is squarely on the table. That single distinction should change how you read the absence of a policy in your search results.
Why Do Self-Insured DBA Employers Behave Differently in Claims?
When a traditional carrier handles a DBA claim, the carrier and the employer have partially separate interests. The carrier wants to control loss costs. The employer wants to protect its workforce relationships and its government contract standing. Those interests do not always align, and a sharp claimant attorney can sometimes work the gap.
With a self-insured employer, that gap closes. The company is paying every dollar of indemnity and medical benefits out of its own pocket. The decision-maker who approves or denies treatment is, ultimately, the same entity that signs the contractor's paycheck. This concentration of interest changes the tone of negotiations. There is no carrier adjuster to blame and no underwriter to escalate to. You are dealing with the principal directly.
It also changes the documents that matter. With an insured employer you chase the policy, the letter of authorization, and the carrier's claim file. With a self-insured employer you should be looking at the DOL authorization itself, the security instrument, and the identity of the third-party administrator the company hired to process claims. Understanding how to spot a TPA versus an actual DBA carrier becomes essential here, because the TPA is often the only outward face of a self-insured program.
Self-insured employers also tend to be repeat players. A large prime that has handled hundreds of overseas injuries has settled patterns, in-house counsel, and a defined appetite for litigation. That cuts both ways. They know the system, but they also have reputational and contractual reasons to avoid ugly, prolonged fights. Reading those incentives correctly is the strategic payoff of identifying self-insurance early.
How Can You Spot a Self-Insured Employer Before You Waste Weeks Hunting a Carrier?
The clearest signal is the one you already noticed in the opening scenario. You run a thorough carrier search and come up empty, even though the employer is plainly large and active in federal contracting. When a small subcontractor has no findable carrier, that usually means your search was incomplete. When a major prime has no findable carrier, self-insurance jumps to the top of the list.
A second signal is the presence of a third-party administrator with no underwriter behind it. In normal claims a TPA like ESIS or Gallagher Bassett sits in front of a real carrier, and the analytical work is resolving the TPA to its underwriter. With a self-insured employer, the TPA traces back to nothing. The chain ends at the administrator because the employer is the risk-bearer. That dead end is itself diagnostic.
A third signal lives in the federal contracting record. Self-insured contractors are concentrated among firms with massive, sustained award histories. ClaimTrove links employers to 43,298 prime contract awards and 4,315 subcontract awards. When an employer shows that kind of volume and longevity but shows no carrier signal, the data is telling you something. The pattern of consolidation matters too, which is why the impact of defense contractor consolidation on DBA coverage often surfaces self-insured successors hiding behind merged corporate names.
The trap is name confusion. A self-insured parent may run claims for a dozen subsidiaries, each appearing under a different name in federal records. If you do not connect those names, you may conclude one subsidiary is uninsured when it is actually covered under the parent's self-insurance authorization. This is the same problem that makes hidden carrier families with multiple names so difficult, except the entity hiding behind the aliases is the employer itself.
ClaimTrove was built to resolve exactly this ambiguity. It tells you whether an employer's records point to an authorized carrier, a TPA fronting a carrier, or a self-insurance authorization with no underwriter at all. Check the self-insured status of any DBA employer in ClaimTrove before you spend a week chasing a policy that was never issued.
Which DBA Employers Are Most Likely to Be Self-Insured?
You cannot predict self-insurance from a name alone, but the data points to a clear profile. The employers most likely to hold self-insurance authorization are large, long-tenured defense and technology primes with deep balance sheets and sustained federal award volume. These are the firms that can satisfy the DOL's security requirements and absorb the cash-flow swings of paying claims directly. Smaller subcontractors and newer entrants almost never qualify, which is why a missing carrier for a small sub usually means an incomplete search rather than self-insurance.
Sector matters too. Self-insurance shows up disproportionately among contractors performing technical services, systems integration, and large-scale logistics, where a single firm has handled overseas work for many years across many task orders. The longer an employer has operated in the federal space, the more likely it has built the internal claims infrastructure that self-insurance demands. A company that has weathered base operations through multiple deployment cycles often has both the financial strength and the institutional appetite to carry its own risk.
Corporate history is the wildcard. Mergers, acquisitions, and spinoffs can move an employer in or out of self-insured status, and they scatter the entity across multiple names in federal records. A self-insurance authorization granted to a parent may quietly cover a newly acquired subsidiary that still files under its old name. Without resolving those corporate relationships, you can badly misread an employer's coverage structure. This is why investigating self-insurance is inseparable from resolving employer aliases and tracing corporate lineage across the full record.
How Does Self-Insurance Change Your Claim Strategy?
Once you confirm self-insurance, several strategic decisions shift at once. Service of process and notice run to the employer directly, not to a carrier's claims office. Discovery should target the employer's internal claims handling, its authorization file with the DOL, and the TPA's processing records. You are no longer trying to pierce a separate corporate insurer. You are dealing with one entity that wears every hat.
Settlement dynamics change as well. A self-insured employer is spending its own money, so it weighs litigation cost against payout more directly than an insurer spreading risk across a book of business. That can make a well-documented claim settle faster, because protracted litigation is pure expense to the company. It can also make a contested claim harder, because there is no carrier with an independent incentive to close a file.
Security becomes a live issue if the employer's finances deteriorate. The bond or letter of credit the DOL holds is your client's backstop. Knowing whether that security is current and adequate is part of protecting a long-tail claim, especially for permanent disability. The same defensive instincts that apply to carrier insolvency and open claims apply when a self-insured employer faces financial stress, because the protective mechanism is different but the risk to your client is similar.
Finally, self-insurance affects how you read the company's track record. A repeat self-insured player has a discernible pattern of which injuries it accepts, which it fights, and how it handles return-to-work disputes. That history is investigable, and it is far more useful than guessing. The strategic edge comes from treating the employer as the carrier, because under self-insurance, that is exactly what it is.
What Records Actually Confirm Self-Insured Status?
Confirmation is not a single document. It is a convergence of signals that all point the same direction. The DOL authorization record is the anchor, because it explicitly classifies an entity as self-insured rather than insured. ClaimTrove surfaces that classification directly, so you are not inferring status from absence.
Coverage filings and federal contract data provide corroboration. When an employer appears across thousands of award records and 154,886 coverage filings in our FOIA database results without a stable underwriter ever attaching, the self-insured reading strengthens. The absence of a carrier across many years and many contracts is meaningful precisely because it is consistent.
The third-party administrator is the operational tell. Identify the TPA processing the claims, then test whether it resolves to a real carrier. If it does, you have an insured employer using an administrator. If it dead-ends, you likely have a self-insured employer running claims through hired hands. Distinguishing those two situations is the core skill, and it overlaps heavily with the process of identifying the correct DBA carrier for a claim in the ordinary case.
One caution. Status is not permanent. An employer can hold self-insurance for one period and carry traditional coverage in another, or vice versa, as its risk appetite and DOL standing change over time. Date-scoping matters. The question is never simply whether an employer is self-insured. It is whether the employer was self-insured on the date of injury, which is the only date that controls liability.
Confirm Status Before You Build Your Case
The cost of misreading self-insurance is measured in wasted weeks and misdirected discovery. Attorneys send carrier demand letters to companies that have no carrier. They subpoena underwriter files that do not exist. They negotiate as if a third party were footing the bill when the employer is paying every dollar itself. Each of those mistakes flows from the same root cause, which is not knowing the employer's coverage structure on day one.
ClaimTrove collapses that uncertainty into a single lookup. It draws on the DOL authorized list, federal contracting awards, coverage filings, and SME-confirmed mappings to tell you whether an employer was insured, fronted by a TPA, or self-insured on a given date. Run your employer through ClaimTrove and find out whether you are hunting a carrier or building a case against a self-insured principal. Knowing the answer before you draft your first letter is the difference between strategy and guesswork.