How to Use

FCE is baseline-relative. It compares your current performance to your own usual range. This page describes the basic workflow.

“Build baseline first. Use Check later. Read history, not just one result.”
Baseline Check Training History-first Retest when needed
Open instrument

Before you begin

  • Use the same device and input method for baseline and checks.
  • Try to test in reasonably similar conditions.
  • If you are new to the tasks, use Training first.

If you want the logic behind FCE, read Concept, What FCE Measures, and Scope & Limits.

Step 1 — Build baseline

Start by creating a personal reference range.

  • Run Baseline sessions under normal conditions.
  • Aim for 3–5 usable sessions per test type.
  • If a session is marked Not usable, do not count it. Repeat later.

Baseline is not your best score. It is your usual range.

Step 2 — Use Check for comparison

After baseline exists, use Check when you want to compare today’s performance to your normal range.

  • Run the task in Check mode.
  • Read the result together with your history.
  • Do not treat one session as final on its own.

Step 3 — Use Training to practice

Training is for familiarization and practice.

  • Training does not update baseline.
  • Use it when learning a task.
  • Use it again if you have not used FCE for a while.

How to read results safely

  • Prefer patterns over one-off sessions.
  • Use History to see whether a result is isolated or repeated.
  • Respect Not usable when it appears.
  • Do not infer cause from deviation alone.

When to retest

  • if you were interrupted
  • if you clicked too early
  • if the result looks inconsistent with the session quality
  • if the session was marked Not usable

Retesting is normal. The goal is a cleaner signal, not forcing an output.

Where to go next

For task-by-task explanation, continue to:

How the tests work FAQ