You pull an old LS-202 or a coverage card for an overseas contractor, and the carrier line reads SeaBright Insurance Company. The injury happened in 2011. The claim is still open, the disability is permanent, and now you need to know who actually pays. You search the current DOL authorized carrier list and SeaBright is not there. You search the carrier's website and the domain redirects somewhere unfamiliar. The name on the policy points to a company that no longer writes business.
This is one of the most common dead ends in Defense Base Act carrier work. A carrier that was active when the injury occurred has since been acquired, merged, placed into runoff, or absorbed into a larger group. The policy is still valid. The obligation still exists. But the entity that services it has a different name, a different claims operation, and a different address than anything printed on the original document.
SeaBright is a textbook case of this problem. It was a real, DOL-authorized DBA writer that insured federal contractors during the peak years of overseas operations. Then it stopped being SeaBright. The policies did not vanish. They moved. For any attorney holding a claim tied to a SeaBright policy, the question is not whether coverage existed. It did. The question is who is responsible for it today, and that answer requires tracing.
This article explains SeaBright's corporate lineage, why claims tied to old SeaBright policies still need active tracing, and what makes acquired-carrier identification harder than looking up a name in a list.
Who was SeaBright Insurance Company in the DBA market?
SeaBright Insurance Company, originally SeaBright Insurance Holdings, was a Seattle-based specialty workers' compensation insurer. It built its book around hard-to-place comp risks, including maritime employers under the Longshore and Harbor Workers' Compensation Act and federal contractors under the Defense Base Act. That specialty focus is exactly why its name shows up on DBA documents from the late 2000s and early 2010s.
During those years, the overseas contracting surge in Iraq and Afghanistan pushed demand for DBA coverage to historic highs. Carriers willing to write the risk were in a strong position. SeaBright was one of the authorized writers operating in that environment, alongside the larger groups that dominated the market.
In early 2013, SeaBright was acquired by Enstar Group, a company that specializes in acquiring and managing insurance companies in runoff. Runoff means the acquired carrier stops writing new policies but continues to administer and pay claims on policies already in force. The SeaBright brand wound down. The liabilities did not disappear; they were taken over and managed by the acquiring structure.
That distinction matters enormously for DBA claims. A DBA injury can produce decades of medical and indemnity liability. A worker injured under a SeaBright policy in 2011 may still be receiving benefits today. The policy that responds to that claim is the one that was in force on the date of injury, regardless of what happened to the carrier afterward. This is the same temporal principle that drives all DBA carrier identification, and it is why the NAIC number as a stable carrier identifier often outlasts the brand name printed on the policy.
SeaBright is not unique here. It is one example of a broader pattern: carriers that were active during the contracting boom have since been acquired, restructured, or pushed into runoff. The name on a ten-year-old policy is frequently a name that no longer trades.
Why do old SeaBright policies still need tracing today?
The instinct is to treat an acquisition as a simple substitution. SeaBright became X, so write down X and move on. That instinct produces wrong answers in DBA work, and here is why.
First, the responsible entity depends on the date of injury, not the date you are researching. A claim tied to a SeaBright policy issued in 2010 may sit under a different administrative arrangement than one issued in 2012, even though both carry the same carrier name. Runoff portfolios get sub-divided, reinsured, and re-administered over time. The carrier on the policy is fixed at the date of injury; the servicer can change repeatedly after that.
Second, third-party administrators add a layer of confusion that survives the acquisition. The entity sending checks and authorizing treatment is frequently not the carrier at all. ClaimTrove's data includes documented TPA-to-carrier normalizations where the name on correspondence is a Gallagher Bassett, an ESIS, or a Broadspire, while the actual underwriter sits behind them. When a carrier goes into runoff, a new TPA often takes over, so the name a claimant sees today bears no resemblance to the carrier of record. Untangling this is the same discipline required for the Blackwater to Academi to Constellis carrier trail, where five corporate name changes obscured a single underlying claims history.
Third, the DOL authorized carrier list is a snapshot of who can write DBA coverage now. It is not a historical record. SeaBright dropping off that list tells you it stopped writing new business. It tells you nothing about the live policies it left behind. Attorneys who rely on the current list to validate an old policy reach a false conclusion: that the coverage is gone. It is not gone. It is administered elsewhere.
Fourth, coverage evidence is scattered across record systems that were never designed to talk to each other. ClaimTrove maintains 154,886 DOL coverage card filings spanning 1944 to 2022, sourced through FOIA. Those filings capture employer, carrier, and policy date as a single piece of direct evidence, which is exactly the proof an acquired-carrier claim needs. But matching them requires resolving 2,056 raw carrier name variations down to canonical groups, because the same underwriter appears under dozens of spellings and abbreviations across decades of filings.
How does a carrier acquisition break carrier identification?
The mechanics of an acquisition create four specific failure points in carrier identification. Each one trips up manual research.
The brand disappears from search. Once a carrier winds down, its website, marketing, and public-facing presence go dark or redirect. A paralegal searching the carrier name finds a successor's homepage with no explanation of the relationship. The connection between the old policy and the new administrator is not published anywhere obvious.
The corporate entity may survive under a different parent. In runoff, the legal entity that issued the policy frequently continues to exist as a subsidiary of the acquirer, even though it no longer writes new business. So the policy is still technically issued by SeaBright Insurance Company as a legal entity, while the operational control and claims handling belong to the parent. Both facts are true at once, and conflating them produces errors.
NAIC and group affiliations shift. The carrier's group membership changes when it is acquired. A carrier that scored as independent in 2011 now rolls up under a different group code. Our entity relationship graph models exactly these date-scoped group memberships, because a carrier's family at the date of injury can differ from its family today. The same modeling problem appears in the Leidos and SAIC split, where a corporate separation forces date-aware analysis of which entity controls a given claim.
The claims operation relocates. Files get transferred. Adjusters change. The address on the original notice routes to nowhere. For a claimant with an open medical condition, this is not academic. It is the difference between a check arriving and a check disappearing into a defunct mailbox.
None of these failure points are visible from a single document. They only resolve when you cross-reference the carrier across multiple time-stamped sources and reconstruct what the carrier was on the date that controls the claim.
What records actually prove SeaBright coverage on a specific claim?
General knowledge that SeaBright wrote DBA business does not win a coverage dispute. You need direct evidence tying a specific employer to SeaBright on a specific date. Several record types can supply that proof, and they carry different evidentiary weight.
Coverage card filings are the strongest direct evidence. A filed insurance card proves coverage existed for a named employer, with a named carrier, on a stated date. This is filed-document proof, not inference. When a SeaBright coverage card surfaces for the right employer and date range, it answers the threshold question outright.
OALJ and BRB decision parties are the next tier. When a SeaBright-insured claim was litigated, the decision header names the employer and carrier together. ClaimTrove auto-mines these employer-carrier pairs from a corpus of 5,022 OALJ and BRB decisions, which means a litigated SeaBright claim from years ago can confirm the relationship for a new claim involving the same employer.
Industry performance reports and federal contract data provide corroboration. They establish that the employer operated overseas during the period, under a contract type where DBA applied. They do not name the carrier directly, but they place the employer in the right time and place to make a SeaBright policy plausible and to narrow the search.
The weakest evidence is correlation: the carrier appeared alongside similar employers in the same period. This is a fallback, not a foundation. It points you toward a likely carrier when nothing stronger exists, and it must be verified before it goes into a filing.
The discipline that ties these together is temporal. A 2011 injury typically surfaces in a litigated decision around 2014, because DBA cases are commonly filed roughly three years after the injury. Knowing that lag lets you weight a decision's date against the injury date and decide whether it actually speaks to your claim or a different policy period entirely. That same temporal reasoning underpins every data-driven breakdown of who insures DBA contractors in a given theater and year.
How is acquired-carrier tracing different from current-carrier lookup?
A current-carrier lookup is close to a single-step query. The employer is active, the policy is current, the carrier is on the authorized list, and the name on the document matches a live operation. You confirm and move on.
An acquired-carrier trace is a multi-step reconstruction. You are working backward from a name that no longer trades, through an acquisition event, to an entity that exists today under different branding. Every step introduces a chance to lose the thread.
You start by confirming the carrier of record at the date of injury, because that is the entity whose obligation you are enforcing. Then you map the acquisition: when it happened, what runoff structure absorbed the book, and whether the original legal entity survived. Then you identify the current claims administrator, which is frequently a TPA layered on top of the runoff portfolio. Then you reconcile any name variations across the filings you have, because the same carrier appears under multiple spellings and the acquisition adds new ones.
Government contracting structure complicates this further. If the employer worked under an IDIQ vehicle, the controlling carrier can depend on which task order governed the work, not the master contract. Sorting that out is its own analysis, covered in depth in our breakdown of which task order controls the carrier under an IDIQ contract. Layer an acquired carrier on top of a task-order question and the manual approach becomes genuinely unreliable.
This is the gap ClaimTrove was built to close. The investigation engine searches 18 federal data sources in parallel, resolves employer aliases and carrier name variations automatically, applies date-scoped group membership, and ranks carriers by their proximity to the actual date of injury. It treats an acquired carrier like SeaBright the way the claim requires: as a date-anchored question, not a name lookup.
Run the employer name and the date of injury through ClaimTrove and the engine reconstructs the carrier of record for that specific claim, surfaces the supporting coverage cards and decisions, and flags where a TPA or an acquisition sits between the document and the responsible entity. Stop guessing whether an old SeaBright policy is still live. Trace it.