Every FERPA records request proved, blacked out, signed by a named officer and logged, with the 45-day limit watched on every one
Every records request answered inside 45 days, and no other student's details released.
See one case, screen by screen ↓It is software for answering every FERPA records request a registrar's office receives — from students, parents, employers, other schools, courts and police. Eight agents read each request in its own language, prove who is asking against the student's consents and dependency evidence, cite the FERPA basis, collect the records, black out other students and draft the 34 CFR 99.32 disclosure log entry. A FERPA compliance officer approves every release with a reason code.
AI in education: a buyer's guide to agentic AI for colleges, universities and school districts →
Updated
A FERPA records request asks the registrar's office three questions: who is asking, on what FERPA basis, and what exactly may leave the building. At a university the rights belong to the student (34 CFR 99.5), so a parent may see his records only with his signed, dated consent naming the records, the purpose and the party (99.30), or under an exception such as the dependent-student exception (99.31(a)(8)). Access is due within 45 days (99.10(b)), a group record may show only the requester's student (99.12), and every disclosure without consent goes into the record of disclosures the student may read (99.32).
Today a specialist answers those questions by hand across five systems: the student information system for age and the FERPA flag, the student portal for a consent, the family for a tax return, the conduct office, advising notes, document management and an email export from IT. Other students are blacked out with a PDF tool, the packet is approved by reply email, the answer goes back in English to a family that wrote in Vietnamese, and the log entry is typed in if anyone remembers. FERPA Records Request & Disclosure Management puts eight agents in front of that work, so the compliance officer signs a proof instead of rebuilding one.
Estimated working days of one parent request, by hand and with the agents. Elapsed time also depends on the requester and on other offices; our arithmetic, kept modest.
Eight agents read, prove the requester's standing, black out other students and draft the log; a FERPA officer approves every release.
On Friday, October 2, 2026, at 9:14 PM, Phạm Thị Thu writes to Halden State University's records office in Vietnamese, asking to see her son's spring semester grades. Lê Minh Khoa, Halden ID 3048-8172, is a 20-year-old junior in chemical engineering, and no consent on file names a parent. Here is what happens to request REQ-2026-08417, screen by screen, in the working solution.
386 requests are open. The agents read 41 overnight, said who is asking and started every clock; 27 are ready for an officer's approval, 9 are with counsel and 6 across the office are past day 35. A banner says the email archive has one export overdue since October 9, with Retry beside it.
41 requests came in from the student portal, the records email, scanned mail and the registrar's counter, in English, Spanish, Vietnamese and Korean. The Intake agent named who is asking and what for, started each 45-day clock, sent two subpoenas to counsel and routed a reporter's question to the public records officer.
The release review reads left to right: the request, who is asking, and what may leave. "Tôi muốn xem điểm học kỳ mùa xuân của con trai tôi." sits beside "I would like to see my son's spring semester grades." Pointing at an English sentence lights the Vietnamese one it came from, and each carries a citation. The counter shows the due date, November 16, 2026.
She is confirmed by a one-time code sent to the parent email in the aid record, entered at 10:02 AM. Khoa has two active consents, an official transcript to a co-op employer and his term GPA to a scholarship fund, and neither names a parent. The one that named his parents covered fall 2023 grades and expired on December 31, 2023.
His parents' 2025 Form 1040, page 1, uploaded to the aid file for a special-circumstances review, lists "Minh Khoa Le — son" as a dependent. The agent proposes the dependent-student exception, 34 CFR 99.31(a)(8), at confidence 0.94, and says why the others fail: the rights are his, no consent names a parent, grades are not directory information, and there is no case on his conduct record.
Read in place. The return itself is never released, and only the dependents line is shown.
The Sweep agent searched the student information system, document management, the email archive, advising notes and the conduct system. The spring 2026 grade report, the CHE 2200 grade change record and the grade appeal decision go in. Jamal leaves out two emails about the appeal, because the request asks for grades.
The Redaction agent blacked out 8 items on pages 3 and 4: the names, Halden IDs and peer-evaluation scores of the two other students in Khoa's project group. The Second reader, reading every page on its own on a different model, found a first name the first pass missed. Now 9 items are blacked out, covering 2 other students, and both readers agree on all 4 pages.
“Jonah”, line 14 — a first name alone still points to one student.
Farida approves with reason code FR-04, "Dependent student: most recent return confirms it". Jamal prepared the request, so he could not approve it. Linh Tran, a staff reader of Vietnamese, has already confirmed the reply. The packet goes by a secure link that expires October 28, 2026, and Khoa is told, as Halden policy asks.
Released on day 12 of 45 by secure link to Phạm Thị Thu. Entry LOG-2026-14302 written.
LOG-2026-14302 records the party, the records, the basis 99.31(a)(8) and the legitimate interest, citing the 2025 Form 1040, page 1. Each entry is marked Required when 34 CFR 99.32 demands it and Policy when Halden keeps it anyway, and a toggle shows the log as Khoa can see it. The Log agent checks every morning that no release lacks an entry.
Subpoenas, court orders and law enforcement requests go to counsel, with the advance notice drafted by the Notice agent and the notice period on a clock. In SUB-2026-0117 the student was notified October 7. One release is held because a student filed a motion to quash, and a sheriff's request under a court order not to disclose is released without notice.
Release opens October 17, when the notice period ends.
The same request, seen by the five people who carry it — what their day looked like, and what it looks like now.
Eight agents read, prove the requester's standing, black out other students and draft the log; a FERPA officer approves every release.
Reads every request from the portal, the records email, scanned mail and the counter in the language it was written in, names the requester, the student and what is asked, starts the 45-day clock, and drafts the reply in the same language with the English beside it.
Confirms who is asking, by a one-time code to a contact already on record or the identification seen at the counter, and tests every consent the student signed for its scope, party and date.
Chooses the FERPA basis — the student's own right, consent, directory information, or an exception in 34 CFR 99.31 — cites it with its evidence and confidence, and lists every basis it set aside and why.
Collects the records from the student information system, the conduct office, advising notes, the email archive and document management, and proposes what is inside the request.
Blacks out other students in group records — names, first names, student IDs, grades and scores, email addresses — and anything protected by a directory hold, with a reason for each box.
Re-reads every page on its own, on a different model, before it sees the first pass; any disagreement locks the release until a person decides.
Reads subpoenas and court orders, checks for an order that forbids notice, drafts the advance notice to the student and keeps the notice period.
Drafts the 34 CFR 99.32 entry beneath every packet, writes it when the release is approved, marks whether the rule requires it, and builds the export packs.
Approves every release with a reason. The agents propose; a named person decides.
Ask about any request, student, rule or disclosure — or say what to change. Every answer cites its source and opens the screen it is about.
Why does the dependent-student exception apply to Khoa?
Because his parents' most recent federal return, the 2025 Form 1040, page 1, lists him as a dependent. Under 34 CFR 99.31(a)(8) a university may then show his records to his parents without his consent. The other bases fail: the rights are his, not his mother's; neither active consent names a parent; and grades are not directory information. The release still needs your approval, and it will be written to his record of disclosures.
Which requests could miss the 45-day limit?
6 requests are past day 35, and none is past day 45. REQ-2026-08115, day 41: the conduct office has not confirmed the case file is complete. REQ-2026-08011, day 38: the email archive export has been overdue since October 9; retried this morning. 4 more on other desks, days 35–37, each with a named owner. I can reassign the two on this desk to Bettina Shaw, who has the most room.
Show every disclosure of Khoa's records
His record of disclosures has 2 entries, and 1 is drafted today: LOG-2026-13877, August 19, 2026, official transcript to Ardent Process Systems, on his consent; LOG-2026-14270, October 13, 2026, spring 2026 term GPA to the Halden Engineering Alumni Fund, on his consent; and LOG-2026-14302, drafted, his spring grades to his mother under the dependent-student exception, written when you approve.
What can counsel release today?
One release can go out today: LE-2026-0042. The court ordered that the subpoena not be disclosed, so no advance notice is due. ORD-2026-0031: the notice period ends tomorrow, October 15. SUB-2026-0117: it ends October 17. SUB-2026-0121: the notice is drafted and waiting for your signature. SUB-2026-0109: held, because the student filed a motion to quash.
13 screens from the working solution, on its sample data. Pick one to see it large.
The clocks, the approvers, the evidence the office accepts and who may look under a black bar are settings. The rules that protect students are locked, and every change is a new version.
| Setting | Default | Choose from |
|---|---|---|
| Legal limit | 45 days, locked (34 CFR 99.10(b)) | A shorter state limit: none, 30 or 15 days |
| Halden's own target | 10 business days | Shown on every desk; not a legal limit |
| Escalation day | Day 35 | Escalated to the registrar from this day |
| Advance notice period | 10 days | Between the notice to the student and a subpoena release |
| Dependency evidence accepted | Aid file or a copy from the parent | A copy from the parent only |
| Tell the student after a parent receives records | On | Halden policy; FERPA does not require it |
| Who may see under a redaction | FERPA compliance officer and internal auditor | FERPA compliance officer only; every view logged with a reason |
| Agent thresholds | Basis agent 0.90 · Redaction agent 0.85 | Below it, a person decides; every override needs a reason code, FR-01 to FR-09 |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
Sources: 34 CFR Part 99, eCFR (ecfr.gov) — 99.5, 99.10(b), 99.12, 99.30, 99.31(a)(2), (a)(8) and (a)(9), 99.32, 99.36, 99.37 · U.S. Department of Education, Office of Inspector General, audit of the Student Privacy Policy Office's FERPA complaint process (285 open investigations, September 2017) · "demo" = seen in the working solution, on its sample data · "target" = design goal, measured in the live solution · "typical" = published figures and the rule's own 45-day limit · "estimated" = our arithmetic, including annual volume for a public university of about 38,000 students. Halden State University and the people, students, employers and court cases named on this page are fictional — characters and sample data in the working solution.
It is software for answering every FERPA records request a registrar's office receives — from students, parents, employers, other schools, courts and police. Eight agents read each request in its own language, prove who is asking against the student's consents and dependency evidence, cite the FERPA basis, collect the records, black out other students and draft the 34 CFR 99.32 disclosure log entry. A FERPA compliance officer approves every release with a reason code.
Under 34 CFR 99.10(b), no more than 45 days after the request, and a state law can set a shorter limit. The solution starts the clock when a request arrives, shows it on every request, escalates to the registrar from day 35, and can be set to a shorter state limit.
Only what an exception in 34 CFR 99.31 allows, or directory information under 99.37 when the student has not opted out — for example to the parents of a dependent student, to a school where the student seeks to enroll, or under a subpoena after advance notice. The Basis agent proposes one basis with its citation and evidence and lists every basis it set aside; a person approves, and each disclosure without consent goes into the student's record of disclosures.
At a university the rights belong to the student, so a parent needs the student's signed consent naming the records, the purpose and the party, or an exception such as the dependent-student exception, which needs evidence that the parents claimed the student on their most recent federal return. The Identity agent tests every consent for scope, party and date, and the Basis agent cites the return page while showing only the dependents line.
Subpoenas, court orders and law enforcement requests go to associate general counsel. The Notice agent checks for an order that forbids notice, drafts the advance notice to the student for counsel to sign, and holds the release until the notice period ends or the court rules on a motion to quash.
The Redaction agent knows whose record it is, so it blacks out the other students — names, first names, IDs, grades and scores, email addresses — and never the requester's own student. A second reader on a different model re-reads every page before it sees the first pass, and any disagreement locks the release until a person decides.
Yes. The agents read, prove and draft; they never release a record, send a notice or edit a log entry. A FERPA compliance officer approves every release with a reason code, the person who prepared a request can never approve it, counsel decides every subpoena, and an internal auditor can read and export everything and approve nothing.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your annual FERPA notice, your records policy and a sample of past requests — and it goes live once every quality gate has passed. We will walk you through it on your own requests first.
Every graduate cleared with evidence, honors and names locked before printing.
1-min demoCurriculum Proposal & Catalog ManagementComplete on first reading, with every program a change touches listed before the vote.
1-min demoArticulation Agreement & Transfer Equivalency ManagementEvery partner change caught when its committee votes, before a student loses a credit.
1-min demoWe'll run FERPA Records Request & Disclosure Management on a sample of your own requests and records.