What to Do When Your Child Does Not Want to Enter the ABA Clinic

Describe the event precisely

Record arrival time, location, people present, what changed, available AAC, observable actions, the person's messages, adult responses, and outcome. Separate one difficult arrival from a repeated pattern. Do not infer escape, attention, or another function from the event alone.

Check health, safety, and access

Use the appropriate medical or emergency route for concerning health or imminent danger. Keep communication available. ASHA says AAC users should always have their tools or devices. Offer the agreed space, wait time, help, break, or exit.

Route clinical review correctly

The BACB Ethics Code addresses medical needs, assent when applicable, assessment, risk, and evaluation for covered professionals. Ask the qualified clinician whether arrival supports, timing, setting, staffing, or the service plan needs review.

Keep denominators honest

Jaden has six planned arrivals. Four proceed, one pauses and proceeds later, and one ends before entry. Report 4 of 6 proceeding as planned, one delayed, and one ended. The team reviews all six rather than excluding the difficult arrivals.

Build the clinic-arrival concern log

Use the clinic-arrival concern log to respond to clinic refusal or distress with observable facts, accessible communication, immediate health and safety checks, and qualified follow-up. 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: planned arrival; date and time; travel; people and setting; recent changes; pain, illness, sleep, food, medication, or sensory concerns; AAC and other supports; observable actions; person's messages; adult responses; immediate outcome; medical or safety route; and follow-up owner. 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. Protect immediate safety and make communication available. Describe what occurred before, during, and after arrival without assigning a function. Ask about pain, fear, access, recent changes, and the person's preference. End or pause when needed, use urgent care routes when indicated, and send the factual record to the qualified clinician for broader review. 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 clinic-arrival concern log. The person communicates willingness, discomfort, and needs through a reliable form. Caregivers and staff act on immediate safety within their roles. Medical professionals address health concerns. A qualified clinician interprets behavior and changes clinical supports. Operations can adjust arrival logistics without deciding behavioral function. 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 need a clear option to pause or leave, an explanation of any immediate risk, and a plan for the next arrival. Ask whether timing, travel, staff, setting, communication, or the service itself should change. A single difficult arrival should not become a permanent label. 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 did the person communicate? Was AAC available? Could pain, illness, fear, or fatigue matter? What changed from usual? Which response protected safety and choice? Who reviews the pattern? What must be different before the next arrival? 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 clinic-arrival concern log should define a release gate for the action at issue. Another planned arrival needs resolved urgent concerns, available communication and health supports, a safe route, known staff and setting, an accessible explanation, the person's applicable assent process, a response to early distress, and a qualified review when clinical conditions changed. 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. Concern rises when adults block the exit, remove AAC, repeat demands, ignore pain, crowd the person, call distress manipulation, exclude failed arrivals from data, or restart the same routine without review. An appointment attendance target never overrides urgent medical or safety action. 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 clinic-arrival concern log 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

Jaden has eight planned clinic arrivals. Five proceed, one proceeds after a quiet pause, one ends after Jaden reports pain, and one ends when AAC is unavailable. Report five of eight as planned, one delayed, and two ended, then keep both ended arrivals in clinical and operational review. 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 clinic-arrival concern log. 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

Review patterns across arrivals, including successful ones. Compare travel, staff, setting, wait, health, communication, response, and person feedback. Test one corrected condition at a time when safe and appropriate. Record whether the next arrival improves access, while avoiding a causal claim from a small uncontrolled comparison. A calendar entry, sent message, portal status, staff promise, or completed form is an intermediate artifact. Close the clinic-arrival concern log 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 clinic-arrival concern log 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 clinic-arrival concern log. 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.

Keep the person's message available during arrival

ASHA's AAC portal says AAC users should always have access to their communication tools or devices. Arrival distress is a particularly important time to preserve pain, help, stop, break, location, and preference messages. Record the offered access and partner response so clinical review does not mistake a communication barrier for evidence about behavioral function. Prepare the next-arrival plan with observable early indicators, one named adult response, an agreed pause or exit, and the route for medical concerns. Tell the person what will happen in their reliable form before travel begins. If the setting or staff will differ, name that change instead of presenting the next visit as identical. Ask the family which recovery time or support is needed after an ended arrival before proposing another appointment.