ABA maintenance and prompts should be reported together rather than treating every supported response as failure. Maintenance asks whether a useful skill continues over time or after teaching changes. Independence asks what help is present. Ordinary supports such as AAC, checklists, mobility tools, and chosen reminders may remain, while added teaching prompts should be named and tracked by level.

ABA maintenance and prompts

Define the meaningful response, ordinary support, teaching-prompt hierarchy, opportunity, wait time, partner response, and scoring rule. Report independent responses, responses with each prompt level, declines, missing opportunities, and invalid trials separately. Compare like conditions across maintenance dates.

The word “independent” needs a written definition. It may mean initiating without another person's instructional prompt while using ordinary tools. It may refer to completing a routine with a checklist. It should not imply functioning without communication, mobility, sensory, language, or health access that the person uses in daily life.

Sort supports into clear categories

CategoryExamplesHow to reportOrdinary accessAAC, glasses, mobility tool, interpreter, chosen visual scheduleAvailable or unavailable during every opportunityEnvironmental supportarranged materials, quieter space, labeled storageRecord the condition and any setup failureNatural cueschedule time, arriving at a location, an ordinary requestDefine the opportunity it createsTeaching promptadded model, gesture, verbal cue, physical guidanceRecord level and timing separatelyPartner responsewaiting, acknowledging, providing the agreed outcomeMeasure apart from the client's response

The same item can have another role in another plan. Define it around the person's ordinary use and the clinical question.

Define the conclusion carefully

Prompt use can show where support is still useful. A shift from a full model to a brief reminder may be meaningful even when the independent count is unchanged. Conversely, removing a needed access tool can lower performance while creating the appearance of a stricter probe.

Report the full response distribution

Suppose ten maintenance opportunities produce six responses without added teaching prompts, two after one verbal reminder, one after a model, and one decline. Report each count. Calling the result 60% maintained hides useful supported performance and the client's decision to decline.

Compare the same categories across dates. If the prompt hierarchy changes, start a new phase or explain the mapping. A shorter prompt or longer wait time can materially affect the label.

Ask whether prompt reduction is the right goal

Reducing added teaching help may be useful when the person wants greater autonomy and the plan preserves access. It can be irrelevant or harmful when the “prompt” is actually a reasonable accommodation or chosen tool. The client and family should understand the expected benefit and burden.

Do not withhold communication, food, water, bathroom access, mobility, prescribed care, or emergency help to create an unprompted response. Those are outside a performance test.

Use current clinical and measurement sources

The CASP public summary places assessment, planning, implementation, and evaluation within its autism-treatment scope. The BACB Ethics Code addresses client involvement, consent and assent when applicable, assessment-based intervention, risk, documentation, and evaluation for covered behavior analysts.

The BCBA Test Content Outline covers programming for generalization and maintenance as examination content. It does not create a universal probe count, maintenance interval, independence definition, or authority to practice.

Use the historical framework with current judgment

Stokes and Baer organized generalization-programming tactics in a 1977 conceptual paper. It remains historically influential, while current clinical use still requires individualized goals, evidence, supports, client choice, and review.

Keep ordinary access supports available

The ASHA AAC portal supports continuous communication-tool access. AAC, visual schedules, mobility supports, and other ordinary access tools can remain part of independent daily participation when they fit the person and goal.

When the person selects a reminder, record that choice. Independence can include knowing when and how to use a tool or ask another person for support.

A practical example

Sloane completes a packing routine in five weekly probes. Her chosen checklist remains available each time. She completes three without added teaching prompts and two after one verbal reminder. The report shows 3 of 5 without added prompts and 2 of 5 with one reminder, with checklist access present in all five.

At the next check, staff accidentally remove the checklist for two opportunities and Sloane asks for it back. Those opportunities are recorded as setup failures, not independent-skill failures. The checklist is restored, and Sloane completes the next four opportunities without teaching prompts.

The team discusses whether the reminder still serves a useful purpose. Sloane chooses to keep a phone alert before the routine. The plan labels it an ordinary chosen support rather than a prompt to fade.

Questions for a maintenance report

Ask which supports were available, which prompt levels occurred, how the person requested help, whether opportunities were valid, what partner actions followed, what the client preferred, and whether any support change altered the task.

Watch how support use changes over time

Maintenance data are more useful when each prompt level and ordinary support stays defined across checks. A pattern may show that the person continues the outcome while requesting one reminder in unfamiliar settings. Another pattern may show increasing help after a health or schedule change. Report the distribution rather than compressing it into “maintained” or “lost.”

If the team changes the wait time, prompt hierarchy, or response definition, label a new phase. Historical data can remain visible while direct comparison may need qualification.

Avoid a prompt-dependency shortcut

Frequent prompt use can prompt a clinical review of teaching, opportunity, motivation, access, and partner behavior. It does not establish that the client is dependent on prompts or that supports should be removed quickly. The clinician should examine whether staff provide prompts earlier than the plan allows, whether natural cues are clear, and whether the outcome matters to the client.

Families can ask for staff-fidelity data on the wait time and prompt rule. If staff prompt before the client has a fair chance to respond, client prompt-level data alone misdescribe the problem.

Define help-seeking as a possible outcome

Asking for help can be independent problem solving. A packing routine may include noticing that an item is missing and requesting assistance. The goal should distinguish a planned help response from an instructional prompt supplied before the person asks.

Record whether the partner honored the help request and whether the person completed the valued outcome. This broader view can preserve autonomy without requiring every task to occur alone.

Decide what a decline triggers

The plan can specify a review after a certain pattern, while avoiding one universal threshold. Check access, health, setting, implementation, client priority, and opportunity quality. The response may be environmental repair, adjusted support, renewed teaching, interdisciplinary referral, or a decision that the goal no longer fits.

Questions families can use

Ask which supports count as ordinary, which count as teaching prompts, how prompt level is recorded, whether access changed, what outcome matters to the client, and how the pattern changes over time.

Related resources

Sources

Finni resources

Ready for the next step?

Find ABA care near you