Disclosure Across Departments Within One College
Disclosure Across Departments Within One College explained for colleges: the rule, the exceptions, and the record an institution should keep.
- Record
- education record in consent and disclosure exceptions
- Data
- Disclosure Across Departments Within One College
- 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
Put simply, disclosure across departments within one university is regarding control over an education record that belongs, in a practical sense, to a student and is retained in trust by an institution. The institution might use it for the purpose it was collected for, disclose it where the law or a valid consent allows, and must safeguard it everywhere else. Everything in this guide is a way of making that sentence workable at a desk, stage by stage.
Security controls safeguard a record from unauthorised access, but they do not make an unauthorised sharing lawful, and the two issues must be asked separately.
Copies of records given to students ought to be full enough to be useful, and redactions of third-party information ought to be explained.
Training changes behaviour only when it is tied to the determinations employees actually make, with a named person to request when the answer is unclear.
Mixed-audience platforms need a child-directed analysis for their younger users, not a single policy documented for adults.
What this covers
Site card platforms retain transaction and location information, and their retention should reflect that sensitivity rather than the convenience of indefinite logs.
Accessibility data in an education system can reveal disability status, and access to it should be limited to employees who need it for support.
Disclosed drives accumulate copies that outlive their objective, and periodic review of disclosed folders is a privacy task, not housekeeping.
Video surveillance retains images of identifiable students, and its retention, access and disclosure requirements should be written before cameras are installed.
Parents of dependent students might receive files under an exception, but dependency must be established, not assumed from a family relationship.
State biometric laws add duties that vary by state, and a campus operating across states must not assume one state's rule covers another's.
How to work through it
Read exceptions narrowly and on their own terms, and do not stretch an exception to cover an objective that merely resembles the named one.
Limit accommodation letters to what a lecturer needs to provide the accommodation, and do not contain the underlying diagnosis.
Contain subprocessors in vendor contracts by name or by category with notification of alters, because an unnamed chain is an uncontrolled chain.
Limit the disclosure to the minimum the objective needs, and treat extra data as extra risk rather than extra helpfulness.
Audit vendor adherence, and do not accept a vendor's self-assessment as a substitute for evidence where the information is personal.
Retain applicant records on a specified schedule, and delete them when that schedule expires, rather than keeping them indefinitely.
Honour deletion rights for children's data promptly, and make deletion reach backups and subprocessors on a specified timetable.
Separate duties so that the person who approves a disclosure is not the solely person who may see that it happened.
A worked illustration
Consider a student who requests for a file that has previously been lawfully disclosed to another office, and who is told where it went and why.
In that illustration the answer depends on whether the notes were ever disclosed, and the service files the reasoning for future cases.
In that illustration the request is answered for the employment capacity only, and the academic file is not disclosed by error.
In that illustration a review finds the storage unjustified, the birth dates are deleted, and the screening is redesigned to collect the minimum required.
In that illustration the directory omits every student who opted out, and the omission is checked by a second person before publication.
Where guides go wrong
This guide does not substitute for a college's own policies or counsel, and a conflict between the two ought to be resolved in favour of the college's own advice.
Disclosing on the strength of a letter alone, without a court order or subpoena process, is a mistake that may be avoided by a single phone call to the confidentiality officer.
Forgetting that a studies agreement must limit use and need destruction is a mistake that leaves research data in circulation after the study ends.
Auditing surveillance platforms solely for image quality, and not for access and retention, is a mistake, since cameras generate files continuously.
Giving a small college no disclosed-service option for confidentiality review is an error, because a college without a dedicated officer still carries the same duties.
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