AI in IEPs & Special Education: 10 Questions to Ask Before a School Pilot Starts

Why AI “Pilots” Matter More for IEP Students

Schools are moving fast on AI—sometimes with the best intentions: saving teacher time, improving reading support, or offering new ways for students to communicate. But when AI tools are used with students who have IEPs (or 504 plans), the stakes are higher.

AI can be a powerful form of assistive technology in schools, especially for students who benefit from text-to-speech, speech-to-text, reading supports, language scaffolds, executive function coaching, or alternative communication. At the same time, not all “AI” is designed for special education. And not all school pilots are built with the guardrails families expect.

If your child’s school says they’re piloting an AI tool, you deserve clear answers before it’s turned on in a classroom—especially if it touches IEP goals, accommodations, or student records.

Below are 10 practical, parent-friendly questions to ask about AI for IEP students, with notes on what good answers sound like.

The 10 Questions to Ask Before the Pilot Starts

Use these questions in an IEP meeting, an email to the principal, or a call with the special education team. You’re not “being difficult.” You’re doing what good advocacy looks like.

1) What specific student need is this AI tool solving?

Ask for a plain-language statement of the problem.

Good signs:

• The school names a clear need (e.g., “supporting written expression for students who struggle to start assignments”).
• They can explain what the tool does and what it does not do.

Watch-outs:

• “We’re trying it because it’s popular.”
• “It helps everyone learn better” (without specifics).

2) Is this an assistive technology (AT) tool—or a general ed tool being used as AT?

This matters because AT decisions should connect to documented needs and accommodations.

Ask:

• Will the tool be listed as AT, an accommodation, a supplementary aid/service, or just a classroom resource?
• Who decided that, and based on what data?

Good signs:

• The team can map the tool to IEP supports (e.g., “speech-to-text for written output”).
• There’s a plan to update the IEP if the tool becomes necessary for access.

3) How will the tool align to my child’s IEP goals and accommodations?

AI can accidentally undermine the skill an IEP is trying to build.

Ask:

• Which IEP goals does it support (or not support)?
• When is it allowed—and when is it not allowed?

Examples:

• If the goal is planning and organizing writing, an AI “write it for you” feature might reduce practice.
• If the goal is access to grade-level content, AI summaries or vocabulary supports might be appropriate.

4) What student data is collected, and is it considered part of the education record?

This is the heart of student data privacy in special education AI.

Ask for specifics:

• What data is collected (voice recordings, writing samples, behavior data, prompts, chat logs)?
• Who can see it (teachers, vendor staff, subcontractors)?
• How long is it stored and how is it deleted?

Good signs:

• The school can provide a clear data list and retention timeline.
• The vendor contract states data is not used to train public models.

5) Does the tool comply with FERPA, COPPA, and state student privacy laws—and how?

Don’t accept “Yes, it’s compliant” without details.

Ask:

• What’s the legal basis for using the tool with minors?
• Is parent consent required for this pilot?
• Has the district approved it through a formal vetting process?

Good signs:

• The district has a written review process and documentation.
• You can get the vendor’s privacy policy and the district’s signed data agreement.

6) What accessibility standards does the tool meet?

“Works on iPads” isn’t the same as accessible.

Ask:

• Does it support screen readers, captions, keyboard navigation, and font/contrast controls?
• Is it usable for students with dyslexia, low vision, hearing differences, motor challenges, or AAC needs?

Good signs:

• The tool has an accessibility conformance report (often called VPAT).
• The school has tested it with actual student accessibility needs.

7) How will the school prevent bias, misinterpretation, or harmful outputs?

AI can misunderstand a child’s language patterns, disability-related behaviors, or communication style.

Ask:

• What guardrails limit inappropriate responses?
• Can the AI be restricted from sensitive topics?
• How does the school handle incorrect information (“hallucinations”)?

Good signs:

• Adults supervise use, especially early on.
• The tool is configured for education (not open-ended public chat).

8) What training will staff and students receive (and how will usage be monitored)?

