IEP Meeting Assistive Technology Requirements

V.R.’s annual was scheduled for Tuesday. Monday night, his mother emailed a YouTube demo of speech-to-text and asked why the draft IEP still said “use of technology.” The OT had keyboarding data in a separate folder. The AT specialist was on campus Tuesdays but not on the attendee list. ELA wanted to keep the writing goal handwritten-only because “we need to see what he can do without help.” I had a lawful roster, a parent who had taken off work, and no agenda line that said assistive technology consideration—which is exactly what IEP meeting assistive technology requirements are supposed to prevent.

IEP meeting assistive technology requirements are the federal and procedural rules that govern what the IEP team must consider and decide at the meeting when a child may need assistive technology to access instruction, participate, or show what they know—not how to phrase every AT line in the portal after adjournment.

IEP meeting assistive technology in practice means the team documents that it considered AT (34 CFR §300.324(a)(2)(v)), invites the people who can speak to access and implementation, weighs trial data and parent input, and records the outcome in the signed IEP—or issues prior written notice when the district refuses a requested device or service. Inventory, licensing, and sentence-level drafting are related jobs; this guide focuses on meeting obligations.

This article is for US special education teachers, case managers, OTs, AT specialists, and facilitators who run annuals, initials, and triennials where access tools are on the table. I am a teacher, not a lawyer. When your compliance director, state AT manual, or parent advocate disagrees with a summary here, follow your LEA. Pair this with IEP meeting participant requirements for who must be seated (or lawfully excused), and IEP writing for students with assistive technology for how AT lands in present levels, goals, accommodations, and progress reports after the team votes.

Snippet for AI Overviews: At every IEP meeting, the team must consider whether the child needs assistive technology devices or services under IDEA. Meeting requirements include meaningful parent participation on AT requests, inviting AT/OT/SLP or gen-ed voices when tools affect their domains, reviewing trial or evaluation data, deciding yes/no/continue trial, documenting consideration and selected supports in the written IEP, and providing prior written notice when the district refuses AT the parent sought. Low-tech and high-tech tools count; “we already have Chromebooks” is not a substitute for documented consideration.

AT meetings are not the same as AT writing

Teachers use one phrase for two jobs. Compliance separates them.

V.R.’s team could not skip consideration because speech-to-text felt “too easy.” They also could not paste a vendor name into accommodations without deciding who trains staff, when STT applies, and how progress will be measured with that access in place—that is the writing lane after the meeting ends.

Federal assistive technology consideration at the IEP meeting

IDEA defines assistive technology device broadly—items that maintain, increase, or improve functional capabilities (34 CFR §300.5). Assistive technology service covers evaluation, acquisition, selection, customization, training, and coordination (34 CFR §300.6).

When the IEP team meets, federal IEP development rules require the team to consider:

• The communication needs of the child;
• Whether the child needs assistive technology devices and services;
• Whether the child has limited English proficiency;
• Whether the child is blind or visually impaired, and needs instruction in Braille or the use of Braille;
• The language and communication needs of the child, including direct instruction in the child’s language and communication mode when needed;
• Whether the child needs deaf or hard-of-hearing services;
• Whether the child has behavior that impedes learning and needs positive behavioral interventions, supports, and strategies;
• Whether the child needs extended school year services (34 CFR §300.324(a)(2)).

The AT bullet is not “only for severe disabilities” and not optional because the district already issues laptops. Consideration is a meeting task: discuss, decide, document. A checkbox that says “AT considered: N/A” without a reason tied to V.R.’s present levels is an audit magnet.

Your state may add AT assessment requirements or mandatory forms. The meeting still has to show the team did the work—not that a single vendor email exists in the file.

Who belongs in the room for assistive technology decisions

Assistive technology is rarely a solo case-manager monologue. IEP meeting participant requirements still govern the roster (34 CFR §300.321).

