Your Claimant Worked on an IDIQ Contract. Now What?
A paralegal pulls up a claimant's employment records and finds a contract number. They search USAspending.gov and discover the number belongs to an Indefinite Delivery, Indefinite Quantity contract with 200+ task orders spanning 25 countries. The employer held this master contract for eight years. The claimant was injured in year five, on a task order in Kuwait.
Which DBA carrier covers this worker? The answer depends on whether the employer purchased one blanket DBA policy for the entire IDIQ, or secured coverage at the task-order level. In many cases, the carrier changed mid-contract as task orders shifted scope, location, and risk profile.
IDIQ contracts dominate federal overseas procurement. ClaimTrove's contract award data includes 10,488 task orders issued under 1,359 distinct parent IDIQ contracts. The Department of Defense alone accounts for 8,848 of those task orders. For DBA practitioners, these numbers translate to a single problem: the master contract number is not enough to identify the carrier. You need the task order.
This article breaks down how IDIQ structures create carrier identification challenges, why the task order number is the critical data point, and how multi-award IDIQs add another layer of complexity to DBA investigations.
How Do IDIQ Contracts Work in Overseas Government Services?
An IDIQ contract is a federal contract vehicle that establishes a ceiling price and a minimum order quantity without committing the government to a specific total purchase. The contracting agency issues individual task orders (for services) or delivery orders (for supplies) against the master contract as needs arise. Each task order specifies the work scope, performance location, period, and funding.
For overseas operations, IDIQs are the preferred vehicle because they give agencies flexibility. A single IDIQ might cover base operations support in Afghanistan, construction management in Iraq, and logistics coordination in Kuwait. Each of those missions becomes its own task order with distinct requirements.
The Federal Acquisition Regulation (FAR) governs how agencies structure these contracts. FAR 52.228-3 requires DBA insurance on contracts involving work outside the United States. That clause appears in the master IDIQ contract. But the practical question for DBA practitioners is whether the insurance obligation flows uniformly across all task orders, or whether each task order triggers its own coverage decision.
The answer varies by contractor and contract structure. Large defense contractors with broad IDIQ portfolios often maintain a single DBA policy covering all work under the parent contract. Smaller contractors, or those with task orders in high-risk locations, may secure separate policies for individual task orders. Some contractors change carriers between task-order periods as their risk profile shifts.
Why Does the Task Order Number Matter More Than the Parent Contract?
The parent IDIQ contract number (the PIID in federal procurement terminology) identifies the umbrella agreement. The task order number identifies the specific work a claimant performed. For DBA carrier tracing, the task order is the more useful data point for three reasons.
First, task orders define the actual work location. A parent IDIQ might list the contractor's home office as the place of performance. The task order specifies that the work happens at Bagram Airfield or Camp Arifjan. Since DBA coverage is location-dependent, the task order's performance location determines whether the Defense Base Act even applies.
Second, task orders have their own performance periods. An IDIQ might run for ten years. A task order under that IDIQ might last 18 months. The DBA policy in effect during the task order's period is what covers the worker. If you only have the parent contract dates, you cannot narrow down which policy year applies. Understanding how to read USAspending data for task-order-level detail is essential to this process.
Third, task orders carry their own funding and sometimes their own subcontracting chains. A prime contractor on an IDIQ might subcontract portions of individual task orders to different companies. The subcontractor's DBA carrier is separate from the prime's. Without the task order number, you cannot trace the subcontracting chain to the correct employer and carrier.
What Happens with Multi-Award IDIQ Contracts?
Multi-award IDIQs add a significant complication. Under a multi-award IDIQ, the government awards the same master contract to multiple prime contractors. When a task order comes up, those primes compete for it. The winner performs the work under their own contract terms and their own DBA policy.
ClaimTrove's contract data shows parent contracts with up to three distinct prime contractors receiving task orders under the same PIID. This means the same master contract number can lead to completely different employers and completely different carriers depending on which task order you examine.
Major programs like LOGCAP operate as multi-award IDIQs. Multiple contractors hold LOGCAP positions simultaneously, each with their own DBA insurance arrangements. A claimant who says they worked on "the LOGCAP contract" has given you the program name but not the task order, contractor, or carrier. You need to drill down further.
The Department of Defense is the largest issuer of IDIQ task orders for overseas work. DOD's procurement structure relies heavily on multi-award IDIQs for everything from IT services to base operations. Each task order competition produces a winner with its own insurance arrangements. The master contract tells you who could have performed the work. The task order tells you who actually did.
How Do You Trace the Carrier from a Task Order Number?
Start with the task order number, not the parent contract. If your claimant or their employer can provide the specific task order, you can search federal procurement databases to identify the performing contractor, the performance location, and the contract period. Those three data points significantly narrow carrier identification.
Federal procurement records on USAspending.gov distinguish between base IDIQ awards and individual task orders. Each task order has its own entry with a unique PIID and a parent PIID linking it to the master contract. The FPDS data system provides even more granular detail, including the specific contracting office and place of performance codes.
Once you have the task order's contractor and performance period, the carrier search becomes a standard DBA investigation. You check whether the employer held a blanket policy or a task-order-specific policy. You verify whether the work location fell under any agency mandatory carrier program. You cross-reference FOIA database results and DOL filings for that employer during that period.
The challenge is that many claimants do not know their task order number. They know the employer name, the country, and the approximate year. From there, an investigator must work backward through procurement records to identify which IDIQ and which task order applied. With 10,488 task orders across 1,359 parent contracts in ClaimTrove's data alone, this is not a quick manual search.
ClaimTrove's contract award data distinguishes between base IDIQ awards and individual task orders, enabling you to search by employer name and narrow results to the specific task order that controls DBA coverage. Search ClaimTrove for your employer's specific IDIQ task order to identify the carrier.
What Are the Most Common IDIQ Pitfalls in DBA Investigations?
The first pitfall is treating the parent contract number as the answer. Attorneys sometimes find the IDIQ contract number, identify the prime contractor, and assume that contractor's current DBA carrier is the right one. But if the claimant worked under a task order from five years ago, the carrier may have been different. Carriers shift every few years for most large contractors.
The second pitfall is ignoring multi-award structures. If you find the parent IDIQ and see a contractor name, you might assume that contractor performed all work under the contract. On a multi-award IDIQ, that is wrong. Multiple contractors share the same parent PIID. The task order determines which one actually employed your claimant.
The third pitfall is confusing task orders with modifications. Contract modifications (mods) amend existing task orders. They change funding, extend periods, or adjust scope. A modification is not a new task order. If you see a long list of modifications under a task order, the original task order number is still the controlling document for DBA purposes.
The fourth pitfall is overlooking subcontracting. An IDIQ prime contractor may subcontract entire task orders. The subcontractor carries its own DBA policy. If your claimant was a subcontractor employee, the prime's carrier is irrelevant. You need the sub's task order relationship and the sub's insurance arrangements.
Each of these pitfalls adds time to an investigation. Getting the task order right at the start saves hours of dead-end research later. Run your employer through ClaimTrove to identify task-order-level contract data and trace the correct DBA carrier.