AI Grading and the Record It Creates
AI Grading and the Record It Creates explained for colleges: the rule, the exceptions, and the record an institution should keep.
- Record
- student input to an AI tool in ai tools and student privacy
- Data
- AI Grading and the Record It Creates
- Safeguard
- a pre-adoption review and a contract term on training use
- First check
- Name the record and its holder before any use or disclosure.
The short answer
For ai grading and the record it produces, think in terms of a chain: a student, a student input to an AI tool, an objective, an authorization, a receiver, a safeguard and a retention date. Break any link and the disclosing fails, even if every other link is sound. This guide walks that chain link by link, so the reader can see exactly where a proposed disclosing retains and where it breaks.
Amendment is not the same as removal: a successful challenge corrects or explains a file, and the original entry often remains in the file with the challenge noted.
Health surveys on campus may trigger additional protections, and the survey design ought to settle those protections before distribution.
Analytics can improve teaching, but analytics built on identifiable student data need the same authorization analysis as any other use.
The safest test for any proposed disclosing is to write it down in one sentence naming the record, the receiver, the purpose and the authorization, and then to read that sentence back critically.
What this covers
Audit and evaluation disclosures must be limited to the audit or evaluation purpose, and the receiver must be bound to that purpose.
Alumni directories raise the same designation issue, because former students retain an interest in how their information is published.
Platforms that feed directory information to outside directories need an opt-out check built into the feed, not added as a manual afterthought.
Biometric templates ought to be deleted when a student leaves, on a specified timetable, and the deletion ought to be verifiable.
Attendance data, participation logs and advising notes may all be education records when they are maintained regarding an identifiable student.
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.
How to work through it
Publish directory designations where students encounter them at enrolment, not only in a handbook appendix.
Design age screening to collect as little as possible, since screening that collects more than it needs becomes the problem it was meant to solve.
Assess surveillance proposals for necessity and proportionality, not solely for legality, since lawful surveillance may still injury trust.
Settle survey protections before distribution, including anonymity, storage and reporting, since retroactive protection is rarely credible.
Retain applicant records on a stated schedule, and delete them when that schedule expires, rather than retaining them indefinitely.
Honour deletion rights for children's data swiftly, and make deletion reach backups and subprocessors on a specified timetable.
Apply the highest notification and consent standard to sensitive survey topics, since the harm of unwanted disclosure is greatest there.
Distinguish employee files from student files for student employees, since the capacity in which a record was created matters.
A worked illustration
Consider a college that adopts the same platform without an alternative, and that discovers too late that some students cannot or shall not enroll.
In that illustration the logs are released only to the extent the procedure needs, with redactions for students not involved.
Consider a vendor audit that finds a subprocessor nobody had recorded, holding a copy of student records for a retired integration.
Consider an education analytics project that begins with an issue about retention and ends with a dashboard that nobody can explain to a student.
Consider a student who asks to see an advising note that contains a factual error, and who receives the note, the correction process and a written determination.
Where guides go wrong
Running an audit that finds problems and then monitoring nothing to closure is worse than running no audit, since it proves the college knew.
Auditing surveillance platforms only for image quality, and not for access and retention, is a mistake, because cameras generate files continuously.
Adopting a free tool without reviewing its information practices is a mistake, because the price is often paid in information uses nobody reviewed.
Disclosing a full record when a summary would serve is an error, because the extra information adds risk without adding value to the objective.
Analysing a marketing use as routine, and therefore authorised, is a mistake, since routine is not authorization.
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.
- US Department of Education, ed.gov - guidance, Dear Colleague letters and enforcement information.
Evidence basis: 34 CFR Part 99, Department of Education guidance, FTC AI guidance Applies when: When a college holds, uses or discloses a student input to an AI tool in the context of ai tools and student privacy