Even a great tool fails without training.

Ask:

• Which staff are trained (special ed teachers, paras, related service providers)?
• Will students be taught how to use it responsibly?
• How will the school monitor use without turning it into surveillance?

Good signs:

• Short, practical training with examples tied to IEP accommodations.
• Clear rules for when AI is allowed during instruction and assessment.

9) How will success be measured—and what happens if it doesn’t work?

A “pilot” should have a beginning, middle, and end.

Ask:

• What metrics define success (reading fluency, writing output, assignment completion, independence)?
• What baseline data will be used?
• What is the exit plan if it’s ineffective or harmful?

Good signs:

• The school names 2–4 measurable outcomes and a review date.
• There’s an alternative plan so your child doesn’t lose support.

10) What are the boundaries for grades, discipline, and evaluation?

This one is easy to overlook.

Ask:

• Will AI outputs affect grades?
• Could AI logs be used in discipline decisions?
• Will AI be used to evaluate staff or to make high-stakes decisions about students?

Good signs:

• The school commits: no high-stakes decisions based solely on AI.
• Clear policy: AI is a support tool, not an authority.

A Simple Parent Checklist (With What to Ask and What to Request)

Use this table as a quick reference when you email the school or prepare for a meeting.

Area	What to ask	What to request in writing	Red flags
Purpose	“Which student need is this solving?”	Pilot goals + student groups impacted	Vague benefits, no defined need
IEP alignment	“How does it support IEP goals/accommodations?”	How it will be used during instruction/assessment	Tool replaces skill-building without plan
Data collection	“What data is collected and stored?”	Data inventory + retention/deletion timeline	Chat logs stored indefinitely
Privacy compliance	“How does it meet FERPA/COPPA/state law?”	Signed district data agreement (DPA)	“Vendor says it’s compliant”
Accessibility	“Is it usable with my child’s access needs?”	VPAT/accessibility documentation	No screen reader/caption support
Human oversight	“Who monitors outputs and use?”	Supervision plan + escalation path	Students using unsupervised open chat
Measurement	“How will you measure success?”	Baseline + review date + decision criteria	No baseline, no end date
Boundaries	“Can it affect grades/discipline?”	Policy on grading/discipline and AI logs	AI used as evidence or sole decision-maker

What Parents Can Say (Scripts That Keep Things Calm and Clear)

If you’re not sure how to bring this up without sounding confrontational, try these.

• “I’m open to innovation, and I want to make sure it truly supports my child’s IEP goals. Can we walk through how it will be used day-to-day?”
• “Before my child is included, I’d like to understand what data the tool collects and whether it’s used to train the vendor’s model.”
• “If the tool becomes necessary for access, how will we document it so my child isn’t dependent on something that disappears next semester?”
• “Can we agree on a review date and what success looks like, so we’re not guessing later?”

Also consider asking for these practical guardrails:

• A “no surprises” rule: you’re notified before your child’s account is created.
• An opt-in or opt-out process for the pilot (if available in your district).
• A single point of contact (case manager, AT specialist, or admin) for questions.

Next Steps: How to Get Started Before the Pilot Rolls Out

Here’s a simple, realistic plan you can do this week.

1. Ask for the pilot one-pager

   • Request the tool name, purpose, who it’s for, and the timeline.

2. Request the privacy and data documents

   • Ask for the vendor privacy policy and the district’s signed data agreement (DPA) or equivalent.

3. Schedule a short check-in with the IEP team

   • Keep it focused: IEP alignment, allowed uses, and how progress will be measured.

4. Agree on “when AI is on” and “when AI is off”

   • Especially important for assessments, writing samples, and skill-building goals.

5. Set a review date

   • Put it on the calendar (e.g., 6–8 weeks). Decide what data you’ll look at together.

When AI tools in special education are chosen carefully, set up responsibly, and reviewed with real data, they can help students access learning with more independence. Your questions aren’t roadblocks—they’re the guardrails that make a pilot worth running.