To build an ABA personal technology and digital communication support playbook, separate Samir's chosen uses and observable digital skills from device, account, identity, content, and money ownership; legal or service authority; accessibility; authentication; cybersecurity; platform rules; privacy; emergency response; and safeguarding. Give each action a current source, qualified owner, protected practice method, accessible message, release gate, stop rule, recovery path, and return-of-control condition. Start with usable access and real authority.

Define Samir's page-specific decision

To build an ABA personal technology and digital communication support playbook, define the person, purpose, device, account, content, audience, authority, access, authentication, privacy, security, supporter, release condition, stop rule, recovery route, and control-return condition. Map the complete digital action: purpose, person, device, account, content, audience, authority, authentication, data, payment, accessibility, communication, risk, recovery, and control return.

Protect Samir's communication, secrets, and ownership

Samir's support plan keeps AAC, device access, emergency help, private content, credentials, recovery secrets, identity data, and funds protected under the authorized arrangement. Samir's personal-technology clinical playbook cannot create account ownership, identity, platform permission, financial authority, cybersecurity, legal consent, or permission to inspect private content.

Build Samir's personal-technology clinical playbook

Create one versioned record for the home, clinic, work, and community settings. Include Samir's purposes, emergencies, devices, accounts, content, audiences, ownership, authentication, access, communication, privacy, payments, supporters, restrictions, incidents, recovery, outcomes, missingness, and reassessment evidence. Use separate tabs for person choice, emergencies, devices, accounts, identity, authentication, access, communication, privacy, payments, supporters, restrictions, incidents, recovery, outcomes, and review.

Validate Samir's counts and evidence

Reproduce 28 units, six held, 22 released, 13 messages, 11 timely responses, one late response, and one missed response.

Connect Samir's evidence to a bounded action

The team repairs six system gaps and two response gaps before adding instruction. Person, platform, account, security, financial, clinical, emergency, and supporter decisions keep separate owners.

Work through Samir's example

Samir's team predeclares 28 digital-support units. Six stay held for unclear account ownership, missing accessibility, an untested recovery route, exposed credential risk, absent AAC backup, or unresolved payment authority. Across 22 released units, Samir sends 13 share, private, suspicious, help, recover, or stop messages. Partners respond within the agreed window to 11; one is late and one is missed. Preserve every planned and eligible unit, device and account version, authority, access, authentication, content and audience, communication, person choice, response, restriction, incident, recovery, repair, and endpoint. This fictional example supplies no account ownership, platform decision, identity determination, security assurance, treatment effect, compliance result, or promised outcome.

Address Samir's main interpretation risk

Eleven of 13 measures partner response after a message. It cannot establish account ownership, authorization, cybersecurity, identity, consent, independent use, fraud prevention, or treatment effect. Six held units remain visible. Review immediate danger, account and platform rules, ownership, authentication, accessibility, privacy, security, financial boundaries, communication, supporter response, instruction, restrictions, person priorities, incidents, burden, missingness, and design strength separately.

Set Samir's ABA scope and ethics boundaries

Samir's personal-technology clinical playbook uses the CASP public summary only for high-level ABA behavioral-health-treatment scope for autistic people. The current BACB Ethics Code addresses competence, collaboration, consent and assent when applicable, confidentiality, assessment, risk, documentation, and evaluation for covered people. Device, account, platform, identity, cybersecurity, financial, emergency, safeguarding, employment, and legal authority remain with qualified owners.

Use CISA's four practices within Samir's real accounts

CISA Secure Our World emphasizes recognizing and reporting phishing, strong passwords and password managers, multifactor authentication, and prompt software updates. These are general security practices, not permission to access Samir's account, hold credentials, choose an authenticator, or override accessibility. The personal-technology clinical playbook records which current service supports each control and who owns it.

Route suspicious messages through verified channels for Samir

The FTC phishing guide explains that deceptive emails and texts may seek passwords, account numbers, or other information. It advises contacting the company through a number or site already known to be real instead of using the message link. Samir's team may teach that bounded check with synthetic messages while leaving incident response, account action, and money decisions to authorized roles.

Use IdentityTheft.gov only after the right classification for Samir

IdentityTheft.gov recovery steps provide an FTC reporting and recovery route for U.S. identity theft, including contact with affected companies and credential changes. That route does not classify every suspicious message or authorize clinical staff to freeze accounts, access credit reports, file as Samir, or control funds. Preserve the person's authority and the qualified recovery owner.

Apply NIST digital-identity terms cautiously for Samir

Final NIST SP 800-63 Revision 4, released in July 2025, covers digital identity proofing, authentication, and federation for government information systems. It is a technical reference, not a universal consumer-account rule or clinical protocol. Samir's actual platform determines supported authenticators and recovery methods; account ownership, accessibility, risk, and delegated help remain separate decisions.

Treat cognitive accessibility as design evidence for Samir

The W3C cognitive-accessibility page distinguishes WCAG standards from supplemental informative guidance and describes needs involving perception, memory, language, attention, comprehension, and error correction. It cannot diagnose Samir, authorize account access, or guarantee usability. Testing for Samir uses the real interface, assistive technology, authentication, timing, and recovery path with the person.

Keep emergency action ahead of digital data for Samir

The National 911 Program says an emergency requiring immediate police, fire, or ambulance assistance belongs with 911 and that call-takers may provide instructions. Local systems differ, and the guidance is U.S.-specific. Samir's team follows qualified responders rather than completing a teaching trial, screenshot, percentage, or routine approval first.

Make digital communication accessible for Samir

The DOJ effective-communication guidance explains that covered entities consider the nature, length, complexity, context, and person's usual communication method. Platforms and account owners can have separate duties. Communication checks in Samir's personal-technology clinical playbook cover instructions, authentication, messages, warnings, reports, and recovery explanations while sending provider-access decisions to the responsible entity.

Preserve Samir's AAC and authorship

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Samir's primary and tested backup communication remain available during login, messaging, support, recovery, compromise, and emergencies. A supporter may facilitate access without supplying Samir's message, consent, audience, account answer, payment choice, or incident report.

Use technology evidence cautiously for Samir

A systematic review of assistive technology for practical skills included 18 studies involving autistic people or people with intellectual disabilities across varied targets and tools. It cannot establish that an app, reminder, password manager, passkey, filter, tracker, communication device, or recovery aid will teach Samir's skill, prevent compromise, generalize, or improve wellbeing.

Choose Samir's next review trigger

Reopen after a device, account, platform, credential, recovery method, update, accessibility need, supporter, incident, restriction, or Samir request changes. Record the qualified owner, current source, effective date, device and account version, ownership and access state, authentication and recovery arrangement, communication, intervention and restriction authority, implementation check, accessible explanation, complaint route, and reassessment date.

Close Samir's personal-technology plan

Review the personal-technology clinical playbook with Samir, the qualified behavior analyst, authorized supporter when applicable, direct team, and specialists named in the manifest. Confirm that emergencies, account and platform decisions, identity, authentication, accessibility, privacy, cybersecurity, communication, assessment, teaching, restrictions, incidents, recovery, and outcomes remain separate; every denominator is reproducible; AAC, authorship, refusal, withdrawal, private content, secrets, funds, and emergency help remain protected; and conclusions stay bounded to sampled conditions. Keep this page draft and noindex until every required review is complete.

Related resources

Sources