Box Clicking Test

Technical Manual

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com), Millisecond

Created: October 29, 2026

Last Modified: October 29, 2026 by K. Borchert (katjab@millisecond.com), Millisecond

Script Copyright © Millisecond Software, LLC

Background

This script implements Millisecond's version of the Box Clicking Task (BCT); a screening measure of visual–motor integration (VMI) developed by Hernandez et al (2024) that can be used across devices.

References

Hernandez, R., Gatz, M., Schneider, S., Finkel, D., Darling, J. E., Orriens, B., Liu, Y., & Kapteyn, A. (2024). Visual–motor integration (VMI) is also relevant for computer, smartphone, and tablet use by adults: Introducing the brief box clicking test. American Journal of Occupational Therapy, 78, 7805205010. https://doi.org/10.5014/ajot.2024.050680

Duration

< 1min

Description

Participants are asked to click four gray boxes on the screen as quickly as they can. Each clicked box changes its color to yellow.

Procedure

The trial sequence presents the instructions along with the four response boxes that are presented in
a 2x2 grid in the center of the screen.
Each time a new box is clicked, it changes its color to yellow to give visual confirmation that it was
clicked. The script tracks how many times a box was clicked.
Participants are asked to click all four boxes as fast as possible.

the continue button at the end does not actually have to be clicked. The task will end
automatically end at most 1 second after the last button was pressed.

Stimuli

provided by Millisecond Software - four gray boxes in the center of the screen

Stimuli Sizing
In this script, the response boxes are sized as follows:
The script uses the diagonal device size to categorize the device into one of four categories
(Phone, Tablet, Laptop, LargeMonitor).

All devices judged to be larger than a phone get absolutely sized response buttons with the
default sizes of 4cm. The empty space in between buttons is set to 2cm.
This ensures that response buttons and distances are the same size across most devices.

For "phone" devices, the response buttons are sized proportionally. By default, the buttons will
be sized to be 35% of the device's height and the empty space will be sized to be 15% of the
device's height.

Instructions

provided by Millisecond Software - can be edited in script 'bct_instruct_inc.iqjs'
The instructions are based on the published ones by Hernandez et al (2024)

Scoring

Fieldname
Details about how fieldName was calculated, relevant references, special considerations, etc

Summary Data

File Name: bct_summary*.iqdat

Data Fields

NameDescription
startDate Date the session was run
startTime Time the session was run
subjectId Participant ID
groupId Group number
sessionId Session number
inquisit.version Inquisit version number
computer.platform Device platform: win | mac |ios | android
computer.touch 0 = device has no touchscreen capabilities; 1 = device has touchscreen capabilities
computer.hasKeyboard 0 = no external keyboard detected; 1 = external keyboard detected
elapsedTime Session duration in ms
completed 0 = Test was not completed
1 = Test was completed
deviceHeightCM The cm-height of the current device
deviceWidthCM The cm-width of the current device
deviceSizeCM The cm-diagonale Size of the current device
deviceCategory Device category based on deviceSizeCM (not guaranteed but educated guess based on size)
smaller < 18cm => "phone"
smaller < 33cm => "tablet"
smaller < 46cm => "laptop"
anything bigger => "largeMonitor"
responseBoxSizeCM The size of the presented response boxes Size in cm
responseBoxDistanceCM The empty distance between response boxes in cm
for any device other than a "phone", the sizes are absolutely sized, so that distances etc are the same across monitors
for "phones", the sizes are proportional
Dv
durationMS The task duration (in ms), measured from onset of page until the LAST response box is clicked
logDurationMS The log-transformed task duration ( used the natural log transformation)
p1 Duration (in ms) from onset of page until the FIRST box is clicked
logP1 Log-transformation of time period 'p1'
p2 Duration (in ms) from clicking of FIRST box until the LAST box is clicked
logP2 Log-transformation of time period 'p2'
Counts
b1 Number of times response button b1 was pressed (upper left button)
b2 Number of times response button b2 was pressed (upper right button)
b3 Number of times response button b3 was pressed (lower left button)
b4 Number of times response button b4 was pressed (lower right button)

Raw Data

File Name: bct_raw*.iqdat

Data Fields

NameDescription
date Date the session was run
time Time the session was run
subject Participant ID
group Group number
session Session number
build Inquisit version number
computer.platform Device platform: win | mac |ios | android
computer.touch 0 = device has no touchscreen capabilities; 1 = device has touchscreen capabilities
computer.hasKeyboard 0 = no external keyboard detected; 1 = external keyboard detected
blockcode The name the current block (built-in Inquisit variable)
blocknum The number of the current block (built-in Inquisit variable)
trialcode The name of the currently recorded trial (built-in Inquisit variable)
trialnum The number of the currently recorded trial (built-in Inquisit variable)
trialnum is a built-in Inquisit variable; it counts all trials run
even those that do not store data to the data file.
response The response of participant (scancode of response button)
correct Correctness of response (1 = correct, 0 = error)
latency Response latency (in ms); measured from: onset of page
rtTimestamp The script.elapsedtime timestamp of the trial response (in ms)
Counts
b1 Number of times response button b1 was pressed (upper left button)
b2 Number of times response button b2 was pressed (upper right button)
b3 Number of times response button b3 was pressed (lower left button)
b4 Number of times response button b4 was pressed (lower right button)
stop 1 = stop criterium reached (all four boxes pressed); 0 = game continues

Parameters

The procedure can be adjusted by setting the following parameters.

NameDescriptionDefault
Sizing Parameters (For Devices Larger Than Phones)
responseBoxHeightCM Height and width of the responses in cm4
responseBoxDistanceCM Empty space between response boxes in cm2