School District Public Records Requests demo

What the demo shows

Records officers gather responsive files, redact student data under FERPA and log exemptions

An Intake agent reads each request, tells a public records request from a parent's FERPA access request or a subpoena, and starts the right clock. A Scoping agent drafts a clarification when a request is too broad, with the counts and fees for each narrower option. A Search agent searches the email archive and document management and gives a reason for every responsive record. Two Redaction agents on two different models mark every page blind to each other, and only disagreements reach the records officer; a re-identification check asks the student information system how many students match what is left. The exemption log writes itself from every box, counsel second-reviews every withholding, and the records officer releases.

Transcript

1. 0:00School district public records requests: answered on the state clock, with student data redacted under FERPA.
2. 0:09One district went from under a hundred requests a year to over five hundred.
3. 0:15Every open request is a bar on its state clock.
4. 0:20A reporter asked for September emails about bus route fourteen; 214 are responsive.
5. 0:28The page shows what the reporter will see, each black box labeled with its exemption.
6. 0:36The exemption log builds itself from every box: sixty-six student names so far.
7. 0:44A second Redaction agent read every page blind, and caught what the first missed.
8. 0:51The student in the wheelchair at the Quarry Gate stop: only one student matches.
9. 0:59Lorena redacts it, then applies the agent's smallest fix to one more page.
10. 1:08Counsel second-reviews every withholding, and every step is in the audit trail.
11. 1:13Released: 532 pages on day nine of ten, every withholding cited.
12. 1:21Built on Botminds: agents, data, screens and governance on one platform.

The narration as written for the film. Captions are on the player.