Some behaviors leave evidence behind. A finished worksheet, a stack of folded towels, or toys back in the bin all tell you something about what a learner did, even if you were not watching at the moment it happened. This lesson covers how to measure behavior through those lasting results.
Why it matters
As an RBT you often support more than one thing at once: running a program, setting up materials, or helping another learner in the same room. Permanent product recording lets you measure some target behaviors after they occur, so you do not have to watch every second to get accurate data.
It also produces data that are easy to check. Because the product is still there, your supervisor or a second observer can count it again later, which makes agreement checks simple. Practice items on this task usually ask you to name the method, pick a behavior that fits it, or spot a reason the data may be wrong.
Key ideas
- Measure the outcome, not the moment. Permanent product recording measures a behavior by examining a tangible result it produced in the environment. You record after the behavior has ended.
- The behavior must leave something lasting. Writing, assembling, sorting, and cleaning up leave products. Smiling, crying, or making a request usually do not, so those need to be observed as they happen. Your supervisor may decide to video-record sessions so behavior can be scored later; follow your agency's privacy and consent rules for any recording.
- Only the target behavior should make the product. If a sibling, peer, or staff member could create the same outcome, the count may not reflect the learner's behavior.
- Each occurrence should produce the same kind of product. One completed problem, one folded towel, or one placed puzzle piece each equals one response, so the count stays meaningful.
- Measure before the product changes. Record the product before it is cleaned up, moved, erased, or thrown away. Once it is gone, so are your data.
- Products show what, not how. A finished worksheet does not tell you how many prompts were given, how long the task took, or whether problem behavior happened along the way. If the plan needs that information, it calls for an additional measure.
Definitions
- Permanent product: a lasting, tangible outcome of a behavior that can be measured after the behavior has ended, such as written answers, assembled parts, or items put away.
- Permanent product recording: measuring a behavior by counting or scoring its permanent products, often reported as a count, a percentage (for example, percentage of problems correct), or a rate (for example, kits packed per hour).
- Work sample: a completed piece of a learner's work kept for scoring, such as a worksheet, a writing sample, or a finished craft.
- Operational definition: an objective description of the target behavior. For permanent products, it should say exactly what counts as one product and what "correct" or "complete" means.
Examples from a session
Products across settings
- School: Malik, 8, completes a 20-problem math worksheet while his RBT helps another student. Afterward, she scores it: 16 of 20 correct, or 80%.
- Clinic: Ana, 5, strings beads during an independent-work program. At the end, her RBT counts 9 beads on the string.
- Home: Priya, 16, folds towels as part of a daily-living goal. Her RBT counts 12 folded towels that meet the definition (edges lined up, folded in thirds).
- Vocational program: Mr. Okafor, 34, stuffs envelopes at a supported job site. His RBT counts 40 sealed, correctly filled envelopes at the end of the shift.
In each case, the RBT records the product after the work is finished and before it is moved or put away. Notice what these data do not say: whether Ana needed physical prompts, or how long it took Priya to start. If your supervisor needs that information, the plan will name an additional measure such as prompt level or latency.
Now picture a different situation. Malik's homework comes back finished, but you learn an older cousin helped him with most of it. The worksheet still exists, yet it no longer shows only Malik's behavior. Score it as the plan directs, note what you learned, and tell your supervisor rather than recording it as independent work.
Common mistakes / exam traps
- Using it for behaviors with no lasting outcome. Crying, eye contact, and vocal requests leave nothing to count later unless the session is recorded. Pick a continuous or discontinuous method instead.
- Waiting too long. Toys get put away and whiteboards get erased. Measure the product before it is changed or discarded.
- Filling in missing data. If the product was lost before you recorded it, do not estimate. Record that the data are missing and tell your supervisor.
- Changing the denominator. If the plan says "percentage correct out of problems presented," divide by every problem on the page, not only the ones the learner attempted.
Exam trap
If a question says the RBT measured the behavior "after the session" by counting something the learner made or changed, the method is permanent product recording, even though the RBT did not watch each response. The trap is momentary time sampling: checking at set moments whether the learner is writing scores the behavior itself, while permanent product recording scores what the behavior left behind.
Exam trap
A finished product is not the same as independent target behavior. The product counts only if the learner's target behavior alone could have made it. If someone helped, the answers were copied, or prompts were given, the count still says what exists but not who made it or how: note it and tell your supervisor.
Quick check
Deshawn, 7, builds a block tower during a clinic program, and his RBT plans to count the blocks he stacked. Which step matters most for accurate permanent product data?
Related topics
- A-01: Continuous measurement: frequency, rate, duration, latency, and IRT
- A-02: Discontinuous measurement: interval recording and time sampling
- A-05: Writing observable, measurable descriptions of behavior
- A-06: Summarizing data with rate, mean duration, and percentage
- A-08: Why unreliable data and weak procedural fidelity are risky