An intermittent reinforcement ABA plan delivers a consequence after some eligible responses or intervals rather than every one. A clinician may consider it when a skill is established and the everyday environment cannot provide the programmed outcome each time. Families should see the exact schedule, signals, average and range where relevant, client preference, missed-delivery rules, side-effect measures, and criteria to advance, hold, return, or stop.

Explain the intermittent reinforcement ABA plan

Name whether the rule depends on response count, time, another schedule, or naturally occurring opportunities. Define the response, clock or count, reset, signal, consequence, and partner action. Avoid describing a changing schedule as random when a programmed rule exists.

Ask to see the rule in a form that another trained person could follow. “Sometimes praise the skill” leaves the count, timing, and decision to the moment. A usable rule might say that the software confirmation appears after every correct save, while a chosen celebration appears after a programmed number of completed projects. The record should show what was planned and what actually happened.

Intermittent schedules can depend on different events. A response-count schedule links delivery to a specified number or pattern of eligible responses. A time-based schedule considers the first eligible response after an interval or another defined timing rule. A multiple schedule signals when one rule or another is active. Natural outcomes may also occur unevenly. Families need the page’s exact rule because the general label does not reveal the person’s experience.

Tie the change to a meaningful goal

The plan may aim to make performance practical under ordinary conditions, transfer control to natural outcomes, or reduce dependence on one programmed item. The person and family should understand the purpose and how daily life will improve. A thinner schedule is a treatment change rather than an automatic reward for progress.

Readiness should be stated in advance. The skill may need to occur reliably under the current schedule across a defined number of relevant opportunities. The team should also confirm that the consequence still has value, the person understands the signal, partners deliver the current plan accurately, and efficient communication remains available. Stable performance during a highly controlled session alone may offer too little evidence for a change across home, school, or community settings.

The endpoint should fit real life. Some actions already produce an immediate natural result, such as a device confirming a saved file or a listener responding to a clear request. Those reliable outcomes may remain. The intermittent part might apply only to an extra programmed celebration, token, or activity. Separating the natural and added outcomes helps families see what is actually changing.

Make availability understandable

An unpredictable experience can create confusion even when the clinician has a written schedule. Use signals when the plan depends on availability. A timer, colored card, schedule icon, or spoken explanation may help, provided the person can access and understand it. Teach what the signal means and how to ask for clarification.

Record whether the signal was present, noticed, and used consistently. If partners forget the signal or deliver the outcome outside the rule, the person experienced a different schedule. That is an implementation issue to correct, not evidence that the client failed.

Use conceptual sources carefully

The ABAI page and BACB outline cover basic schedules, maintenance, and schedule thinning. These sources provide concepts rather than a universal readiness rule, ratio, interval, or terminal schedule.

Preserve transparency and communication

The Ethics Code supports understandable communication, client involvement, consent and assent when applicable, and continual evaluation. ASHA supports continual communication access. The person should have an accessible way to ask when an outcome is available, request help, pause, or report confusion.

Basic access to communication, food, water, bathrooms, mobility, prescribed care, and emergency help stays outside the intermittent rule. Health and safety breaks should follow their own plan. The team should also avoid placing most enjoyable interaction behind work requirements. A narrow schedule with freely available relationships, rest, and choice is easier to understand and review.

Monitor more than the target response

A schedule can look successful if the team reports only completed responses. Also track response quality, time to begin, pauses, requests for help, repeated requests, errors, distress, withdrawal, fatigue, and earlier patterns that the plan is intended to replace. Record partner fidelity and missed or late deliveries. Family and staff burden belong in a separate feasibility measure.

Predeclare decision rules. An advance rule may require stable responding plus acceptable burden across a set number of eligible opportunities. A hold rule gathers more evidence without further thinning. A rollback rule returns to the last effective version after defined deterioration. A stop or clinical-review rule addresses injury, serious distress, loss of communication access, or another safety concern.

At review, show the raw counts beside each percentage and describe the version that produced them. Compare similar opportunity types and identify changes in people, settings, task difficulty, health, and access. The clinician should explain why the next decision fits this person’s evidence. Software may flag a threshold, while clinical interpretation and treatment changes remain with the qualified role.

A practical example

Celia is learning to save a music project. The software confirmation follows every correct save, while an optional celebration animation shifts from every save to selected saves. A visible icon tells Celia when the animation is available. The team defines one eligible opportunity as a completed editing segment with the save button available and the project online.

Across ten eligible opportunities, Celia saves independently nine times and asks about the animation once. The animation is delivered on all three programmed occasions. One additional planned opportunity is excluded because the software is offline, and the team reports that invalid event separately. It keeps the reliable software confirmation as the natural outcome.

The result supports holding the current version for another set of opportunities. It does not establish that a thinner schedule will work during longer projects or with another device. The next review includes Celia’s report about the icon, save accuracy, latency, repeated questions, and whether the optional animation still feels worthwhile.

A family checklist

  • What exact outcome becomes intermittent, and which natural outcome remains?
  • Is the rule based on responses, time, signals, or another event?
  • What makes an opportunity eligible, and what resets the count or clock?
  • Can the person understand availability and ask for clarification?
  • Which data cover quality, latency, communication, distress, and partner delivery?
  • How many valid opportunities are required before a decision?
  • What triggers an advance, hold, rollback, pause, or stop?
  • Which basic needs, supports, and preferred activities stay freely available?

Questions families can use

Which outcome becomes intermittent? Which natural outcome stays? Is the rule understandable? What signals availability? What counts as confusion or distress? Are missed deliveries visible? Which data would return to the earlier schedule?

Related resources

Sources

Finni resources

Ready for the next step?

Find ABA care near you