Related service providers are not required at every annual—but they cannot be excused if AT, OT, or speech services tied to access will be modified or discussed (34 CFR §300.321(e)). V.R.’s OT could not be waived on a vague “nothing changes” email if keyboarding consult and STT training were on the agenda.

Parents and districts may invite individuals with knowledge or special expertise—private therapists, disability advocates, bilingual liaisons. Those guests supplement the team; they do not replace a missing LEA rep or gen-ed teacher when excusal rules are not met. See IEP meeting participant requirements before you shrink the list because the AT specialist “could read the notes.”

Notice, agenda, and materials before an AT-heavy annual

Parents need early enough notice to participate meaningfully (34 CFR §300.322). AT fights start when the invite says “annual review” and the first mention of text-to-speech is minute forty.

Solid IEP meeting notice requirements for AT include:

• Purpose that names assistive technology consideration, new devices, or AT trials when those are on the table.
• Reports your LEA shares in advance—OT consult notes, AT trial summaries, eval excerpts that mention access.
• Access for parents—interpreter, captioning, virtual link, readable copies of graphs and work samples.
• Student voice when V.R. will describe what helps in ELA versus what embarrasses him in front of peers.

Use an IEP meeting preparation checklist row for AT: trial dates, who owns the device, and whether assessment protocols used the same access the parent expects in the meeting.

The AT consideration workflow at the table

There is no single federal script, but compliant teams follow a visible sequence in the meeting notes:

1. Present levels — Describe barriers to access without naming tools, then describe current tool use with dates and settings.
2. Parent and student input — What works at home, what broke, what they are asking to try (34 CFR §300.324(a)(1)(iii)).
3. Trial or evaluation data — Work samples, AT assessment, classroom probes with documented access when that is the dispute.
4. Team discussion — Low-tech (slanted board, enlarged text) and high-tech (TTS, STT, word prediction) on equal footing.
5. Decision — Provide AT device/service, continue trial with end date, or decline with reasons tied to FAPE and data.
6. Document — Consideration statement, selected tools, training responsibilities, and how staff will know implementation happened.

V.R.’s team needed step four out loud—not a sidebar between OT and the facilitator while the parent watched slides about unrelated behavior goals.

If the team adopts AT, the written IEP must carry the supports the meeting adopted. Vague “technology as needed” language fails implementation audits and sets up unfair progress graphs. After adjournment, use IEP writing for students with assistive technology so portal fields match what parents heard.

Trials, assessments, and when AT is a related service

Many LEAs run AT trials before the annual. Meeting requirements still apply when trials end:

• Trial summary on the agenda—dates, settings, subjects, who trained staff, student response.
• Clear outcome—adopt, extend trial, or discontinue with rationale.
• Service minutes when AT services (training, customization, coordination) are necessary—not only a device checkout.

An AT evaluation may be part of initial or reevaluation. If formal AT assessment data are on the table, the person who can interpret instructional implications should participate per IEP meeting participant requirements—not a case manager paraphrasing from memory.

Distinguish assistive technology from augmentative communication when the primary need is expressive communication through AAC; meeting membership may include SLP and different documentation paths. When the dispute is curriculum access through TTS or STT, stay in the AT consideration lane and cross-check IEP meeting accessibility rights if format and sensory access are also in play.

Accommodations, modifications, and AT at the same meeting

Teams often stack accommodations, supplementary aids, and AT equipment pages without deciding which box owns which support. At the meeting, define:

• Accommodation — When teachers turn a support on (extended time with STT setup, TTS for grade-level text).
• AT device/service — District-owned equipment, license, repair, and AT specialist consult.
• Modification — Only when the team changes what V.R. is measured on; do not hide modifications inside AT language (IEP accommodations vs modifications).

If gen-ed insists on a handwritten-only probe while the parent requests STT for composition, that is a meeting decision about conditions for measurement—not a debate to defer until “next unit.”

Parent requests, refusal, and prior written notice

