- Confirm the FERPA and student-data-privacy posture in writing.
- Ask about a signed data privacy agreement, available at the district level.
- Review how role-based access limits who sees which students.
- Understand what happens to data over time and when staff leave.
- Bring procurement and technology reviewers in together to avoid rework.
Before a district adopts any tool that holds student data, someone on the technology or legal side runs a review. Here are the questions worth asking about Evident so that review goes quickly and you get clear answers.
Start with the regulatory floor
FERPA, role-based access, and student-data-privacy agreements are the floor, not the differentiator. Begin your review by confirming that floor is met: how student data is handled, who can access it, and what protections are in place. These are reasonable, expected questions, and you should get straight answers.
It helps to separate the floor from the value. Many tools can claim baseline compliance. What you are really evaluating is whether the daily evidence the tool produces is objective and timestamped enough to hold up when a meeting turns adversarial, which is the actual reason to adopt it.
Ask for the data privacy agreement
At the district level, you can request a signed data privacy agreement to share with your technology or legal team. This is the document your reviewers will want, and it is a normal part of a district purchase, so ask for it early in the process.
If your state or consortium uses a standard data privacy agreement framework, raise that. Working from a framework your district already recognizes usually moves the review faster than a bespoke document.
Examine access controls
Role-based access is central to how Evident protects student data. In your review, confirm how access is scoped: a case manager sees their caseload, a teacher shared on a student can log against that student without broader permissions, and an administrator sees building or district rollups rather than every individual record by default.
It is also worth confirming the honest framing of administrator visibility. Leaders see coverage rollups, evidence readiness, and per-teacher logging status such as the most recent log date, but not the content of individual logging sessions. For a privacy review, that distinction matters: visibility is scoped to need, not granted broadly.
Understand the data lifecycle
Ask what happens to data over time and at key transitions: when a student is archived, when a plan changes, and when a staff member leaves. Evident treats daily evidence as records you may need to defend later, so it is preserved through plan changes and archiving rather than deleted on a billing event.
For staff departures, this connects to provisioning and access removal. Confirm how an account is deactivated when someone leaves, so access does not linger. Your technology team will care about this specifically.
Bring the right reviewers in together
Reviews stall when procurement, technology, and special-education leadership each evaluate in isolation and surface conflicting requirements late. Bring them in together early, so the data agreement, the access model, and the instructional value are all examined in one pass.
If it helps, use this as a checklist to structure the conversation, and lean on the compliance and procurement material for the specific questions each reviewer should bring. A coordinated review is faster and produces fewer surprises before sign-off.
Frequently asked questions
Is Evident FERPA-aligned?
FERPA and student-data-privacy practices are the floor we build on. Confirm the specifics in writing during your review; these are expected questions and you should get straight answers.
Can we get a signed data privacy agreement?
Yes, at the district level you can request a signed agreement to share with your technology or legal team. If your state or consortium uses a standard framework, raise it to speed the review.
How is student data kept appropriately contained?
Through role-based access. Staff see the students relevant to their role, and administrator visibility is scoped to rollups and readiness rather than every individual record by default.
What happens to data when a teacher leaves?
Access is removed when an account is deactivated, which connects to provisioning at the district level. The student evidence itself is preserved, not deleted, since it may be needed later.