College Transparency Act
- Sponsor
- Rep. Krishnamoorthi, Raja [D-IL-8]
- Committees
- Education and Workforce Committee (primary)
- Last action
- Jul 29, 2025
Bottom line
The College Transparency Act creates a comprehensive federal student data system designed to enhance transparency and accountability in higher education, while incorporating explicit privacy and security safeguards.
What it actually does
This bill establishes a secure, privacy-protected postsecondary student-level data system within the National Center for Education Statistics (NCES) to track student enrollment, progression, completion, and postcollegiate outcomes. It mandates data sharing agreements with various federal agencies for aggregate reporting, aims to reduce institutional reporting burdens, and repeals the existing prohibition on a federal student unit record system.
Proponents argue
Proponents argue this bill will empower students and families with accurate, customizable information to make informed decisions about postsecondary education, improve institutional accountability by providing better data on outcomes, and streamline data reporting requirements for colleges and universities, ultimately enhancing the effectiveness of federal aid programs.
Opponents contend
Opponents typically raise significant concerns about student privacy, fearing that a centralized federal student data system, even with safeguards, is inherently vulnerable to data breaches and potential misuse. They also worry about federal overreach into higher education, the creation of a 'federal database,' and the possibility of the data being used for unintended purposes such as federal rankings or law enforcement activities.
The bill is relatively concise for its scope, allowing for a thorough review within a reasonable timeframe for an informed reader.
Section 2, amending HEA Section 132(l)(1)
Establishment of Postsecondary Student Data System
This provision mandates the Commissioner of the National Center for Education Statistics (NCES) to develop and maintain a secure, privacy-protected student-level data system within four years. The system's goals include evaluating student outcomes, enhancing transparency, providing information to students and families, and reducing reporting burdens for institutions.
Supporters argue
Supporters argue that establishing this system is crucial for providing accurate, complete, and customizable information that students and families need to make informed decisions about college, while also improving accountability and evaluation of federal aid programs.
Critics contend
Critics contend that creating a centralized federal student data system, regardless of stated intentions, poses inherent risks to student privacy and could lead to federal overreach in higher education policy.
Tradeoffs
The provision balances the desire for greater transparency and data-driven accountability in higher education with concerns about federal data collection and potential privacy infringements.
Section 2, amending HEA Section 132(l)(1)(C)
System Development Process and Safeguards
This section outlines specific requirements for developing the data system, emphasizing user needs, modern privacy- and security-enhancing technology, adherence to federal data security standards (like FIPS and NIST), and data minimization practices. It also requires providing notice to students about the data included and its uses.
Section 2, amending HEA Section 132(l)(2)(B)
Postsecondary Student Data System Advisory Committee
This provision establishes an Advisory Committee within two years to consult with the Commissioner on determining data elements. The committee must include representatives from diverse institutions, state higher education agencies, students, relevant federal agencies, data privacy and security experts, and other stakeholders, ensuring broad input.
Section 2, amending HEA Section 132(l)(2)(C)
Required Data Elements
The bill mandates specific student-level data elements, including those necessary for existing IPEDS 'student-related surveys' (with privacy exceptions), and data to report enrollment, persistence, retention, transfer, and completion for all credential levels. This data must be disaggregated by categories such as enrollment status, attendance intensity, race/ethnicity, age, gender, program of study, military/veteran status, distance education status, and Federal Pell Grant/loan recipient status.
Section 2, amending HEA Section 132(l)(2)(F)
Prohibited Data Elements
This critical provision explicitly prohibits the inclusion of individual health data, student discipline records, elementary and secondary education data, exact addresses, citizenship status, migrant status, national origin status, course grades, postsecondary entrance examination results, political affiliation, or religion in the postsecondary student data system.
Section 2, amending HEA Section 132(l)(3)
Periodic Matching with Other Federal Data Systems
This provision mandates NCES to enter into secure, privacy-protected periodic data sharing agreements with several federal agencies, including the Treasury/IRS, Defense, VA, Census Bureau, Federal Student Aid, Social Security Administration, and Bureau of Labor Statistics. The purpose is to calculate aggregate program- and institution-level earnings, assess educational benefits use, and evaluate labor market outcomes of former students. It explicitly states that matches are periodic, not continuous, and will not create a single standing, linked federal database.
Section 2, amending HEA Section 132(l)(4)
Publicly Available Information
NCES is required to make summary aggregate information publicly available through a user-friendly consumer information website and analytic tool. This tool must allow users to customize and filter information, build comparative reports across institutions and programs, and use statistical disclosure limitation techniques to prevent individual identification. The information will cover student access, progression, completion, costs, and postcollegiate outcomes (employment, earnings, loan repayment).
Section 2, amending HEA Section 132(l)(5)
Permissible Disclosures and Use Limitations
This section details how data from the system can be used and explicitly prohibits certain uses. It allows student-level, non-personally identifiable information for vetted research, provides feedback reports to institutions and states, and permits state data queries. Crucially, it prohibits the sale of data, limits other federal agencies' use to vetted research or explicitly authorized purposes, and forbids using data to limit student services, for law enforcement/debt collection, or to establish federal rankings or summative ratings of institutions.
Section 3
Repeal of Prohibition on Student Data System
This section repeals Section 134 of the Higher Education Act of 1965, which currently prohibits the establishment of a federal student unit record system. This repeal is necessary to allow the creation of the postsecondary student data system outlined in Section 2 of this bill.
This clause states that if another provision of the Higher Education Act requires the same reporting or data collection as the new postsecondary student data system, institutions or the Secretary/Commissioner shall use the data from the new system to satisfy both requirements, thereby avoiding duplicated reporting.
Section 2, amending HEA Section 132(l)(1)(B)
Why it matters:This is standard legislative practice for efficiency clauses, but its placement might obscure its significant practical impact on institutional burden.
Case for: Proponents argue this is a crucial mechanism for achieving the bill's goal of reducing institutional reporting burdens, ensuring that the new system genuinely streamlines data collection rather than adding to it.
Case against: Critics might argue that while the intent is good, the practical implementation of 'avoiding duplicated reporting' can be complex and may not fully materialize, potentially leaving institutions with ongoing dual reporting requirements during transition.
Estimated impact: Potentially significant reduction in administrative overhead for institutions over the long term, once the system is fully operational and integrated.
This clause explicitly states that the periodic matching or sharing of data through the system 'does not result in the creation of a single standing, linked Federal database at the Department that maintains the information reported across other Federal agencies.'
Section 2, amending HEA Section 132(l)(3)(C)(iii)(III)
Why it matters:This is a critical safeguard against a major privacy concern, and its specific placement might be to ensure it's legally binding without being the most prominent feature of the bill's public messaging.
Case for: Proponents highlight this as a fundamental privacy protection, directly addressing fears of a 'Big Brother' federal database by legally prohibiting its creation and ensuring data remains distributed and matched only periodically.
Case against: Opponents might argue that while the letter of the law prohibits a 'single standing, linked' database, the practical effect of extensive periodic data matching across agencies could still lead to similar privacy risks or create a de facto linked system over time.
Estimated impact: Provides a crucial legal firewall against the most significant privacy concern related to federal data centralization, influencing public trust and the system's long-term design.
This clause explicitly prohibits the Secretary or any Federal entity from using the comprehensive data collected for the postsecondary student data system to 'establish any Federal ranking system of institutions of higher education or a system that results in a summative Federal rating of institutions of higher education.'
Section 2, amending HEA Section 132(l)(5)(F)
Why it matters:This is a key concession to institutions and states concerned about federal overreach and the potential for federal agencies to dictate educational priorities through rankings. Its placement ensures it is legally binding without being the primary focus of the bill's public presentation.
Case for: Proponents argue this provision is essential to reassure institutions that the data system is for transparency and research, not for federal control or punitive measures, thereby fostering cooperation and trust.
Case against: Some advocates for stronger accountability might argue that prohibiting federal rankings limits the potential for the data to drive institutional improvement or hold underperforming institutions accountable, seeing it as a missed opportunity.
Estimated impact: Significantly impacts how the federal government can use the collected data for accountability, preventing direct federal ranking or rating systems.