Advising at scale
A counselor with hundreds of students on the caseload drafts individual family outreach, with student identifiers screened before a prompt leaves and every draft landing on the record.
Verillian governs what AI may do with student data on the device where the work happens. The student identifiers your policy flags are screened out before a prompt leaves. Every captured action lands in a record the district holds for FERPA.
In a school district, AI arrives the way most tools do, one classroom and one office at a time: a counselor drafting outreach, a records office summarizing transcripts, a special education team working through IEP paperwork. The tools help, and nearly everything they touch is an education record protected by FERPA, the Family Educational Rights and Privacy Act. An acceptable use policy cannot decide what a tool may read, and it leaves nothing behind to show what happened. A rule that runs on the staff device can do both.
Everyday school work runs under rules the district writes once: what each tool may do, what may leave a machine, and what goes into a record of every decision that only you can read.
A counselor with hundreds of students on the caseload drafts individual family outreach, with student identifiers screened before a prompt leaves and every draft landing on the record.
Teachers use AI to draft rubric-based feedback and lesson materials, with your policy deciding what a tool may read from a roster or a student's work.
Records, enrollment, and student services put AI on transcripts, verifications, and state reporting, where a governed tool's export nobody approved is refused before it happens.
FERPA hands families and students rights over the education record, and hands the district the duty to guard it. Verillian does that guarding on the device, at the point of action.
The student names and dates of birth it catches are replaced on the device, so the tool works on the task rather than on a named student.
Every captured action seals under your key on your hardware. When a parent, a student, or the Department of Education asks, the answer exists.
Teachers, counselors, and the records office each get their own declared policy, because drafting feedback and releasing a transcript shouldn't run under the same rule.
The checkpoint runs on the district's managed Mac and Windows machines today, on-prem or in the tenancy you already operate, and no student data reaches Verillian, ever.
The AI nobody asked IT about is governed by the same policy as the AI you licensed, because the rule lives on the device and not on an approved list.
FERPA compliance belongs to the district, and no tool changes that. What Verillian adds is the part policy memos can't do alone: student identifiers screened at the machine, uses governed before they run, and evidence of all of it under your control.
Your district holds its obligations. Verillian supplies the on-device controls and the record that back them up.