School Surveillance Video Redaction Under FERPA

School districts have added far more security cameras to hallways, cafeterias, and bus loops over the past several years, and that expansion has quietly created a records problem most districts were not built to handle. A single disciplinary incident can now generate footage from six or eight overlapping camera angles, and parents, journalists, and attorneys increasingly know to ask for it. Unlike a police body-worn camera (BWC) release, a request for school surveillance video runs through a different, more restrictive federal statute: the Family Educational Rights and Privacy Act (FERPA). Getting school surveillance video redaction wrong exposes a district to complaints with the U.S. Department of Education or to a state open-records challenge, and getting it right requires a framework that looks nothing like the public-records rules built for law enforcement footage.

When School Surveillance Video Becomes an "Education Record" Under FERPA

FERPA protects "education records," a term the U.S. Department of Education's Student Privacy Policy Office (formerly the Family Policy Compliance Office) has interpreted to reach further than most districts assume. According to the department's official guidance on photos and videos under FERPA, a recording qualifies as an education record when it is directly related to a student and maintained by the school or a party acting on the school's behalf. The guidance lists several factors that point toward "directly related," including:

• Disciplinary use. Footage relied on for a disciplinary decision or investigation is treated as directly related to the student who was disciplined.
• Focus and intent. If the recording was made with the intent of capturing a specific student, rather than a wide-angle view of a room or hallway, that student's presence in the footage weighs toward FERPA coverage.
• Health or safety events. A recording that depicts a student violation, injury, illness, or medical emergency is more likely to be treated as an education record.
• Incidental appearance. A student who merely appears in the background of a general activity, such as a hallway camera catching a crowd during passing period, is not the focus, and that footage is less likely to trigger FERPA protection for that student.

The practical effect is that a hallway camera recording an entire school day is not automatically an education record for every student who walks past it. It becomes one, for a specific student, the moment the district uses it, or intends to use it, in a way that is directly related to that student.

The Law Enforcement Unit Exception: When FERPA Does Not Apply

FERPA's regulations, at 34 C.F.R. 99.8, carve out a separate category that trips up a lot of districts: records of a school's own "law enforcement unit," meaning any office, department, or individual the school has authorized to enforce laws or maintain campus physical security. A record created by that unit, for a law enforcement purpose, and maintained by that unit is not an "education record" at all and falls outside FERPA entirely. The regulation is specific about the boundary, though: footage created for a law enforcement purpose but maintained by a general administrative office, rather than by the designated law enforcement unit itself, does not qualify for the exception and remains subject to FERPA.

The Department of Education's separate guidance on turning video over to police reinforces the same line: law enforcement unit records "may be released subject to school policy, State law, and other applicable laws," since FERPA itself neither requires nor prohibits their disclosure. That makes the exception a matter of which office holds the file and why it was created, not a blanket rule that anything captured on a school security camera is automatically a public record. Districts with a school resource officer or dedicated campus police unit need a clear, written policy on which footage sits in that unit's custody and which stays with general administration.

Redacting Multi-Student Footage: What FERPA Requires (and Will Not Let a District Charge For)

Most school surveillance footage that qualifies as an education record depicts more than one student. FERPA gives a parent or eligible student the right to inspect and review the portion of a recording that directly relates to their own child, but it does not give that parent a right to see other students in the same frame. The Department of Education's guidance addresses that overlap directly: when a video is an education record for multiple students, the school must redact or segregate the portions directly related to other students, without destroying the meaning of the record, before allowing inspection.

A few points from that guidance matter for building an actual workflow:

1. Redaction is the default, not an optional courtesy. If it is reasonably possible to obscure other students while preserving the record's meaning, the school must do it rather than deny access outright.
2. An unredactable record narrows access instead of expanding denial. When the footage cannot be segregated without destroying its meaning, only the students the video is genuinely about, and their parents, get a right to inspect it; it is not simply withheld from everyone nor released to everyone.
3. Districts generally cannot bill parents for the redaction itself. Legal commentary on the department's guidance, including analysis from the education law group at Pullman & Comley, has noted that redaction costs function more like the search-and-review work schools already absorb than like a standard copy fee, a meaningfully different posture than the redaction cost-recovery many law enforcement agencies build into a public-records fee schedule.

That distinction matters for budget planning: a school district cannot simply adopt the fee structure a police department uses for public-records video and apply it to a parent's FERPA inspection request. Our earlier guide to building a defensible video redaction fee policy covers how agencies that are permitted to recover redaction costs, such as law enforcement responding to FOIA requests, can structure those charges.

Title IX Investigation Records and Video: A Narrower, Slower Track

Video tied to a Title IX sexual harassment or assault investigation adds another layer on top of the general FERPA analysis. Because Title IX investigation files are themselves education records for the students named in them, the same redaction obligation applies: the Student Press Law Center's guide to commonly requested FERPA records notes that schools must redact identifying student information from an investigation record "in most cases" when doing so does not destroy the record. A few strategies come up repeatedly for parties and their counsel trying to access this material:

