A timer for each target
Start and pause a live timer on the target. The elapsed time is added to the session’s total, so a behavior that happens in bursts is timed across all of them.

Start the timer when the behavior starts, pause it when it stops, and the time is banked for the session. Count and time together for behaviors that happen several times, or measure how long a learner takes to respond.
Each timed run is stored with its start time, so the Analysis tab can show when behaviors happen. This is a sample with made-up data.
The timer lives on the same screen as the rest of the session’s data.
Start and pause a live timer on the target. The elapsed time is added to the session’s total, so a behavior that happens in bursts is timed across all of them.
For an episode the timer missed, or time that was taken elsewhere, type the minutes and seconds instead.
Count how many times a behavior happened and how long it lasted, together, on the same target.
Latency targets use the same timer, so you can time how long a learner takes to respond after an instruction.
Every timed run is stored with when it started, which feeds the behavior analysis by day and hour.
The session note states the incidents and the total time, for example how many incidents of a behavior and how long they lasted in all.
Set the target up as duration, duration with frequency or latency.
Start the timer, pause it, and keep going. Enter a time by hand if you need to.
The session’s total is saved with the visit and plotted on the target’s graph.
Yes. The timer can be started and paused as often as you need, and the time adds up for the session.
Enter the minutes and seconds by hand.
With the same timer: start it when the instruction is given and stop it when the learner responds.
Yes. Each timed run is stored with its start time and appears in the behavior analysis by day and hour.
Request a demo and we will walk you through it.