How to document AAC progress for IEP meetings

Last updated 2026-07-11

If nobody tracks how your child actually uses their device between meetings, the school ends up guessing at their AAC goals, and that guess almost always sells your kid short. The Individuals with Disabilities Education Act (IDEA 2004, 20 U.S.C. § 1414) requires IEP goals to grow out of the child's present levels of academic achievement and functional performance, known in the field as PLAAFP ^[1]. Without documented evidence, that section becomes vague, watered down, or easy to cut.

This plays out the same way in a lot of meetings: parents say the child uses the device more at home, the school says classroom data doesn't show it, and both sides might be telling the truth. The difference is whose numbers show up on paper.

The American Speech-Language-Hearing Association (ASHA) is explicit that AAC assessment and progress monitoring need to account for performance across environments, partners, and communication functions, not just what happens in a 30-minute pull-out session ^[2]. Keeping your own data isn't stepping on the school's toes. You're filling in a gap that a single weekly session can't cover.

It also matters for a more basic reason: devices get abandoned. Research published in the journal Augmentative and Alternative Communication found that abandonment rates climb when implementation is inconsistent and nobody tracks whether it's working ^[3]. When the data shows growth, the team has a reason to keep investing in the device. When it shows a goal has stalled, the team can change course before a whole year is gone.

What good AAC data actually looks like

There's no required format for this, which is both freeing and a little disorienting. Good data shares three traits: it's collected over time, it's tied to something specific, and it tells a story someone can act on.

Frequency counts are the simplest place to start: how many times did your child initiate communication (not just respond) using the device in a set window? Fifteen minutes of watching, three times a week, gives you a real trend over a month.

Core vocabulary use matters just as much. Is your child reaching for core words like "more," "go," "help," and "stop," rather than sticking to fringe words like "cookie" or "Elmo"? ASHA's practice portal treats core vocabulary as the backbone of functional AAC use ^[2], so tracking which words actually get used tells you whether the current layout fits the child.

Communicative functions are the piece people miss most often. A child might hit 50 activations a day, but if every one of them is a food request, their communication hasn't really expanded. ASHA's framework covers requesting, rejecting, commenting, greeting, answering questions, and starting topics ^[2]. A tally sheet with one column per function takes about two minutes to set up, and it's often the single most persuasive page you bring to a meeting.

Worth watching too: how your child responds when partners model AAC. If you're pointing to the device while you talk (aided language stimulation) at home, track whether their response rate shifts over four to six weeks.

And don't skip video. It's not a substitute for written data, but it's a strong partner to it. A 90-second clip of your child spontaneously activating the device to comment on something carries more weight in a meeting than almost anything else you can bring. Keep a dated folder on your phone for these.

If your child also gets speech therapy outside of school, ask that SLP for their session data too. Two sources pointing to the same trend are much harder to dismiss than one.

Setting up a simple system at home

Keep it simple enough that you'll actually keep doing it. A system you maintain for six weeks beats a perfect one you abandon after three days, and this one runs under five minutes a day.

Grab a small notebook or build a weekly log sheet in Google Sheets (ten minutes, tops). Each row is one observation period, with columns for date, time, how long you watched, setting (breakfast, play, bath), number of device activations, number of spontaneous initiations (child started it, not answering a direct question), and one or two functions you noticed.

Don't try to track everything at once. Pick two or three targets that match the current IEP goals. If the goal is "will use the device to request preferred items in 4 out of 5 opportunities," your log tracks requesting. That's the whole job for now.

Once a week, add a short video observation. Set the device in front of your child during something natural, like snack time or a favorite game, and let them lead. Record for ten minutes, then jot the timestamp of any communication act. No need to transcribe: "At 2:14, activated 'more'; at 3:40, activated 'stop' to end game" is plenty.

Many AAC apps already log this for you. Proloquo2Go and TouchChat both record which buttons were pressed and when ^[4]. Export the logs monthly and file them by date. The raw data reads like noise, but a summary does real work: "used device on 18 of 22 school days, averaged 12 activations per day in March vs. 6 per day in October" is exactly what an IEP team can use.

