An ABA plan quick reference for implementers is a role-specific job aid for locating and carrying out the critical actions of the controlling plan. Identify the exact version, scope, valid opportunities, required supports, steps, timing, client communication, stop conditions, prohibited actions, data events, and escalation route. Link to the complete plan and require training and demonstrated readiness separately. A quick reference cannot expand scope or replace qualified supervision.

Define the user's role

List only the decisions and actions assigned to that role, required supervision, permitted supports, unavailable authority, setting, service, and escalation contacts.

Create different references when roles genuinely have different actions or decision rights. A technician aid should not invite an independent clinical change, while a supervisor version may include coaching and escalation responsibilities. State what the user must do when information is missing or conditions fall outside scope. This reduces clutter and makes unauthorized improvisation less likely without hiding necessary safety or access information.

Identify the controlling content

Show client, plan and component version, fingerprint or stable link, effective scope, generated time, online or offline state, and conflict instructions.

Place the identifier on every page or screen that can be separated from the full aid. Tell the implementer how to compare the reference with the source plan and what to do if versions differ. A generated timestamp alone is insufficient when an old file can be downloaded later. Preserve historical references for audit while removing them from active use and preventing cached or printed copies from appearing current.

Show the critical sequence

Define start condition, valid opportunity, observable steps, timing, choices, accepted response forms, partner response, data event, completion, and branches.

Write the sequence at the point-of-care level, including what happens after a different response, no opportunity, a request to stop, or a system failure. Preserve Lina's AAC and other valid response forms rather than compressing them into one convenient modality. Use visual organization only when the reading order and meaning remain clear in accessible formats. Link complex rationale to the full plan instead of omitting it entirely.

Protect access and safety

Keep AAC, movement, health supports, breaks, exits, prescribed care, stop criteria, emergency routes, and prohibited practices immediately visible.

Separate ordinary needs from performance contingencies and place urgent instructions before troubleshooting or data entry. The aid should name who can pause, which route applies to medical or safety concerns, and how Lina requests help or correction. If an access or health condition is missing, hold the affected procedure under the applicable plan rather than continuing because the quick reference appears otherwise complete.

Test the aid with users

Use representative scenarios, allowed materials, client communication, environmental failures, and role-specific decisions. Record misunderstandings and redesign the aid where they cluster.

Ask users to locate and carry out key tasks without coaching, then test edge cases such as a stale version, failed device, ambiguous response, or absent supervisor. Training success and aid usability are separate measures. If several competent users misread the same branch, revise the artifact or source language. Retest with the actual mobile, print, portal, and offline formats used across settings.

Control every copy

Synchronize mobile, print, portal, and offline forms; remove stale versions; log distribution and questions; and connect acknowledgment, training, readiness, and natural observation separately.

Assign a copy owner and require evidence for withdrawal, not just publication of the new file. Confirm each setting receives the correct role-specific version and that offline packets have a refresh rule. Acknowledgment does not prove understanding or competence, so observe first use and record deviations separately. Escalate recurring questions to clinical review when they reveal plan ambiguity rather than repeatedly answering them through informal messages.

Build Lina's implementer quick reference

Lina's role-specific quick reference maps each critical action to the exact approved plan component and assigned role. It states the valid opportunity, what to do, allowed supports, AAC access, wait rule, stop condition, escalation, version, effective scope, and where to find the full plan. The control record also keeps distribution, online and offline copies, implementer testing, questions, defects, corrections, readiness decisions, review dates, and owners so a reviewer can reproduce the check and locate stale cards.

Work through Lina's example

Lina's reference covers a four-step community request routine. It names the opportunity, AAC access, a ten-second partner wait, the response to a recognizable message, and when to stop. Five of six implementers perform all four critical actions; one misses the wait rule. Readiness is therefore five of the six assigned implementers, while the sixth remains visible for redesign and retest. The card is revised before reassessment. This fictional center team example sets no universal format, clinical recommendation, legal conclusion, pass threshold, or outcome guarantee.

Address Lina's main access risk

A compact card may strip away context or turn optional supports into rigid commands. Lina's version marks critical, conditional, and informational content visibly. Test whether communication works in both directions and whether the complete clinical meaning survives the format. Technical availability, readability, understanding, agreement, training, competence, and correct implementation remain separate outcomes.

Choose Lina's next action

The supervisor repairs the wait-time display, reassesses the affected action, and samples early natural implementation rather than treating job-aid use as proof of integrity. Record the responsible role, authority, affected users and scope, interim accessible option, due date, correction evidence, communication, retest, version effect, and next review. Software may render and distribute content. Qualified clinicians retain responsibility for clinical meaning within scope.

Protect Lina's communication and privacy

Keep Lina's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, pain communication, health support, movement, rest, relationships, and emergency help available. Use approved systems and purpose-needed access. Offer a private way to ask, decline, pause, withdraw when applicable, report discomfort, and correct the record without making one response form the price of participation.

Apply current sources to Lina's access review

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, documentation, evaluation, and training context.

An evidence-based ABA framework and treatment-integrity practitioner guide, Essig review, impact study, and reporting review support contextual decisions, explicit procedures, implementation evidence, and bounded conclusions.

ASHA supports continuous AAC access. DOJ effective-communication guidance addresses covered Title II and Title III entities, while HHS language-access guidance addresses applicable HHS-funded programs and OCR authorities. Verify entity and rule scope.

Rehearse Lina's usability workflow

Test the implementer quick reference with a client request, visual impairment, hearing or speech disability, AAC outage, preferred language, low literacy, interpreter need, screen reader, magnification, phone, print, weak connection, EHR outage, stale cache, inaccessible table, missing stop rule, privacy limit, plan correction, and emergency. Confirm that effective communication, clinical meaning, safe action, version control, and follow-up remain intact.

Close Lina's access review

Review the implementer quick reference with Lina, the responsible clinician, representative users, and the specialists named by the manifest. Preserve source content, language and format choices, direct client input, tests, defects, corrections, limits, and open findings. Keep the page draft and noindex until required clinical, client or family, AAC, disability-access, language-access, interpreter, privacy, security, software, payer, and legal reviews are complete.

Related resources

Sources