The Difference Between a Record and a Note
The Difference Between a Record and a Note explained for colleges: the rule, the exceptions, and the record an institution should keep.
- Record
- education record in student privacy foundations
- Data
- The Difference Between a Record and a Note
- Safeguard
- a published notice and a named owner for every record
- First check
- Check that the recipient is bound to use the data only as agreed.
The short answer
Put merely, the difference between a file and a note is regarding control over an education file that belongs, in a practical sense, to a student and is retained in trust by an university. The university may use it for the objective it was collected for, disclose it where the law or a valid consent permits, and must protect it everywhere else. Everything in this guide is a way of making that sentence workable at a desk, stage by stage.
Sensitive survey topics need the highest standard of notification and permission, because the injury of an unwanted disclosure is greatest there.
Readiness for a regulator inquiry is built in ordinary weeks, via inventories and logs, not in the week the inquiry arrives.
When security and privacy requirements appear to conflict, the conflict should be escalated and documented, not resolved by ignoring one side.
Course evaluations can become education records when they are maintained regarding identifiable students, and that possibility should be checked, not assumed away.
What this covers
Video surveillance retains images of identifiable students, and its retention, access and sharing requirements ought to be written before cameras are installed.
Language access matters for confidentiality notices, since a student who can not read a notification can not meaningfully consent or opt out.
Advising platforms hold some of the most personal narrative data on campus, because advisers file context that grades alone never demonstrate.
Event and attendance systems hold location information regarding students, and that information can reveal patterns that deserve safeguarding.
Disciplinary releases to victims and others have specific limits, and the outcome that might be disclosed depends on the offence and the recipient.
International student systems retain visa and immigration data, and the sensitivity of that data should shape each disclosing determination regarding it.
How to work through it
Contain students in oversight, because students notification confidentiality problems that staff have normalised.
Review third-party access routinely, and remove access that is no longer required, rather than leaving it in place for convenience.
Retain applicant records on a stated schedule, and delete them when that schedule expires, rather than keeping them indefinitely.
Prepare documentation a regulator would request for, and keep it in one place, because scattered documentation reads as no documentation.
Limit financial aid releases to what the aid determination needs, and do not include unrelated record details because they happen to be in the same file.
Run internal audits on a stated cycle, and track findings to closure with owners and dates.
Plan for remote work explicitly, with controls that travel with the record to staff homes and personal devices.
Give former students a workable procedure for exercising rights over files retained about them, because graduation should not end practical access.
A worked illustration
Consider a faculty member who wants to use a free AI grading tool and discovers the tool retains submissions for training by default.
The cost of fixing the badly done adoption, in renegotiation, migration and lost trust, is far higher than the cost of the review that was skipped.
Where the full record is genuinely needed in such a case, the disclosing is limited, explained to the student where required, and noted in the record.
Consider an instructor who wants a second opinion from a colleague about support for a student, and who first checks whether a summary without identifiers would serve.
In that illustration the merged college reconciles the schedules before migrating data, and deletes files that both schedules agreed had expired.
Where guides go wrong
Accepting a vendor's consumer confidentiality policy as a substitute for a contract is an error, since consumer policies describe the vendor's own practices, not the college's purposes.
Handling a transfer or withdrawal as if it ended a student's rights is an error, since rights over records previously retained do not end when enrollment ends.
Treating internal disclosing as unrestricted is an error, because internal receivers still need an objective and authority for the record.
Retaining audit evidence too long is an error of its own, because evidence kept beyond its schedule becomes a record that itself needs safeguarding.
Retaining information just in case is an error dressed as caution, since information kept without purpose is information exposed without benefit.
Sources and evidence on the record
- Family Educational Rights and Privacy Act, 20 U.S.C. 1232g, statutory text.
- 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.
Evidence basis: FERPA statute and regulation, Department of Education guidance Applies when: When a college holds, uses or discloses a education record in the context of student privacy foundations