Skip to main content
Latency times the gap between a cue, such as the teacher’s direction, and the student’s response. It times one behavior per observation.
1

Set up

Set up an observation and choose Latency. In Clock starts when, describe the cue that begins every trial, or pick one with From library. Name and define the response behavior. There is no length or trial count: you end the observation when you have the trials you need.
2

Time each trial

Select Start when you begin watching. When the cue happens, select Mark prompt, or press Return or Enter. When the student responds, select the response, or press its key. If you decide no response came, select No response, or press 0.
Latency recorder for Sam Sample timing trial 2 at 1.8 seconds, with Task initiation and No response controls and one responded trial under Completed trials.

Trial 2 is running; trial 1 is under Completed trials. Shown in demo mode.

Each finished trial appears under Completed trials. Under the newest one, you can type the exact words of the cue or what happened.
3

End and save

Select End and confirm. If a trial is still running, Sightline asks whether to record it as No response; select Continue Session to finish the trial first. Add any final context, then save.

​
Where your data appears

In Results, the Summary card shows the average latency of trials with a response, and how many trials had no response. Latency by Trial shows each trial as a bar, and Trials lists them. The range, from shortest to longest response, appears in written summaries and exports. How the average is calculated

​
Good to know

Decide when a trial ends without a response. Sightline has no automatic timeout, so choose a cutoff, such as 30 seconds, and note it in Context. Pausing. You can pause only between trials. Finish or cancel the running trial first. Started a trial by mistake? Select Cancel or press Esc. Outside a text field, ⌘Z or Ctrl+Z removes the latest completed trial. Fix a mistake covers changes after saving.