IEP meeting transcription for special education teams

An IEP meeting transcript is not the IEP. The IEP is the federally-mandated written document — goals, services, accommodations, signatures — that the team produces under IDEA. A transcript is the working record of what was discussed, who committed to what, and which parent question got a real answer versus a "we'll get back to you." Used well, AI transcription frees the case manager from typing during the meeting so they can actually look the parent in the eye. Used badly, it creates a FERPA-covered education record that nobody planned for.

This article is for special education coordinators, case managers, school psychologists, and district administrators trying to decide if AI transcription belongs in the IEP workflow. We'll be direct about where it helps, where it doesn't, and what your district needs to settle before the first pilot.

What IDEA requires — and what a transcript is not

Under IDEA (34 CFR §300.320–300.324), the IEP itself is the legally binding document. It must include present levels of performance, measurable annual goals, special education and related services, accommodations, and the team's signatures. There is no federal requirement to record or transcribe the meeting that produces it.

The useful framing: the IEP is the deliverable. The transcript is engineering notes — it captures the reasoning, the parent's exact words, the SLP's recommendation that didn't make it into the final goal section, and the principal's verbal commitment to a one-on-one aide review in 30 days.

The transcript also feeds Prior Written Notice. If a parent requests a specific 1:1 reading intervention and the team declines it, the PWN must reflect both the request and the district's reasoning. A verbatim record makes that drafting honest — you can quote the parent's words and the team's exact response, rather than reconstruct them from memory three days later when the dispute is already brewing.

Minutes vs. transcript — the practical difference

Minutes are summarized. Someone — usually the case manager — decides what mattered. Two months later, when the parent asks "you said you'd reassess the reading goal by November," minutes will say "team discussed reading goal." A transcript will say:

Ms. Rivera (case manager): "We'll bring updated DIBELS data to the November check-in and revisit the fluency target then."

That specificity is the point. It also means the transcript is a contemporaneous record of a meeting about a specific student — which puts it squarely inside FERPA.

FERPA — who holds the recording matters

A recording or transcript of an IEP meeting is an education record under FERPA the moment it is maintained by the school district. Parents have the right to inspect and review it. It cannot be disclosed to third parties without written consent (with the usual exceptions for school officials with legitimate educational interest, transfer schools, audits). The district must have a retention and destruction policy that covers it.

The FERPA "sole possession records" exception is narrow — a teacher's private memory aid, never shared. A full AI-generated transcript sitting on a vendor's server is not a sole possession record. Treat it like an evaluation report.

Two practical implications for AI transcription:

1. The vendor is a school official only if the contract says so. Under 34 CFR §99.31(a)(1), an outside service provider can receive PII from education records without consent only if the district has designated them as a school official with a legitimate educational interest, under the district's direct control, and contractually bound to FERPA terms. A click-through SaaS signup by an individual teacher does not meet that bar.

2. Personal accounts on personal devices break the chain. If a case manager uses their personal Otter.ai account to record an IEP meeting, the district has arguably created an education record outside its own systems. That's a FERPA exposure, not a productivity win.

When you scope a vendor, ask the boring procurement questions early. Who can delete recordings? Can access be limited by role? What happens when a staff member leaves the district? Does the vendor train models on your audio? We don't — your meeting audio is not training data for us, and deletion in the dashboard purges it from our servers. Some consumer tiers of other tools do train on user audio. For special education data, that is the wrong default.

On the AI side — what we ship and what we don't

We run AssemblyAI Universal-3 in production for audio-to-text and meeting transcription. On clean conference-room audio with a decent omnidirectional mic, we see roughly 92% accuracy (WER ~7.88%) on English. On a laptop mic across a 12-foot table with HVAC noise — closer to the typical IEP room — expect worse. If a parent dials in by speakerphone, that leg is 8 kHz telephony and our accuracy drops to ~82% (WER ~17.7%).

We are HIPAA-grade in our data handling at rest, but we are not a HIPAA BAA-covered product yet. For IEP work, the relevant framework is FERPA — but the gap matters if related-services notes (OT, SLP, counseling, school nurse) live in a Medicaid-billable medical record system. Ask your district counsel which framework applies to which artifact.

We support 99 languages at one price, every language. That helps when a meeting is conducted entirely in Spanish or Vietnamese. It does not replace a qualified interpreter, and consecutive interpretation tends to confuse diarization — the interpreter's voice keeps reappearing between every parent and team turn. The transcript will be readable but speaker labels will need cleanup.

What we don't ship, stated plainly:

• No live in-meeting captions. We transcribe the recording after the meeting. If a parent needs realtime CART captioning as an accommodation, use a CART provider — that's a different service.
• No native iPhone app. Web only, mobile-responsive.
• No automatic SIS or IEP-software integration. You export the transcript (TXT, DOCX, SRT, VTT, JSON) and paste or upload into Frontline, SEAS, SpedTrack, or whatever your district uses.

Telling parents you're recording — and why it changes the room

Two-party consent isn't only legal hygiene. It changes the meeting dynamic in ways the case manager will feel within the first ten minutes.

When the team announces "we're recording so we can focus on the conversation instead of typing, and you'll get a copy of the transcript," the parent stops watching the case manager's laptop and starts talking to the team. Commitments get made on the record, which makes them stick.

