Compliance guide
FERPA-conscious IEP meeting documentation
FERPA-conscious IEP meeting documentation means student education records are processed only for authorized school purposes, under agreement, with consent before capture, human review before sharing, and an audit trail of access.
Why this matters for AI note tools
IEP meetings contain education records. A generic business transcription tool may create convenient notes, but districts need clearer limits on who can process the content, how long raw media is kept, and whether anything can leave the building without staff review. AI does not remove those obligations.
Practical controls checklist
School official / DPA relationship
Limit processing to documenting IEP meetings for the contracting district. Prohibit sale of student data and advertising use.
Consent before documenting
Do not start capture until consent is recorded. Decline must stop the workflow cleanly.
Human review before sharing
Treat AI output as a draft. Require staff approval before family-facing or final-record use.
Access controls + audit logs
Scope staff access by district/school role and log access actions on student meeting documentation.
Retention / media purge
After structured documentation is generated, purge raw meeting media from the capture provider according to policy.
No training on customer education records
For enrolled organizations, configure zero-retention / no-training commitments for the documentation workflow and capture vendors.
How IEP Note Taker implements these controls
IEP Note Taker is designed for district IEP workflows: DPA / school official posture, consent before documenting, draft-only AI output until staff approve, role-scoped access, audit logging, and purge of raw capture media after structured documentation is produced. Details are on the Security & FERPA and Privacy & DPA pages.
FAQ
Can districts use AI to document IEP meetings under FERPA?
Yes, when the vendor acts as a school official / contractor under a Data Processing Agreement that limits use to authorized educational purposes, access is controlled, and student data is not sold or used for advertising. Technical and procedural controls (consent, review, audit) remain essential.
Should parents consent before an IEP meeting is recorded or documented?
Best practice is to record parent/guardian or authorized-host consent before capture begins. If consent is declined, documentation should stop and nothing should be retained from that capture attempt.
Should AI IEP notes be auto-sent to families?
No. AI output should remain a draft until staff review and approve it. Human review before distribution reduces risk of inaccurate or incomplete statements entering family communications or the student record.
What audit trail should an IEP documentation tool keep?
Districts should be able to show who viewed, exported, approved, or deleted student meeting documentation. Audit logs support FERPA accountability without putting student PII into application logs.