How to Plan a Digital Communication Goal in ABA

To plan a digital communication goal in ABA, start with a digital interaction the person chooses and preserve their authentic writing, AAC, emoji, image, voice, or video style. Define the platform, privacy, timing, access, blocking and reporting tools, partner expectations, and help route. Use real opportunities with permission, protect account security, and measure useful communication and experience without requiring rapid replies or conventional social style.

Choose the digital outcome

Ask whether Kira wants to start, answer, clarify, set a boundary, coordinate, share, correct, block, report, or leave an interaction and why it matters.

Begin with one real communication setting Kira chooses, such as a family group chat or messages used to coordinate a club. Ask what currently works, what feels burdensome, and what outcome would make the interaction more useful. She may want a reliable way to say she will answer later, correct a misunderstanding, or leave a thread without repeated follow-up.

Define a decision or message rather than a social-normality target. Fast replies, long messages, reciprocal questions, and constant availability are not inherently better. Kira can retain templates, support people, AAC, reminders, or delayed response and can decide that no message is needed in an eligible thread.

Preserve authentic style

Accept text, AAC, emoji, image, reaction, audio, video, template, silence, or delayed response as appropriate. Avoid tone policing and forced disclosure.

Ask Kira what each form means in the selected context and how partners should clarify uncertainty. A reaction may fully acknowledge a plan, while silence may mean she has not seen the message or does not want to engage. Partners should avoid assigning motive from punctuation, capitalization, eye contact on video, or response speed.

Build the aid around her style instead of replacing it. Optional templates can support scheduling, boundary setting, or clarification, but spontaneous language remains valid. Record which support Kira wants for composing, reviewing the audience, or checking private information before sending.

Define the platform context

Record account, participants, audience, privacy setting, device and connectivity, message window, notification state, permanence, moderation, and partner expectations.

Take a current snapshot because platform settings and group membership change. Verify whether a post is private, group-limited, public, temporary, searchable, or downloadable, and who can add participants. Explain that screenshots or forwarding may extend the audience even when a platform label suggests limited visibility.

Define when a thread counts as available. The device, account, access method, connection, and message must be usable, and Kira needs a reasonable window to respond. Muted notifications, an expired invitation, a removed account, or a message outside the agreed period stays in platform-readiness data rather than becoming a missed client response.

Protect privacy and security

Keep passwords, authentication codes, private images, location and sensitive conversations out of teaching records. Use approved synthetic practice when real data are unnecessary.

Use invented contacts, fictional content, and test accounts when possible. If Kira chooses to review a real message, show only the minimum content needed and follow the approved privacy route. Do not copy a live conversation, access token, recovery code, address, health detail, or image into a clinical worksheet.

Clarify who may help with the device or account and what they are permitted to see. Kira should have an accessible way to end screen sharing, decline help, log out of a shared device, and report unexpected access. A security or privacy incident goes to the responsible platform, organizational, or legal route.

Plan boundaries and help

Include mute, block, report, screenshot rules, scam or harassment route, trusted support, urgent safety response, declined contact, and platform failure.

Let Kira choose which boundaries fit each relationship. Define the immediate partner response to “stop,” “later,” or a request for help, and explain what mute, block, or report can and cannot do on the current platform. Keep urgent threats, exploitation, self-harm content, account compromise, and other safety concerns on distinct qualified response routes.

Practice boundaries with fictional messages rather than arranging unwanted contact. Include a fallback when the tool is inaccessible or the report receives no answer. The goal is a usable range of choices, not requiring Kira to manage platform moderation or prove that a concerning message violates a rule.

Measure useful communication

Report eligible threads, chosen messages, partner responses, help use, access failures, unwanted contact, Kira's comfort, burden, and desired change.

Use platform readiness as one denominator and Kira's chosen communication opportunities as another. Partner response begins when an agreed message calls for action, such as honoring “later” or correcting group membership. Track delivery failures, deleted messages, unwanted recontact, and moderation delays separately.

Review samples with Kira rather than relying on message counts. Ask whether communication achieved the purpose, whether privacy felt acceptable, and whether notifications or support added burden. A lower response rate may reflect a healthy boundary, while frequent messages can still represent poor access or pressure.

Build Kira's digital communication goal plan

Define which group threads Kira wants included, when a thread becomes available, and when it expires. Record participants, audience and privacy setting, device and connectivity, notification state, Kira's accepted message forms, help route, boundaries, and options to delay, mute, block, report, or leave. Keep platform and partner duties separate from Kira's actions. Measure thread availability, Kira's chosen response, partner follow-through, privacy cost, and burden in different fields, with response speed included only if Kira finds it meaningful.

Work through Kira's example

Kira chooses to confirm plans in a group message. Across eight identified threads, she sends six confirmations, asks for clarification once, and has one thread expire before she views it. The accounting reconciles as 6 + 1 + 1 = 8. The expired thread retains a system-state label, while the seven viewable threads preserve Kira's six confirmations and one help request. Response speed stays outside the goal, and these counts do not establish a universal participation or availability standard.

Address Kira's main fit risk

A reply-rate goal can reward constant availability. Kira defines eligible windows and keeps silence, delay, muting, blocking, and leaving available. A client measure can improve while privacy, access, partner behavior, burden, safety or lived experience worsens. Review those dimensions separately and retain useful supports.

Choose Kira's next planning action

The team clarifies the expired-thread rule, checks whether notifications are burdensome, and asks Kira which support should remain. Record the qualified owner, authority, affected person and setting, access or interim support, evidence needed, due date, client communication, correction route, goal disposition and next review. Software may coordinate workflow while qualified people make case-specific decisions within scope.

Apply current professional sources to Kira's goal

For Kira's goal, the BACB ethics hub identifies the current Ethics Code, which addresses client involvement, consent and assent when applicable, assessment, medical needs, risk, intervention, documentation and evaluation for covered people. BACB has no separate organizational jurisdiction. The BCBA outline is examination content, not practice authority. The CASP public summary gives high-level planning context for ABA treatment of autistic people. An evidence-based ABA framework supports integrating research, clinical expertise, client values and context.

Use implementation and access evidence for Kira

In Kira's plan, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative implementation evidence and cautious interpretation. They create no universal participation threshold. Breaux and Smith offer assent-focused practice guidance while describing an evolving evidence base. ASHA supports continuous access to AAC tools or devices.

Close Kira's goal review

Review the digital communication goal plan with Kira, the responsible clinician, affected partners and the specialists named in the manifest. Preserve direct client communication, ordinary supports, disagreement, environmental duties, versions, decisions, limits and open gaps. Keep this page draft and noindex until the required clinical, client or family, AAC, access, digital-safety, privacy, healthcare, personal-care, nutrition, movement, civic, medical, safety, ethics and legal reviews are complete.