FPDS Query Library
About Us
Contact Us

Contract Bundling

Indicates whether the award is coded as bundled in FPDS. This is a flag field, and the observed values may include coded responses such as "D" and "H," where "H" denotes not bundled.

Family: Award
Category: Product Or Service Information
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__award__productOrServiceInformation__contractBundling
Title
Contract Bundling
FPDS Path
award/productOrServiceInformation/contractBundling
Description
Indicates whether the award is coded as bundled in FPDS. This is a flag field, and the observed values may include coded responses such as "D" and "H," where "H" denotes not bundled.
Business Meaning
Bundling status matters because bundled procurement can affect competition, small business participation, contract structure, and policy compliance review. Analysts use it to identify awards that may warrant scrutiny for consolidation effects or set-aside impacts.
Example Value
D
Observed Non-Null Count
93,239,773

FPDS Compare

FPDS Query Variable
content__award__productOrServiceInformation__contractBundling
FPDS XML Path
award/productOrServiceInformation/contractBundling
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'award/productOrServiceInformation/contractBundling' into the SQL-ready variable 'content__award__productOrServiceInformation__contractBundling'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building

Common Usage

  • Filter awards flagged as bundled for small business impact analysis
  • Segment obligations by bundling status
  • Support compliance or acquisition review of consolidated requirements

Common Mistakes

  • Assuming any non-null value means the contract is bundled
  • Comparing raw codes without checking the code set or description

Query Guidance

Use explicit code checks in SQL, for example filter on the bundled code(s) only after validating the FPDS value set. If the field is stored as a boolean_or_code_flag, account for coded responses such as 'H' for not bundled and test for nulls separately when measuring data completeness.

SQL Examples

Preview values

SELECT
    content__award__productOrServiceInformation__contractBundling AS contract_bundling
FROM fpds.data
WHERE content__award__productOrServiceInformation__contractBundling IS NOT NULL
LIMIT 25

Flag distribution

SELECT
    content__award__productOrServiceInformation__contractBundling AS flag_value,
    count() AS record_count
FROM fpds.data
WHERE content__award__productOrServiceInformation__contractBundling IS NOT NULL
GROUP BY flag_value
ORDER BY record_count DESC

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.