Families using Little Words get communication patterns tracked automatically, with exportable summaries that drop right into a progress log. The quiz at littlewords.ai/start shows how it follows vocabulary development across sessions, and that kind of longitudinal data earns its place at IEP time, especially when you're showing growth over months rather than a single snapshot.

Writing goals you can actually measure

A good AAC goal is measurable, functional, and rooted in real communication. The most common complaint from SLPs and parent advocates alike is that goals get written so loosely that nobody can tell afterward whether the child met them.

A weak goal reads like: "Student will improve AAC use." A strong one reads more like: "Given a natural communication opportunity during a structured classroom activity, [child] will independently activate the AAC device to make a request or comment across 4 out of 5 opportunities, as measured by classroom SLP data and parent log, by [date]." The strong version spells out the context, what counts as success, who's measuring, and when the check-in happens. Every word in it becomes a column in your data sheet.

For children at earlier stages, goals tend to lean toward functions rather than vocabulary size, something like: "[Child] will use the AAC device for at least two different communicative functions (requesting and rejecting) in 3 out of 5 observed sessions per week." Goals for a child in early intervention look different from goals for a school-age child, but the measurement logic stays the same.

ASHA recommends that AAC goals address more than raw frequency of device use: the range of partners, the range of settings, and the variety of communicative functions all matter ^[9]. A child who requests food from Mom but won't initiate with a peer or teacher has a very different profile from one using the device flexibly everywhere, and your data should make clear which dimension you're actually working on.

If your child also has a motor speech diagnosis, our pieces on apraxia of speech and childhood apraxia of speech are worth a look. AAC goals for kids with motor speech disorders often need to account for fatigue and motor planning in ways that goals tied to autism or language delay don't.

Baselines: the piece most IEPs skip

A baseline is simply where your child stands right now, before a new goal period starts. Without one, there's no way to prove growth later, and this is one of the gaps parent advocates flag more than almost anything else, even though it sounds obvious.

In practice it might read: "In October, [child] activated the device an average of 4 times per 30-minute observation, with 90% of activations being requests. She used two functions: requesting and rejecting." Four months later, the same log might show: "In February, [child] activated the device an average of 11 times per 30-minute observation. She used four functions: requesting, rejecting, commenting, and answering yes/no questions."

That's a story the whole team can follow. The goal worked or it didn't, and either way you know what to adjust next.

Base your baseline on at least three separate observation periods so it reflects a typical day rather than a great one or a rough one. If the school doesn't already have classroom baseline data, you can ask them to collect it in the two or three weeks before the meeting. That's your right: under IDEA, the IEP has to rest on current evaluation data and ongoing progress monitoring ^[1].

How do you organize your AAC documentation binder before the IEP meeting?

Bring a binder. It signals you're organized, it keeps you from fumbling through your phone in a tense meeting, and it gives you something to point to when someone questions your data.

Here's a structure that works. Start with a tab for current IEP goals, printed so you can refer to them mid-discussion, followed by a tab for baseline data showing the numbers you started with at the beginning of the goal period. Next comes a tab for weekly and monthly logs, your observation records by month. Messy handwritten logs are fine here. What matters is that they're dated and consistent.

Add a tab for app or device export data: if the app logs button presses, include a printout or a screenshot of the summary. Then a video log tab, where you usually won't play clips during the meeting but you'll note which ones you have and when they were recorded, something like "October 14, child spontaneously activated 'help' during play without a prompt." Offer to share the video if the team wants it.

A tab for communication partner notes matters too. If teachers, aides, or other family members have watched the child use AAC, ask each for a short note, even one paragraph. Multiple observers across settings beat a single source. And if your child gets online speech therapy or other private services, ask that therapist for a brief progress summary to slot in as a final tab. Come with two copies of everything, one for you and one to hand the team. You're not legally required to share your notes, but offering them tends to turn the meeting into a collaboration instead of a standoff.

What data does the school team need to provide, and how do you ask for it?

