Clinger Cohen Act

Boolean or coded flag indicating whether the award record reflects Clinger-Cohen Act compliance. In FPDS, the value marks the presence or absence of this legislative mandate condition at the award level; the example value "N" indicates no. Treat it as a compliance indicator rather than a narrative description.

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

Variable Overview

FPDS Query Variable
content__award__legislativeMandates__ClingerCohenAct
Title
Clinger Cohen Act
FPDS Path
award/legislativeMandates/ClingerCohenAct
Description
Boolean or coded flag indicating whether the award record reflects Clinger-Cohen Act compliance. In FPDS, the value marks the presence or absence of this legislative mandate condition at the award level; the example value "N" indicates no. Treat it as a compliance indicator rather than a narrative description.
Business Meaning
This field helps analysts evaluate whether awards are associated with information technology governance and acquisition control requirements under the Clinger-Cohen Act. It is useful for compliance screening, portfolio segmentation, and identifying awards that may fall under IT acquisition oversight or related policy reporting.
Example Value
N
Observed Non-Null Count
111,335,847

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter awards that are marked as Clinger-Cohen Act compliant
  • Segment procurement activity by legislative mandate status
  • Support compliance-oriented counts and cross-tabs

Common Mistakes

  • Treating the flag as a textual explanation rather than a coded indicator
  • Assuming null and "N" have the same meaning without checking the data definition

Query Guidance

Use it in WHERE clauses as a flag filter, for example `WHERE content__award__legislativeMandates__ClingerCohenAct = 'Y'` or the equivalent approved value in your extract. If your dataset stores boolean-like values or description pairs, inspect the observed code set and filter on the stored code rather than the label.

SQL Examples

Preview values

SELECT
    content__award__legislativeMandates__ClingerCohenAct AS clinger_cohen_act
FROM fpds.data
WHERE content__award__legislativeMandates__ClingerCohenAct IS NOT NULL
LIMIT 25

Flag distribution

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