What is FPDS and who maintains it?

FPDS (Federal Procurement Data System) is the federal government's authoritative database for contract award data above the micro-purchase threshold. It is managed by the General Services Administration (GSA) and captures every executive branch contract action within three business days of execution.

Does FPDS contain DBA insurance carrier information?

No. FPDS tracks contract awards, not insurance policies. It records the contractor, awarding agency, place of performance, and contract value. You need separate sources like DOL industry reports, OALJ decisions, and FOIA records to identify which DBA carrier covered a specific contractor.

What is the difference between FPDS and USAspending?

FPDS is the raw procurement data system with granular search over 100 fields. USAspending.gov is a more modern portal that pulls FPDS data and adds visualizations and recipient profiles. USAspending is easier to use but may aggregate some FPDS detail, particularly individual contract modifications.

What FPDS field indicates a contract is DBA-relevant?

The place of performance country code is the primary DBA indicator. If the place of performance is outside the United States under a federal contract, the Defense Base Act almost certainly applies. The labor standards field and Product Service Codes starting with R, S, or J also signal DBA-relevant work.

What is a PIID in FPDS?

A PIID (Procurement Instrument Identifier) is the unique contract number assigned to each federal award. PIID formats vary by agency. For example, W912HQ prefixes indicate USACE awards. The PIID is the primary key for tracking a specific contract across base awards and modifications.

Why does one contract show dozens of records in FPDS?

Each contract action generates a separate FPDS record. The base award (Action Type A) is the original contract. Every modification for additional funding, period extensions, scope changes, or option exercises creates another record. A five-year service contract commonly has 30 or more modification records.

How far back does FPDS data go?

FPDS has tracked contract awards since fiscal year 2004. Data before FY2004 is less reliable or unavailable in the system. For injuries predating 2004, investigators should use archived procurement records, OALJ decisions, or FOIA requests instead.

Can FPDS show subcontractor relationships?

FPDS only tracks prime contract awards directly. Sub-award data comes from the Federal Subaward Reporting System (FSRS) and is accessible through USAspending. However, sub-tier relationships beyond the first level are generally not reported, which is a significant gap for DBA investigations.

What is the difference between an IDV and a task order in FPDS?

An IDV (Indefinite Delivery Vehicle) is an umbrella contract that sets terms and conditions. Task orders (or delivery orders) are issued against the IDV for specific work. The IDV may show a domestic place of performance while its task orders show overseas locations like Kuwait or Afghanistan.

FPDS Contract Data: Find DBA Carrier Details in Federal Records

Your Claimant Worked Overseas, but the Employer Won't Name the Carrier

A paralegal calls your office. The claimant was injured at Camp Arifjan in Kuwait while working for a subcontractor. The employer's HR department claims they "don't have that information." The claimant's supervisor left the company two years ago. The only document you have is a pay stub with a contract number fragment.

That contract number fragment is more valuable than you think. It points to FPDS, the Federal Procurement Data System, which is the federal government's authoritative record of every contract action. FPDS captures the awarding agency, the contractor, the place of performance, the contract value, and the NAICS code that describes the work. For DBA practitioners, FPDS data answers the threshold question: was this work performed overseas under a federal contract?

The challenge is that FPDS was built for procurement officers, not attorneys. The interface assumes you already understand the difference between a base award and a modification, or why a single contract might have 47 separate action records. This guide breaks down the FPDS fields that matter for DBA carrier investigations, how to access them, and what to do with the data once you find it.

What Is FPDS and What Data Does It Actually Contain?

FPDS, managed by the General Services Administration, is the single authoritative source for federal contract award data above the micro-purchase threshold (currently $10,000). Every executive branch agency must report contract actions to FPDS within three business days of execution. The system has tracked awards since fiscal year 2004, giving DBA investigators two decades of searchable procurement history.

Each FPDS record contains dozens of fields. For DBA investigations, these are the ones that matter:

PIID (Procurement Instrument Identifier): The unique contract number. This is the thread that connects a claimant's work assignment to a specific federal award. PII formats vary by agency. A PIID like W912HQ-11-D-0004 tells you it was awarded by USACE (W912 prefix).
Referenced IDV PIID: The parent Indefinite Delivery Vehicle. Many overseas service contracts are task orders under a larger IDIQ vehicle. The parent PIID links the specific task order to the umbrella contract, which may carry the FAR 52.228-3 DBA insurance clause.
Place of Performance (Country and State): The single most important field for DBA. If the place of performance is outside the United States, the Defense Base Act almost certainly applies. FPDS records this as a country code (e.g., KWT for Kuwait, AFG for Afghanistan, IRQ for Iraq).
Awarding Agency and Sub-Agency: Identifies which federal entity awarded the contract. This matters because certain agencies historically maintained mandatory DBA carrier programs. Knowing the awarding agency narrows the carrier search significantly.
NAICS Code: The North American Industry Classification System code describes the type of work. Codes in the 561000-561999 range (administrative and support services) and 236000-238999 (construction) are the most common in DBA-relevant overseas contracts.
Award Date and Period of Performance: The start and end dates establish when the contractor was obligated to maintain DBA coverage. Carriers change over time, so the injury date must fall within the contract's active period.
Total Obligated Amount: Contract value helps distinguish between prime and subcontract relationships. A $2 million task order under a $4 billion IDIQ vehicle (like LOGCAP) tells you the claimant worked under a massive program with well-documented carrier relationships.

FPDS also records set-aside types (8(a), HUBZone, SDVOSB), which can indicate smaller contractors that are more likely to carry their own DBA policies rather than falling under a prime contractor's blanket coverage.

How Do You Access FPDS Data for DBA Research?

There are three primary access points, each with trade-offs for DBA investigators:

FPDS.gov (fpds.gov/ezsearch): The native interface offers the most granular search capability. You can query by PIID, contractor name, awarding agency, place of performance country, NAICS code, and date range. The "EZ Search" mode handles basic lookups. The "Advanced Search" mode exposes over 100 filterable fields. The downside: the interface was designed in the mid-2000s and shows its age. Results export as XML or CSV, not formatted reports.

USAspending.gov: This is the more modern, user-friendly portal that pulls FPDS data (among other federal spending datasets). USAspending adds geographical visualizations and recipient profile pages that group all awards by contractor. The trade-off is that USAspending aggregates some FPDS detail. You may not see individual contract modifications, which can matter when tracking carrier changes mid-contract.

USAspending API: For bulk research, the API at api.usaspending.gov exposes FPDS-sourced contract data programmatically. ClaimTrove's own database of 43,298 overseas contract awards was built from this API, filtered to DBA-relevant foreign places of performance. The API returns JSON with full FPDS field detail, including the labor standards flag that indicates DBA applicability.

For a single-claimant investigation, FPDS.gov or USAspending.gov works fine. When you need to research an employer's full contracting history across multiple agencies, or trace subcontract chains back to their prime awards, the manual approach breaks down quickly.

What Is the Difference Between Base Awards, Modifications, and IDV Orders?

This is where most attorneys get lost in FPDS data. A single federal contract does not produce a single FPDS record. It produces many, sometimes dozens.

Base Award (Action Type "A"): The initial contract action. This is the "birth certificate" of the contract. It establishes the contractor, the scope, the place of performance, and the initial obligated amount. For DBA purposes, the base award confirms that a contractor was working overseas under a federal contract.

Modifications (Action Types "B" through "H"): Every change to the original contract generates a new FPDS record. Additional funding, period extensions, scope changes, and option exercises all appear as modifications. A five-year service contract might have 30 or more modifications. Each modification can change the place of performance or extend the period, which is critical for matching an injury date to active coverage.

IDV Orders: Indefinite Delivery Vehicles are umbrella contracts. The actual work happens under task orders (also called delivery orders) issued against the IDV. When you search FPDS for a contractor like a major DOD service provider, you will often find the IDV (the parent) and dozens of task orders beneath it. The task orders carry the specific place of performance and period details.