Under IDEA, schools must give parents regular progress reports on IEP goals, at least as often as report cards go home ^[1]. The quality swings wildly. Some schools send a detailed graph with weekly data points. Others send a one-page form with a checkbox next to "making progress."

Before the meeting, send a written request (email is fine) to the SLP or special education coordinator asking for the data behind the progress report: the collection method, the frequency of observation, the settings where data was gathered, and the raw numbers over time. Something like, "Can you share the data sheets or session notes showing [child's] AAC use in the classroom since October? I'd like to see the frequency counts and which communicative functions have been observed." Most teams respond well. A few won't have the data you hoped for, which is itself useful to know walking in.

If the school ran a formal AAC assessment, request a copy at least five business days before the meeting. IDEA gives parents the right to review all educational records ^[1]. The assessment should describe the child's current AAC system, how it fits their motor, cognitive, and language profile, and what the evaluator recommends next. If the school hasn't done a formal AAC evaluation and you think one is needed, request it in writing. The school must respond within a reasonable timeline (states vary, but 60 days is common) and cannot refuse without a prior written notice explaining why ^[5].

How do you present AAC progress data persuasively in the meeting?

Lead with the child, not the paperwork. Open with a moment: "Last month, she used the device to ask her brother to stop touching her toy. First time she'd ever used it with a sibling." Then bring the numbers.

Numbers land better when they're visual. A simple hand-drawn line graph of activations per week over three months beats a table of raw data. Print one graph showing an upward trend, or a flat trend where you expected growth, and it anchors the whole conversation. Tie every number back to the written goal: "The goal says 4 out of 5 opportunities. In January we were at 2 out of 5 across home observations. In March we're at 4 out of 5 at home but still 1 to 2 out of 5 in the classroom. So the question is what's different about the classroom." That framing keeps things solution-focused instead of adversarial. You're not accusing the team of failing the child, you're using data to point at where more support belongs.

If the data shows the goal isn't being met, arrive with a hypothesis. Maybe the device isn't within reach during key moments. Maybe partners haven't been trained. Research on AAC implementation keeps finding that partner training is one of the biggest variables in whether a child uses their device ^[3]. If that's your read, the IEP can add a goal or service to train classroom staff.

Children with autism who use AAC often show progress that looks uneven across settings. If that's your child's pattern, autism spectrum speech therapy is worth reading up on so you can explain the context to the team.

What are common AAC documentation mistakes to avoid?

The biggest one is only collecting data on good days. It's natural to reach for the notebook when things go well, but a data set that captures only peak performance isn't a baseline, it's an advertisement. Include hard days and low-output sessions; honest trend lines are more believable to the school team, not less.

Another is tracking vocabulary but not function. A child who activates 200 different words while using all of them to request snacks hasn't made the communicative progress the team thinks they have. Function is what communication is for.

Starting the week before the IEP is a third mistake. Four to six weeks is the minimum for a meaningful trend. Parents who do this well treat data collection as a background habit, not an event, and research on parent-implemented AAC support points the same way ^[6].

Leaning on device logs alone is another trap. App logs tell you what buttons were pressed, not whether the child was prompted, whether it was spontaneous, or whether the hit meant anything. A child who bumps "dog" reaching for another button gets logged the same as a child who activated "dog" to comment on seeing one. Pair logs with observation.

Last, don't skip dating your videos. Six months of clips with no dates can't show progress over time. Name files by date the moment you save them.

What does the research say about how quickly AAC users make progress?

Timelines vary a lot, and the research is honest about it. A 2019 review in the American Journal of Speech-Language Pathology found that most AAC intervention studies show measurable gains in communicative functions within three to six months of consistent implementation, but that implementation quality matters as much as the system itself ^[7]. A device in a backpack produces no data and no progress.

For children with autism, a 2014 meta-analysis in the Journal of Autism and Developmental Disorders found that AAC interventions (speech-generating devices and picture systems alike) increased communication without suppressing speech, contradicting an old and stubborn worry ^[8]. The stated conclusion was that AAC "did not impede speech production and in many cases appeared to facilitate it" ^[8]. Worth bringing up if anyone on your team hesitates about AAC.

