FPDS Query Library
About Us
Contact Us

Extent Competed

Human-readable value that records the extent to which an award action was competed. It is the descriptive label associated with the competition status captured in FPDS, such as a coded indication of full, partial, or no competition.

Family: Award
Category: Competition
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__award__competition__extentCompeted
Title
Extent Competed
FPDS Path
award/competition/extentCompeted
Description
Human-readable value that records the extent to which an award action was competed. It is the descriptive label associated with the competition status captured in FPDS, such as a coded indication of full, partial, or no competition.
Business Meaning
This field is central to competition reporting because it helps analysts distinguish competed awards from sole-source or other limited-competition actions. It supports assessments of acquisition strategy, competition rates, and compliance with competition requirements.
Example Value
A
Observed Non-Null Count
108,269,517

FPDS Compare

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

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Competition and sole-source analysis

Common Usage

  • Calculate competed versus noncompeted award counts
  • Segment awards by competition level for trend analysis
  • Support compliance and justification reviews

Common Mistakes

  • Assuming the raw string is self-explanatory without a code lookup
  • Mixing this field with separate synopsis or rationale fields that describe why competition was limited

Query Guidance

Use exact-value filters or a CASE statement after mapping codes to business meanings. When joining or aggregating, normalize the coded values to standard competition categories first, and do not compare against descriptive text unless you have confirmed the stored value format.

SQL Examples

Preview values

SELECT
    content__award__competition__extentCompeted AS extent_competed
FROM fpds.data
WHERE content__award__competition__extentCompeted IS NOT NULL
LIMIT 25

Top values

SELECT
    content__award__competition__extentCompeted AS value,
    count() AS record_count
FROM fpds.data
WHERE content__award__competition__extentCompeted IS NOT NULL
GROUP BY value
ORDER BY record_count DESC
LIMIT 25

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