A paralegal opens a DBA claim and the LS-202 names the employer as "Centerra Group LLC." The injury happened on a federal installation, the worker was a security officer, and the date of injury falls in 2017. Simple, right? Then the broker correspondence comes back referencing a different entity. The contract was held by a joint venture. And the carrier that paid medical bills three years earlier on a sister contract was not the carrier on this one. You are now four moves deep on a single name, and you have not even confirmed coverage yet.
This is the Centerra problem. Centerra Group is one of the largest security and base-operations contractors working federal installations, and its corporate history runs straight through some of the most aliased names in the DBA space. The company you see on a coverage card may not be the company that actually employed the claimant. The carrier may have changed when the contract changed hands. And the joint-venture structure means coverage can split between two parent companies on the same job site.
For a Centerra Group DBA insurance security contractor investigation, the employer name is the start of the work, not the answer. ClaimTrove indexes more than 1 million federal records across 18 data sources precisely because employers like Centerra do not sit still. This article explains what Centerra's footprint looks like, why its DBA exposure is unusually hard to trace, and what you need to resolve before you trust a single carrier name.
Who is Centerra Group and what does it actually do?
Centerra Group LLC provides security services, fire and emergency response, and base-operations support across federal sites. Its lineage traces through Wackenhut Services and G4S Government Solutions, and the brand has lived under multiple corporate owners over the past two decades. Today it operates inside the Constellis corporate family, which is itself one of the most renamed organizations in private security history.
That matters for one reason: a security officer or firefighter injured on a federal base is squarely inside Defense Base Act jurisdiction when the work supports a covered government contract overseas, and inside LHWCA or state coverage when it does not. The employer's contract portfolio, not its logo, decides which regime applies.
Centerra's work clusters into a few recognizable buckets:
- Armed and unarmed security at government installations, national laboratories, and federal facilities
- Fire and emergency services on military and civilian sites
- Base-operations support (BOS), often delivered through joint ventures with engineering and logistics primes
- Protective services on contracts that can shift between domestic and overseas places of performance
Across ClaimTrove's federal contract data, security and base-ops contractors show up under recipient names that rarely match the parent brand exactly. Centerra is no exception. A single company can appear under the legacy name, the current name, and a joint-venture name in the same fiscal year. Each variation may carry its own UEI and CAGE code in the 865,232 SAM.gov entity registrations we index, which means three searches, not one, before you have the full picture.
Private security is also a high-claim sector. The injury patterns that drive DBA volume in security work are well documented in the broader DBA data on private security contractor injury rates, and Centerra's mix of armed posts, response duties, and austere locations puts it in the higher-risk band of that distribution.
Why does Centerra's corporate structure scatter its DBA coverage?
The hardest part of a Centerra investigation is not finding a carrier. It is figuring out which entity the carrier insured, and when.
Centerra sits inside the Constellis umbrella, and Constellis carries one of the deepest alias trails in the industry. ClaimTrove's alias data tracks Constellis across at least six linked names, including Triple Canopy, Academi, Blackwater, and USTC Holdings. When an employer absorbs or sits beside companies with that kind of history, name resolution stops being a formality. We break down the full lineage in our analysis of how five name changes built the most complex DBA carrier trail in history, and Centerra inherits a piece of that complexity by association.
Three structural features make Centerra coverage scatter:
Legacy names. Wackenhut and G4S-era contracts may still surface in older coverage records and decisions. A claim with a long latency period, common in occupational exposure cases, can reach back to a filing under a name the company no longer uses.
Joint ventures. Base-operations contracts are frequently awarded to a joint venture rather than to Centerra alone. A JV like Centerra-Parsons is a distinct legal entity. It can hold its own DBA policy, its own carrier, and its own claims-handling arrangement separate from either parent. A worker may be a Centerra employee on paper while the policy that covers the loss sits with the JV.
Carrier-by-period shifts. Carriers change when contracts are re-competed, when corporate ownership changes, and when agency mandates apply. ClaimTrove data shows most contractors shift carriers every three to five years, so the carrier on a 2014 contract is not a safe assumption for a 2019 injury under the same brand.
This is the same trap that makes large engineering and IT contractors so difficult. The mechanics that make AECOM's 19 name variations the hardest carrier trace in construction apply directly to Centerra: subsidiaries, acquired entities, and JV vehicles each generate their own paper trail, and a search on the parent name alone misses most of it.
How do joint ventures split DBA carrier responsibility?
Joint ventures are where Centerra investigations most often go wrong. A JV exists to bid and perform a specific contract, and for DBA purposes it behaves like its own employer.
Here is what that means in practice. When two companies form a base-operations JV, the partners decide which entity procures DBA insurance and which carrier writes it. That decision is contractual and private. It does not have to match either parent's standing program. So a security officer hurt on a JV-run base might be covered by a carrier that neither Centerra's standalone contracts nor the partner's standalone contracts ever used.
The split creates three live questions you have to answer in order:
- Who was the contract awardee? Centerra alone, the partner alone, or the named JV. The contract record settles this.
- Which entity employed the claimant? The W-2 or assignment may name a parent even when the JV held the contract.
- Which entity procured the DBA policy? This is the carrier question, and it is the one that controls who pays.
Get the order wrong and you can chase a carrier that never had exposure on the loss. ClaimTrove's contract award and subaward data links primes to the entities operating beneath them, and the engine resolves JV names against the federal awardee record rather than guessing from the brand. This is the same disciplined subsidiary-and-split logic that makes carrier work on technology primes so demanding, the kind we walk through in the breakdown of why the SAIC split makes Leidos carrier identification so difficult.
If your Centerra claim involves a JV and you are working from the brand name alone, you do not yet have enough to file with confidence. Resolving the awardee, the employer of record, and the policy holder is exactly the work ClaimTrove automates.
What federal data confirms a Centerra worker's DBA exposure?
Before carrier identification, you confirm jurisdiction. DBA applies when the work supports a covered U.S. government contract performed overseas, on a military base abroad, or under specified agency programs. For a security or base-ops contractor, the place of performance is decisive.
ClaimTrove pulls from several federal sources to establish that footprint:
- Federal contract awards. We index 43,298 overseas prime contract awards with place-of-performance country codes, PIIDs, and labor-standards flags. A "Y" labor-standards flag on an overseas contract is a strong DBA signal.
- Subaward chains. 4,315 subaward records link primes to the companies working beneath them, which matters when Centerra is a sub rather than the prime.
- FOIA contractor records. For Afghanistan-period work, FOIA database results confirm contractor presence, contract numbers, and prime/sub relationships across 2009 to 2018.
- Coverage filings. FOIA-sourced DOL coverage records provide the most direct evidence possible: a filed insurance record tying an employer to a carrier on a specific date.
For security firms specifically, there is an extra layer. Companies that handle defense articles or operate under arms-export rules generate a parallel registration trail, and that trail can corroborate which entity was active on a given contract. We explain how that works in the piece on how ITAR registration creates a carrier paper trail. For Centerra's armed-security lines, those registrations help confirm the operating entity behind a contract name.
Place of performance also tells you whether other statutes stack onto the DBA claim. Work in a designated war-zone country can trigger War Hazards Compensation Act considerations on top of DBA coverage, which changes the reimbursement picture for the carrier. The engine flags those countries automatically so you are not surprised by a WHCA issue late in the file.
How do agency mandates change the carrier answer for base-ops work?
One of the biggest mistakes in security-contractor carrier identification is treating every contract as an open-market policy. Some are not. Certain federal agencies have, during defined periods, required all their overseas contractors to use a single mandated DBA carrier.
When an agency mandate applies, it overrides the contractor's normal program. It does not matter what carrier Centerra used on its other contracts. If the awarding agency mandated a specific carrier for the period in question, that carrier covers the loss. ClaimTrove treats agency mandates as the highest-confidence, deterministic signal in its carrier waterfall for exactly this reason.
The catch is that mandates are time-bounded. They start, they end, and coverage reverts to the open market afterward. A contract performed inside a mandate window and a contract performed two years after it ended can have completely different carriers even under the same agency and the same contractor. The date of injury, mapped to the correct fiscal year, decides which rule applies. We index eight mandatory-agency carrier arrangements with their exact date boundaries, and the engine checks the awarding agency from the contract record against those windows automatically.
This is the kind of determination you cannot make from a brand name and a hunch. You need the contract's awarding agency, the place of performance, the period of performance, and the injury date, all aligned. For a JV-held base-operations contract, you need that for the right entity. Missing any one of these is how attorneys end up naming the wrong carrier in a filing.
For a broader view of which carriers dominate overseas contractor coverage and how that landscape is structured, our data-driven look at who insures DBA contractors in Afghanistan shows how concentrated and how period-dependent the carrier market really is.
Run the Centerra investigation instead of guessing
Centerra Group is a textbook example of why the employer name is the easy part. The company spans legacy identities, sits inside a heavily renamed corporate family, and performs much of its base-operations work through joint ventures that hold their own policies. Layer agency mandates and carrier-by-period shifts on top, and a single Centerra claim can have three plausible carriers depending on the contract, the entity, and the date.
ClaimTrove resolves all of it from one search. Enter the employer, the location, and the date, and the engine resolves Centerra's aliases and JV entities, checks 18 federal data sources in parallel, applies the agency-mandate logic, and ranks carriers by confidence with the source documents attached. You get the entity chain, the period-correct carrier, and the citations to defend it, instead of a name and a guess.
Stop trying to untangle Centerra's structure by hand. Start a ClaimTrove investigation and get the period-correct carrier, the JV split, and the alias chain resolved in seconds. This tool provides information from public DOL records. It is not legal advice. Always verify with primary sources.