Written Consent Under FERPA: What Counts
Written Consent Under FERPA: What Counts: what it means for an education record, who may use it, and the check to make before it moves.
- Record
- education record in consent and disclosure exceptions
- Data
- Written Consent Under FERPA: What Counts
- Safeguard
- written consent, or an exception that fits the facts, recorded in the log
- First check
- Confirm consent, a named exception, or a contract term before sharing.
The short answer
A practical way to approach written consent under ferpa: what counts is to request what a student would expect if they saw the sharing described in plain language. Where the sharing matches that expectation and the authorization supports it, it can proceed with a log entry; where it surprises, it needs consent, an identified exception or a fresh determination, not a quiet assumption.
A sharing log is not bureaucracy: it is the record that lets a student, an auditor or a regulator reconstruct what happened.
The safest test for any proposed sharing is to write it down in one sentence naming the record, the receiver, the objective and the authority, and then to read that sentence back critically.
Small releases add up: a series of minor sharings may reveal a picture of a student that no single disclosing intended to create.
A policy that nobody has read is not a control, and the test of a policy is whether employees can state its key rule without opening the document.
What this covers
Undocumented students face grave consequences from record disclosure, and employees ought to be especially careful regarding disclosing that could reveal status.
Disability documentation is among the most sensitive information an university retains, and it should never travel with general academic files by default.
Third-party tools connected to an education system may receive more data than the integration was meant to pass, and the actual data flow ought to be tested, not assumed.
Accessibility information in an education platform may reveal disability status, and access to it ought to be limited to employees who need it for support.
An education file is defined by how it is maintained and whom it is regarding, not by the folder it sits in or the system that holds it.
Fingerprint and palm platforms for building access produce a biometric record for each student who enrols in them, and an alternative must exist for students who decline.
How to work through it
Explain redactions in access responses, because an unexplained gap teaches a student that files are edited at will.
Hold a confidentiality committee that may actually stop a project, since a committee that only advises shall be ignored when it matters.
Give small colleges a shared-service option for privacy review, because a college without a dedicated officer still carries the same duties.
Answer complaints about access in writing, with reasons, because an unexplained refusal can not be challenged or learned from.
Full both the COPPA and the FERPA analysis for AI tutors used by younger students before any pilot begins.
Analyse marketing uses of student information for consent even when the marketing feels routine, since routine is not authorization.
Give former students a workable procedure for exercising rights over files held regarding them, since graduation should not end practical access.
Require documented agreements for studies conducted on behalf of the university, with limits on use, de-identification where possible, and destruction on schedule.
A worked illustration
Consider an alumni department that wants to publish a class directory and that checks opt-outs and designations for former students before publishing.
In the badly done illustration, personal comments were included in the export, no removal date was agreed, and the student notification still described the old system.
Consider an institution that runs a wellness survey with sensitive issues and settles anonymity, retention and reporting before a single response is collected.
In that illustration a review finds the retention unjustified, the birth dates are deleted, and the screening is redesigned to collect the minimum needed.
In that illustration students who decline biometrics are not disadvantaged, and the biometric templates of students who leave are deleted on schedule.
Where guides go wrong
Approving a disclosure without recording it is an error, because a reviewer, auditor or student will eventually ask what happened and why.
A reader who applies that structure, and who escalates the cases it cannot settle, will make better determinations than a reader who memorises any single requirement in this ledger.
Letting group mailboxes and shared drives accumulate members without an owner is an error that turns access control into archaeology.
Answering a complaint regarding denied access without reasons is an error, since an unexplained refusal cannot be challenged or learned from.
Treating a course evaluation as anonymous without checking whether it is maintained regarding identifiable students is a mistake.
Sources and evidence on the record
- Family Educational Rights and Privacy Act regulations, 34 CFR Part 99, text on eCFR.
- US Department of Education, Student Privacy Policy Office, studentprivacy.ed.gov - FERPA guidance, FAQs and model notices.
- Family Educational Rights and Privacy Act, 20 U.S.C. 1232g, statutory text.
Evidence basis: 34 CFR Part 99, disclosure and consent provisions Applies when: When a college holds, uses or discloses a education record in the context of consent and disclosure exceptions