FunPrep RBT Exam Prep
Built on the new RBT 3rd edition outline (effective January 2026)

Skill Acquisition Plans: Your Role as the RBT

The BCBA writes the skill acquisition plan. You bring it to life: run the teaching procedure exactly as written, prompt and fade on schedule, take data, and report back. How to read a plan and where the boundaries are.

The short answer: A skill acquisition plan is the supervisor's written recipe for teaching a skill: the target, materials, teaching procedure, prompting, reinforcement, mastery criteria, and data method. The RBT implements it exactly as written, collects data, and reports progress or concerns. RBTs do not write, modify, or declare mastery of plans.

What is inside a skill acquisition plan

ComponentWhat it tells you
Target skillThe observable, measurable behavior being taught
Materials and setupWhat you need and how to arrange it
Teaching procedureThe steps: discrete-trial, naturalistic teaching, chaining, or shaping
Prompting and fadingThe prompt hierarchy and when to fade it
Reinforcement scheduleWhat to deliver, and how often
Mastery criteriaWhen the skill counts as learned
Generalization planHow the skill spreads to new settings and people
Data methodHow to measure and record progress

Read the target first, then the procedure, then the data method. If any piece is unclear, clarify with your supervisor before the session, not during it.

Your job: implement as written

"As written" is the most tested phrase in this domain. It means the plan is the authority, not your judgment in the moment. Run the trials the way the plan describes, deliver the prompts in the order specified, reinforce on the schedule given, and record data the way the plan says.

When something is not working, you do not fix the plan. You collect data showing it is not working and report it. That data is what lets the BCBA fix it properly, and it is also what protects you: you followed the plan, and the numbers tell the story.

Prompting and fading inside the plan

Plans specify a prompt hierarchy, most-to-least or least-to-most, and when to fade. Follow the fading steps on the schedule in the plan, not when you feel the client is ready. Fading too fast creates errors; fading too slow creates prompt dependence.

If the client is stuck at a prompt level, document the pattern across sessions and report it rather than inventing a new prompt level. Stuck data is valuable data; improvised prompting is just noise.

The lines you do not cross

Never add targets, change a procedure, decide a skill is mastered, or discharge a goal on your own. Those are BCBA decisions. The exam loves this trap: an option that "fixes" a failing program by changing it will always be wrong for the RBT. The right answer is almost always: keep implementing as written, take clean data, report to the supervisor.

Reporting back: data, not opinions

"He did great today" is not a report. "Completed 8 of 10 trials independently at the current prompt level; errors clustered on step 3" is. Objective session notes and verbal updates built on your data are what supervisors need to make decisions.

The 3rd edition's documentation domain rewards exactly this habit. Every plan you implement is also a writing exercise: can you describe what happened so precisely that someone who was not there can see it?

Plan Smarts: 4 Scenario Questions

Every question tests the same rule: the plan is the authority, and data plus reporting is your job.

The plan says to use least-to-most prompting, but the client is struggling. What do you do?

B. Implement as written. Documenting the pattern and reporting it gives the BCBA the data needed to revise the plan properly.

Which part of the plan tells you when the skill counts as learned?

B. Mastery criteria define the performance standard for a learned skill. Only the BCBA decides when the criteria are met.

You notice the client is using the skill independently at home, beyond the plan's target. What now?

C. Generalization is worth reporting, not deciding. Record the observation objectively and let the supervisor determine what it means for the plan.

The plan's data method is frequency count, but duration feels more informative. You...

C. Use the method as written so your data stays comparable across sessions. Suggesting an idea to the supervisor is fine; changing the method on your own is not.

0 of 4 answered

Sources

Last reviewed: October 7, 2026 against the BACB RBT 3rd edition task list.

Behavior acquisition is 25% of the exam. Own it.

A quarter of your scored questions come from this domain. Practice implementing, prompting, and reporting in the simulator.

Try the 85-Question Simulator Skill Acquisition Guide

Frequently asked questions

Do RBTs write skill acquisition plans?

No. The BCBA or BCaBA designs the plan. The RBT implements it exactly as written, collects data on it, and reports progress or concerns to the supervisor.

What if the plan is not working?

Keep implementing it as written, collect clean data showing what is happening, and report it. The data you collect is what allows the supervisor to revise the plan properly.

Can I change the prompting if the client seems prompt dependent?

No. Follow the plan's prompting hierarchy and fading schedule, document the pattern you are seeing, and report it. Changing prompts on your own is outside the RBT role.

Who decides when a skill is mastered?

The BCBA, using the plan's mastery criteria and the data you collected. An RBT never declares mastery or discharges a goal independently.

What should I read before a session?

The target skill, the teaching procedure, the prompting and fading steps, the reinforcement schedule, and the data method. If any piece is unclear, ask before the session.

How detailed should my session notes be?

Objective and tied to the plan's targets: trial counts, prompt levels, and error patterns, not opinions. Someone who was not there should be able to picture the session.