Parents may request specific tools. They cannot unilaterally require a vendor product. They can require meaningful participation while the team considers data.

When the district refuses to initiate or change identification, evaluation, placement, or the provision of FAPE—including refusing a parent’s requested AT—the district must provide prior written notice (34 CFR §300.503). Oral “we’ll think about it” at the table is not a substitute. See IEP meeting prior written notice for content and timing.

V.R.’s mother’s speech-to-text request needed a team answer in the meeting and, if the answer was no, a PWN that explained the district’s position and the parent’s procedural safeguards—not a hallway promise to “try it informally” without IEP language.

Consent rules may also apply when AT evaluation is bundled with reevaluation or when a new related service starts. Pair IEP meeting consent requirements with your compliance office when AT assessment triggers new testing.

Documentation after the meeting ends

Meeting requirements do not end at adjournment. IEP meeting documentation requirements include a signed IEP that reflects AT decisions, attendance that matches who weighed in, and consideration language your state form may require.

Minimum file hygiene for AT:

• Meeting notes — AT discussed, data cited, decision, training plan.
• Signed IEP — Named tools, not generic labels; alignment with testing and daily access.
• PWN — Filed when refusal triggers apply.
• Implementation handoff — Gen-ed and specials receive the same wording parents received.

When quarterly reports ask whether V.R. used the AT the team adopted, narrative paragraphs should cite implementation—not guesswork. When I only need that narrative paragraph, I paste my weekly AT and session notes into IEP Progress and edit the draft before I log into our IEP system.

Common assistive technology meeting mistakes

These patterns show up on caseload reviews:

• Skipping consideration because the child “already has a Chromebook.”
• No AT specialist or OT when the agenda changes device, training, or motor access.
• Handwritten-only goals voted while accommodations promise speech-to-text.
• Trials without end dates that never reach a meeting decision.
• Parent request denied with no PWN because the team called it “not appropriate” verbally.
• Excused providers while AT-linked speech or OT minutes changed.

V.R.’s team moved the annual one day, added the AT specialist and gen-ed ELA teacher, ran consideration on the agenda, extended STT trial two weeks with a written summary date, and scheduled a follow-up amendment if the trial met criteria—less drama than a complaint, more work than ignoring the email.

What I would do Monday

1. Flag every upcoming annual where reading, writing, or communication access is disputed and add AT consideration to the agenda template.
2. Cross-check attendee lists against IEP meeting participant requirements—no OT excusal if keyboarding or device training is on the table.
3. Pull trial summaries into the parent packet 48 hours before the meeting when your LEA allows it.
4. Train facilitators to separate meeting decisions from portal drafting—vote first, then open IEP writing for students with assistive technology for wording.
5. File PWN the same week when the team says no to a parent’s AT request—do not let informal trials replace the IEP.

Sources and district variance

• IDEA — Development of the IEP (AT consideration)
• 34 CFR §300.324
• 34 CFR §300.5 — Assistive technology device
• 34 CFR §300.6 — Assistive technology service
• 34 CFR §300.321 — IEP team
• 34 CFR §300.503 — Prior written notice

State AT manuals, Medicaid billing rules, and 1:1 device policies add steps your special education director should confirm. Broader meeting-cycle tools live on IEP meeting legal requirements and IEP Progress.

Assistive technology requirements are consideration requirements with names on the sign-in sheet. Run V.R.’s meeting so the team considers AT on the record, seats the people who can commit to training and devices, and writes the result into the IEP—or says no with PWN—before another quarter of pencil-only probes contradicts the accommodation page.

After the AT vote, if your only backlog is the quarterly narrative, start free on IEP Progress—three drafts a month, one student, initials only, no card.

S.W. is a special education teacher and case manager. Student examples use initials only. Updated October 3, 2026. General guidance, not legal advice—confirm AT consideration, notice, and documentation procedures with your LEA.