A paralegal pulls a DBA coverage record and finds the named insurer listed as "Berkley Regional Insurance Company." The injured contractor never heard that name. The retainer letter references a different Berkley unit. The declarations page names a third entity. Every document points at Berkley, yet no two documents agree on which company issued the paper.
This is not a clerical error. It is how W. R. Berkley Corporation is built. The company runs a decentralized structure of many separate operating units. Each unit can issue policies through one of several licensed member insurers. So the name on a Defense Base Act record is one of a small set of specialty writing companies. It is not the parent brand you searched for.
For a DBA attorney or paralegal, that gap between the brand and the writing company is the whole problem. You need the exact legal entity to serve a Notice of Controversion. You need it to confirm authorization and to trace policy history. Guessing "Berkley" is not enough.
This guide explains how Berkley's specialty units surface on DBA policies. It covers which member companies hold federal authorization. It also shows how the assigned-risk side of the business can send you chasing the wrong entity. The specific employer and policy details still live in the record. Knowing what to look for cuts the search from hours to minutes.
Why Does a DBA Policy Show a Berkley Member Company Instead of "W. R. Berkley"?
W. R. Berkley Corporation is a commercial lines insurance holding company founded in 1967 by William R. Berkley. It trades on the New York Stock Exchange under the ticker WRB. Unlike a single-brand insurer, Berkley operates through dozens of semi-autonomous businesses. Each one has its own underwriting focus and its own issuing paper.
The practical result is simple. "W. R. Berkley" is a parent company, not a writing company. You will almost never see that exact name on a DBA declarations page. Instead you see the licensed insurer that issued the policy. That distinction matters because the DOL authorizes specific legal entities. A claim runs against the entity, not the brand.
This pattern is not unique to Berkley. Large groups spread their federal book across member insurers with unrelated names. The same challenge appears with how AIG member companies like National Union Fire appear on DBA policies. The group brand and the named insurer look nothing alike. Berkley simply pushes the decentralized model further than most competitors.
When you find a Berkley entity on a record, treat the name as a clue. It is not the final answer. The next step is confirming which member company issued the coverage. Then you check whether it held Defense Base Act authorization on the date of injury.
Which Berkley Companies Are Authorized to Write DBA Coverage?
The DOL publishes a list of carriers authorized to write coverage under the Longshore and Harbor Workers' Compensation Act and its extensions. The Defense Base Act is one of those extensions. Only a portion of the listed insurers carry DBA authorization. ClaimTrove data puts that DBA-authorized group at 268 carriers. Four of them are Berkley member companies.
According to the DOL authorized carrier list captured in ClaimTrove, four Berkley entities hold Defense Base Act authorization. Each one carries its own authorization date.
- Berkley Casualty Company. Authorized January 28, 1998, the earliest of the four.
- Berkley Regional Insurance Company. Authorized May 16, 2005.
- Berkley National Insurance Co. Authorized December 20, 2010.
- Berkley Insurance Company. Authorized May 1, 2017, the most recent.
All four carry the same set of act codes on the DOL list. DB stands for the Defense Base Act. LS is the Longshore Act. OC is the Outer Continental Shelf Lands Act. NF is the Nonappropriated Fund Instrumentalities Act. That breadth means a Berkley writing company can appear on longshore, maritime, and overseas contractor files alike.
The spread of authorization dates is a tracing signal on its own. A 1998 policy could only have come from Berkley Casualty. The other three had not yet been authorized. A 2016 policy could not name Berkley Insurance Company, which did not gain authorization until 2017. Injury date narrows the field of possible writers before you read a single policy page.
How Does Berkley's Specialty and Assigned-Risk Structure Change Carrier Identification?
Berkley is known across workers' compensation for two very different kinds of business. One is specialty and excess coverage written through its member insurers. The other is a recognized presence on the assigned-risk and residual-market side of state workers' compensation. There, servicing carriers handle policies that the voluntary market declines.
Those two roles look similar on paper and confuse attorneys constantly. A Berkley entity servicing a state assigned-risk plan operates inside a state system. It is not part of the federal DBA framework. The Defense Base Act has no state assigned-risk pool. So a Berkley name tied to a state residual-market program is not the same as a Berkley member company that holds federal DBA authorization.
Reading the act codes and the authorization status keeps these straight. Say the record ties to overseas contract work and names one of the four authorized Berkley companies. Then you are in DBA territory. If it references a state assigned-risk plan or a purely domestic policy, you are probably not. Confirming which entity issued the policy is the same discipline that untangles other groups. It mirrors the broader work behind the carrier family identification problem, where several names resolve to a single group.
This is where a purpose-built investigation pays off. ClaimTrove maps this carrier's employers and policy periods directly from the federal record. You can see which Berkley writing company touched a given contractor and when. That beats guessing from the brand alone.
How Do You Confirm the Exact Berkley Writing Company on a Claim?
Start with the declarations page if you have it. The named insured, the named insurer, and the policy number all live there. The issuing entity is the company you serve and litigate against. Separating the writing company from the broker and the adjuster is a core skill. That is why reading a DBA declarations page correctly deserves its own careful pass.
When the declarations page is missing, work the identifiers. Cross-check the entity name against the DOL authorized carrier list. Confirm DBA authorization on the injury date. Then verify the corporate identity through a NAIC number lookup. That cuts through name variations and confirms you have the right legal entity, not a similarly named affiliate.
Never assume the adjuster on the letterhead is the carrier. A Berkley claim may be handled by an in-house unit or an outside administrator. The servicing entity is often not the insurer at all. Distinguishing the paperwork requires the same instinct that separates a third-party administrator from the actual DBA carrier on any file.
Finally, anchor everything to the date of injury. Berkley's four authorization dates create hard boundaries. They tell you which member company could have written a policy in a given year. Combine that boundary with a coverage record. You can usually name the writing company with confidence.
How Should You Document the Berkley Entity in Your Case File?
Once you identify the writing company, record it precisely. Write the full legal name exactly as the DOL list spells it. Note the authorization date and the act codes next to it. Add the injury date and explain why that date points to this specific Berkley entity. This short note saves you from re-running the same analysis months later.
Precision also protects your pleadings. A Notice of Controversion or a claim caption that names the wrong Berkley company can draw a challenge. Serving Berkley Regional when the policy came from Berkley Casualty is a real error. The four entities are separate corporations with separate authorization histories. Treat them that way in every filing, and confirm the entity against the record before you serve anyone.
What Makes Berkley Harder to Trace Than a Single-Name Carrier?
The core difficulty is that Berkley presents as one brand but writes through many entities. A single contractor can show different Berkley member companies across different policy years. The group can shift which unit holds the account. That is a temporal problem as much as a naming problem.
Federal databases compound it. The employer may appear under several corporate aliases. Each alias can tie to a different Berkley writing company. A name search that stops at the parent brand misses all of them. Before you match a carrier at all, you often have to verify the entity against the DOL list. That confirms it is a real, authorized insurer and not a lookalike.
Decentralization also means no single public page tells you which Berkley unit wrote which contract. The answer is assembled from coverage filings, contract records, and decision parties. Then it is reconciled against the four authorization dates. Doing that by hand for one contractor across a decade is slow and easy to get wrong.
This is where a focused tool earns its place. ClaimTrove pulls the coverage filings, contract awards, and decision records into one investigation. It resolves the employer's aliases. Then it surfaces the specific Berkley writing company and policy period tied to the claim. Run the employer through ClaimTrove and let the record name the entity instead of guessing from the Berkley brand.