Prepare for the RESNA ATP by studying the six knowledge areas as one connected service-delivery process: understand function and activity needs, assess in context, match features to activities, document for funding, implement and train, then follow up. Practice writing functional justifications and tracing complete cases rather than memorizing product lists.
ATP vs. SMS vs. RET: Which Credential Does Each Scenario Describe?
The ATP is RESNA's broad-based credential covering all major areas of assistive technology practice. The SMS is a specialty credential for seating, positioning, and mobility; the RET addresses rehabilitation engineering depth. Knowing the boundaries keeps your study scope honest.
RESNA describes the ATP as recognizing demonstrated competence in analyzing consumers' needs, assisting in selecting appropriate assistive technology, and providing training in the use of the selected devices. That three-part description — analyze, select, train — is a useful skeleton for your entire study plan, because every topic you encounter should connect to at least one of those service activities.
Use the credential boundaries to police your depth. When you find yourself spending days on wheelchair seating measurement techniques or engineering design calculations, you are drifting toward SMS or RET territory. For ATP purposes, keep a working knowledge of seating and engineering concepts, but reserve your deepest effort for the generalist decisions that span every device category: assessment reasoning, justification, training, and ethics.
| Credential | Primary scope | Example decision it centers on |
|---|---|---|
| ATP | Broad AT practice: needs analysis, device selection, training | Choosing and justifying an access method for a communication device |
| SMS | Seating, positioning, and mobility specialty | Selecting a seat cushion and frame configuration for a complex posture |
| RET | Rehabilitation engineering | Designing or modifying a custom work-site adaptation |
Connecting the Six Knowledge Areas into One Service-Delivery Process
Instead of six silos, study the ATP topics as a cycle: understand human function and activity demands, assess in context, select and justify features, secure funding, implement and train, then follow up — with professional ethics applying at every step.
Trace the loop explicitly. Human-function knowledge tells you what to observe during assessment; assessment findings supply the evidence a funding report needs; funding approval makes implementation possible; training quality determines whether the device is actually used; follow-up results feed back into reassessment. When you study a fact, place it at a specific point in this loop. A pressure-injury risk factor belongs in assessment; a payer's documentation requirement belongs in funding; a caregiver instruction belongs in training.
A practical filter: for every device, model, framework, or term you review, name which of the six areas it serves and where it sits in the cycle. If you cannot place it, either you have not understood it yet or it is peripheral detail you can deprioritize. This turns a sprawling body of AT knowledge into a structure you can rehearse and recall under exam conditions.
Assessment: Recording Function Before Naming a Device (Cushion Scenario)
Strong assessment practice documents observable function — skin status, posture, mobility, environment, routines — before matching features. The classic mistake is letting a diagnosis trigger a product name. Work through the scenario below to feel the difference.
Scenario: an adult with a spinal cord injury propels a manual wheelchair, works at a desk full time, and has a healed history of pressure injury. The reflexive move is to recommend a well-known air cushion because 'air is best for pressure.' The better decision is to assess first: sitting tolerance and skin status, ability to perform pressure reliefs independently, posture and pelvic position, transfer method, transport setup, home and work surfaces, and willingness to maintain equipment. Only then do you match features — immersion versus envelopment characteristics, stability needs, maintenance demands — to what the assessment actually showed.
Why it matters: the cushion choice genuinely depends on those variables. Someone who cannot perform pressure reliefs, or whose chair is frequently lifted into a car, faces trade-offs that diagnosis alone never reveals. Commonly used frameworks in AT practice, such as the Human Activity Assistive Technology (HAAT) model, organize this thinking by placing the human, the activity, the technology, and the context together — a useful lens for rehearsing assessment questions. For your own study, practice writing an assessment summary in which the word 'because' always connects an observation to a functional consequence.
Matching Features to Activities Instead of Memorizing Device Categories
Learn each major device category — AAC, computer access, EADLs, mobility, seating, daily living aids — by the functional problem it solves and the trade-offs among its features, so you can reason about products you have never seen.
Take computer access as an example. The underlying question is how a person with a given movement pattern, fatigue level, and cognitive profile can control a computer. Options form a rough hierarchy of increasing specialization: standard keyboard with adaptations, alternative keyboards, on-screen keyboards with pointing devices or head tracking, voice input, and switch access with scanning. Each step trades speed for reduced motor demands, and the right answer depends on assessed endurance, accuracy, and the communication or work task — not on which option is newest.
Build a trade-off grid for the major categories as a study artifact: for each category, list the key feature decisions (direct selection versus scanning in AAC; immersion versus postural stability in cushions; standalone versus integrated controls in EADLs) and the client variables that tip each decision. Alongside the grid, learn the shared vocabulary of the field — direct selection, scanning, encoding, interfacing, mounting, positioning — because these named concepts let you describe and compare any device, which is exactly what a broad generalist exam rewards.
Funding Justification: Linking Limitation, Feature, and Activity (AAC Report Scenario)
Funding decisions turn on whether documentation ties a measured functional limitation to a specific device feature and a specific daily activity. The AAC scenario below shows what a feature-only report fails to establish.
Scenario: an adult with aphasia after a stroke is being evaluated for a speech-generating device. The weak report lists the device's vocabulary size, screen specifications, and durability — and stops there. The stronger report first documents the baseline: how the person currently communicates, with whom, and where communication breaks down (medical appointments, phone calls, workplace exchanges), then explains how named features — for example, pre-programmed phrases for frequent requests — address those specific breakdowns, and closes with a training and follow-up plan.
Why it matters: a funding reviewer is asking 'why this solution for this person,' and features alone cannot answer that question. Study funding and policy at the level of reasoning and structure: understand what service-delivery documentation generally must demonstrate, and treat specific program rules as things to verify through current official sources rather than memorize, because program details change. The portable skill is the limitation–feature–activity chain; rehearse it until it is automatic.
Implementation and Training: Decisions After the Recommendation
Implementation covers delivery, setup, customization, training the user and the people around them, and structured follow-up. Study the handoff and follow-up decisions, not just the assembly steps.
Training decisions have a scope beyond the user: family members, caregivers, school or workplace staff who support daily use. Assistive technology abandonment — a documented phenomenon in the AT research literature — is the outcome this domain exists to prevent, and its usual logic is a mismatch between the device, the user, or the environment. In your notes, attach every training topic to a likely consequence: a caregiver who cannot charge or adjust equipment can silently undo a working setup.
Consider a short scenario: a device works perfectly at delivery but is abandoned in the classroom within weeks. The disciplined reading is that this is an assessment or follow-up gap — the environment, partner expectations, or integration into routines was never evaluated — not a user failure. The better decision is a follow-up visit that reassesses context and adjusts the solution. Practice narrating these decision points: what to check, whom to re-interview, what to document, and when a recommendation should be reopened.
Study Sequence, Justification Drill, and Readiness Checks
Rotate through the six domains in cycle order, finish with mixed review, and use the justification-writing drill below as your core skill exercise. Track readiness through observable outputs — written rationales and completed case traces — not question counts.
A realistic adaptable sequence: weeks one and two, human function plus the major device categories and their feature trade-offs; week three, the assessment process and documentation of function; week four, funding reasoning and justification writing; week five, implementation, training, and professional ethics; the remaining time, mixed review using full case traces. Compress or stretch the weeks to fit your schedule — the order matters more than the calendar. Free practice questions and the site's broader study guide collection work best at the mixed-review stage, when you can check whether your reasoning survives unfamiliar wording.
- Exercise: take three device recommendations from your notes — one mobility, one communication, one daily-living aid — and rewrite each as a functional justification.
- Rubric, item 1: a specific daily activity is named first, before any product or feature appears.
- Rubric, item 2: a measurable limitation is stated and linked with 'because' to a device feature.
- Rubric, item 3: at least one alternative option is acknowledged with a reason it was not selected.
- Rubric, item 4: a training and follow-up step is included.
- Expected observation: first drafts almost always name features before activities; after two or three revision rounds, the activity-first order should become your default.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.
