How to Screen Student Footage for FERPA Compliance Before Publishing an Alumni or Donor Video

A donor communications team at a mid-size university spends three weeks cutting a beautiful alumni profile video, the kind meant to anchor a capital campaign landing page, and two days before it's scheduled to go live someone in general counsel asks the question nobody wants to hear that late: does the footage of current students walking through the quad in the background have signed releases on file, and if it doesn't, is anyone in that shot identifiable enough to matter under FERPA? We hear a version of this question constantly from advancement and communications offices, and it's almost never because a team was careless, it's because FERPA review usually gets bolted onto the end of a video project instead of built into it from the first cut.

Why FERPA Applies to Videos That Aren't "About" Students at All

The Family Educational Rights and Privacy Act protects the education records of currently enrolled students, and the part that catches communications teams off guard is how broadly "education record" and "personally identifiable" get interpreted once video is involved. An alumni testimonial video shot on campus might feature current students walking past in the background of a b-roll shot, a current student worker who happens to be visible at a campus event the video is covering, or footage from a class visit where enrolled students are identifiable by name badge or context even if they're never named on camera. None of those students are the subject of the video, and that's exactly the trap, because the rule isn't only about whether a student is the focus, it's about whether they're identifiable and whether their appearance discloses something tied to their enrollment.

What a Documented Review Trail Actually Needs to Show

If a release is ever questioned, whether that's a parent calling the registrar, a student objecting after the fact, or an internal compliance audit, the question you'll get asked isn't "did you think about this," it's "show me exactly when this footage was reviewed, who reviewed it, and what they approved." A verbal sign-off in a hallway conversation or a thumbs-up emoji in a Slack channel doesn't hold up as documentation, and neither does an approval buried in an email thread that's since been archived or deleted by someone who left the department.

• A named reviewer attached to every approval
• A timestamp showing exactly when each clip was reviewed
• The specific frame range that was flagged or cleared
• A record of what was cut or blurred in response to a flag
• A version history proving the final export matches what was approved

Building the Screening Pass Into the Edit, Not After It

The teams who handle this well don't treat FERPA review as a final gate right before publish, they treat it as a pass that happens alongside the rough cut, the same way a legal read happens alongside a script rather than after the film is locked. That means the compliance reviewer, whoever holds that role on your team, whether it's someone in the registrar's office, general counsel, or a designated advancement compliance lead, gets access to the rough cut early and can flag a shot the moment it's assembled rather than after color and sound have already been finished on it.

Why Frame-Level Flags Beat General Notes Here

A note that says "there might be a FERPA issue somewhere around the middle of the video" is functionally useless to an editor, because it forces someone to scrub the whole timeline hunting for a face they may or may not recognize. A note pinned to frame 1,240 that says "the student in the green jacket at the library entrance needs a release check" is something an editor can act on in under a minute. Timecoded commenting exists for exactly this gap, and it's the difference between a compliance pass that adds a day to your schedule and one that adds two weeks because everyone's re-watching the whole cut trying to find what got flagged.

Who Actually Needs a Seat in This Review

FERPA review usually pulls in more people than the core video team expects going in. Advancement or communications owns the project, but the registrar's office or general counsel often needs visibility into anything involving current-student footage, and depending on your institution's policy, the dean of students' office may need to weigh in if the footage was captured at a student event rather than a general campus shot. On a typical capital campaign video with campus b-roll woven through it, we routinely see four or five distinct reviewer roles touch the file before it clears, which is more than most communications teams plan for when they first scope the project timeline. The catch here is that adding each of these reviewers under a per-seat pricing model gets expensive fast, especially for a review pass that might only happen two or three times a year, which is one reason we see university advancement offices specifically asking about flat-price alternatives to Frame.io when this workflow comes up. A flat PlayPause pricing plan means the registrar's office, general counsel, and the dean of students can all get a seat in the review for the two weeks they actually need it, without your office paying for a license they'll touch three times a year. Some offices route release paperwork through DocuSign or a fillable PDF, but the video review still needs to happen inside the same system tracking comments and versions, otherwise a release gets confirmed in one place while a flagged frame sits unresolved somewhere else.

