A paralegal opens a new file. The client drove fuel trucks and ran a motor pool at an overseas support site. The paycheck stub says "Serco." The intake form says "Serco Inc." A prior medical authorization letter says "Serco Group." Three names, one worker, and no carrier in sight.
This is the everyday shape of a Serco North America base and mission support claim. Serco Inc. is the North American arm of Serco Group plc, a large services and outsourcing company. It runs a sprawling federal portfolio spanning naval support, air traffic control, training, logistics, and technical services. Some of that work happens on domestic bases. Some of it happens overseas, and that is where the Defense Base Act attaches.
The problem is not that Serco lacks records. The problem is the opposite. The company shows up across federal databases under overlapping names, multiple registrations, and different contract vehicles. Each fragment holds part of the answer. None of them alone tells you which insurance carrier stood behind a specific worker on a specific date.
This Serco North America base mission support services DBA profile walks through where the covered positions sit. It shows what the public record reveals and why the carrier answer resists a single search. The goal is not to hand you a mapping. The goal is to show you why the mapping is hard, so you know what you are up against before you file. Every number here comes from Department of Labor filings and federal contract data, not guesswork.
What does Serco North America actually do on federal contracts?
Serco Inc. is a diversified federal services contractor. Its work covers naval ship lifecycle support, air traffic control services, records and case management, training and simulation, and command and control technical support. Much of this sits under professional and technical services classifications in the federal registry. In SAM.gov, the primary industry code for the main Serco Inc. entities is 541990, All Other Professional, Scientific, and Technical Services.
That classification matters because it tells you what kind of worker files a claim. A Serco DBA claimant is often not a rifle-carrying guard. Instead the client is a technician, a logistics coordinator, an air traffic specialist, or an embedded support staffer. These are exactly the roles that get missed when an attorney assumes DBA claims only involve armed security or heavy construction.
Base and mission support is a broad umbrella. It can include facility operations, equipment maintenance, supply chain coordination, and personnel support at a military installation. When that installation is overseas, the Defense Base Act at 42 U.S.C. 1651 pulls the worker into federal workers' compensation coverage. The job title on the contract rarely says "DBA covered," so you have to reason from where the work happened, not what it was called.
Serco's domestic footprint is large and well documented. Federal enforcement records show dozens of domestic OSHA inspection entries tied to Serco-named employers. Those records are useful for pattern evidence, but they do not establish overseas coverage. OSHA data is domestic only. The overseas exposure lives in a different set of records entirely.
Where do DBA-covered positions sit inside Serco's contract portfolio?
The DBA-covered positions concentrate wherever Serco performs work outside the United States under a federal contract. That includes overseas base operations, contingency logistics, and technical support embedded with deployed forces. It also includes work on installations that are technically domestic but sit outside the continental United States.
This distinction trips up experienced attorneys. A worker on a base in the continental United States usually falls under state workers' compensation. A worker on an overseas installation usually falls under the DBA. The line is not always obvious. The reasoning deserves careful review, which we cover in our breakdown of DBA coverage on US military bases and the CONUS versus OCONUS distinction.
Serco also performs work in zones where the zone of special danger doctrine expands coverage. Under that doctrine, injuries that happen off the clock can still be compensable if the overseas assignment created the risk. A Serco technician injured during downtime at a remote support site may still have a valid DBA claim. That widens the pool of covered positions well beyond the obvious on-duty injury.
The practical takeaway is simple. Do not screen out a Serco claimant just because the job sounds administrative or the injury sounds ordinary. Screen on location and on contract funding. If the work was overseas and federally funded, the DBA analysis starts, regardless of how mundane the role appears on paper.
Why do Serco's name variations complicate carrier identification?
Serco is a textbook alias problem. In the Department of Labor cumulative case summaries covering 2001 through 2024, Serco appears under at least three distinct employer names. "Serco Inc." carries 25 cases. A bare "Serco" entry carries 22 cases. "Serco Group, Inc." carries another 12. These are separate rows in the same dataset, describing what is functionally the same corporate family.
Add fiscal year detail and the picture fragments further. A single FY2013 line for "Serco Inc." shows 11 cases on its own. If you search only the exact name on your intake form, you see a slice of the record and miss the rest. That undercounting can make a real employer look like a small player when it is not.
This is why alias resolution is not an optional step. It is the foundation of an accurate search. The same challenge shows up across the industry, and we explain the mechanics in our guide to alias resolution when the same employer has many different names. Serco is one of the cleaner examples of why searching a single spelling is a mistake.
The federal contractor registry compounds the confusion. SAM.gov lists multiple active Serco entities with different CAGE codes and different states of incorporation, including New Jersey, Delaware, and Virginia registrations. Some similarly named firms in the registry are unrelated companies entirely. Sorting the real Serco entities from name collisions is its own task. The CAGE code is the tool that does it, as we cover in CAGE codes and UEI numbers for DBA employer identification.
What does the federal contract record reveal about Serco's overseas footprint?
The contract record confirms overseas presence but does not hand you a carrier. FOIA database results tracking contractor activity in Afghanistan place Serco-named entities in more than 150 records. Those records show contract numbers, prime and subcontractor relationships, and periods of performance. They prove the company operated in a DBA jurisdiction. They do not name the insurer.
This gap is the heart of every carrier investigation. Contract data tells you the employer was there. It rarely tells you who wrote the policy. Bridging that gap requires cross-referencing several sources at once and weighing them by date and by confidence. ClaimTrove draws on 43,298 prime contract awards and 865,232 federal registry records to build that bridge, but the reasoning matters more than the raw volume.
Serco's profile also resembles other base-operations primes in a telling way. Companies that run large support contracts tend to accumulate claims across many countries and many fiscal years. That pattern shows up clearly in our profile of a comparable prime, Vectrus and V2X as a base-operations contractor whose carrier keeps moving. The lesson transfers directly. A high-volume base-support prime almost never has one static insurer.
When you pull Serco's record, treat each source as a partial witness. A case summary confirms claim volume. A contract award confirms location. A coverage filing confirms an insurer relationship at a moment in time. Only when you stack them and align them on the injury date does a defensible carrier answer emerge.
Why does Serco resist a single DBA carrier answer?
Three forces combine to defeat the one-lookup approach. First, Serco operates through multiple registered entities, so the policyholder name may not match the paycheck name. Second, base and mission support contracts get re-competed and re-awarded, and insurance can change with each new contract period. Third, large contractors shift carriers over time for reasons that have nothing to do with any single claim.
That third force is the quiet one. Carriers change. A worker injured in one year may fall under an entirely different insurer than a colleague injured two years later at the same site. We explain the underlying dynamics in our piece on why DBA carriers change and how temporal shifts reshape coverage. For an employer as active as Serco, the injury date is not a detail. It is the pivot the whole analysis turns on.
There is also the third-party administrator trap. The name on the denial letter is frequently a claims administrator, not the underwriting carrier. Attorneys who name the administrator as the carrier can end up chasing the wrong entity for months. Getting this right early saves enormous time downstream.
This is where a purpose-built investigation earns its keep. Running Serco through ClaimTrove's DBA investigation engine resolves the aliases and aligns contract data to your injury date. It separates administrators from underwriters, so you start with a carrier answer instead of a guessing game.
How should you investigate a Serco DBA claim?
Start with location and date, not the employer name. Confirm where the injury happened and when. Overseas plus federal funding puts you in DBA territory. A domestic continental site usually does not, and that single fact reshapes the entire claim.
Next, expand the employer name into every known variation before you search anything. Do not search "Serco" alone. Include "Serco Inc.," "Serco Group," and any entity-specific names tied to the contract. The DOL case summary fragmentation shown above is proof that a single spelling leaves records on the table.
Then pull the contract identifiers. A contract number, a CAGE code, or a UEI ties the worker to a specific vehicle and a specific period. That specificity is what lets you match a coverage record to an injury date instead of guessing from a company-wide average. Attorneys skip entity verification at their peril. Our walkthrough of SAM.gov entity search for DBA employer verification shows how to do it cleanly.
Finally, weigh your carrier candidates by evidence quality and by date proximity. A coverage filing from the right period beats a statistical guess. A legal decision naming the insurer beats a contract inference. Rank your sources, document your reasoning, and never present an administrator as the carrier. If you want that entire waterfall run for you in seconds, create a ClaimTrove account and let the engine assemble the ranked carrier answer with citations.
This tool provides information from public DOL records. It is not legal advice. Always verify with primary sources.