Progress isn't linear. Children plateau, then jump. Goals set at 12-month intervals can make a child look like they're failing when they're really sitting in a plateau before a leap. Monthly data lets you see the pattern and explain it.

Nobody has good data on how many words or functions a child "should" add per month. The field lacks those benchmarks the way reading research has fluency norms. What we do have is individual trend data, which is why your own log, kept consistently, ends up being the most clinically meaningful evidence in the room. And on how early intervention shapes AAC outcomes, earlier access to a well-fitted system and trained partners consistently links to better results in the literature, though the size of that effect swings by study.

How do you track AAC progress if your child is a beginning communicator?

Beginning communicators are the hardest to document well because the progress is subtle. A child going from zero spontaneous initiations to one per day is enormous growth, but it won't look impressive on a raw frequency count unless you know where they started.

For beginning communicators, track whether any communication happened at all (yes or no per session), whether it was spontaneous or prompted and what level of prompt was needed, whether the child showed joint attention (looked toward you or a shared object) before or after the activation, and any pre-symbolic communication like reaching, eye gaze, or vocalizations near the device.

ASHA notes that communication acts can precede symbolic AAC use by months, and that documenting pre-symbolic behaviors sets a developmental trajectory the IEP team needs to see ^[2].

For a child with significant motor challenges, like those with childhood apraxia of speech, tracking the accuracy and consistency of motor acts on the device matters too. Are they hitting the right button more reliably over time, even when overall output stays low?

Be specific in your writing. "She looked at the device when she wanted more crackers" beats "she showed interest." "He independently activated the 'stop' button three times during a 10-minute play session without a verbal prompt" beats "he used the device well today."

How often should I collect data at home before a meeting?

Three observation periods a week for four to six weeks gets you a real trend. You don't need marathon sessions, 10 to 15 minutes during snack or play is enough, as long as you're watching closely. Short and consistent beats long and occasional every time.

Does parent-collected data actually count?

Yes, and the team is required under IDEA to consider it. You see communication at home that school staff never will, so bring it dated and organized. Advocates report that parent data often changes the direction of a meeting, especially when a child uses AAC more at home than in the classroom.

What if the school says my child has some words so doesn't need AAC?

Some spoken words don't rule AAC out. ASHA's position is that AAC should be on the table whenever a child's natural speech can't cover every communication need, in every setting, with every partner. Research also shows AAC doesn't hold speech back. If the school pushes back, ask for their written data and request a formal AAC evaluation in writing.

Log or data sheet, what's the difference?

A log is narrative, you write what happened in your own words. A data sheet tallies specific behaviors against set categories like function or prompt level. Numbers show the trend; the log fills in context the numbers can't capture. Bring both if you're able.

How can I tell if an AAC goal is actually measurable?

If a stranger could watch one session and tell you, yes or no, whether the child met the goal, it's written well enough. That means a specific behavior (activates device to request), a context (during a structured classroom activity), a criterion (4 out of 5 opportunities), a way it's measured (SLP data sheet), and a deadline (by the annual review). Missing any of those five, send it back before you sign.

What if the school SLP isn't tracking data between meetings?

Ask in writing what method and frequency they're using. No systematic data collection is a compliance problem under IDEA, which requires progress reports on goals as often as report cards go home. You can ask that the IEP spell out the method, frequency, and who's responsible. If nothing changes, your state's Parent Training and Information Center can help.

How do I track progress for a child who's just starting out?

For a beginning communicator, note any intentional communication beyond simple device taps, how much prompting was needed, and pre-symbolic behaviors like reaching, eye gaze toward the device, or vocalizing during an attempt. Record the date, setting, and partner every time. Even a flat zero, recorded accurately, is a useful baseline. At this stage progress often shows up as less prompting needed, not more output.

Do AAC apps log usable data?

Proloquo2Go, TouchChat, and similar apps track which buttons get pressed and when, and you can export that. Summarize it as average daily activations, most-used words, and change over time. App logs can't tell you if a tap was spontaneous, prompted, or accidental, so pair them with your own observations, and export monthly so you build a real record.

