Grades, Transcripts and the Education Record
A plain-language guide to grades, transcripts and the education record: the record, the purpose, the authority and the safeguard.
- Record
- education record in education records and directory information
- Data
- Grades, Transcripts and the Education Record
- Safeguard
- a published directory designation and a working opt-out
- First check
- Name the record and its holder before any use or disclosure.
The short answer
The first thing to settle in grades, transcripts and the education record is the identity of the education record and the reason it is retained, since each later issue regarding consent, exception or contract depends on those two facts. Where the record is unclear, the rest of the analysis wobbles with it; where the record is clear, the decision usually follows without drama.
An exception that fits the facts of one case does not automatically fit the next case, even when the two cases involve the same platform or the same office.
Opt-out procedures that are hard to find or hard to use shall be treated, fairly, as if they did not exist.
Sensitive survey topics need the highest standard of notification and permission, since the injury of an unwanted sharing is greatest there.
A breach response that starts with notification and skips containment shall notify students about a problem that is still getting worse.
What this covers
Emergency disclosures need a real emergency and a judgment that the sharing is necessary to safeguard health or safety, documented at the time.
Voice information in support and proctoring systems is biometric in substance, even when vendors describe it as audio processing.
Biometric templates should be deleted when a student leaves, on a specified timetable, and the removal should be verifiable.
Grades, transcripts, enrolment facts and disciplinary outcomes are the clearest education files, but the category reaches well beyond them.
Media requests for student information should go through the privacy officer, not through the first office that picks up the phone.
Disability documentation is among the most sensitive data an institution retains, and it should never travel with broad academic files by default.
How to work through it
Assess new systems before purchase, with privacy review as a gate, not as a comment added after the contract is signed.
Read exceptions narrowly and on their own terms, and do not stretch an exemption to cover a purpose that merely resembles the named one.
Review access when roles change, and treat a role change without an access review as an open incident, not an administrative delay.
File the decision where a log is required, and keep the log in a place a future reviewer can really find.
Provide former students a workable procedure for exercising rights over records held about them, since graduation should not end practical access.
Include incident notification in vendor contracts with a stated timetable measured in hours or days, not in vague promptness language.
Establish dependency before disclosing to parents of a student, and do not assume it from a family relationship or a disclosed surname.
Document exceptions to policy with a named approver and an expiry, because permanent exceptions are just undeclared policy changes.
A worked illustration
In that illustration the audit finding becomes a remediation task with an owner and a date, and the subprocessor's copy is deleted on a verified timetable.
Consider an alumni department that wants to publish a class directory and that verifies opt-outs and designations for former students before publishing.
Consider a tutor who wants a second opinion from a colleague about support for a student, and who first verifies whether a summary without identifiers would serve.
Consider a survey of younger users on a learning platform that collects birth dates for age screening and then retains them indefinitely.
In that illustration the university must retrofit an alternative under pressure, and the students affected have previously lost trust in the procedure.
Where guides go wrong
Responding to a media request from the first department that answers is an error, since the first department is rarely the department that knows the disclosure limits.
Writing a notification that no student can find, or that no student can understand, is a mistake that undermines every later reliance on that notification.
Answering a complaint about denied access without reasons is an error, because an unexplained refusal cannot be challenged or learned from.
Responding to an access request slowly, or in an unusable format, is an error, since delay turns a right into a frustration.
Sharing a disciplinary outcome beyond the limits for that offence and recipient is an error that can harm a student long after the process ends.
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 and Department of Education guidance Applies when: When a college holds, uses or discloses a education record in the context of education records and directory information