Audio Recording an IEP Meeting: FERPA, Consent, and the Parent & Counselor Guide
Published November 01, 2026
- FERPA and IDEA are silent on whether IEP meetings can be recorded—state wiretap law and district policy decide, per OSEP's Letter to Savit (Jan. 19, 2016).
- Any recording the school keeps is an 'education record' under 34 CFR Part 99 and cannot be disclosed—or sent to a cloud transcription vendor—without written parental consent.
- If a district prohibits recording, 34 CFR § 300.322(e) requires exceptions whenever a recording is necessary for the parent to understand the IEP process.
- Cloud note-takers (Otter.ai, Fireflies, Zoom AI Companion) create a FERPA disclosure the moment audio leaves the device; on-device transcription avoids that disclosure entirely.
- Counselors should get the district's written recording policy, confirm their state's consent rule, and use an on-device tool like Basil AI that never uploads audio.
Quick answer: FERPA and IDEA don't address audio recording of IEP meetings directly, so whether parents must consent depends on your state's wiretap law and your district's written policy. If the school records, the file becomes an "education record" under FERPA that cannot be disclosed—or sent to a cloud transcription vendor—without parental consent or a written school-official agreement.
Published November 1, 2026 · 11 min read
If you're a parent, school counselor, special education coordinator, or advocate searching "audio recording IEP meeting FERPA consent recording parent," here is the short answer: neither FERPA nor IDEA directly says whether you may record an IEP meeting. The U.S. Department of Education's Office of Special Education Programs (OSEP) has repeatedly said each state (and each district) decides. Whether a parent must give consent for the school to record — or the school must give consent for the parent to record — turns on two things: your state's wiretap/eavesdropping statute (one-party vs. all-party consent) and your local district's written IEP recording policy. But the moment anyone presses "record," a separate FERPA problem starts: any recording the public agency keeps is an "education record" that cannot be shared with a third party — including a cloud transcription vendor like Otter.ai or Fireflies — without parental consent or a formal school-official agreement.
This guide walks through what the federal regulations actually say, what the OSEP policy letters have clarified, how state law layers on top, and what a privacy-conscious school counselor should actually do if they want to capture an IEP meeting without creating a FERPA problem.
What federal law actually says: IDEA, 34 CFR 300.322, and FERPA
The core IDEA regulation governing IEP meetings is 34 CFR § 300.322 (Parent participation). It requires public agencies to take steps to ensure one or both parents attend each IEP Team meeting, to notify them early enough to arrange attendance, and to "take whatever action is necessary to ensure that the parent understands the proceedings of the IEP Team meeting" — including arranging interpreters. Nothing in § 300.322 explicitly authorizes or prohibits audio recording.
That silence is intentional, and OSEP has confirmed it in several policy letters. In the controlling January 19, 2016 Policy Letter to Diana Savit, OSEP stated that Part B of the IDEA "does not address the use of audio or video recording devices at IEP meetings, and no other Federal statute either authorizes or prohibits the recording of an IEP meeting by either a parent or a school official." It remains OSEP's position that "in the absence of IDEA requirements, a State is in the best position to decide the specific criteria it will use to permit audio or video recording devices at IEP Team meetings."
FERPA — the Family Educational Rights and Privacy Act — plays a different role. FERPA controls what happens to a recording after it exists. Per the U.S. Department of Education's FAQs on Photos and Videos under FERPA, a photo, video, or audio recording maintained by a school is an education record when it is "directly related to a student" and "maintained by" the agency. An IEP meeting recording almost always meets both prongs.
If the school records, the file is an "education record"
The Maryland State Department of Education guidance brief on Recording IEP Team Meetings states this cleanly: any recording of an IEP team meeting maintained by the public agency is an education record "protected under the IDEA and the Family Educational Rights and Privacy Act (FERPA), meaning that the recording should not be disclosed without consent." The OSEP Letter to Anonymous (June 4, 2003) reached the same conclusion more than two decades ago.
Practically, that means:
- Parents have the right to listen to and request access to any school-maintained recording of their child's IEP meeting.
- The school cannot share the recording with another parent, another vendor, or the public without written parental consent, except under one of FERPA's narrow exceptions.
- If the recording is uploaded to a cloud transcription service, that upload is a disclosure of PII from an education record to a third party and must satisfy FERPA's rules.
That last bullet is where things get dangerous for well-meaning counselors who grab Otter.ai, Fireflies, or Zoom AI Companion to "just get the transcript" after an IEP. We cover the specific vendor risks in our deeper piece on AI transcription for educators and FERPA.
Does a parent have to consent for the school to record?
Here the answer depends on which state you're in and which policy your district has adopted. The federal floor is: whatever policy a district uses must apply equally to parents and schools. As the parent-advocacy guide Understood.org's Legal FAQs about IEP Meetings explains, if the school is recording the IEP meeting, parents can too — "They can't allow one but prohibit the other."
State-level variation is substantial. In California, the Disability Rights California SERR Manual (§ 4.55) explains that parents may record an IEP meeting without the district's permission as long as they give 24 hours' written notice; conversely, the district may record with 24 hours' notice to the parent, but cannot record if the parent objects — and if the parent objects, neither side can record. Virginia takes a similar "permit and notify" approach codified at 8VAC20-81-170, which requires the LEA to permit audio recording devices at eligibility, IEP, and discipline meetings when the parent gives written notice in advance.
Other states default to their general wiretap statute. Under New York's one-party consent framework, a parent who attends and participates in the IEP meeting can record it without notifying the district — though some districts still impose advance-notice policies. Michigan recording law for schools operates similarly through the participant exception, and confirms that "neither FERPA nor IDEA prohibits parents from recording IEP meetings."
When a district prohibits recording: the required exceptions
A district is allowed to adopt a no-recording policy — but only with mandatory escape valves. Per the OSEP Letter to Savit, if a public agency has a policy that prohibits or limits recording devices at IEP meetings, that policy "must provide for exceptions if they are necessary to ensure that the parent understands the IEP or the IEP process or to implement other parental rights guaranteed under Part B." The same letter notes that even where a district can suspend recording of a meeting, it must still take whatever action is necessary to ensure the parent understands the proceedings.
In practice, that means a district cannot use a "no recording" policy to prevent a non-English-speaking parent, a parent with a hearing or cognitive disability, or a parent who otherwise cannot meaningfully participate in real time from recording. The New Hampshire Department of Education 2022 due process decision IDPH-FY-22-05-037 is a useful illustration: hearing officers have ordered recording to be permitted where it was necessary for parents' meaningful participation.
Comparison: how different approaches handle IEP recording and privacy
| Approach | Who can record? | State consent rule | FERPA treatment of the file | Third-party cloud exposure | Access rights for parents |
|---|---|---|---|---|---|
| Federal IDEA baseline (34 CFR 300.322) | Silent — state/district decides | N/A | Education record if maintained | N/A | Must support parent understanding |
| California (SERR 4.55) | Parent & district, with 24-hour notice | All-party; parent objection blocks | Education record subject to FERPA | Prohibited absent consent/agreement | Inspect, review, challenge |
| New York (one-party consent) | Parent as participant, no notice required | One-party | Education record if district keeps copy | Prohibited absent FERPA basis | Full inspection rights |
| Michigan (participant exception) | Parent as participant | One-party | Education record if maintained | Prohibited absent FERPA basis | Full inspection rights |
| Virginia (8VAC20-81-170) | Must be permitted at eligibility, IEP, discipline meetings with written notice | One-party, plus state SPED rule | Education record subject to FERPA | Prohibited absent consent/agreement | Full inspection rights |
| Counselor using cloud AI note-taker | Depends on state & policy | Varies | Audio uploaded = disclosure to third party | High — vendor storage, possible training use | May be limited by vendor control |
| Counselor using on-device transcription (e.g., Basil AI) | Depends on state & policy | Varies | Education record stays on counselor's device | None — no vendor cloud touches audio | Full inspection rights preserved |
The FERPA trap most counselors don't see: cloud transcription vendors
Here is the scenario we hear repeatedly from school counselors: an IEP meeting runs long, the counselor needs clean notes, and someone on the team suggests dropping the audio into Otter.ai, Fireflies, Rev, or Zoom AI Companion. From a FERPA perspective, that single click is a disclosure of personally identifiable information from a student's education record to a third-party vendor.
Under FERPA, a school may share education records with a contractor only if the contractor qualifies as a "school official with legitimate educational interest" — and that status requires the contractor to be under the direct control of the school with respect to use and maintenance of PII, and to be bound not to re-disclose it. The U.S. Department of Education's Responsibilities of Third-Party Service Providers under FERPA guidance spells out those obligations. A typical consumer sign-up for Otter.ai or Fireflies — with no district-signed data processing agreement — does not meet them.
The vendor policies themselves add risk. Otter.ai's privacy policy describes broad rights to process audio and derived data. Fireflies' privacy policy similarly contemplates cloud storage and processing. Zoom's privacy policy covers meeting content handled across its platform. None of those are inherently illegal — but they are inherently disclosures under FERPA when the content is a student's IEP meeting, and they require either parental consent or a FERPA-compliant written agreement.
What a school counselor should actually do
If you sit in on IEP and parent meetings and need reliable notes, here is a defensible workflow:
- Get the district's written recording policy. If one doesn't exist, ask the special education director to produce it before your next IEP. OSEP has clearly stated states and districts can regulate — but the policy must be written, uniform, and include § 300.322(e) exceptions.
- Confirm your state's consent rule. Resources like the Reporters Committee for Freedom of the Press recording guide catalogue one-party vs. all-party states. For IEP meetings, follow the stricter of state law and district policy.
- Give written notice before you record. Even in one-party-consent states, giving the family and the IEP team advance written notice avoids disputes and models the transparency FERPA expects.
- Keep audio and transcripts on your device. If audio never leaves the counselor's iPhone or Mac, there is no third-party disclosure to analyze under FERPA. This is the simplest way to stay inside your district's existing FERPA perimeter.
- Document retention and deletion. Treat the recording like any other education record: retain according to district policy, honor access requests from parents, and delete when no longer needed.
What this means for school counselors — a 5-item checklist
- Never upload IEP audio to Otter.ai, Fireflies, Rev, or Zoom AI Companion without a district-signed FERPA data-processing agreement and written parental consent.
- Request your district's IEP recording policy in writing; verify it has § 300.322(e)-compliant exceptions.
- Default to the stricter of state wiretap law and district policy for the act of recording.
- Use a transcription tool that processes audio entirely on your device, with no cloud upload.
- Store recordings in your district's existing records system so parents can inspect them under FERPA.
How Basil AI solves this: on-device transcription keeps audio inside FERPA's perimeter
Basil AI is a privacy-first AI meeting transcription app for iPhone and Mac. Its design is specifically relevant to IEP recording:
- 100% on-device processing. Transcription runs locally using Apple's on-device Speech Recognition and the Apple Neural Engine. Audio never leaves the device. See Apple's Speech framework documentation and Apple's privacy overview.
- No vendor cloud, no training. Because Basil never uploads your audio, there is no third-party service that could even theoretically re-use IEP meeting content to train a model.
- 8-hour continuous recording, which comfortably covers back-to-back IEP meetings and lengthy annual reviews.
- Apple Notes integration via iCloud, so your transcript lands in the counselor's existing Apple-ID-protected notes workflow — which, if your district has enabled iCloud Advanced Data Protection, is end-to-end encrypted.
The counselor is still responsible for the act of recording under state law and district policy. What Basil removes is the FERPA "disclosure to a third party" problem that cloud note-takers create by default. For a deeper look at how the on-device architecture works, see our privacy, encryption, and local recordings buyer guide and our no-bot meeting notes explainer.
Edge cases: videoconference IEPs, multiple students, and participant minors
Many IEP meetings now happen on Zoom, Teams, or Google Meet. Three things change in that context:
- Platform-side recording triggers vendor data flows. Zoom's built-in recording stores audio and transcripts on Zoom's infrastructure; Zoom's privacy policy describes how meeting content is processed. If you need a transcript, capturing audio on the counselor's device with an on-device tool avoids adding yet another vendor to the FERPA map.
- Multiple students may be referenced. If an IEP meeting discusses other students (e.g., classroom composition), FERPA's rules on "records of more than one student" apply. The U.S. Department of Education FAQ on multi-student records confirms that a single recording can be the education record of several students.
- Minors may be participants. Students 14+ are often invited to IEP meetings for transition planning. State wiretap laws rarely carve out minors differently, but district policy may add protections.
Documenting consent: a simple template counselors can use
Even if your state is one-party-consent and your district permits recording without parental sign-off, documenting consent is good practice because it (a) creates a paper trail that satisfies district auditors and (b) honors the spirit of FERPA. A workable template:
"On [date], [counselor name] will use an on-device audio transcription tool during the IEP Team meeting for [student name]. Audio and transcripts will remain on the counselor's school-issued device and will be retained as an education record consistent with district policy and FERPA. You may inspect and review the recording and transcript at any time. Please initial to acknowledge this notice."
This is not legal advice; your district counsel should review any template before use. But it demonstrates the key points: who is recording, where the data lives, how long it's kept, and the parent's inspection rights under FERPA.
Bottom line for the "recording IEP meeting" question
Recording an IEP meeting is legal more often than counselors think — but FERPA governs what happens next, and most cloud AI note-takers create a disclosure problem that no district policy fixes. If you are a counselor, SPED coordinator, or parent who wants a reliable transcript without litigation risk, the simplest path is an on-device tool that keeps audio out of any vendor's cloud. For more on the general FERPA framework for educators, see our deep dive on AI meeting transcription for teachers and FERPA; for a plain-English overview of modern AI note-takers, see what is an AI notetaker?; and for the broader picture of consent in meeting recording, see our ABA Formal Opinion 512 analysis (which maps closely to the "meaningful participant consent" question in IEPs).
Record IEP meetings privately — audio never leaves your device
Basil AI runs 100% on your iPhone or Mac. No cloud, no vendor training, no FERPA disclosure to a third party. Built for counselors, SPED coordinators, and privacy-conscious professionals.
Frequently Asked Questions
Does FERPA require parent consent to audio record an IEP meeting?
FERPA itself does not say whether a parent or school may record. The U.S. Department of Education's Letter to Savit (2016) confirms IDEA is silent too. Consent is driven by (1) your state's wiretap law—one-party or all-party—and (2) your district's written IEP recording policy. But any recording the school keeps becomes an education record under 34 CFR § 99.3.
Is a recording of an IEP meeting an 'education record' under FERPA?
Yes. OSEP's Letter to Savit and 34 CFR Part 99 both treat an audio or video recording of an IEP meeting that is maintained by the public agency as an education record. That means parents have the right to inspect it, and the school cannot disclose it—including by uploading it to a third-party transcription vendor—without written parental consent or a qualifying FERPA exception.
Can a school district prohibit a parent from recording an IEP meeting?
Yes, if state law permits. OSEP has consistently said each state (SEA or LEA) may require, prohibit, limit, or otherwise regulate recording devices at IEP meetings. But under 34 CFR § 300.322(e), any policy that prohibits recording must provide exceptions when a recording is necessary for the parent to understand the IEP or the IEP process.
Can a school counselor use Otter.ai or Fireflies to transcribe IEP meetings?
Not without a FERPA-compliant written agreement and, in most cases, parental consent. Uploading IEP audio to Otter, Fireflies, Rev, or Zoom AI Companion is a disclosure of education records to a third party. The vendor must qualify as a 'school official' with legitimate educational interest and be bound by direct control over use and re-disclosure—conditions most consumer AI note-takers do not meet.
What does 34 CFR 300.322 say about recording IEP meetings?
34 CFR § 300.322 governs parent participation in IEP Team meetings. The regulation itself does not grant or deny a right to record; OSEP policy letters interpret it to allow states and districts to regulate recording, so long as policies include exceptions needed to ensure parents understand the IEP (an issue tied to § 300.322(e)'s requirement that the agency take whatever action is necessary for parent understanding).
What's the safest tool for a counselor who sits in on IEP meetings?
A fully on-device transcription app that keeps audio and transcripts on the counselor's iPhone or Mac—never uploading to a vendor cloud—eliminates the FERPA 'disclosure to a third party' problem entirely. The counselor still must follow state consent law and district policy for the act of recording, but the data flow stays inside the school's existing FERPA perimeter.