You get a single PDF from opposing counsel. It is the declarations page of a Defense Base Act policy covering a logistics contractor in Kuwait. Five company names appear on it. One sits in the top-right box. One signs the bottom. One shows up under a "produced by" line. One is buried in a claims-handling endorsement. Your job is to figure out which of these five entities you actually file against, name in the LS-203, and serve with notice.
This is where most carrier identification goes wrong. The largest name on the page is often the broker. The name handling the adjuster's emails is usually a third-party administrator, not the insurer. The entity that actually owes the indemnity and medical benefits, the carrier on the risk, can be the smallest line item on the document. Knowing how to read a DBA insurance policy declarations page carrier section is the difference between filing against the right party and chasing a mailroom for eighteen months.
The Defense Base Act borrows its claims machinery from the Longshore and Harbor Workers' Compensation Act. That means the same policy structure, the same endorsements, and the same cast of intermediaries you see in domestic longshore work. The complication is that overseas contracting layers broker, managing general agent, and TPA relationships on top of a carrier that may itself be a subsidiary of a larger insurance group. This article walks each line of the dec page and shows you how to separate the carrier from everyone else standing near it.
What does a DBA declarations page actually show you?
The declarations page, the "dec page," is the first page of the policy. It is the summary sheet. Insurers issue it on a standardized ACORD-style or carrier-branded form, and it compresses the entire contract into a handful of labeled boxes. Read it like a form, not like prose. Each box has a fixed meaning, and the meaning does not change because a different name sits inside it.
You will typically find six elements. The named insured is the employer buying the coverage. The policy number is the unique identifier you will cite in every filing. The policy period gives the effective and expiration dates, which matter enormously because carriers rotate. The carrier or "company" block names the insurer on the risk. The producer line names the broker. And one or more endorsements modify the base policy, including the all-important DBA coverage endorsement.
The carrier block is what you came for. On a Longshore-style policy it usually reads "Company" or "Insurer" and sits in the upper portion of the page. This is the entity that applied to the DOL on Form LS-272 to become an authorized Longshore/DBA insurer, that the DOL lists as an approved DBA carrier, and that is financially liable for benefits. (The LS-570 is a related but distinct form, the carrier's report of issuance of a specific policy for a specific employer, filed after the carrier is already authorized.) When the SME-confirmed records behind ClaimTrove normalize a coverage match, this is the name they normalize to, never the broker and never the administrator.
The policy period deserves a second look. DBA policies are annual. A contractor working a multi-year LOGCAP task order may sit under three or four different carrier years across one deployment. Reading a single dec page tells you the carrier for that period only. If your client's injury date falls outside the policy period printed on the page in front of you, you are holding the wrong dec page. This temporal problem is exactly why identifying the correct DBA carrier for a claim requires matching the injury date to the right policy year, not just the right employer.
How to read a DBA insurance policy declarations page carrier block versus the broker line
The broker is the easiest entity to mistake for the carrier, because brokers put their name everywhere. They produce the policy, they brand the binder, and on retail accounts they often have larger logos than the insurer. But a broker takes on zero claim liability. They are a sales and placement intermediary.
Find the "producer" line. ACORD forms label it explicitly: "Producer," sometimes "Agent" or "Broker of Record." This is the brokerage that placed the coverage. In the overseas DBA market you will see names like Aon, Marsh, Gallagher, Lockton, and specialty DBA brokers. None of them are carriers. They never appear on the DOL authorized-carrier list as insurers, because they do not write insurance.
Here is the tell that resolves it fast. The carrier has an NAIC number; the broker does not. Every authorized insurer carries a five-digit National Association of Insurance Commissioners code. If a name on the dec page has an NAIC number printed beside it, that name is the carrier. If it does not, and it sits on the producer line, it is the broker. Running a NAIC number lookup on the names on the dec page is the single cleanest way to separate the insurer from everyone else on the document.
One trap to watch. Some large brokers operate affiliated managing general agents, or MGAs, that underwrite on behalf of a carrier. An MGA name can look like a carrier and can appear in an underwriting block. But the MGA still is not the party on the risk. The paper sits with the insurer whose NAIC number appears in the company block. The MGA holds binding authority, not liability. When in doubt, follow the NAIC number, because liability follows the paper, and the paper follows the licensed insurer.
Where does the third-party administrator hide on the page?
The TPA is the entity that will email you, send the adjuster's letters, and run the claim day to day. It is also the entity attorneys most often mistake for the carrier, because the TPA is the only name they ever actually talk to. The TPA does not pay benefits from its own balance sheet. It administers claims under contract to the carrier.
The TPA rarely appears in the carrier block. Look instead in the claims-handling endorsement, a "claims contact" or "notice of claim" box, or sometimes a separate claims-administration page attached to the policy. The language reads something like "claims to be administered by" followed by the TPA name. In the DBA and Longshore world the recurring administrators are well known across the industry: ESIS, Gallagher Bassett, Broadspire, Sedgwick, Crawford, and Helmsman. Seeing one of these names should immediately flag "this is the administrator, find the carrier behind it."
The reason this matters legally is straightforward. You serve notice and file claims against the carrier, the party authorized by the DOL and liable for benefits. Serving the TPA's claims office is not the same as identifying the insurer on the risk. The administrator can change mid-policy, and a new TPA does not change who owes the money. We cover the mechanics of this distinction in depth in our guide to spotting a TPA versus an actual DBA carrier, including the language patterns that signal administration rather than risk-bearing.
There is a further wrinkle worth knowing. The relationship between a given TPA and the carrier it administers for is not fixed across the industry. The same administrator handles claims for several different insurers, and the pairing on any specific policy depends on the contract behind that policy. Industry-level patterns exist and are publicly discussed, and our breakdown of how ESIS, Gallagher Bassett, and Broadspire operate in DBA claims lays out the common pairings. But knowing the general pattern is not the same as confirming which carrier sits behind the TPA on the policy in your hand. That confirmation comes from the dec page itself, cross-checked against the record.
Why does the carrier name on the page still not settle it?
Suppose you have done everything right. You found the company block, confirmed the NAIC number, ruled out the broker on the producer line, and identified the TPA in the claims endorsement. You have a carrier name. You are still not finished, and here is why.
The carrier name on a dec page is frequently a subsidiary, not the parent group most people recognize. A policy will not say "AIG." It says "Insurance Company of the State of Pennsylvania" or "National Union Fire Insurance Company." Both are AIG entities. A Chubb policy reads "ACE American Insurance Company." A policy in the Zurich family might name any of several subsidiaries with different legal names. The coverage card records behind ClaimTrove had to normalize more than two thousand raw carrier name variations down to a few hundred canonical names precisely because of this fragmentation.
This is where subsidiary structure quietly defeats a clean read. Zurich alone illustrates the problem; we trace it in our piece on how Zurich's subsidiaries and name variations complicate carrier identification. If you treat the literal name on the dec page as the answer without resolving it to its carrier group, you may miss that two policies you are comparing are actually the same insurer under two different subsidiary names.
The other unresolved question is verification. A dec page tells you what the policy said it covered. It does not, by itself, tell you whether that named carrier matches the carrier of record in the DOL's filings, the OALJ decision parties for that employer, or the FOIA coverage card on file. Those are independent evidentiary sources. When they agree with the dec page, you have a defensible answer. When they conflict, the dec page in front of you may be stale, may be the wrong policy year, or may have been superseded. ClaimTrove's investigation engine searches eighteen federal data sources in parallel to surface exactly those corroborating or conflicting records.
What is the right workflow for reading a dec page in practice?
Work the page top to bottom in a fixed order, the same way every time. Consistency is what prevents the broker-for-carrier mistake on a tired Friday afternoon.
First, confirm the named insured matches your client's employer of record, accounting for subsidiaries and DBA names. Overseas contractors file under entity names that rarely match the brand. KBR work appears under Service Employees International, Inc. Second, lock the policy period against your client's injury date. If the date does not fall inside the period, stop and find the correct year's dec page. Third, isolate the company block and pull the carrier name plus its NAIC number. Fourth, identify the producer line and label it broker. Fifth, scan the endorsements for the claims administrator and label it TPA.
Then do the step the dec page cannot do for you. Cross-check the carrier name against the actual record. Knowing how to read a DBA insurance policy declarations page carrier block gets you a candidate answer; confirming it against DOL filings, OALJ decision parties, and FOIA coverage records gets you a defensible one. The structure of the DBA market, with its layered brokers, MGAs, administrators, and subsidiary carriers, is genuinely hard to read from a single document, which is the whole reason a verification step exists.
That is the gap ClaimTrove closes. You can confirm whether the named carrier on a given employer's dec page matches the confirmed records before you commit it to a filing. Run the employer and injury date through the investigation engine, and it returns the carrier the evidence actually supports, the subsidiary-to-group resolution, the TPA relationship, and the source citations behind each. The dec page gives you a name. ClaimTrove tells you whether to trust it. Run your first investigation free and cross-check a dec page against the confirmed carrier record before it costs you a deadline.