FPDS Query Library
About Us
Contact Us

A76 Action

Coded competition indicator recorded on the award to show the A-76 action associated with the procurement record. It represents a short code rather than a full narrative description, so the specific meaning depends on the FPDS code set in use.

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__A76Action
Title
A76 Action
FPDS Path
award/competition/A76Action
Description
Coded competition indicator recorded on the award to show the A-76 action associated with the procurement record. It represents a short code rather than a full narrative description, so the specific meaning depends on the FPDS code set in use.
Business Meaning
This field helps analysts identify whether and how an action was associated with A-76 competition-related reporting, which is relevant when evaluating sourcing decisions, competitive versus noncompetitive outcomes, and compliance with public-private competition policies. It can support segmentation of award activity where competition status may be affected by outsourcing or inherently governmental determinations.
Example Value
N
Observed Non-Null Count
105,595,169

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter award records tied to A-76-related competition reporting
  • Group awards by A-76 action code to analyze sourcing patterns
  • Combine with competition fields to study noncompetitive versus competitive outcomes

Common Mistakes

  • Assuming the code is a plain-language description
  • Using the field as a standalone proxy for competition status

Query Guidance

Select and group by the field as a categorical code, and compare it with related competition fields in the same award record. In SQL, filter for specific observed code values only after verifying their meaning in the extract or reference table; avoid LIKE-based interpretation unless the dataset stores descriptive text.

SQL Examples

Preview values

SELECT
    content__award__competition__A76Action AS a76_action
FROM fpds.data
WHERE content__award__competition__A76Action IS NOT NULL
LIMIT 25

Top values

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