Training Student Workers to Spot the Risk Before It Reaches Review

A lot of the footage that eventually gets flagged was shot by a student worker or a junior member of the comms team who didn't know to ask the question in the moment. We tell advancement teams that the cheapest FERPA fix is upstream of the edit entirely, it's a five-minute briefing before any campus shoot that tells whoever's holding the camera to note down where and when identifiable current students appear on tape, even in the background. That note doesn't replace the formal review, but it gives your compliance reviewer a head start instead of asking them to spot every risk cold on a fresh cut, and it means fewer surprises show up two days before a launch date.

The Directory Information Exception, and Why It Doesn't Solve This

A lot of advancement staff have heard that FERPA has a "directory information" exception and assume it covers most of what shows up in a b-roll shot, since directory information, things like a student's name, major, dates of enrollment, and sometimes a photo, can generally be disclosed without individual consent as long as the institution has properly notified students and published what counts as directory information under its own policy. The part that trips teams up is that any currently enrolled student can opt out of having their directory information disclosed at any point, simply by filing a FERPA hold with the registrar, and that opt-out doesn't come with a visible marker on the video itself, there's no watermark or flag on the footage that tells an editor a given student has a hold on file. Depending on the institution, anywhere from two to five percent of a given student body typically has an active FERPA hold in any given year, which sounds small until you remember that a single wide shot of a lecture hall or a dining hall might contain a dozen or more identifiable students, and the odds that at least one of them has an opt-out on file are higher than most communications teams assume going in.

This is exactly why the directory information exception can't substitute for an actual review pass, it narrows the legal exposure in some cases, but it doesn't remove the need to check, because the exception only applies to students who haven't opted out, and nobody on the video team has a way to know who that is without asking the registrar directly. Treating "it's probably fine, it's just directory information" as a reason to skip the frame-level pass is a mistake we see communications teams make more than they'd expect going in.

What Happens When a Release Doesn't Exist

Sometimes the flag comes back and there's no release on file for the student in frame, and at that point the decision isn't really a video-editing decision anymore, it's a compliance decision that the video team needs a clear answer on before they can move forward. Having the flagged frame, the reviewer's name, and the date all attached to one comment thread means whoever makes that call, whether it's blur the face, cut the shot, or track down a release after the fact, has everything they need in one place instead of hunting through separate systems to reconstruct what was even flagged. Some offices keep a running policy of defaulting to a blur or a reframe whenever a release can't be confirmed within 48 hours, simply because the campaign launch date doesn't move just because a release request is sitting in someone's inbox, and having that fallback documented alongside the flag means the editor isn't left waiting on an answer that never comes.

Keeping the Trail Intact After the Video Goes Live

Documentation doesn't stop mattering the day the video publishes. If a question comes up eight months later, and it does happen, having comment history, version history, and reviewer sign-off preserved in one place means you're not reconstructing the story from memory or digging through a former employee's old inbox. This is part of why Sharing Security and clean Approvals tracking matter as much for a university advancement office as they do for a brand agency handling client sign-off, the stakes are just different, but the need for a real paper trail is the same. If your team is separately routing recruitment videos through deans and department chairs, our piece on dean and faculty sign-off on recruitment video covers that adjacent workflow, and for more general guidance on video compliance and rights clearance, the Motion Picture Editors Guild is a solid outside reference.

A Simple Standard to Apply Before Every Alumni or Donor Video Ships

At the end of the day, the standard worth holding your team to is simple even if the legal language behind it isn't: no current student appears identifiably in a published video without either a release on file or a documented decision that the footage doesn't require one. Getting there consistently means the review has to be built into the edit, tracked at the frame level, and tied to a named reviewer every single time, not just when someone happens to remember to ask, and it means the compliance reviewer needs real access to the working cut, not a finished export they're seeing for the first time the week of launch.

Give Your Compliance Reviewer a Real Seat in the Process

If your advancement team is still routing FERPA review through screenshots and email chains, bring your next alumni or donor video into PlayPause so your compliance reviewer can flag exactly the frame in question, your editor can respond without guessing what they meant, and you walk away with a documented approval trail instead of a hope that nobody ever asks.