Here is why this matters for DBA investigations: the base IDV might show a domestic place of performance (the contractor's headquarters), while the task orders beneath it show Kuwait, Iraq, and Afghanistan. If you only look at the parent contract, you might incorrectly conclude the work was domestic. Always drill into the task order level.

Which FPDS Fields Reveal DBA-Relevant Information?

Beyond the core fields listed above, several FPDS data points serve as DBA indicators:

Labor Standards (Field: labor_standards): When this field shows "Y" (Yes) or "DBA" (Davis-Bacon Act, which shares an abbreviation with Defense Base Act), it indicates the contract includes labor standards provisions. While this field technically refers to Davis-Bacon prevailing wage requirements, overseas contracts flagged with labor standards provisions frequently also carry DBA insurance requirements.

Extent Competed: Sole-source contracts (not competed) versus full-and-open competition can indicate the type of contractor. Emergency sole-source awards in conflict zones often went to the same handful of large defense contractors whose carrier relationships are well documented.

CAGE Code: The Commercial and Government Entity code is a five-character identifier assigned to every entity doing business with the federal government. CAGE codes persist even when companies rebrand or merge. When an employer's name doesn't match your records, the CAGE code can resolve the corporate identity and connect it to historical carrier data.

Product or Service Code (PSC): These four-character codes describe what the government bought. Codes starting with "R" (professional, administrative, and management support services), "S" (utilities and housekeeping), and "J" (maintenance and repair) are common in overseas base operations contracts where DBA claims arise most frequently.

Country of Origin vs. Place of Performance: These are different fields. Place of performance tells you where the work happened. Country of origin tells you where the product was manufactured. For service contracts (the bulk of DBA-relevant work), place of performance is the field you need.

How Do You Build a DBA Investigation From FPDS Data?

Once you have the relevant FPDS records, the investigation follows a specific sequence.

Start with the contract number. If your claimant has any documentation, a pay stub, a badge, an onboarding packet, look for a contract number or PIID. Search that number in FPDS or USAspending. The result gives you the prime contractor, the awarding agency, and the place of performance in one record.

Next, identify the awarding agency. The agency determines whether a mandatory carrier program was in effect during the contract period. Some agencies maintained single-carrier DBA insurance programs for all their contractors during specific time windows. Knowing the agency and the date narrows the carrier universe dramatically.

Then trace the contractor chain. If your claimant worked for a subcontractor, the FPDS record shows the prime. USAspending's sub-award data (sourced from FSRS, the Federal Subaward Reporting System) can sometimes show the sub-award relationships. ClaimTrove's database includes 4,315 sub-award records that map prime-to-subcontractor relationships.

Finally, cross-reference the timeline. DBA carriers change. A contractor might use one carrier from 2010 to 2014 and switch to another in 2015. The FPDS period of performance tells you when the contract was active, but you need carrier data from the same period. Our data shows carriers shift every three to five years for most major contractors. An investigation timeline built from multiple database sources prevents you from identifying the wrong carrier based on outdated records.

What Are the Limitations of FPDS Data for DBA Investigations?

FPDS is powerful but incomplete for DBA carrier identification. Understanding its blind spots prevents wasted effort.

No carrier information: FPDS tracks contracts, not insurance. It will never tell you which DBA carrier covered a specific contractor. You need separate data sources, DOL industry reports, OALJ decisions, FOIA records, to make that connection.

Subcontract gaps: FPDS only tracks prime contract awards. Sub-award data comes from FSRS and is less complete. Many sub-tier relationships (sub-sub-contractors) are not reported at all. Yet a significant percentage of DBA claimants work for subcontractors, not primes.

Name variations: FPDS records the contractor's registered name, which may differ from the name on the claimant's employment documents. "DynCorp International LLC" in FPDS might appear as "DI Operated Systems" on a pay stub. ClaimTrove maintains 214 employer alias mappings to bridge these gaps.

Historical coverage: FPDS data becomes less reliable before FY2004. For injuries predating 2004, you will need to rely on archived procurement records, OALJ decisions, or FOIA requests rather than FPDS.

Query complexity: A thorough FPDS search for a single employer can require multiple queries: one for the employer name, one for known aliases, one for the CAGE code, and separate searches for each potential parent PIID. Across the 43,298 overseas awards in ClaimTrove's database, the same employer appears under an average of three different registered names.

FPDS gives you the contract skeleton. Building the full picture, from contract to contractor to carrier, requires layering FPDS data with DOL records, legal decisions, and FOIA-obtained coverage information. ClaimTrove pre-indexes FPDS-derived contract data for DBA-relevant overseas awards, cross-referenced against 18 additional federal data sources. Instead of learning FPDS query syntax and manually connecting the dots, you can search ClaimTrove's database and get the contract-to-carrier chain in seconds.