Advising Notes: Record or Personal Note
Advising Notes: Record or Personal Note: what it means for an education record, who may use it, and the check to make before it moves.
- Record
- education record in education records and directory information
- Data
- Advising Notes: Record or Personal Note
- Safeguard
- a published directory designation and a working opt-out
- First check
- Limit the sharing to the minimum the purpose requires.
The short answer
The first thing to settle in advising notes: file or personal note is the identity of the education file and the reason it is retained, because every later issue about permission, exception or contract depends on those two facts. Where the file is unclear, the rest of the analysis wobbles with it; where the file is clear, the decision usually follows without drama.
International students face additional exposure when records travel across borders, and that exposure should shape storage and disclosing decisions.
Sensitive survey topics require the highest standard of notice and permission, since the harm of an unwanted sharing is greatest there.
Cloud hosting does not move responsibility: the college remains answerable for a record even when another company stores it.
The issue is never only whether disclosing seems useful; it is whether disclosing is authorised for this record, this objective and this receiver.
What this covers
Systems that feed directory information to outside directories need an opt-out check built into the feed, not added as a manual afterthought.
State biometric laws add duties that vary by state, and a campus operating across states must not assume one state's requirement covers another's.
Parent and guardian access via a portal is a disclosure decision, and the portal's permissions ought to reflect rights transfer, not family habit.
Disclosures to other schools where a student seeks to enrol are permitted, but the student should be told that such disclosures occur, via the annual notification.
Library systems hold borrowing and access data that can reveal interests and beliefs, and that data ought not to be treated as low sensitivity by default.
Financial aid disclosures to other institutions and agencies follow their own exemption, and the disclosure should be limited to what the aid decision needs.
How to work through it
Audit access to personal records, and follow up on anomalies, since an audit that finds nothing is either lucky or blind.
Review assistive technology vendors for the usage data they collect, because that data may reveal disability.
Analyse marketing uses of student data for consent even when the marketing feels ordinary, because ordinary is not authorization.
Analyse outside survey requests separately from institutional surveys, because the authorization for one does not cover the other.
Apply disciplinary disclosure limits cautiously, because the outcome that may be shared depends on the offence and on the recipient.
Test the actual information flow of an integration, rather than trusting a diagram, since integrations routinely pass more than intended.
Review confidentiality oversight after a merger or platform alter, because the data map from before the alter shall no longer be accurate.
Review shared folders periodically, and treat shared-folder review as a privacy task with an owner, not as housekeeping.
A worked illustration
Consider a campus police unit that produces a law enforcement file and is asked to share it with the dean's department, and that checks the objective of the sharing first.
Consider a vendor that suffers a breach affecting student records, and an institution whose contract required notification within three days.
In that illustration the survey report demonstrates solely aggregates above a specified threshold, and no small-group result can identify a respondent.
In that illustration the rules are published to residents, access is logged, and footage is deleted on schedule unless it is needed for a particular investigation.
Where the full file is genuinely needed in such a case, the disclosing is limited, explained to the student where required, and noted in the file.
Where guides go wrong
Responding to an access request slowly, or in an unusable format, is an error, because delay turns a right into a frustration.
Publishing a directory without verifying the opt-out list is a mistake that is apparent to every student who opted out, and to their peers.
Delaying removal of children's information following a removal request is a mistake, because the information continues to be used while the request waits.
Writing a policy that employees cannot state without opening the document is an error, since the policy will not be followed under time pressure.
This guide does not interpret the law for a specific college, and readers ought to escalate cases it can not settle rather than treating its structure as a determination.
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