Your Client Guarded an Embassy in Baghdad. Now You Need Their Carrier.
A paralegal lands a new DBA claim. The injured worker provided armed security at the U.S. Embassy in Baghdad from 2014 to 2017. The employer field on their intake form reads "Triple Canopy." The paralegal searches DOL records and finds 22 different name variations for companies connected to that employer. Some records reference Constellis Group. Others list Constellis Group/Triple Canopy. A few mention Academi or even Blackwater.
The confusion multiplies when they try to identify the DBA insurance carrier. Was this worker covered under a State Department mandatory carrier arrangement? Did Triple Canopy hold its own commercial policy? Which corporate entity actually employed this person during their injury period? These questions define the daily reality of DBA practice involving the Worldwide Protective Services program.
The WPPS contract is the State Department's largest single vehicle for armed security at diplomatic facilities overseas. It has generated over $5.6 billion in contract awards tracked through USAspending data in ClaimTrove's database. The contractors who hold WPPS task orders face some of the highest DBA risk profiles in the industry: armed personnel operating in active conflict zones, high injury and death claim rates, and corporate structures that change through mergers and acquisitions.
For attorneys handling DBA claims against WPPS contractors, carrier identification requires understanding how the contract itself works, which companies have held task orders across its three major iterations, and how the State Department's shifting DBA insurance requirements affect coverage tracing.
What Is the WPPS Contract and How Did It Evolve?
The Worldwide Protective Services program is a Bureau of Diplomatic Security contract vehicle that provides armed security for U.S. diplomatic personnel and facilities overseas. The program has gone through three major iterations, each restructuring how task orders are awarded and who holds them.
WPPS I launched in the mid-2000s as the State Department's response to escalating security demands in Iraq and Afghanistan. The original contract included companies like Blackwater Security Consulting, DynCorp International, and Triple Canopy. These three firms divided task orders across high-threat diplomatic posts, primarily in Iraq.
WPPS II followed after the 2007 Nisour Square incident involving Blackwater contractors. The State Department restructured the program, and the successor contract saw DynCorp, Triple Canopy, and SOC LLC emerge as the primary awardees. USAspending records show SOC LLC alone received over $803 million in Baghdad embassy security task orders during this period. Triple Canopy's Baghdad protective services awards exceeded $948 million.
WPPS III, the current iteration, began awarding task orders in 2022. ClaimTrove's federal contracting data shows Triple Canopy holding a $450 million Baghdad movement protection task order running through February 2027. GardaWorld Federal Services entered the program with a $356 million Baghdad embassy security force contract. SOC LLC secured a $76 million Jerusalem task order. The competitive landscape shifted again, and with it, the carrier identification challenge grew more complex.
Each WPPS iteration brought new prime contractors, new corporate structures, and potentially new DBA insurance carriers. A worker injured in 2008 under WPPS I faces a completely different carrier landscape than one injured in 2023 under WPPS III. Understanding the State Department's DBA insurance history is the first step in navigating this complexity.
Which Companies Have Held WPPS Task Orders?
Five primary contractors have held significant WPPS task orders across the program's history. Each brings its own carrier identification challenges due to name changes, mergers, and corporate restructuring.
Triple Canopy / Constellis Group: Triple Canopy has been the most consistent WPPS presence, holding task orders across all three program iterations. The company was absorbed into Constellis Group, which also acquired Academi (formerly Blackwater/Xe Services). ClaimTrove's employer alias database tracks this family tree: Constellis maps to at least 6 distinct subsidiaries and predecessors including Triple Canopy, Academi, Blackwater Security Consulting, Blackwater USA, and Xe Services. In DOL records alone, the Constellis/Triple Canopy family appears under 22 different name variations across carrier mapping records.
DynCorp International: DynCorp held WPPS I and II task orders covering protective services in Kirkuk, Irbil, and other Iraqi posts. USAspending data shows $190 million in protective security services and $157 million in personal protective services contracts from the State Department. DynCorp later became part of Amentum through a series of acquisitions. Tracing DynCorp's DBA coverage history requires mapping through its transition from an independent company to an Amentum subsidiary.
SOC LLC: SOC has been a consistent WPPS performer, particularly for Baghdad and Jerusalem posts. Their contract awards total over $1.7 billion in protective services from the State Department. SOC's own corporate history includes a predecessor entity, SOC-SMG, that appears under multiple name variations in federal records. Tracking SOC LLC's DBA insurance carrier history requires resolving at least 9 name variations across DOL filings.
Blackwater / Academi: Blackwater Security Consulting held early WPPS I task orders before losing its State Department contracts. The company rebranded to Xe Services, then Academi, before being absorbed into Constellis. USAspending records show over $742 million in protective services contracts under the Academi Training Center entity alone.
GardaWorld Federal Services: The newest WPPS entrant, GardaWorld secured a $356 million WPPS III task order for Baghdad embassy security starting in late 2022. Their entry introduces yet another carrier tracing variable into the program.
Why Does the WPPS Task Order Structure Create Carrier Tracing Problems?
The WPPS program is not a single contract with a single carrier. It is an indefinite-delivery, indefinite-quantity (IDIQ) vehicle with multiple task orders awarded to different companies for different locations and time periods. This structure creates three distinct carrier tracing problems.
Problem 1: Task orders overlap in time. A single WPPS iteration may have Triple Canopy covering Baghdad movement security while SOC handles Baghdad embassy static guard services. Both are WPPS contracts. Both are State Department awards. But each company maintains its own DBA insurance policy. A claimant who says "I worked WPPS in Baghdad" has not given you enough information to identify the carrier.
Problem 2: Contract transitions create coverage gaps. When WPPS II transitioned to WPPS III, the same physical security posts often changed hands between contractors. A worker who remained at the Baghdad embassy might have been employed by SOC under WPPS II and then by GardaWorld under WPPS III. The injury date relative to the contract transition determines which employer, and therefore which carrier, bears liability.
Problem 3: The State Department's DBA insurance requirements changed over time. During the early WPPS years, the State Department maintained a mandatory carrier arrangement that required all contractors to use a single designated DBA insurer. That program ended. After 2012, WPPS contractors procured their own DBA insurance on the open market. A WPPS claim from 2010 follows completely different carrier tracing logic than one from 2020.
How Do PMC Mergers Compound the WPPS Carrier Problem?
Private military contractor mergers have created some of the most tangled employer family trees in DBA records. The WPPS program concentrates these mergers into a single contract vehicle, amplifying the complexity.
Consider the Constellis family. A worker injured in 2007 might have been employed by Blackwater Security Consulting. In 2009, that same company became Xe Services. By 2011, it was Academi. In 2014, Academi merged with Triple Canopy to form Constellis Group. Each name change potentially involved a new DBA policy, a new carrier, or a new TPA handling claims.
ClaimTrove's database captures this through 110 carrier mapping records across WPPS-related employers. The data reveals multiple carriers appearing across different time periods for the same corporate family. Name variations in DOL filings range from formal legal names to abbreviated versions, slash-separated combinations, and parenthetical clarifications. One OALJ filing references "CONSTELLIS GROUP/TRIPLE CANOPY (OLIVE GROUP)" as the employer. Another lists "CONSTELLIS GROUP and TRIPLE CANOPY." A third simply says "CONSTELLIS."
For attorneys, this means a single search for "Triple Canopy" in DOL records will miss claims filed under Constellis Group, Academi, Blackwater, or any of the 22 name variations in federal databases. Missing even one alias could mean missing the correct carrier identification entirely.
The DynCorp side carries similar complexity. DynCorp International became part of Amentum through acquisitions that also pulled in PAE, V2X, and GIS. A WPPS claim against DynCorp from 2018 might need to be traced through an entirely different corporate entity than one from 2008.
What DBA Risk Factors Make WPPS Claims Different?
WPPS contractors operate in the highest-risk DBA environments. This affects both claim frequency and the stakes of carrier identification errors.
Armed security contractors at diplomatic posts face direct combat exposure, vehicle-borne IED threats, and small arms fire. The DBA claim profile for WPPS workers skews heavily toward traumatic injuries and death claims rather than the occupational disease and repetitive stress injuries common in construction or logistics DBA work. DOL case summary data consistently shows private security employers among the highest-volume DBA claim generators.
The financial exposure for carriers is substantial. WPPS contracts place workers in locations where medical evacuation costs alone can exceed $100,000 per incident. Permanent disability awards for combat-related injuries under the DBA can reach into hundreds of thousands of dollars. Death benefits under the Longshore Act formula, which the DBA incorporates, carry significant ongoing survivor obligations.
This risk profile means carriers have cycled through the WPPS contractor space. Some carriers entered the private security DBA market during the Iraq surge years, then exited when claims experience deteriorated. Others were acquired by larger insurance groups. The result is a carrier landscape for WPPS contractors that shifts more frequently than in lower-risk DBA sectors like base support services or construction.
For practitioners, the elevated risk profile means WPPS carrier identification errors carry outsized consequences. Filing against the wrong carrier on a $500,000 death claim wastes months of litigation time. Getting the date of injury wrong by even a few weeks near a contract transition could mean naming an entirely incorrect employer and carrier.
How Should Attorneys Approach WPPS Carrier Investigations?
Effective WPPS carrier investigations require a structured approach that accounts for the program's unique complexity.
Step 1: Pin down the exact task order. "WPPS" is not specific enough. You need to know which task order, which location, and which contract period. A Baghdad movement security task order is different from a Baghdad embassy static guard task order, even though both fall under WPPS. The claimant's specific job site and duties narrow the field.
Step 2: Resolve the employer name. Use the claimant's pay stubs, W-2 forms, and employment contract to identify the exact legal entity. "Triple Canopy" could mean Triple Canopy, Inc., Constellis Group, or Constellis Holdings, LLC. The legal entity name determines which DBA policy applies.
Step 3: Determine the insurance regime. Was this task order performed during a mandatory carrier period or during the open market era? The answer changes your entire investigation approach. During mandatory periods, the carrier is the same regardless of employer. During open market periods, each WPPS contractor selected its own carrier.
Step 4: Cross-reference multiple data sources. No single federal database contains complete WPPS carrier information. OALJ decisions reveal carrier names from litigation. DOL case summaries show claim volumes. Federal contracting data confirms which companies held task orders during specific periods. FOIA database results provide additional coverage confirmations. The most reliable carrier identifications come from triangulating across multiple sources.
ClaimTrove automates this process by resolving employer aliases, cross-referencing carrier records across 18 federal data sources, and scoring carrier matches by confidence level. For WPPS contractors specifically, the platform traces carrier coverage across contract periods and task orders, accounting for the corporate restructuring that defines this space. Investigate your WPPS contractor's carrier history through ClaimTrove and cut weeks off your carrier identification timeline.