Answer every school district public records request on the state clock, with every withholding cited and no student identified
Requests met on the state clock, every withholding cited, no student identified.
See one case, screen by screen ↓A school district public records request asks a district for its records under the state public records act: staff email, dispatch logs, board texts. The district must answer on the act's clock and withhold only what the law protects, with each withholding cited. School District Public Records Requests puts seven agents on that work: they classify each request, search the email archive, redact student data under FERPA in two blind passes and write the exemption log, and the records officer decides every flag and releases.
AI in education: a buyer's guide to agentic AI for colleges, universities and school districts →
Updated
A school district public records request runs on the state act's clock, and most of what it asks for is email. The records office finds every message about a topic across staff mailboxes, removes the duplicates, decides which are responsive, and blacks out what the law protects before the requester sees a page. In a school district the hardest part is the students. FERPA protects not only a child's name and ID number but any detail that, alone or in combination, would let a reasonable person in the school community identify the child (34 CFR 99.3). A bus route, a stop, a grade and a wheelchair can name a child as surely as her name does.
Today that is done by hand, one box at a time, with tools that flag phone numbers and Social Security numbers but not “the kindergartner who rides alone from Larkspur Court”. The exemption log is written at the end, so the log and the boxes disagree, and counsel sees the reasons only when an appeal arrives. Requests have grown several-fold since 2020, and the commonest records-office breach is a student identified in a release. School District Public Records Requests puts seven agents on that work, so the records officer decides the pages that need judgment instead of reading every one.
Estimated staff hours on one request the size of PRR-26-0583 (214 responsive emails, 538 pages), by hand and with the agents. This is our arithmetic, kept modest, not a measured result.
Seven agents classify, scope, collect, redact twice and log; the officer decides and counsel reviews.
Request PRR-26-0583 at Marlow Bay Unified School District, about 48,000 students in 62 schools: a reporter asks for a month of transportation email about canceled bus runs. It is Wednesday, October 21, business day 9 of 10. Here is the request, screen by screen, in the working solution.
Kendra Haliburton of the Marlow Bay Ledger asks through the records request portal for all emails of district transportation staff about the cancellation of bus route 14 runs in September. The Intake agent classifies it as a media public records request, not a FERPA access request or a subpoena, starts the 10-business-day clock, due Thursday, October 22, and links PRR-26-0595, a request for the route's GPS logs. The acknowledgment goes out at 2:15 p.m. and a $0 estimate on October 9, under the two free staff hours in Board Policy 1340.
The Search agent searched 9 custodians' mail and the dispatch folder in document management for September 1–30 with six terms: 1,862 emails, 1,197 after duplicates, 214 responsive with 37 attachments, 538 pages. Each sampled record shows why it is responsive. Ama checks 40 responsive and 30 not responsive records and confirms the search.
The first pass marks 66 student names, 9 student ID numbers, 39 personal phone numbers and emails, 2 security codes and 3 attorney-client emails withheld in full. The second pass, on a different model and blind to the first, reads the same 538 pages. They agree box for box on 531 pages; only the 7 disagreements go to the records officer.
Lorena's morning brief cites every line: PRR-26-0583 is due tomorrow with two pages waiting, PRR-26-0591 is too broad at 14,200 emails, and document management did not answer at 9:58 a.m. Of the seven disagreements she has decided six: two kept with a reason code, one kept as a public office number, three redacted.
In a dispatcher's email of September 15, the second pass caught “the student in the wheelchair at the Quarry Gate stop”. The page appears as the reporter will see it, each black box labeled F-1 or P-1, with the exemption log building beside it. Above the page, a warning: the phrase matches 1 student, below the district threshold of 10.
No name, but the student information system shows 1 route 14 rider at Quarry Gate with a lift-bus accommodation, so a reasonable person in the school community could identify her (34 CFR 99.3(f)).
Lorena redacts the phrase as F-2, an indirect identifier under FERPA, 34 CFR 99.3(f), with IDEA confidentiality (34 CFR 300.622) noted. The log line is written beside the page in category words, never the redacted content. With the phrase boxed, 212 route 14 riders match.
A principal's email says “the kindergartner who rides alone from the Larkspur Court stop at 7:12”. Both passes left it, but the re-identification check found that route 14, kindergarten and the Larkspur Court stop together match 1 student. Boxing only the stop leaves 6; only the grade, 4. Boxing “kindergartner” and “Larkspur Court” leaves 212.
That is the smallest fix; it is your decision.
Lorena accepts the smallest fix: two F-2 boxes, and the sentence still tells the reporter what happened. The page is marked “Redacted as F-2 by you” with 212 matching students, and a new line joins the exemption log, waiting for counsel's second review.
The exemption log has 124 lines: F-1 75, F-2 5, P-1 39, S-1 2, AC-1 3. Renata reviewed lines 1–119 at 8:55 a.m.; now she approves the last 5, on pages 312, 415, 268, 147 and 88. Each line gives the page, the category withheld, its basis and who placed it, and F-2 lines note the same rule in an earlier release.
The officer places the box; counsel second-reviews it before it is cited. Lorena cannot approve her own lines.
The sign-off chain is complete: search confirmed and package prepared by the clerk, redactions decided by the officer, 124 of 124 lines reviewed by counsel. Lorena releases 532 pages, with 6 withheld in full, and the exemption log to Kendra Haliburton through the portal, with no fee. Tobias Wren had his heads-up the afternoon before.
One request, four people, each with a part only they can do: what their week looked like, and what it looks like now.
Seven agents classify, scope, collect, redact twice and log; the officer decides and counsel reviews.
Reads each request, tells a public records request from a parent's FERPA access request or a subpoena, starts the clock the law sets on the district calendar and links related requests so redactions stay consistent.
Counts what a request would return, finds the ones too broad to meet the clock and drafts a clarification with narrower options, their counts, pages, hours and fees, from the requester's own stated purpose.
Builds the search plan, searches the email archive and document management, removes duplicates and marks each record responsive or not, with a reason.
First pass: marks student names and numbers, indirect identifiers, personal contact details, security details and privileged records, each with an exemption code.
Second pass, blind to the first and on a different model family; then the re-identification check: how many students in the student information system match what is left, and the smallest redaction that fixes it.
Writes the exemption log from every box, in category words, and checks each line against the district's past releases.
Costs each request from Board Policy 1340 and drafts the acknowledgment, estimate, clarification, extension and release letters, and the media heads-up.
Decide each disagreement, review each withholding. The agents propose; a named person decides.
The assistant answers with the page, the rule and the source cited, and opens the screen where the work is. It drafts; the records officer decides.
Why did the second pass flag page 147?
A dispatcher writes about “the student in the wheelchair at the Quarry Gate stop”. No name, but the student information system shows 1 route 14 rider at Quarry Gate with a lift-bus accommodation, so a reasonable person in the school community could identify her (34 CFR 99.3(f)). The first pass looked for names and numbers and missed it. Boxing the phrase leaves 212 matching riders.
Which requests are due this week?
Three by Friday: PRR-26-0583, route 14 emails, due Thu Oct 22 with 2 pages waiting for you; PRR-26-0560, administrator salaries, due Thu Oct 22 and ready to release; and PRR-26-0562, grievance settlements, due Fri Oct 23 with counsel. Both requests due tomorrow were escalated to counsel at 7:00 a.m.
How many students match what is left on page 88?
Right now, 1: route 14, kindergarten, the Larkspur Court stop. Boxing only the stop leaves 6; only the grade, 4. Boxing both “kindergartner” and “Larkspur Court” leaves 212, above the district threshold of 10. That is the smallest fix; it is your decision.
Draft the clarification for PRR-26-0591
As asked, the request is 14,200 emails, about 118 staff hours and $3,306.00. Mr. Farrow said he is researching the consolidation vote, so the letter offers that scope: 610 emails, $99.75 under Board Policy 1340, plus two other options. The clock pauses while he chooses. Nothing is sent until you approve.
13 screens from the working solution, on its sample data. Pick one to see it large.
Clocks, exemption codes, privacy and agent thresholds are settings. Changes need a second administrator; a change to an agent also needs counsel and is tested on 3 closed requests first.
| Setting | Default | Choose from |
|---|---|---|
| Response time | 10 business days, as the state act sets | Follows the state act, on the district calendar |
| One written extension | Up to 10 business days | Up to 5 business days |
| While a clarification is open | Pause the clock | Keep counting |
| Escalate to counsel | 1 business day before the due date | 2 business days · Same day |
| Re-identification threshold | Warn when fewer than 10 students match | Fewer than 5 · Fewer than 20 |
| Box confidence shown to a person | Any box below 0.90 | 0.85 · 0.95 |
| Keep request files | 3 years after the request closes | 5 years · 7 years |
| Heads-up before a media release | Business day before | Same day · Two days before |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
Sources: a school records-request software provider's published account of district request volumes (one Virginia school district, under 100 requests a year to more than 500 by late 2021; one Michigan request estimated at $900,000 to fulfill) · state public records acts (response clocks of 3 to 10 business days in many states) · 34 CFR 99.3 (personally identifiable information, indirect identifiers, targeted requests) and 34 CFR 300.622 (IDEA confidentiality) · “target” = design goal, measured in the live solution · “demo” = seen in the working solution, on its sample data · “typical” = published figures · “estimated” = our arithmetic, kept modest. Marlow Bay Unified School District and the people named on this page are fictional: characters and sample data in the working solution.
A school district public records request asks a district for its records under the state public records act: staff email, dispatch logs, board texts. The district must answer on the act's clock and withhold only what the law protects, with each withholding cited. School District Public Records Requests puts seven agents on that work: they classify each request, search the email archive, redact student data under FERPA in two blind passes and write the exemption log, and the records officer decides every flag and releases.
The state public records act sets the clock: from 3 to 10 business days in many states, often with one written extension. The solution runs your state's clock on the district calendar, skipping holidays, can pause it while a clarification is open, escalates to counsel the business day before a due date, and drafts the extension letter with the new date for the officer to approve.
FERPA governs the student information inside the records a district releases. It protects a student's personally identifiable information, including details that, alone or in combination, would let a reasonable person in the school community identify the student (34 CFR 99.3). Both redaction passes mark direct and indirect identifiers with exemption codes, and a parent asking for her own child's records is routed to a FERPA access request on its own 45-day clock.
Details that are not a name but can point to one student: a bus stop, a grade, an accommodation, a time. In the sample request, “the kindergartner who rides alone from the Larkspur Court stop at 7:12” matched 1 student. The re-identification check asks the student information system how many students match what is left on each page, warns when fewer than 10 do, and proposes the smallest redaction that fixes it. The records officer decides.
The list of every withholding in a release: the page, the category withheld and its legal basis. Here the Log agent writes a line from every box as it is placed, in category words and never the redacted content, and checks it against the district's past releases. Counsel second-reviews each line before it is cited; the sample request's log has 124 lines.
Yes. The agents may not release, deny a request, send a letter, waive a fee, change a legal due date or remove a box a person placed. The clerk confirms every search, the records officer decides every disagreement and every release, counsel second-reviews every withholding, nobody approves their own work, and every override carries a reason code.
The Agentic Solution Engine builds and deploys it from your requirements and documents, such as your state's public records act, your board policy on records and fees, your exemption codes and a sample of closed requests, and it goes live once every quality gate has passed. We will walk you through it on your own requests first.
Every notice and deadline held to the rule; investigator and decision-maker kept apart.
1-min demoStudent Conduct Case ManagementEvery sanction checked against three years of like cases, with a complete hearing record.
1-min demoClery Act ComplianceEvery published number tied to its source reports, ready for a program review.
1-min demoWe'll run School District Public Records Requests on a sample of your own closed requests, your board policy and your exemption codes.