Clinger-Cohen Act (CCA)

The Clinger-Cohen Act (CCA) of 1996, formally titled the Information Technology Management Reform Act, is federal legislation that established the Chief Information Officer (CIO) position in federal agencies, created the framework for IT investment management and portfolio analysis, and overhauled federal IT acquisition to improve efficiency and accountability.

What is the Clinger-Cohen Act?

CCA was enacted in response to decades of failed or over-budget federal IT projects. Its two core reforms were: (1) requiring each major federal agency to designate a Chief Information Officer with agency-wide authority over IT planning, budgeting, and performance; and (2) establishing an IT investment management framework requiring agencies to analyze, select, control, and evaluate IT investments using a disciplined portfolio approach before seeking funding. CCA also repealed the Brooks Act, which had previously given GSA monopoly over most federal IT acquisition, and opened federal IT procurement to broader competition and commercial products. The result was a significant expansion of agency authority to make IT purchasing decisions and a corresponding increase in competitive contracting for federal IT. CCA's IT investment management framework is implemented through OMB's capital planning guidance and is visible today in the IT Dashboard (itdashboard.gov) where agencies report on major IT investments. For contractors, CCA-era reforms created the broad competitive federal IT market and the CIO-driven agency IT modernization programs that generate substantial contract opportunities.

Why the Clinger-Cohen Act matters for government contractors

CCA's most lasting impact on contractors is the competitive federal IT market it created and the CIO-authority model it established. Agency CIOs drive major IT modernization investments that generate large contract opportunities. Understanding the CIO's authority and the IT investment management process helps contractors engage effectively at the right organizational level within agencies.

Example

An IT consulting firm targeting civilian agency CIO offices understands that under CCA, the agency CIO controls IT investment decisions and must approve major IT program funding. The firm builds relationships with CIO office staff, positions its capabilities in the context of the agency's IT Strategic Plan, and responds to solicitations that flow from CIO-approved investment decisions, a CCA-shaped market structure.

Frequently Asked Questions

What did CCA replace in terms of federal IT procurement?

CCA repealed the Brooks Automatic Data Processing Act, which had given GSA near-exclusive authority over federal IT procurement. CCA distributed that authority back to individual agency CIOs while retaining GSA's role as an optional purchasing mechanism rather than a mandatory one.

What is the IT Dashboard and how does it relate to CCA?

The IT Dashboard (itdashboard.gov) is OMB's public reporting tool for major federal IT investments, implementing CCA's requirement for portfolio-based IT investment management. Contractors can use the IT Dashboard to track agency IT program status, identify at-risk programs, and monitor modernization investments that may generate contracting opportunities.

Did CCA create the CIO role in the federal government?

Yes. CCA required each major federal agency to designate a CIO with authority over IT planning, budgeting, and management. Before CCA, federal IT leadership structures varied widely. CCA standardized the CIO model across the federal government and established the agency CIO as the primary IT governance authority.

How does CCA relate to FITARA?

The Federal Information Technology Acquisition Reform Act (FITARA) of 2014 built on CCA by strengthening CIO authority, particularly regarding review and approval of IT procurement actions. FITARA made the agency CIO's role more explicitly authoritative over IT contract actions, reinforcing the CCA framework.