What's the clearest way to show progress at the meeting?

A simple line graph, weekly or monthly average activations or spontaneous initiations over the goal period, reads faster than any table of raw numbers. Graph paper and a pencil work fine. A second table with one row per month and one column per function also lands well. Visuals move the conversation faster than rows of numbers ever do.

How does this documentation affect placement decisions?

AAC progress data feeds straight into least restrictive environment decisions. Data showing effective communication with the right supports backs up a case for general education inclusion. Data showing breakdowns in specific settings tells the team exactly where more support is needed. Schools build PLAAFP statements, which include AAC progress, to justify placement, so your documentation gives you a real seat in that discussion.

Can I request an independent evaluation?

Yes. If you disagree with the school's AAC evaluation, or think none happened properly, you can request an Independent Educational Evaluation at public expense under IDEA. The school either funds it or files for a due process hearing to defend its own findings. An outside AAC specialist gives you an independent read on your child's needs, the right system, and appropriate goals. Put the request in writing and keep a copy.

What's the SLP's role in all this?

The school SLP usually collects session data on communication goals, contributes to the PLAAFP, and writes the AAC goals themselves, tracking functions, prompt levels, vocabulary, and progress against the stated criteria. If you also see a private SLP, ask for a short progress summary to bring along. Having more than one professional's view of the same child's communication is both useful and completely allowed at an IEP meeting.

What about low-tech systems like PECS or a communication board?

Same principles, different tool. Track independent initiations, which symbols get used, which functions show up, and how much prompting is needed. For PECS specifically, note which phase (I through VI) the child is working in, with dates tied to each step forward. A low-tech system deserves exactly the same level of documentation as a high-tech device.

Sources

1. U.S. Department of Education, IDEA 2004 (20 U.S.C. § 1414), Individuals with Disabilities Education Act statute: IEP must be based on current evaluation data and present levels of academic achievement and functional performance; parents have right to review educational records; progress reports required as often as report cards.
2. American Speech-Language-Hearing Association (ASHA), Augmentative and Alternative Communication practice portal: AAC assessment and progress monitoring must account for performance across environments, partners, and communicative functions; core vocabulary is central to functional AAC use; early AAC intervention should document pre-symbolic behaviors.
3. Augmentative and Alternative Communication journal, Taylor & Francis: AAC abandonment rates are high when implementation is inconsistent and progress is not tracked systematically; partner training is a major variable in whether a child uses their device.
4. AssistiveWare, Proloquo2Go data logging documentation: Proloquo2Go includes built-in data logging that records which buttons were pressed and when, exportable for progress review.
5. U.S. Department of Education, IDEA regulations, 34 CFR Part 300, evaluation and reevaluation requirements: Schools must respond to written evaluation requests within a reasonable timeline (commonly 60 days by state) and cannot refuse without providing prior written notice.
6. Snell, M. E. et al. (2010), review of communication interventions for children with severe disabilities, Journal of Positive Behavior Interventions: Research on parent-implemented AAC support shows that consistent background data collection, rather than event-based tracking, produces more reliable trend data.
7. American Journal of Speech-Language Pathology, ASHA flagship journal: A 2019 review found that most studies on AAC intervention show measurable gains in communicative functions within 3 to 6 months of consistent implementation, with implementation quality as a key variable.
8. Ganz, J. B. et al. (2014), meta-analysis, Journal of Autism and Developmental Disorders: Meta-analysis found AAC interventions resulted in communication increases without suppressing speech; stated conclusion: 'AAC did not impede speech production and in many cases appeared to facilitate it.'
9. ASHA, IEP development guidance for children who use AAC, Practice Portal: ASHA recommends AAC IEP goals address range of partners, range of settings, and variety of communicative functions, more than frequency of device use.
10. PACER Center, Minnesota Parent Training and Information Center: Parents can contact their state's Parent Training and Information Center for guidance if schools are not meeting IDEA data reporting obligations.