A paralegal opens a new file. The LS-203 names the employer as "Reed, Inc.," a logistics support contractor, and the injury happened at a forward operating base in Afghanistan. The claimant drove a fuel and supply truck on convoy runs. The first task looks routine. Find the DBA insurance carrier so the claim can be filed against the right policy.
It is not routine. Search the DOL case summaries and the name splinters into half a dozen spellings. Search the federal award databases and the results shift depending on which name you type. The claimant remembers the truck, the base, and the fuel runs. He does not remember the corporate entity that signed the government contract.
This is the daily reality of Reed Incorporated as a DBA employer profile. The work is real, the injuries are documented, and the paper trail is fragmented across federal systems that never agreed on a single name. This article walks through what the records show about Reed. It maps where the fuel and logistics support crews sit in the coverage chain, and why the carrier answer is harder than it looks.
What Kind of Work Does Reed Incorporated Do Overseas?
Reed Incorporated appears in federal records as an overseas logistics and support contractor. The Department of the Army is the awarding agency behind most of its recorded presence. That places Reed in the same operational space as the large base-support and sustainment primes that ran the wars in Iraq and Afghanistan.
Fuel and logistics support is a broad category. It covers convoy drivers hauling fuel and supplies, warehouse and yard crews, equipment maintainers, and the local nationals who load and move cargo. These are the roles that generate DBA claims. A driver on a fuel run faces roadside blast risk, vehicle rollovers, and the same combat-zone hazards a soldier faces.
Reed's footprint in the records is consistent with subcontracted support work rather than a single flagship prime contract. That distinction matters. It changes where you look for the carrier and which contract clause put the DBA policy in place. The work is dangerous, the coverage is mandatory, and the entity that bought the policy is not always the entity on the injured worker's badge.
For an attorney, the practical takeaway is to treat Reed as a support contractor first and a name second. The role your client held, driver, mechanic, or yard crew, tells you which contract and which policy tier are in play. Reed's records reward that approach and punish a name-only search.
Why Does Reed Show Up Under So Many Names in DBA Records?
ClaimTrove's DOL case-summary data records Reed under at least six distinct spellings. "Reed, Inc." appears alongside "Reed Inc," "Reed Inc.," "Reed, Inc," a bare "REED," and "Reed International Inc." Each spelling is tracked as a separate line by the Department of Labor.
This is not a clerical footnote. It is the core of the problem. Several of these spellings each carry hundreds of recorded DBA cases in the cumulative 2001 to 2024 totals. One variation, "Reed, Inc.," carries 35 death claims by itself. If you search only the exact name on the LS-203, you miss the other five buckets of history.
There is a second trap. "Reed, Inc." and "Reed International Inc" may or may not be the same corporate entity. Assuming they are one company, or assuming they are two, both carry risk. Sorting that out is part of resolving a single employer's many recorded name variations before you ever reach the carrier question. Get the entity wrong and every downstream record you pull belongs to the wrong company.
What Do Reed's Death Claims Reveal About the Risk Profile?
Fuel and logistics support is one of the deadliest jobs in a war zone. Convoy drivers move slowly on fixed routes, which makes them targets. Fuel is flammable cargo, so a single strike can turn an accident into a fatality. The claim numbers reflect that reality.
The 35 death claims tied to the Reed, Inc. spelling are not spread thin across a giant workforce. They are concentrated in a support contractor whose crews ran roads and yards in a combat theater. For a claimant attorney, that number signals two things at once. It confirms the work was genuinely dangerous, and it warns that death-benefit claims here are common enough that carriers litigate them hard.
The concentration also shapes the coverage question. A death claim in 2011 and a death claim in 2023 may answer to entirely different insurers, because the underlying contracts and policies turned over in between. That temporal spread is why a Reed carrier answer must always be pinned to a specific injury or death date, not to the company name alone.
Where Do DBA-Covered Fuel and Logistics Crews Actually Sit?
Overseas support work is built in tiers. A large prime holds the government contract. Below it sit subcontractors, and below them sit sub-subcontractors and staffing firms. A fuel truck driver may be paid by a small company three tiers down from the name on the base gate.
The FOIA contractor-presence records for Afghanistan place a Reed entity in exactly this position. Reed appears as a subcontractor under several different primes across separate task orders, all under the Department of the Army. That means the DBA carrier is not automatically the prime's carrier. It flows down through the subcontract, and each tier can carry its own policy.
For an injured worker, the tier matters enormously. The subcontractor's own DBA policy is the primary target for the claim. When you are tracing a subcontractor's insurance up the contract chain, the prime becomes relevant only if the sub was uninsured. Reed sitting as a sub under multiple primes means there is no single upstream policy to point to. The right carrier depends on which task order the worker was actually on.
What Does the Federal Contract Record Reveal and Hide About Reed's Coverage?
Three federal record sets each tell a partial story about Reed, and none of them tells the whole one. Learning what each database can and cannot show is the difference between a fast answer and a dead end.
The overseas contract award data is the first stop for most investigators. For Reed, that data is quiet. A search for Reed among foreign-performance prime awards returns little, which would fool an attorney into thinking Reed had no overseas exposure. That is a false read. The gaps in award data are exactly why reading federal contract award data for a DBA investigation requires knowing what the data structurally omits, especially for lower-tier subcontractors.
The FOIA presence records fill part of that gap. They catch Reed as a subcontractor in Afghanistan even when the prime-award data does not. That corroboration matters because corroborating an Afghanistan contractor's presence through FOIA records can prove your client's employer was in-theater during the relevant window, which is the threshold DBA fact. The case-summary data adds the third layer. It confirms Reed generated real DBA claim volume and real fatalities, but it does not name the carrier.
Why Can't You Just Look Up Reed Incorporated's DBA Carrier?
Put the three record sets together and the carrier still does not appear. The case summaries count claims but list no insurer. The presence records name primes and subs but no policy. The award data is thin for a subcontractor. Nowhere in the public tables does one field say "here is Reed's DBA carrier."
Even if a single record named a carrier, one name would not settle it. Overseas support contracts rebid every few years, and coverage moves with them. Understanding why a contractor's DBA carrier shifts from one period to the next is essential for a company like Reed with claims spanning 2009 through 2024. The carrier for a 2011 fuel-convoy injury is likely not the carrier for a 2023 one.
This is the gap ClaimTrove was built to close. Run Reed Incorporated through ClaimTrove and the engine resolves the name variations, separates the subcontractor tiers, cross-references the presence records, and returns carrier candidates ranked by the injury period. Instead of five name buckets and no insurer, you get a scored shortlist tied to the date that matters.
How Do You Run a Reed Incorporated DBA Carrier Investigation?
Start with the entity, not the carrier. Confirm which Reed spelling matches your client's employer, and decide whether "Reed, Inc." and "Reed International Inc" are one company or two before pulling any coverage history. Everything downstream depends on that decision.
Next, fix the injury date and the task order. Reed's claim history spans more than a decade, so the period controls the answer. Identify the prime your client's crew worked under, because a subcontracted fuel or logistics role changes which policy responds first. Then confirm whether an adjuster's name on a letter is the actual insurer or a third-party administrator standing in for one.
Finally, verify any carrier candidate against the DOL authorized list and the coverage evidence, rather than trusting a single record. Stop guessing which Reed entity your claim belongs to. Run this employer through ClaimTrove to resolve aliases, separate the subcontractor tiers, and pin down the carrier-by-period in one search. Then you can file against the right policy the first time.