You just ran a great session. Your client requested a snack with core words, took a turn in a game, and even fixed a breakdown when their partner misunderstood. Then you sit down to write it up, and the real work begins. Getting AAC documentation and goals right is its own skill, and it's the part of the job that rarely gets taught well.
Here's the tricky thing about AAC documentation and goals: they have to do two jobs at once. They guide your therapy, and they justify it. A good goal tells you (and the next clinician, and the supervisor, and the payer) exactly what you're working toward and how you'll know when you get there. Good notes prove the progress happened.
So let's walk through it. How to write AAC goals that anyone could measure, how to document sessions and device trials so the record holds up, and how to keep all of it connected instead of scattered across five different places.
Start with the principle that fixes most weak AAC goals: AAC therapy is language therapy with a different output. The synthesized voice, the symbols, the device, those are the medium. The language is still the target.1
That means "the student will use the iPad" is not a language goal. It's a goal about a tool. What are they saying with it? Requesting, commenting, asking questions, protesting, repairing a misunderstanding? That's the part you write down. When you're writing AAC goals, name the communicative behavior, not the equipment.
It also helps to remember that good AAC goals span more than one kind of skill. Janice Light's framework, still the field standard, describes four areas of communicative competence: linguistic, operational, social, and strategic.5 Operational competence (finding the word, navigating the pages) matters, but a goal set that's all navigation misses the point. You want goals that build real linguistic and social communication too.
One more anchor: core vocabulary. A small set of high-frequency words (want, more, go, stop, that, help, and so on) makes up roughly three-quarters of what any of us say all day.4 Goals that build flexible core-word use give your client far more communicative reach than goals built on memorized phrases for one situation.
Once you're targeting communication, the structure is the same one you already use for other language goals: a DO statement, a CONDITION, and a CRITERION, plus a time frame.3 The DO is the observable behavior. The CONDITION is the support and context. The CRITERION is how you'll measure it.
There's a simple test for whether a goal is actually measurable. Could another SLP pick it up cold, run a session, collect clean data, and tell you whether your client is making progress?2 If the goal is vague, the answer is no, and you've got a problem at the next progress review.
The CONDITION is where AAC goals tend to go fuzzy, so be specific about aided language input and your prompting hierarchy. Independent or prompted? What level of cue? Naming that up front keeps your data honest.
Here are three examples, broken into their parts.
Requesting with core words. Given access to their speech-generating device and aided language input during a play activity, [client] will request a preferred item using a one-word core request (want, more, go) in response to an indirect cue, in 4 of 5 opportunities across three consecutive sessions.
Initiating with a peer. During a classroom routine, [client] will independently initiate a comment or question to a peer using their device, in 3 of 5 opportunities across three sessions.
Repairing a breakdown. When a communication partner signals they didn't understand, [client] will repair the message (repeat, add a word, or add a symbol) using their device, in 3 of 4 opportunities across three sessions.
Notice what each one avoids. There's no "will improve communication" and no "will use the device appropriately." Those aren't measurable, and they aren't really goals. For AAC goals SLP teams can actually track, every one names the behavior, the support, and the number.
Goals tell you where you're going. Your session notes prove you got there, and that's where solid AAC documentation earns its keep. Most SLPs already live in the SOAP format, and it maps cleanly onto an AAC session.2
In the Subjective, capture what the client or caregiver reported: a new word the family saw at home, frustration with a page that's hard to reach, a win worth noting. In the Objective, record the data you collected against each goal. The Assessment is your clinical read of what that data means. The Plan is what you'll do next session and what you'd adjust.
The part worth slowing down on is the data itself. It's tempting to log button presses, because they're easy to count. But raw presses don't tell you much about communication. The data that matters captures real growth: independent initiations versus prompted ones, the range of communicative functions your client is using, and whether the skill shows up across different partners and settings.6
For a busy session, especially a group, short interval sampling works well. Divide the activity into one or two minute chunks and note whether the target behavior happened.6 You end up with usable frequency data without trying to chart every moment in real time.
Two habits make a big difference here. Keep your data consistent from session to session, so progress is visible instead of buried in free text. And make sure each note maps back to a specific goal. When it's time for a progress report, the story should already be sitting in the record.
If your client needs a dedicated device, your documentation has another audience: the payer. And funding requests live or die on medical necessity. You'll need a clear picture of the client's medical history and a narrative that explains why this device is necessary for them to communicate.5
This is where a lot of requests get denied, so it's worth knowing the common gaps. Reviewers want to see that a real range of systems was trialed, with comparison data showing why the recommended device performed best.5 A request that names one device and skips the trial evidence gives the reviewer no way to follow your clinical reasoning, and vague documentation is a leading reason claims come back denied.2
A few specifics save real headaches. Ask for a "dedicated communication device," not an "iPad." The everyday term can get a report rejected outright.5 And proofread for copy-paste errors. A wrong client name or a stray pronoun signals that the report was recycled from another case, and reviewers notice.5
If a request does come back denied, don't read it as the end. Persistence is the single biggest predictor of approval: the large majority of appeals supported by new documentation eventually go through, though it can take anywhere from one to six months.5 Getting the documentation right the first time is how you avoid losing those months.
Here's the problem that quietly makes all of this harder. The goals live in one document. The session notes live somewhere else. The device-trial evidence is in a third place, maybe a folder, maybe an email thread. So you re-key the same information over and over, and inconsistencies creep in.
University clinics feel this most. Students draft the documentation, supervisors have to review and co-sign it, and everyone needs to follow one repeatable method so the records stay consistent across a whole cohort. When the goal, the note, and the data don't talk to each other, oversight turns into detective work.
This is the one spot where the right software genuinely helps. When goals, SOAP notes, and trial evidence live in a single record, you stop duplicating entry, progress is easy to see, and you can catch a documentation gap before a payer does. ClinicNote supports AAC as one of its disciplines, with customizable templates so a clinic can standardize its goal structure once and reuse it, and real-time supervisor review built for the way university clinics actually work.
The point isn't the tool, though. It's the principle: AAC documentation and goals work best when they're one connected story, not four disconnected ones.
Looking for an EMR that keeps AAC goals and documentation in one place? ClinicNote is a full-suite EMR built for speech clinics and university training programs, with customizable templates, connected SOAP notes, and real-time supervisor review. Get a demo and see how it fits your clinic.