Why Is GardaWorld So Hard to Track in DBA Records?
GardaWorld Federal Services is one of the largest private security contractors operating under the Defense Base Act. But if you search DOL records for "GardaWorld," you will miss most of the relevant filings. The reason is straightforward: the company's current form is the product of a 2015 acquisition that merged two distinct corporate histories, each with its own set of DBA filings, carrier relationships, and regulatory footprints.
Before the acquisition, Aegis Defence Services Ltd operated as an independent British private military company founded in 2002. After GardaWorld completed the purchase, the combined entity continued operating under various legal names depending on the contract, jurisdiction, and filing date. The result is a fragmented trail that spans more than two decades of federal contracting records.
For DBA practitioners, this fragmentation is not an academic problem. It directly affects your ability to identify the correct insurance carrier for a given claim period. A claimant who was injured in 2013 working for "Aegis Defense Services" and a claimant injured in 2019 working for "GardaWorld Federal Services LLC" may be dealing with entirely different carriers, even though the corporate entity is arguably the same.
How Many Name Variations Exist in Federal Records?
Our database tracks more than 25 distinct name variations associated with the GardaWorld/Aegis corporate family, making it one of the most extreme examples of the employer alias problem in DBA investigations. These are not theoretical possibilities. Each variation appears in at least one federal filing, DOL record, contract award, or carrier authorization document.
The variations fall into several categories. First, there are spelling differences between American and British English: "Aegis Defense Services" versus "Aegis Defence Services." Federal databases are inconsistent about which spelling they use, and a search for one will not return results for the other.
Second, there are corporate entity distinctions. "Aegis Defence Services Ltd" is the British parent entity. "Aegis Defense Services LLC" is the American subsidiary. "GardaWorld Federal Services LLC" is the post-acquisition domestic entity. "GardaWorld Government Services" appears in some contract modifications. Each of these may have separate CAGE codes, DUNS numbers, and SAM registrations.
Third, there are abbreviations and informal references. "Aegis" alone appears frequently in OALJ decisions and DOL case summaries. Some contract records reference "GardaWorld/Aegis" as a transitional name. Others use "GW Federal Services" or simply "GWFS."
The practical impact is significant. If you search only for the name your client gave you on intake, you are likely seeing a fraction of the available records. Our data shows that searching for just one name variation typically returns less than 40% of the total filings associated with this employer family.
What Happened During the 2015 Acquisition?
GardaWorld, a Canadian-headquartered security firm, completed its acquisition of Aegis Defence Services in 2015. The deal combined GardaWorld's existing security operations with Aegis's substantial portfolio of U.S. government contracts, particularly in Iraq and Afghanistan.
From a DBA perspective, the acquisition created an immediate complication. Existing Aegis contracts continued under their original terms, with their original carrier arrangements. New contracts were issued under GardaWorld entity names. Some contracts were novated (transferred to the new entity), while others ran out their terms under the Aegis name.
This means the 2015-2017 period is particularly messy. During those years, you can find active DBA filings under both Aegis and GardaWorld names for what is functionally the same workforce. The carrier arrangements may differ between these filings. A claimant's rights under the DBA do not change based on the employer's corporate restructuring, but identifying the responsible carrier becomes substantially more difficult.
Our records show that the carrier picture shifted noticeably around the acquisition period. The pre-acquisition Aegis carrier arrangements were not automatically continued for all GardaWorld contracts. Some contracts saw carrier changes at renewal, while others maintained continuity through the transition.
Where Did GardaWorld/Aegis Operate Under the DBA?
The GardaWorld/Aegis footprint spans virtually every major U.S. military and diplomatic operation zone of the past two decades. Afghanistan and Iraq represent the largest concentration of DBA-covered employees, but the company has also operated in Africa, South America, and various other regions where U.S. government contracts require DBA coverage.
In Afghanistan specifically, which was the dominant theater for DBA claims for over a decade, our FOIA database results show substantial contract activity spanning from the mid-2000s through the withdrawal period. The company held contracts with multiple agencies, including the Department of Defense and Department of State. Each agency relationship potentially involves different carrier arrangements.
Iraq operations were similarly extensive. Aegis won a high-profile DOD contract in 2004 for security coordination in Iraq, which was one of the largest private security contracts of the early occupation period. That contract and its successors generated a significant volume of DBA claims.
The geographic scope matters for DBA practitioners because carrier arrangements sometimes varied by theater of operations. A carrier providing coverage for GardaWorld's Afghanistan operations was not necessarily the same carrier covering Iraq operations during the same fiscal year.
How Many Carrier Changes Has This Employer Family Experienced?
Our data identifies multiple distinct carrier relationships associated with the GardaWorld/Aegis employer family across different fiscal years. The exact count depends on how you define the boundaries: whether you treat Aegis and GardaWorld as separate employer lines or as a single continuous entity.
Taking the combined view, we can trace at least four different carrier arrangements spanning from the early Aegis contracts through the current GardaWorld period. Some of these changes correlate with contract rebids, some with the acquisition, and some with standard carrier market dynamics in the DBA space.
The carrier changes are not random. They follow patterns that are common in the DBA market and documented in our analysis of why DBA carriers change over time: carriers entering and exiting the space, premium increases driving employer switching, and acquisition-related insurance restructuring. Understanding these patterns helps narrow the search when you are trying to identify the carrier for a specific claim date.
One pattern worth noting: the pre-2015 Aegis carrier history and the post-2015 GardaWorld carrier history do not always align cleanly. The acquisition itself appears to have been a trigger point for at least one carrier transition.
What About Subcontractors in the GardaWorld/Aegis Network?
Like most large security contractors, GardaWorld/Aegis used subcontractors extensively, particularly for local national employees. These subcontractor relationships create additional complexity for DBA claims.
A claimant may identify their employer as a local subcontractor name, unaware that the DBA coverage obligation flows through the prime contractor relationship. Alternatively, a claimant may know they worked "for Aegis" but technically their employer of record was a subcontractor entity.
Our contract award data shows dozens of subcontract relationships associated with Aegis and GardaWorld prime contracts. Some of these subcontractors have their own DBA coverage, while others are covered under the prime's policy. Determining which arrangement applies requires examining the specific contract terms and the date of injury.
The subcontractor issue is especially acute for claims involving local national employees in Afghanistan and Iraq. These claimants often have limited documentation and may not know the precise corporate structure of their employment. Systematic database searching across the entire GardaWorld/Aegis alias network, including known subcontractors, is frequently the only way to establish the coverage chain.
How Does Alias Resolution Work for GardaWorld/Aegis Claims?
Effective alias resolution for this employer family requires a multi-step approach. First, you need a comprehensive alias list. Our database maintains 25+ validated aliases for the GardaWorld/Aegis family, including historical names, entity variations, and common misspellings found in federal records.
Second, you need to search across multiple data sources simultaneously. A name that appears in DOL case summaries may be spelled differently in USAspending contract records, which may differ again from the SAM.gov entity registration. Cross-referencing across these sources is the only way to build a complete picture.
Third, temporal context matters. If your claim date is 2011, you should be searching primarily under Aegis variations. If your claim date is 2020, GardaWorld variations are more relevant. The 2015-2017 transition period requires searching both.
ClaimTrove automates this alias resolution, searching all 25+ name variations across every data source in a single query. What would take hours of manual searching across multiple federal databases returns results in seconds.
What Are the Common Mistakes Practitioners Make?
The most common mistake is searching for only one name. If a claimant says they worked for "Aegis," the natural instinct is to search for "Aegis" in the DOL database. That search will return results, but it will miss filings under the full legal entity names, the GardaWorld post-acquisition filings, and any filings that use variant spellings.
The second most common mistake is assuming corporate continuity. Just because GardaWorld acquired Aegis does not mean the DBA carrier remained the same. Each contract period needs to be evaluated independently.
A third mistake is overlooking subcontractor relationships. A claimant who worked on an Aegis-managed project may have been technically employed by a subcontractor. The carrier for the subcontractor may be different from the carrier for Aegis/GardaWorld. Failing to investigate the subcontractor layer can lead to filing against the wrong carrier.
Finally, practitioners sometimes fail to account for the geographic dimension. GardaWorld/Aegis operated across multiple theaters with potentially different carrier arrangements. Establishing where the claimant was working, not just when, is critical for accurate carrier identification.
What Should You Do When You Get a GardaWorld or Aegis Claim?
Start by establishing the precise date and location of the injury or last exposure. This determines which corporate entity and which contract period apply. An injury in Iraq in 2012 maps to the Aegis era. An injury in Afghanistan in 2020 maps to GardaWorld.
Next, determine the exact employer name from whatever documentation is available: the LS-202 form, the contract, the claimant's employment records. Then expand your search to include all known aliases for that employer family.
Search DOL records, USAspending contract data, and carrier authorization files for all relevant name variations within the applicable time window. Pay particular attention to the 2015-2017 transition period, where both Aegis and GardaWorld filings coexist.
Check for subcontractor relationships if the claimant was a local national or if the employment documentation is ambiguous. The prime contractor's DBA carrier may be the responsible party even if the claimant was technically employed by a sub.
Document your search methodology. In contested cases, showing that you searched comprehensively across all known aliases strengthens your position on carrier identification issues.
ClaimTrove runs this entire workflow automatically, resolving aliases, cross-referencing data sources, and identifying carrier candidates ranked by confidence score. For a complex employer family like GardaWorld/Aegis, automated investigation saves hours of manual research per claim.