FPDS Query Library
About Us
Contact Us

Subcontract Plan

Boolean or coded flag indicating whether a subcontracting plan is required for the IDV. In FPDS, this is part of Preference Programs and captures the presence of a subcontract plan requirement rather than the full narrative of the plan itself.

Family: IDV
Category: Preference Programs
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__preferencePrograms__subcontractPlan
Title
Subcontract Plan
FPDS Path
IDV/preferencePrograms/subcontractPlan
Description
Boolean or coded flag indicating whether a subcontracting plan is required for the IDV. In FPDS, this is part of Preference Programs and captures the presence of a subcontract plan requirement rather than the full narrative of the plan itself.
Business Meaning
This field is important for assessing small business subcontracting obligations, compliance exposure, and the extent to which an award includes statutory subcontracting requirements. Analysts use it to segment awards by preference-program obligations and to evaluate whether contract vehicles are subject to subcontracting-plan reporting or oversight.
Example Value
C
Observed Non-Null Count
4,398,587

FPDS Compare

FPDS Query Variable
content__IDV__preferencePrograms__subcontractPlan
FPDS XML Path
IDV/preferencePrograms/subcontractPlan
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/preferencePrograms/subcontractPlan' into the SQL-ready variable 'content__IDV__preferencePrograms__subcontractPlan'.

Use Cases

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

Common Usage

  • Identify IDVs subject to subcontracting-plan requirements
  • Filter awards for small business and compliance analysis
  • Compare obligation patterns across contract vehicles and agencies

Common Mistakes

  • Assuming the field is always a simple true/false flag
  • Interpreting a code value without checking the dataset’s code meanings

Query Guidance

Use this field in WHERE clauses only after confirming the valid code values and their meanings. If multiple representations exist, map them to a standardized indicator such as required/not required before aggregating or joining to compliance metrics.

SQL Examples

Preview values

SELECT
    content__IDV__preferencePrograms__subcontractPlan AS subcontract_plan
FROM fpds.data
WHERE content__IDV__preferencePrograms__subcontractPlan IS NOT NULL
LIMIT 25

Flag distribution

SELECT
    content__IDV__preferencePrograms__subcontractPlan AS flag_value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__preferencePrograms__subcontractPlan 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.