How to Explain an ABA Schedule to Your Child

Use concrete information

Replace 'therapy later' with a name, place, start cue, approximate end, transportation plan, and two or three likely activities. Mark uncertain parts as uncertain. A calendar, countdown, photo, or object cue can support understanding when it matches the person's communication.

Include choice and change

Explain which parts are fixed, which choices are available, and what happens after a cancellation or delay. The BACB Ethics Code addresses understandable communication, client involvement, consent, and assent when applicable for covered professionals.

Keep AAC available

ASHA says AAC users should always have their tools or devices. Build the schedule around accessible messages for yes, no, who, where, help, wait, break, pain, and finished. Honor the message rather than requiring speech or eye contact.

Check understanding without a quiz

Leo reviews five schedule facts and communicates questions about two. The family answers one and asks the provider to confirm the other. Report 5 facts presented and 2 questions, not a comprehension score. The next preview includes the confirmed transportation change.

Build the child-facing schedule explanation

Use the child-facing schedule explanation to give the child concrete, accessible information about upcoming ABA visits, choices, changes, and ways to ask or stop. Lock the person, review period, and eligible events before calculating any rate. Give each row a source, observed state, owner, next action, due date, and closure artifact. Keep the family's accessible summary linked to the detailed operational record so a new staff member can understand the current situation without relying on memory.

Collect only records that serve the named decision: the actual day and time; location; travel; people; expected sequence; planned duration; ordinary supports; communication and AAC; choices; caregiver presence; breaks; food, bathroom, and health access; transition home; known changes; visual, written, spoken, signed, or tactile format; and the child's questions. Label the author or issuing party, effective date, scope, and version of each item. A schedule screen, portal message, call note, clinical record, authorization, and billing artifact answer different questions. Preserve conflicting items together until the responsible role resolves the difference.

Work in an order that can be audited. Start with what is confirmed. Use the child's ordinary communication and a format they can revisit. Name who, where, when, what happens first, what may change, and what happens afterward. Include real choices and a reliable way to ask questions, pause, decline when applicable, or report discomfort. Update the explanation when the schedule changes, and compare the preview with what actually happens. Preserve the original event when a correction occurs, then add a dated correction with its author and reason. Store health, education, and financial details in approved systems, limit access by role and purpose, and avoid copying sensitive narrative into a broadly visible scheduling queue.

Keep each decision with the right person

Write the decision owner beside every open field in the child-facing schedule explanation. The child communicates preferences, questions, assent, dissent, and experience through any reliable form. The legally authorized person handles consent when required. A qualified clinician explains clinical activities and responds to clinical concerns. Operations supplies accurate logistics. Caregivers support understanding without promising outcomes or speaking over the child. The explanation does not create consent or authorization by itself. Administrative staff can collect evidence, calculate from verified inputs, and route questions. Software can flag omissions or conflicts. Neither should invent a clinical conclusion, disclosure authority, payer decision, family preference, or emergency instruction.

Turn the record into an understandable choice. Families can choose the timing and format of the explanation based on how the child uses information. Some people prefer an early calendar, while others need a shorter same-day preview. The goal is usable predictability. Avoid presenting tentative staff or activities as certain, using threats, or promising a reward or result that the provider has not confirmed. Explain which facts are confirmed, which are provisional, what could change, and what the person and family can do next. Use the person's usual communication. Provide language, disability, sensory, mobility, and AAC access throughout calls, meetings, visits, and written follow-up.

Prepare for the next conversation with specific questions: What is certain? What may change? Who will be there? How long might it last? Which supports and choices are real? How can the child ask, pause, or say something feels wrong? What happens afterward? Who updates the explanation if staff, location, timing, or activities change? Read the answers back, name the owner and date, and send a written summary through an approved channel. When the contact cannot answer, ask for the role or formal process that controls the question instead of treating a convenient response as final.

Use a release gate and failure plan

The child-facing schedule explanation should define a release gate for the action at issue. Before sharing the schedule, verify the confirmed date, time, location, people, broad purpose, duration range, supports, choices, changes, and return plan. Label uncertainty. Provide the child's communication system and a way to revisit or correct the information. Update the plan promptly when a material fact changes. A cleared gate applies only to the named person, staff, provider, site, service, communication supports, and time period. Recheck any field that can change before the visit, information transfer, service record, claim, fee, or return occurs.

Plan for realistic failures before the family is under pressure. The explanation fails when it uses vague words such as later, omits travel or duration, shows a familiar therapist who will be absent, removes AAC during the conversation, treats a visual schedule as unchangeable, tests recall as obedience, ignores the child's no or pain message, or describes every clinic visit as the same despite known differences. Record the observed problem rather than an assumed motive. Preserve the evidence, protect live safety and administrative deadlines, stop the affected action when appropriate, and tell the family what remains available while review continues.

Give the child-facing schedule explanation a written fallback for each high-impact failure. Name the trigger, person authorized to decide, immediate safe action, information needed, family contact, clinical or financial effect, alternate route, and review time. Immediate health, safety, emergency, or reporting duties use their applicable route while routine administrative correction continues.

Work through a realistic complication

Leo receives a six-part visual and AAC-supported preview. Five parts match the visit; the assigned therapist changes that morning. The caregiver updates the therapist image and explains who will greet him. Leo selects a question about the new person. Preview accuracy is five of six before correction and six of six after the update. State the numerator, denominator, unit, time window, and status of every excluded or open item before interpreting the result. A percentage cannot show which event was unsafe, burdensome, clinically significant, expensive, or still waiting on another party.

Add one later complication to the child-facing schedule explanation. A staff change, new health fact, school update, access failure, corrected service record, payer response, or family preference may invalidate an earlier decision. Link the new artifact to every downstream event that relied on the old state. Keep the history visible so the family and provider can see what was known at each point.

Verify the full cycle and improve the process

After the visit, ask what matched, what surprised the child, and which support or wording helped. Compare the promised sequence with actual events, including breaks and return home. Use the result to improve the next explanation rather than assuming limited speech means the child did not notice or care about the change. A calendar entry, sent message, portal status, staff promise, or completed form is an intermediate artifact. Close the child-facing schedule explanation only when the expected real-world outcome and family-facing record agree. Name who performs that reconciliation and how an unresolved mismatch returns to the active queue.

Measure the child-facing schedule explanation with explicit units. Name the start and end event for every duration and every eligible event in a denominator. Report pending items by count and oldest age. Keep sessions, minutes, staff assignments, communications, forms, service records, claims, and households separate. Pair every rate with raw counts and relevant exceptions.

Finish with a short retrospective specific to the child-facing schedule explanation. Ask which fact was hardest to verify, which handoff or support failed, whether the person and family could communicate and participate, and which narrow control should change. Test the correction in the setting where the failure occurred. The examples on this page support planning; they do not establish another person's clinical need, legal right, coverage, or likely outcome.

Treat the schedule as accessible communication

DOJ guidance explains that covered entities consider communication context and the person's normal method. A visual schedule is one possible aid, not a universal solution. Some people need AAC, sign, spoken language, large print, tactile information, captioning, simplified text, or a combination. Check whether the child can receive information, ask questions, and correct the preview through the chosen method.