A.1 Continuous measurement

What the outline says

Task A.1 in content area A, Data Collection and Graphing (13 of the 75 scored questions): "Implement continuous measurement procedures (e.g., frequency, duration, latency, interresponse time)."

What makes measurement continuous

A measurement procedure is continuous when nothing is left out: every instance of the behavior that meets the operational definition is recorded from the start of the observation to the end. That is the difference from discontinuous procedures such as partial interval recording or momentary time sampling, which record only a sample and give an estimate.

Because every occurrence is captured, continuous data are the most complete picture of a behavior. The trade-off is effort: you must watch the client the whole time and record as things happen.

Each continuous procedure measures a different dimension of behavior:

• Frequency (count): how many times the behavior occurs.
• Duration: how long each occurrence lasts.
• Latency: how long after a cue the behavior begins.
• Interresponse time (IRT): how much time passes between one response and the next.

Frequency and rate

Frequency recording (also called event recording) means making a mark every time the behavior occurs: a tally on a data sheet, a click on a hand counter, a tap in a data app, or even moving a small object from one pocket to the other. It works best for behaviors with a clear beginning and end that last about the same amount of time each time, such as requests, hand raises, hits or throws.

A count only means something alongside the time it was collected in. Twelve requests in a 20-minute session is very different from twelve requests in two hours. That is why you always record how long you observed. Dividing the count by the observation time gives rate: 18 mands in 30 minutes is 18 ÷ 30 = 0.6 mands per minute. Rate lets your supervisor compare sessions of different lengths.

Counting is hard when a behavior happens so fast or so continuously that you cannot tell where one instance ends and the next begins, such as rapid rocking or hand-flapping. Supervisors usually choose duration or an interval procedure for those behaviors.

Duration

Duration recording measures how long a behavior lasts, from onset to offset. You start a timer when the behavior begins and stop it when it ends, using the onset and offset rules in the operational definition. Duration fits behaviors where length matters: tantrums, crying, time on task, time seated at a meal, cooperative play.

There are two common ways to report duration. Total duration adds up every episode in the session (tantrums of 3, 5 and 2 minutes give 10 minutes). Duration per occurrence keeps each episode separate, which requires writing down the start and stop time of every episode. If your supervisor wants to know whether each episode is getting shorter, you need per-occurrence data; a single running timer gives only the total.

Read the definition carefully for rules about pauses. A definition may say, for example, that a pause of less than 5 seconds does not end an episode. In that case a short pause is part of the episode, and you keep timing until the behavior has truly stopped.

Latency

Latency is the time from the onset of a stimulus, usually an instruction, to the start of the response. If you say "Put on your shoes" at 2:15:10 and the client starts at 2:15:25, the latency is 15 seconds. Stop timing when the response begins, not when it is finished; how long the response takes is a separate duration measure.

Latency is the right measure when the concern is a delay in getting started, such as a child who waits a long time before following directions. Falling latency means the client is responding sooner.

Interresponse time

Interresponse time is the time between two responses in a row, measured from the end of one response to the start of the next. It is useful when the pace of responding matters: a client who eats too quickly (time between bites) or a student working through problems (time between answers).

IRT and rate are linked. When IRTs shrink, responses come closer together and more of them fit into the same time, so rate rises. When IRTs grow, rate falls. Latency and IRT both describe when a response happens in time relative to another event; latency is anchored to a stimulus, IRT to the previous response.

Doing it well in session

• Read the operational definition before the session, and record only what meets it.
• Have your tools ready: data sheet or app, counter, stopwatch.
• Record each occurrence as it happens. Totals written from memory at the end of a session are not reliable.
• Write down the actual observation time, including any gaps when you could not observe.
• Never fill in, estimate or copy data you did not observe.
• If you cannot carry out the procedure accurately, or the definition does not fit what you are seeing, note it and tell your supervisor. Changing the procedure or definition is the supervisor's decision.

Continuous data feed directly into the next tasks in this domain: you will enter them and update graphs (A.4), summarize them as rate, mean duration or percentage (A.6), and look for trends (A.7). Inaccurate recording here makes every later step wrong (A.8).

Common mistakes

• Recording a count without the observation time. Always note how long you observed so the count can be converted to a rate.
• Stopping the latency timer when the response ends instead of when it begins.
• Using one running timer when the supervisor wants the length of each episode. Record start and stop times for every episode.
• Mixing up latency and interresponse time. Latency starts at a cue such as an instruction; IRT starts at the end of the previous response.
• Changing what counts as an occurrence on the spot. Follow the operational definition and ask your supervisor when something does not fit.

How it's tested

Expect short scenarios where you name the procedure from what the RBT is doing: counting is frequency, timing how long is duration, timing from an instruction to the start is latency, and timing between responses is IRT. Some questions ask you to pick the measure that matches a concern ("takes a long time to start" points to latency) or to do a simple calculation such as rate or total duration. Watch for answer options that switch latency and IRT, or that stop the latency timer at the end of the response.