Offer the parent a copy of the transcript by default. If they decline the recording, default to traditional minutes — don't argue. The recording exists to serve the parent and the student, not to corner anyone. A weaponized transcript is worse than no transcript.

One concrete script we've seen districts use:

"We'd like to record this meeting so [case manager] can be fully present with you instead of typing. The recording stays in district systems under the same FERPA protections as the IEP itself, and you'll get a copy of the written transcript. Is that okay with you? You can ask us to stop at any point."

For virtual meetings on Google Meet, Zoom, or Microsoft Teams, our bot (Recall.ai under the hood) joins the participant list under a name you configure and posts a consent disclosure in chat. The opt-out endpoint at /opt-out/{token} is live.

Diarization with five people in the room — and the hybrid case

A typical IEP meeting has the parent, general ed teacher, special ed teacher / case manager, related service provider, and an LEA representative. Five to seven speakers is normal. A reevaluation can push to nine.

Our setup:

• Channel-split (per-speaker tracks): near-perfect. Available when each participant has their own mic — typical for fully virtual meetings.
• Mono with pyannote-3.1: good for 2–4 speakers, degrades beyond 6. On a six-person IEP with overlapping turns, expect the model to occasionally merge two quiet speakers, or split one speaker into two when their voice shifts (leaning forward vs. back).

Hybrid is the hardest case. Three staff in a conference room plus a parent on Zoom: the parent's audio is clean and isolated, the in-room voices blur together. Either use separate mics in the room, or build a closing-script habit — the chair restates each decision and follow-up out loud before ending. Three minutes of structured restatement at the end improves the transcript more than any model setting.

Two more mitigations:

1. Do a voice round at the start. "I'm Maria Rivera, case manager." Thirty seconds of clean labeled audio gives the case manager an anchor for relabeling speakers in post.
2. Use one mic in the middle of the table. A $60 USB conference mic (Jabra Speak, eMeet) cuts WER materially compared to a built-in laptop mic across the room.

After the meeting, the case manager spends 5–10 minutes renaming "Speaker 3" to "Dr. Patel (school psych)." That's the realistic time investment.

Turning the transcript into a structured review — not a wall of text

A 60-minute IEP meeting produces around 9,000 words. Nobody reads 9,000 words to find out who is mailing the consent-for-evaluation form. The transcript is the source of truth; the artifact the parent uses is shorter.

A workable post-meeting structure separates five things:

• Decisions — items the team agreed to include in the IEP.
• Requests — what the parent or staff asked for during the meeting.
• Refusals — what the district declined, with the reasoning (this feeds PWN).
• Action items — who will do what by when.
• Open questions — items needing follow-up before the IEP is finalized.

This matters because IEP meetings contain negotiation. A parent may request a 1:1 aide at 10:12, the team may discuss alternatives at 10:24, and the administrator may agree to collect more observation data at 10:41. "Team discussed aide support" loses all of that.

Example action items from a 75-minute meeting:

• Ms. Rivera will share updated DIBELS data before the November 14 check-in.
• Dr. Patel will complete the FBA observation by October 30.
• Mr. Chen will trial extended time + manipulatives starting Monday.
• Principal Adams will confirm the 1:1 aide review outcome by December 1.

Mandatory human-review zones before any of this becomes a record:

• Service minutes ("15 minutes weekly" and "50 minutes weekly" sound similar and mean different things).
• Goal criteria and percentages.
• Dates and deadlines.
• Evaluation, medication, and evaluator names.
• Placement language.
• Any refusal that may trigger Prior Written Notice.

AI is good at recall. The district is responsible for accuracy. We don't auto-generate commitments lists yet — a summarization layer is on our roadmap, and we'd rather ship it with the case manager in the loop than have it hallucinate a commitment the principal didn't actually make.

A district-level pilot — how to start

Three or four meetings is enough to know if this fits your team.

1. Get district counsel sign-off on the vendor relationship — FERPA school-official designation, data processing agreement, retention schedule. Personal accounts are not a pilot.
2. Pick low-risk meeting types. Annual reviews for one program. Do not start with manifestation determinations, due-process-adjacent meetings, or meetings where a parent has already objected to recording.
3. Update the IEP meeting notice with a recording consent line. Track consent and refusal rates.
4. Pick three case managers across grade bands. One device, one good mic per case manager.
5. Define the artifact — transcript in district drive under the student folder, structured review (decisions/requests/refusals/actions/open questions) emailed to parent within 48 hours, traditional minutes as fallback.
6. Review after 4–6 meetings. Ask case managers: did you make eye contact more? Ask parents: did the action list reflect what you remembered? How many corrections did staff make to service minutes and dates?

If the answer is yes and the correction rate is low, expand. If diarization is poor in your rooms, fix the audio before deciding the tool doesn't work.

What next

• Try a real IEP recording (with consent) on our Free plan — 30 audio-minutes per month, exports unlocked. Local recording uploaded as MP3 uses 1 credit/minute; the meeting bot uses 2 credits/minute, so for in-person meetings, a USB recorder stretches your minutes further.
• Read the meeting-notes feature page for export formats and the webhook payload.
• If you're a district administrator scoping a FERPA rollout, email us — we can walk through the data processing agreement and retention configuration before you commit.
• If a related-services team works under HIPAA rather than FERPA, ask us about BAA status before that pilot, not after.