Inherently Governmental Function

Boolean or coded indicator showing whether the award action involves inherently governmental functions. It flags records where the contract scope includes duties that, by statute or policy, must be performed by government personnel rather than contractors.

Family: Award
Category: Contract Data
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__award__contractData__inherentlyGovernmentalFunction
Title
Inherently Governmental Function
FPDS Path
award/contractData/inherentlyGovernmentalFunction
Description
Boolean or coded indicator showing whether the award action involves inherently governmental functions. It flags records where the contract scope includes duties that, by statute or policy, must be performed by government personnel rather than contractors.
Business Meaning
This field supports oversight of outsourcing boundaries and compliance with federal restrictions on contracting for inherently governmental work. Analysts use it to identify awards that may warrant policy review, trend the extent of sensitive functions being contracted, and segment procurement activity by governance risk.
Example Value
OT
Observed Non-Null Count
22,300,193

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter awards for governance or compliance reviews
  • Segment contracts involving sensitive or restricted functions
  • Trend inherently governmental classifications over time or by agency

Common Mistakes

  • Assuming a coded value is self-explanatory without checking the code set or paired description
  • Using the flag as evidence of actual performance rather than reported award classification

Query Guidance

Filter on the specific code values observed in your FPDS extract, not on the English label alone. In SQL, compare against the stored code or normalize to a boolean in a CASE expression after confirming the code list, and join to related contract data when you need context for interpretation.

SQL Examples

Preview values

SELECT
    content__award__contractData__inherentlyGovernmentalFunction AS inherently_governmental_function
FROM fpds.data
WHERE content__award__contractData__inherentlyGovernmentalFunction IS NOT NULL
LIMIT 25

Flag distribution

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