A claims examiner sends you a coverage letter naming an insurer you have never heard of. The policy looks legitimate. It has a policy number, effective dates, and a signature block. Your client was injured on an overseas defense contract two years ago, and the carrier on that letter is now the entity you will negotiate against. Before you accept that the letter settles the question, you have to answer something simpler and more important: is this carrier even authorized to write Defense Base Act coverage?
That question trips up experienced practitioners more often than it should. A policy can be issued, premium can be collected, and a claim can be administered for years by an entity that was never on the Department of Labor authorized carrier list. When that happens, the consequences land on the worker. Knowing how to verify a DBA carrier DOL authorized list check is not a clerical step. It is a substantive part of building a clean claim.
The DOL maintains a roster of insurers authorized to write DBA and Longshore coverage. ClaimTrove tracks 637 authorized carriers and cross-references them against more than a million federal records. This article explains what authorization actually means, how to read the list correctly, why an unauthorized policy is a red flag, and the traps that make a simple list check harder than it looks.
What does DOL carrier authorization actually mean?
The Defense Base Act extends Longshore and Harbor Workers Compensation Act coverage to employees working on overseas military bases and public works contracts. Under the LHWCA framework, an employer must secure its compensation liability either by purchasing insurance from an authorized carrier or by qualifying as a self-insurer. The key word is authorized.
The DOL Office of Workers Compensation Programs maintains a list of insurance carriers it has authorized to write this coverage. Authorization is not the same as a state insurance license. A carrier can be licensed to sell workers compensation in forty states and still not be authorized to write DBA coverage federally. The two approvals come from different regulators and mean different things.
Authorization matters because it ties the carrier to the federal compensation system. An authorized carrier has agreed to the DOL reporting requirements, the security and surety obligations, and the jurisdiction of the OWCP district offices and the Office of Administrative Law Judges. When a carrier is on the list, you know the federal machinery applies to it.
There is a separate category to keep straight. Some large contractors are authorized self-insurers, which means no commercial carrier sits behind the policy at all. The employer itself holds the liability. That is a legitimate arrangement, but it changes who you deal with and how you verify the obligation. A self-insured employer will not appear on the carrier list because there is no carrier.
So when you run a verification, you are really asking two linked questions. Is the named insurer on the authorized carrier roster, or is the employer an approved self-insurer? If neither is true, the security behind your client's claim is in doubt.
How do you read the DOL authorized carrier list correctly?
The authorized list looks simple. It is a roster of company names. The trouble starts the moment you try to match a name on a coverage letter to a name on the list, because insurance company names are not stable, clean, or unique.
Three problems show up immediately. First, carriers operate under corporate families. A single insurance group may write DBA coverage through several named legal entities, and only the specific entity that issued the policy is the one that has to be authorized. A parent brand being on the list does not guarantee the subsidiary that signed your policy is. We walk through this in detail in our breakdown of the hidden carrier families where multiple names mean one company.
Second, names drift over time. Carriers merge, rebrand, and get acquired. The entity that issued a 2014 policy may have been absorbed into a different named company by the time you investigate the claim. The historical name might not appear on today's list even though the obligation is perfectly valid.
Third, a third-party administrator is not a carrier. The name on the claim correspondence is frequently a TPA handling administration, not the insurer carrying the risk. TPAs never appear on the authorized carrier list because they do not bear the liability. If you check a TPA name against the carrier roster, you will get a false negative every time. Learning how to spot a TPA versus the actual DBA carrier is a prerequisite to running an accurate list check.
The practical lesson is that a name match is a starting point, not an answer. You need the precise legal entity, the historical name in effect on the date of injury, and confirmation that the administering party is distinct from the insuring party. Get any of those wrong and your verification produces a confident, incorrect result.
How do you match a carrier name to a unique identifier?
Because names are unreliable, the reliable path runs through identifiers. Every authorized insurer carries a NAIC number, a unique code assigned by the National Association of Insurance Commissioners that does not change when the company rebrands. The NAIC number is the single most useful anchor for confirming you are looking at the right legal entity.
When a coverage letter gives you a carrier name but no identifier, your first move is to resolve that name to its NAIC number, then verify the number against authorization records. This is far more dependable than name matching, and we cover the full method in our guide to NAIC number lookup for DBA insurance carriers.
The identifier approach also solves the corporate family problem. Two entities in the same insurance group will have different NAIC numbers. When you anchor on the number rather than the brand, you stop conflating a parent that is authorized with a subsidiary that may not be. You are checking the exact entity that issued the policy.
Identifiers do not solve every problem on their own. You still have to confirm the entity was authorized as of the date of injury, not just today. Authorization status is a point-in-time fact. A carrier authorized in 2012 might have exited the DBA market by 2020, and a carrier active today might not have been authorized when your client got hurt. The number tells you which entity; the date tells you whether that entity was valid for your specific claim.
Why is an unauthorized policy a red flag?
If you check carefully and the named insurer is not on the authorized list, not a known historical name of an authorized carrier, and the employer is not an approved self-insurer, you have found something that needs immediate attention.
An unauthorized policy can mean several things, none of them good for an unsuspecting claimant. It can signal that the employer secured coverage that does not satisfy its DBA obligation, leaving a gap in the security behind the claim. It can signal that the wrong entity is being named in correspondence, which means you may be negotiating with a party that has no legal duty to pay. It can also signal an administrative error that, left uncorrected, delays benefits for months.
The stakes are concrete. If an employer failed to secure authorized coverage, the LHWCA framework exposes responsible parties to direct liability and penalties. That changes your strategy entirely. Instead of negotiating with a carrier, you may be pursuing the employer directly, or analyzing whether a controlling contractor up the chain carried the obligation.
This is exactly the kind of anomaly that belongs on your intake checklist. We catalog the warning signs that should stop an investigation cold in our piece on red flags in DBA investigations. An unnamed or unauthorized carrier sits near the top of that list, because every downstream decision depends on knowing who actually backs the claim.
The flip side is reassurance. When a carrier checks out clean against the authorized roster, you can move forward knowing the federal compensation system applies and the entity you are dealing with has accepted DOL jurisdiction. Verification is not just defensive. It tells you the ground you are standing on is solid.
Where does the carrier name on your paperwork actually come from?
Attorneys often assume the carrier name is settled because a document supplied it. In practice, the name reaching you has passed through several hands, each of which can introduce error. The employer reports coverage. A broker placed the policy. A TPA administers the claim. The OWCP records the security. By the time a name lands on your desk, it may reflect any of those parties rather than the insurer carrying the risk.
This is why a single source is rarely enough to verify a carrier with confidence. Federal contract records, coverage filings, and litigation records each capture the relationship at a different moment and from a different angle. Cross-referencing them is how you separate the real insurer from the administrator and the historical name from the current one. Our overview of how federal contract data reveals DBA carrier information explains why no one record is authoritative on its own.
ClaimTrove was built to collapse this multi-source reconciliation into a single search. It holds 637 authorized carriers, 154,886 coverage filing records, 43,298 prime contract awards, and 5,022 OALJ decisions, plus alias mappings that connect historical and current carrier names. When you run a verification, the system resolves the name to a legal entity, checks it against authorization records, flags TPAs, and surfaces the point-in-time status that matters for your date of injury. Run a free sample investigation to see how a name on a coverage letter resolves to a verified, authorized entity.
What is the verification workflow you should run on every claim?
A reliable check follows the same sequence every time. Start with the name exactly as it appears on the coverage letter or the OWCP correspondence. Do not clean it up or guess at the parent. Capture it verbatim, including any entity suffix.
Next, determine whether that name is the insurer or an administrator. If it is a known TPA, set it aside and keep digging for the carrier behind it. The administrator can help you with claim status, but it cannot answer the authorization question.
Then resolve the insurer name to its NAIC number and to its corporate family. This is where alias and subsidiary mapping earns its keep. You are trying to land on the single legal entity that issued the policy, not the brand it markets under.
Finally, confirm authorization as of the date of injury. Check that the resolved entity appears in DOL authorization records, and that it was authorized during the relevant period rather than only before or after. If the entity is not a carrier at all, confirm whether the employer is an approved self-insurer. If neither holds, you have a red flag that reshapes the case.
This workflow sounds straightforward written out, but every step hides a trap that produces a wrong answer if you skip it. That is the whole point. Carrier verification is not hard because the list is hidden. It is hard because names move, administrators masquerade as insurers, and authorization is a moving target. ClaimTrove exists to run all four steps at once and hand you a verified result instead of a plausible guess. Start a verification and confirm any carrier against the authorized list before you build a strategy on top of it.