How the tests work

Simple procedural instructions for each test type. What to do, what counts as an error, and how to practice.

Open instrument

What to do

Each test measures different aspects of functional execution. Follow the on-screen instructions, respond as quickly and accurately as you can, and avoid clicking before the signal appears.

Reaction Time

What it reflects: response initiation speed and consistency under simple conditions.

  • Wait for the green signal to appear
  • Click or tap as quickly as possible when you see it
  • Repeat for each trial

What counts as a false start: Clicking before the signal appears. False starts are recorded but don't affect your reaction time average.

Go / No-Go

What it reflects: inhibitory control and timing under decision pressure.

  • When you see GO (green), click or tap immediately
  • When you see NO-GO (red), do nothing — wait for the next trial
  • Most trials will be GO, but some will be NO-GO

What counts as an error: Clicking on NO-GO (false alarm) or missing a GO signal (miss). Both are recorded and affect your results.

Divided Attention

What it reflects: execution stability while attention is split between action and a secondary signal.

  • Do the Go / No-Go task (respond to GO, ignore NO-GO)
  • At the same time, count brief blue flashes that appear during trials
  • After the session, enter the number of flashes you counted

What counts as an error: Missing GO signals, clicking on NO-GO, or miscounting flashes. All are recorded.

Precision (Target Pointing)

What it reflects: motor execution accuracy and correction consistency across repeated trials.

  • Tap or click the target as accurately as possible when it appears
  • Error is measured as distance from the target center
  • Both average accuracy and consistency (spread) are evaluated

Best practice: Use fullscreen mode and maintain a stable posture for consistent results.

Practice first

If you're new to FCE or returning after a break, use Training mode first. Training runs the same tasks but doesn't update your baseline. Use it to get familiar with the tasks before building a baseline or running checks.