Collecting data is only half the job. The numbers you record become useful only once they are entered correctly and added to a graph your supervisor can read at a glance.
Why it matters
Your supervisor reviews graphs to decide whether a program is working, whether to change a prompt level, or whether a behavior plan needs revising. If data is entered late, entered wrong, or left off the graph, those decisions are made on an incomplete or false picture. A learner could stay on a program that is not helping, or move on before a skill is solid.
Practice questions on this task are usually short scenarios: an RBT makes a recording mistake, a session is missed, or a new phase begins, and you choose the next step. The best answer is usually the one that keeps the record accurate, complete, and honest.
Key ideas
- Enter data promptly. Record during the session and enter or upload it as soon as possible afterward, following your agency's policy. Waiting until the end of the week invites memory errors.
- Enter exactly what you observed. Copy values from the data sheet as recorded. Never round a number to look better, skip a "bad" session, or fill in a value you did not observe.
- Double-check before you leave. Compare what you entered against the data sheet, especially the date, the target, and the units (seconds versus minutes, count versus percentage).
- Correct errors openly. On paper, a common method is to draw a single line through the mistake so it stays readable, write the correct value, and add your initials and the date. In an electronic system, use the edit feature so the change is tracked. Follow your agency's procedure either way.
- Add context in a note. If something unusual happened (the learner was sick, a fire drill cut the session short, a new staff member was present), enter the data as recorded and add a brief note. Context helps your supervisor interpret the numbers.
- Keep data confidential. Data sheets and graphs are part of the learner's record. Use only approved systems and devices, and keep paper sheets out of view.
Definitions
- Data sheet: the form, paper or electronic, where you record what you observe during the session. It is the original record, so graphs and entries are checked against it, never the other way around.
- Session note: a brief written account of the session that gives context for the data, such as an illness, a short session, or a session that was canceled.
- Line graph: the most common graph in ABA. It shows how a behavior changes across sessions or days.
- x-axis (horizontal): shows time, usually session numbers or dates, in order.
- y-axis (vertical): shows the measure of behavior, such as count, rate, duration, or percentage correct. It needs a clear label with units.
- Data point: one plotted value, usually the summary of one session.
- Data path: the line that connects consecutive data points within the same phase. It breaks at a phase change line and across sessions that never happened.
- Phase change line: a vertical line, often dashed, that marks when conditions changed, such as moving from baseline to intervention. Each phase is labeled at the top, and data points are not connected across this line.
- Operational definition: the description of the behavior that tells you exactly what counts. Your entered data should always match it.
Examples from a session
Three entries, three decisions
- Clinic: Mateo, age 6, gets 8 of 10 trials correct on matching colors. His graph's y-axis is percentage correct, so his RBT, Dana, plots 80% at today's session, not "8."
- Home: Rosa, age 15, misses Wednesday's session because she has the flu. Her RBT leaves Wednesday without a data point and does not draw the data path across that gap. A zero would wrongly say the session happened and the behavior never occurred.
- School: After five baseline sessions, the supervisor starts a token system for Jamal, age 10. His RBT adds a phase change line between sessions 5 and 6, labels the new phase "Token system," and starts a new data path on the other side of the line.
Many agencies use apps that graph data automatically. That saves time, but it does not remove your responsibility. After each session, glance at the graph and make sure the newest point matches what you recorded. A typo of 40 instead of 4 can look like a dramatic spike.
If you notice an error after the fact, such as a point plotted at 80 when the data sheet says 60, correct it using your agency's procedure and let your supervisor know. They may have already used that point to make a decision.
Common mistakes / exam traps
- Connecting data across a phase change line. The data path stops at the line and starts again in the new phase, so each phase can be compared on its own.
- Mixing up units. If the data sheet shows seconds and the graph is in minutes, convert before plotting: 210 seconds is 3.5 minutes.
- Erasing or hiding mistakes. Correction fluid, scribbling out, or deleting entries removes the record of what changed. Correct errors so the original stays visible or tracked.
- Making the graph look cleaner. Skipping an "unusual" session, adjusting a number, or estimating a value hides real information. Enter what you recorded and add a note.
- Changing the plan because of one data point. Your job is to record and report. Decisions about the intervention belong to your supervisor.
Exam trap
Zero vs. no data point. Plot a 0 only when the session happened and the behavior did not occur. If the session never happened (an absence or a cancellation), leave no data point and break the data path there. Ask yourself: did anyone observe?
Exam trap
Planned trials vs. trials run. Percentage correct divides by the trials actually run, not the trials planned. If a session ends after 10 of 15 planned trials and the learner is correct on 8, plot 80%, not 53%.
Quick check
An RBT's agency uses an app that graphs data automatically. After entering today's session data, what should she do next?