What Is a Mandatory DBA Insurance Contract?
Most DBA insurance works like any other commercial insurance market. Employers shop for coverage, compare carriers, and buy a policy. The employer picks the carrier.
But for certain federal agencies during certain time periods, the government picked the carrier instead. These agencies awarded single-source contracts requiring all their contractors to obtain DBA insurance from one designated carrier. No shopping. No alternatives. If you worked on that agency's contracts, your DBA coverage came from one place.
These mandatory arrangements are some of the most useful data points in DBA carrier identification. If you know the funding agency and the contract period, you may be able to identify the carrier without searching any other source. But only if you know the exact dates, which most practitioners do not.
Why Did Agencies Create Mandatory Carrier Programs?
The history starts with a problem. In the early years of large-scale overseas contracting, DBA insurance was expensive, inconsistently available, and poorly administered. Contractors working in conflict zones had trouble finding carriers willing to write DBA coverage at reasonable rates. Claims administration was fragmented across dozens of carriers with varying levels of competence.
Federal agencies, particularly those managing large contractor workforces overseas, saw an opportunity to consolidate. By awarding a single DBA insurance contract, the agency could negotiate better rates through volume, ensure consistent claims handling, and simplify oversight. The contractor got coverage as a pass-through cost on their government contract rather than shopping the open market.
A 1990 Office of Inspector General audit of one major agency's contractor insurance practices helped catalyze the first mandatory program. The audit found inconsistent coverage, gaps in documentation, and difficulty verifying that contractors maintained required DBA insurance. A single-carrier mandate addressed all of these problems.
Which Agencies Had Mandatory DBA Carrier Programs?
Three federal agencies operated mandatory DBA insurance programs during the period most relevant to current claims. Each program had distinct start and end dates, and each involved different carriers.
State Department: The State Department ran the longest mandatory DBA program. It began in 1991 with a contract awarded to CIGNA, which held the mandate through 2001. When that contract expired, CNA won the recompetition in a process that drew four bidders. CNA held the State Department mandate from July 2001 through July 2012. After CNA's contract ended, the State Department attempted to re-solicit but received zero bidders. Since August 2012, State Department contractors have obtained DBA coverage on the open market. For context on how the economics of DBA insurance drove these market dynamics, see our analysis of DBA insurance premium trends since 2010.
USAID: The U.S. Agency for International Development has maintained a mandatory DBA carrier program since March 2010, when it awarded a contract to Allied World (AWAC). This mandate has been renewed through successive Acquisition and Assistance Policy Directives. The current contract, issued under AAPD 22-01, runs through March 2027. USAID contractors during this entire period, from 2010 to present, have been covered by Allied World. The program used AON as the insurance broker.
U.S. Army Corps of Engineers (USACE): USACE operated a mandatory DBA program from December 2005 through September 2013. CNA held this contract under agreement W912HQ-11-D-0004, with Rutherfoord (later acquired by Marsh McLennan) serving as broker. When the Joint Contracting Command-Iraq/Afghanistan (JCC-IA) was established, its contractor coverage was folded into the existing USACE program rather than creating a separate mandate. The USACE program ended on September 30, 2013, and was not renewed. After that date, USACE contractors returned to the open market, where rates reportedly doubled.
Why Are These Mandates Time-Bounded?
A common misconception is that agency DBA mandates are permanent. They are not. Every mandatory program has specific start and end dates tied to a contract vehicle.
The State Department program lasted 21 years across two carriers, then ended when no bidders responded to the re-solicitation. The USACE program ran for approximately eight years and was not renewed. Only the USAID program remains active, and it is structured as a series of fixed-term contracts that must be periodically recompeted.
The reasons mandates end vary. For the State Department, the DBA insurance market had evolved enough that the agency believed open-market competition would serve contractors better. For USACE, the drawdown of U.S. military operations reduced the contractor workforce to the point where a single-source mandate was no longer justified.
The time-bounded nature of these programs is critical for carrier identification. An attorney investigating a State Department contractor's claim from 2015 cannot assume the mandatory carrier (CNA) is still on risk. The mandate ended in 2012. Coverage after that date came from the open market, and the employer could have chosen any authorized DBA carrier. Understanding why DBA carriers change over time is essential for investigating post-mandate claims.
What Are the Common Mistakes Attorneys Make With Mandatory Contracts?
The most frequent error is assuming a mandate is still active when it has already expired. This happens because the existence of mandatory programs is relatively well-known in DBA circles, but the specific expiration dates are not. An attorney who knows that "the State Department had a DBA contract with CNA" may assume that relationship still holds, even though it ended over a decade ago.
A second common mistake is applying the wrong agency's mandate. USAID and the State Department are frequently confused in DBA research because they both operate overseas and sometimes share contracting infrastructure. But their DBA insurance programs are completely separate. A USAID contractor is covered by Allied World. A State Department contractor (post-2012) is on the open market. Confusing the two leads to wrong carrier identification.
A third error is assuming the mandate covered all contractor types equally. Some mandatory programs applied only to personal services contractors, not to all contractors working under agency funding. The scope of each mandate is defined in the contract vehicle and associated policy directives.
Finally, some practitioners incorrectly attribute mandatory relationships to agencies that never had them. Not every federal agency with overseas contractors operated a mandatory DBA program. The Department of Defense, for instance, has never had a single-source DBA mandate for all its contractors, despite being the largest employer of overseas contractors by volume.
How Do Mandatory Contracts Interact With the Open Market?
When a mandatory program is active, the designated carrier has exclusive rights to write DBA coverage for that agency's contractors. Employers cannot opt out or choose a different carrier for work performed under that agency's contracts.
However, an employer may have contracts with multiple agencies simultaneously. A large defense contractor might have State Department contracts (mandatory carrier), USAID contracts (different mandatory carrier), and Department of Defense contracts (open market) all at the same time. Each contract may be covered by a different carrier depending on the funding agency.
This means the same employer can have three different DBA carriers in the same fiscal year for different contracts. The carrier identification depends not just on the employer and the date, but on which specific contract the injured worker was performing under.
ClaimTrove's investigation engine checks mandatory contract periods as the first step in every carrier search. If the employer's contract was funded by an agency with an active mandate during the injury period, the system identifies the mandatory carrier with high confidence before searching other sources. Try an investigation to see mandatory contract checking in action.
What Happened When the State Department Mandate Ended?
The end of the State Department's mandatory DBA program in 2012 is a useful case study in how market dynamics shift when a mandate expires.
Under the CNA mandate, all State Department contractors had consistent coverage from a single carrier. Claims administration was centralized. Carrier identification was straightforward: check whether the employer had a State Department contract during the mandate period, and you had your carrier.
After the mandate expired, State Department contractors dispersed across the open market. Different employers chose different carriers. Some changed carriers between contract periods. The relatively simple carrier identification ("State Department equals CNA") was replaced by the same complex multi-source research required for any other agency.
For claims that straddle the transition date, the analysis is especially nuanced. An injury that occurred in June 2012 (during the mandate) would be covered by CNA. An injury in September 2012 (after the mandate ended) could be covered by any carrier the employer chose on the open market.
How Reliable Is Mandatory Contract Data for Carrier Identification?
When applicable, mandatory contract data is among the most reliable evidence for carrier identification. If you can confirm the funding agency, the contract period, and the active mandate dates, you have a near-certain carrier match.
The confidence level is high for several reasons. The data comes from official contract vehicles, not from secondary records that may reference TPAs or incorrect entity names. The carrier relationship is documented in publicly available policy directives and contract awards. And the mandatory nature of the program eliminates the possibility that the employer opted for a different carrier.
The limitation is scope. Mandatory programs covered only a fraction of the total DBA market. The vast majority of DBA coverage, including all Department of Defense contractor coverage, has always been obtained on the open market. Mandatory contract data is a powerful shortcut when it applies, but it only applies to specific agencies during specific time periods.
What Does the Future of Mandatory DBA Programs Look Like?
As of 2026, only the USAID mandatory program remains active, with its current contract running through March 2027. Whether it will be renewed depends on USAID's assessment of the program's cost-effectiveness and the availability of willing bidders.
The trend is away from mandatory programs. The State Department and USACE both allowed their programs to expire. The open market has matured enough that agencies can rely on competitive procurement rather than single-source mandates.
For attorneys handling DBA claims, this means mandatory contract data will become a historical reference rather than a current identification tool. But given that many active DBA claims involve injuries from years or even decades ago, the historical data remains highly relevant. A claim filed in 2026 for an injury that occurred in 2008 under a USACE contract still benefits from knowing that CNA was the mandatory carrier during that period. For a broader view of how these contracts fit into the Afghanistan and Iraq claims landscape, see our data breakdown of who insures DBA contractors in Afghanistan.
ClaimTrove maintains the complete timeline of all known mandatory DBA carrier programs, including the specific carrier, contract vehicle, broker, and effective dates for each program. This data is checked automatically at the start of every investigation, before any other sources are queried. Start an investigation to see whether your case falls within a mandatory coverage period.
How Should You Use This Information in Practice?
For every DBA claim, your first question should be: which agency funded the contract? If the answer is State Department, USAID, or USACE, check whether the injury date falls within a mandatory carrier period.
If it does, you have a high-confidence carrier identification with minimal research. Verify the dates, confirm the agency, and you are done.
If the injury date falls outside the mandatory period, or if the agency never had a mandatory program, proceed with standard multi-source carrier identification. Search OWCP coverage cards, OALJ decisions, DOL case summaries, and contract records.
The key takeaway is that mandatory programs are time-bounded tools, not permanent relationships. They simplify carrier identification for specific windows, but using them outside those windows leads to wrong answers. Always verify the dates.