Student Record Redaction: GDPR and FERPA Guide for Schools

This article is for general informational purposes only and does not constitute legal advice. Regulatory requirements vary by jurisdiction and change over time. Consult a qualified legal professional for advice specific to your organization's circumstances.

A school district in Ohio receives a records request from a parent who wants every document the district holds about their child. Down the hall, the special education coordinator is preparing records for a due process hearing under the Individuals with Disabilities Education Act (IDEA). Both situations require someone to understand what must be disclosed, what can be withheld, and how to produce records that comply with the Family Educational Rights and Privacy Act (FERPA).

Schools and universities that receive federal funding are bound by FERPA, which governs access to education records, parental rights, and the limits on disclosure to third parties. IDEA adds a separate layer of rights and procedural protections for students with disabilities. Title IX investigations generate their own records obligations. And court orders can compel disclosure that would otherwise be prohibited.

This guide covers the main scenarios where schools need to redact or prepare records for disclosure: FERPA access requests, IDEA due process hearings, directory information rules, court orders, student transfers, and Title IX records. It also acknowledges the reality that many public schools operate on tight budgets where expensive commercial redaction software is not a realistic purchase.

FERPA: the core framework

The Family Educational Rights and Privacy Act (FERPA), codified at 20 U.S.C. § 1232g, gives parents the right to access their child's education records and to request corrections. When a student turns 18 or attends a post-secondary institution, those rights transfer to the student. Schools subject to FERPA must respond to access requests within 45 days.

Education records under FERPA are broadly defined: any records directly related to a student that are maintained by the school or a party acting on its behalf. This includes grades, transcripts, disciplinary records, financial records, and health records held by the school. It does not include sole-possession records (notes made by a teacher or staff member for their own use that are not shared with anyone else) or law enforcement unit records.

FERPA also restricts what schools can disclose to third parties without consent. The disclosure of education records to anyone other than the parent or eligible student generally requires either written consent or a specific FERPA exception. Redaction is frequently required when producing records that contain information about other students - a disciplinary incident file that names multiple students, for example, must have the other students' personally identifiable information (PII) removed before the requesting student's parents can see it.

Under 34 CFR § 99.12, schools are required to redact or segregate information about other students if it can be done reasonably without compromising the meaning of the record. Per 34 CFR § 99.11(b), schools cannot charge fees for the redaction or segregation required to produce a compliant response.

Directory information and opt-out rights

FERPA allows schools to designate certain information as "directory information" - items like name, grade level, dates of attendance, and participation in school activities - that can be disclosed without consent unless parents opt out. Schools must notify parents annually of what information is designated as directory information and provide the opportunity to opt out.

What counts as directory information is not fixed. Schools define it themselves within the bounds of FERPA's framework. Some districts include student photos; others do not. A school that receives a request for its student directory must check which students have filed an opt-out before responding. Disclosing a directory that includes opt-out students is a FERPA violation. For larger districts producing directories in bulk, automated redaction of opted-out entries is more reliable than manual removal.

IDEA records and due process hearings

Students with disabilities are entitled to a Free Appropriate Public Education (FAPE) under the Individuals with Disabilities Education Act (IDEA). The records generated in meeting this obligation - Individualized Education Programs (IEPs), evaluation reports, prior written notices, meeting notes - are both education records under FERPA and subject to IDEA's own procedural requirements.

When a parent challenges the school's placement or services through a due process hearing, the school is required to submit evidence from the student's records. This document bundle is shared with the parent, the parent's attorney or representative, the hearing officer, and ultimately a review tribunal if the case is appealed. Records about other students - a comparison in an evaluation report, peer observation notes, another student mentioned in an IEP meeting - need to be redacted before the bundle is produced.

IDEA requires that parents be given access to all records relating to the identification, evaluation, and educational placement of their child. Schools cannot selectively withhold records on grounds of inconvenience. But they can redact third-party student information, and they can assert FERPA protections for information about other identifiable students within their records.

Title IX investigation records

Title IX investigations generate records that often need to be disclosed to both the complainant and the respondent during the grievance process. Department of Education regulations require schools to provide both parties with access to evidence directly related to the allegations. This creates a specific redaction challenge: how to share evidence files that may contain personal information about third parties not involved in the complaint.

Third-party witnesses named in investigation records, students mentioned in background information, and non-party staff members whose information appears incidentally should generally be redacted before records are shared under the Title IX process. The relevant evidence - the statements, communications, and records directly related to the complaint - remains. Schools working through Title IX response procedures should confirm requirements with their Title IX coordinator and legal counsel, as the specific procedural rules have been subject to regulatory change.

Court orders and student transfers

A court order compelling production of student records overrides FERPA's consent requirement. The school must comply but should review the order carefully: produce what the order specifies, and redact or withhold anything outside its scope. Before disclosing in response to a court order, schools are generally expected to make a reasonable effort to notify the parent or eligible student, unless the court has directed otherwise.

Student transfers between schools are handled through a specific FERPA exception. Schools may disclose education records to officials of other schools in which the student seeks to enroll, without parental consent. The transferring school should disclose the student's records relevant to enrollment and education - not a wholesale dump of every document ever generated. Disciplinary records, IEPs, and immunization records are typically transferred; internal staff notes that are sole-possession records are not.

Budget reality: free tools are a legitimate option

Many public school districts, particularly smaller districts and charter schools, do not have budgets for dedicated document redaction software. This is a real constraint, not a compliance excuse. The free tier of tools like RedactProof handles the core use cases - redacting a parent's SAR response, preparing a FERPA access packet, removing third-party student information from IDEA records - without requiring IT procurement or a software budget line.

The free tier requires sign-in but is otherwise unlimited on pattern-based detection and pixel-burn redaction. For a district that handles a handful of records requests per year, it is a practical starting point. Larger districts or those handling significant IDEA or Title IX workloads may find the Core or Pro tiers - which add AI-assisted detection and full audit trails - worth the investment.

What matters is that redaction is applied at all, that it is permanent rather than overlay, and that someone has checked the output before the records leave the school. Under-resourced state schools shouldn't be priced out of basic compliance tools.

Redacting student records: the practical steps

• Convert documents to PDF before redacting. Word documents with tracked changes and Excel files with hidden rows can expose data that is not visible in normal view.
• Run automated PII detection for names, student ID numbers, Social Security numbers, dates of birth, addresses, and other standard identifiers.
• Review manually for contextual identifiers - information that could identify a student even without their name.
• Apply pixel-burn redaction only. Overlay redaction leaves the underlying text in the file and can be reversed.
• Verify the output: search for strings you know were redacted, and try to select text in redacted areas before sending.

For more on the redaction process generally, see our guide to redacting documents for disclosure. For schools that want to formalize their approach, our redaction policy template is a starting point that can be adapted to fit a district's specific workflows.