AAC Device Trial Log
Track AAC device trials, access methods, feature matching, and patient performance in one evaluation log. Use it to document what was tested, what worked, and what supports a device acquisition recommendation.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Healthcare · Education · Rehabilitation · Special Education
Overview
This AAC Device Trial Log template is for documenting an augmentative and alternative communication evaluation from the first trial through the final recommendation. It gives you a structured way to record the evaluation context, the patient’s communication profile, the devices and access methods tested, the feature match for each option, and the observed performance during tasks.
Use it when you need to compare multiple AAC devices or access methods and explain why one option is a better fit than another. The template is especially helpful when the evaluation must support a device acquisition request, because it keeps the evidence tied to specific observations rather than general impressions. It also helps teams capture motor, visual, and access barriers that may not be obvious in a narrative note.
Do not use this as a generic intake form or as a substitute for a full clinical assessment. If no device was trialed, or if you only need a brief progress note, a simpler documentation format may be a better fit. The form is also not meant to collect unnecessary personal data; keep the fields limited to what is needed for the evaluation and recommendation. When completed carefully, it creates a clear record of what was tested, what the patient could do with support, and what should happen next.
Standards & compliance context
- If the log includes patient-identifiable information, collect only the minimum necessary data and document consent for documentation in line with GDPR Article 5 principles.
- For public-facing or shared forms, use clear field labels, required-versus-optional markers, and accessible controls that support WCAG 2.1 AA expectations.
- When the form is used in an employment or accommodation context, include only the information needed to evaluate the communication access need and avoid collecting unrelated health details.
- If the template is used in a clinical setting, keep the documentation limited to minimum-necessary information and maintain an audit trail of who completed the evaluation.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Evaluation Context
This section matters because it anchors the trial in the right clinical setting, reason for referral, and documentation consent.
-
Evaluation date
Date the AAC trial or evaluation occurred.
- Evaluation setting
-
Primary reason for AAC evaluation
Briefly describe the communication need or referral reason. Avoid unnecessary PII.
-
Consent to document trial results and share with the care team
Confirm that appropriate consent or authorization has been obtained for documenting and sharing this information.
Communication Profile
This section matters because the patient’s communication mode and access needs determine which AAC options are worth trialing.
- Primary communication mode used today
- Observed access needs
-
Motor, visual, or cognitive considerations affecting access
Include only observations relevant to device selection and access method matching.
Devices and Access Methods Trialed
This section matters because it creates the comparison set and shows exactly which devices and access methods were tested.
- Devices trialed
Trial Details
This section matters because it captures the feature match and barriers for each trial so the recommendation is evidence-based.
-
Device / system name
Enter the specific AAC device, app, or communication system trialed.
- Access method used
-
Feature match rating
Rate how well the device features matched the user’s communication needs.
- Features that supported communication
-
Barriers or limitations observed
Document any usability, access, positioning, or feature limitations observed during the trial.
Patient Performance and Outcome
This section matters because it records what the patient could actually do during the trial, not just what the device can do in theory.
- Observed level of independence
- Communication success during trial
- Tasks completed successfully
-
Trial notes
Summarize observable performance, prompting needs, and any changes in accuracy, speed, or engagement.
Recommendation and Next Steps
This section matters because it turns the trial results into a clear device recommendation, access plan, and follow-up action.
-
Recommended device or system
Enter the device or system recommended for acquisition, if applicable.
- Recommended access method
-
Follow-up plan
Describe any additional trials, training, funding steps, or reassessment needed.
-
What happens after I submit
After submission, the trial log will be reviewed by the care team or assistive technology team and used to support the device acquisition recommendation and documentation trail.
How to use this template
- 1. Enter the evaluation date, setting, referral reason, and consent for documentation before recording any patient-specific details.
- 2. Document the patient’s primary communication mode, access needs, and any motor or visual considerations that affect AAC use.
- 3. Add each device trial in the trialed_devices section and record the device name, access method, feature match rating, supported features, and barriers observed.
- 4. Capture what the patient actually did during the trial by noting independence level, communication success, observed tasks, and brief trial notes.
- 5. Record the recommended device, recommended access method, follow-up plan, and submission note so the log ends with a clear next step.
Best practices
- Record the access method separately from the device name so it is clear whether success came from the hardware, the interface, or the input method.
- Use observable language for feature match and performance, such as what the patient could select, activate, or communicate during the trial.
- Keep the trial list focused on the devices that were actually tested, and avoid adding speculative options that were never observed.
- Note motor and visual considerations early, because they often explain why a device performed well or failed under real conditions.
- Describe barriers in concrete terms, such as fatigue, positioning, calibration issues, or symbol density, rather than using vague labels.
- Document what happened after each trial while it is still fresh so the comparison between devices stays accurate.
- Make the recommendation match the evidence in the log, and explain any need for follow-up trials if the best option is still uncertain.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this AAC Device Trial Log used for?
This template documents an AAC evaluation by capturing the communication profile, devices trialed, access methods, feature match, observed performance, and the final recommendation. It helps clinicians and teams compare options in a consistent way instead of relying on memory or scattered notes. The log is especially useful when a device acquisition decision needs clear support.
Who should complete the trial log?
It is typically completed by the speech-language pathologist or other clinician leading the AAC evaluation, with input from caregivers, educators, or support staff when appropriate. The person documenting should be the one observing the trial and recording the results in real time or immediately after. If multiple people contribute, the log should still identify who observed each trial.
When should an AAC device trial be logged?
Use it during the evaluation process whenever a device, access method, or feature set is being tested. It works well for single-session trials, multi-session comparisons, and follow-up trials after changes in positioning, access, or vocabulary layout. If no device was actually trialed, this template is not the right fit.
How does this template support a device acquisition recommendation?
The template ties the recommendation to specific evidence: what was trialed, how the patient accessed it, what features were supported, and what barriers were observed. That makes the recommendation easier to justify to internal reviewers, funding sources, or care teams. It also shows whether the recommended device and access method match the patient’s demonstrated performance.
What should be included in feature matching?
Feature matching should reflect the communication needs and access needs observed during the evaluation, such as symbol support, text entry, voice output, switch access, eye gaze, or keyguard compatibility. The goal is to document the features that actually affected success, not every possible product feature. Keep it specific to the trialed device and the patient’s profile.
What are common mistakes when using an AAC trial log?
Common mistakes include listing devices without noting the access method, using vague ratings without explaining what they mean, and failing to record barriers that affected performance. Another frequent issue is skipping the consent-for-documentation field when the log includes patient information. The strongest logs are specific, observable, and tied to the actual trial conditions.
Can this template be customized for pediatric, adult, or school-based evaluations?
Yes. You can tailor the referral reason, observed tasks, and follow-up plan to pediatric, adult rehabilitation, school-based, or outpatient settings. You can also adjust the device list and feature fields to match the tools your team trials most often. The structure stays the same even when the clinical context changes.
How does this compare with ad hoc notes or a narrative report?
Ad hoc notes often miss the comparison structure needed to evaluate multiple devices fairly. This template keeps the same fields for each trial so it is easier to compare access methods, feature match, and outcomes side by side. It also creates a cleaner audit trail for later review, handoff, or funding documentation.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
See how MangoApps employee dashboards unify communications, tasks, and company updates in one personalized workspace — no developer required.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Generative AI boosts workplace productivity, upskilling, and knowledge sharing—helping enterprises work smarter and unlock measurable gains.
-
Discover how a mobile-first employee app transforms retail staff training—streamlining onboarding, standardizing SOPs, and reaching every frontline worker.
Ready to use this template?
Get started with MangoApps and use AAC Device Trial Log with your team — pricing built for small business.