• Requesting the underlying video separately. Camera footage referenced in a Title IX investigation report may be treated, and redacted, as its own record rather than as an inseparable part of the written findings.
• Checking the federal Title IX case database. The Department of Education maintains a public, searchable database of pending Title IX investigations opened by its Office for Civil Rights, which can confirm whether a matter has been formally referred even when the underlying school records remain restricted.
• Using state open-records law as a second path. Many state public-records statutes weigh the public interest in disclosure against privacy harm, which can support release of non-student-identifying portions of an investigation file even where FERPA alone would counsel caution.
• Separating employee conduct from student records. Video and records that relate to an employee's conduct during an investigation, rather than to a student, generally are not protected as a student education record, and the employee's identity can often be disclosed even when a student's cannot.

None of this changes the core redaction obligation once video is in scope. It does mean Title IX matters typically move slower than a routine disciplinary-footage request, since a district has to sort what belongs to the investigation record, what belongs to a law enforcement referral, and what remains protected student information before any video goes out.

FERPA vs. State Public Records Law: Two Different Doors

A parent asking to inspect their own child's education record and a journalist filing a state public-records request for the same footage are walking through two different legal doors, and school records staff need to know which one a given request uses. FERPA is a parental-inspection right, not a general public-disclosure statute; it governs what a school must show an eligible parent or student and what it may not disclose to third parties without consent. Most state open-records laws, by contrast, exist to give the public access to government records generally, and nearly all of them include an exemption for records protected by federal law, which pulls FERPA-covered education records out of the public disclosure requirement.

That interaction produced a useful illustration in Connecticut, where the state's Freedom of Information Commission ruled in 2023, in Vasquez v. Hartford Public Schools (FIC 2023-0489), that surveillance video depicting multiple students could be withheld from a public-records requester when the district was unable to edit the footage to remove the other students. The commission relied in part on a 2004 Department of Education guidance letter addressing the same redaction standard discussed above. The outcome is a reminder that a public-records requester generally gets no greater access to multi-student school video than a FERPA request would allow.

Building a Defensible School Surveillance Video Redaction Workflow

Districts that handle these requests well tend to build a process before the first difficult request arrives, rather than improvising one under a deadline. A workable school surveillance video redaction workflow generally includes:

1. Classify the footage first. Determine whether the video was created and is maintained by a designated law enforcement unit, in which case FERPA may not apply, or by general school administration, in which case it likely does.
2. Identify every student whose privacy interest is implicated. A multi-camera incident can involve far more students than the two or three directly named in an incident report; each one's presence in the frame needs to be accounted for before redaction begins.
3. Redact rather than withhold whenever it is reasonably possible. Blurring or otherwise obscuring students who are not the subject of the request preserves both the requester's access and the other students' privacy, and it is what FERPA guidance directs a school to attempt first.
4. Keep a written record of the redaction decision. Note what was obscured, why, and who reviewed the final file, both to support the district's position if a decision is challenged and to keep the process consistent across requests handled by different staff.
5. Route the request through the correct legal framework from the start. A parent's inspection request, a state public-records request, and a Title IX-related request carry different timelines and disclosure standards, and misrouting a request at intake is a common source of delay.
6. Plan capacity for multi-camera incidents. A single hallway altercation can generate footage from several cameras that all need review; our guide to managing high-volume video and audio FOIA requests covers the intake triage that handles this kind of volume.

A district that can show exactly what was redacted, on what legal basis, and by whom is in a far stronger position if a parent, a reporter, or the Department of Education's Student Privacy Policy Office later questions the outcome. Our broader guide to what courts look for in defensible video redaction covers the same documentation discipline in more depth, and the logic applies whether the footage came from a police body camera or a school hallway camera.

Conclusion

School surveillance video redaction runs on a different legal track than police body camera redaction, even though the technical work of obscuring faces and identifying information looks similar. FERPA's education-records framework, its law enforcement unit exception, and the added complexity of Title IX investigation files all shape what a district can disclose, to whom, and under what timeline, well before a state public-records exemption ever comes into play. Districts that classify footage correctly at intake, redact rather than withhold whenever it is reasonably possible, and keep a contemporaneous record of every redaction decision are better positioned to respond to requests quickly and to defend those decisions later.

Focal Forensics helps school districts and their counsel handle exactly this kind of multi-student, multi-camera video, with frame-by-frame human review and a documented redaction log built for FERPA, Title IX, and state public-records scrutiny alike. Learn more about our video redaction services or reach out to discuss how your district's current process handles multi-student footage.

Phone: 303-900-3585 · Email: info@focalforensics.com

Sources

• U.S. Department of Education, Student Privacy Policy Office: FAQs on Photos and Videos under FERPA
• U.S. Department of Education, Student Privacy Policy Office: What Is a Law Enforcement Unit Record?
• Cornell Law School Legal Information Institute: 34 C.F.R. 99.8, What Provisions Apply to Records of a Law Enforcement Unit
• Student Press Law Center: Commonly Requested FERPA Records
• Pullman & Comley: The Latest on FERPA, FOIA and School Videotapes