This page describes the creator's design intent and values; it does not describe system behavior or provide instructions for use.

Norwegian Context

This page frames where FCE (Functional Cognition & Execution) could fit in Norwegian settings without overclaiming what it is. It is written for institutional readers.

“Measure functional performance directly. Keep interpretation human-led.”
Baseline-relative Function-first Offline-first Local-only by default Refusal protects Human interpretation
Open instrument

Recommended reading order

This page assumes the core concept and boundaries are already understood. If you are new to FCE:

  • Concept — what FCE is and why baseline-relative measurement matters
  • Scope & Limits — explicit non-goals and non-negotiable safeguards
  • How to Use — baseline, checks, and safe interpretation

Non-negotiable boundaries

If FCE is ever explored in an institutional setting, these boundaries must remain explicit. They protect people, and they protect the instrument from misuse.

  • Not diagnostic — no clinical labels, no medical conclusions
  • Not a legal verdict — no enforcement outputs, no guilt/innocence framing
  • Not substance detection — it measures function, not causes
  • Not automated decision-making — results require human interpretation
  • Not single-session determinism — trends and context matter more than one-off sessions

For a full statement suitable for referencing in policies, see Scope & Limits.

What “function-first” means in practice

In many Norwegian contexts, decisions must be made under uncertainty: safety-critical work, rehabilitation, and discussions about functional readiness.

FCE is designed as a function signal: it indicates whether a person’s performance deviates from their baseline — without stating why.

Sleep loss, stress, illness, medication effects, distraction, alcohol, cannabis — FCE does not label causes. It measures whether deviation exists under the tested conditions.

1) Traffic safety: functional readiness as a complementary lens

Traffic safety decisions often require separating:

  • Detectability (something can be present without indicating current functional impact)
  • Functional risk (reaction time, attention stability, errors, inhibition under time pressure)

FCE is not a replacement for legal standards or enforcement processes. It is a structured way to discuss functional readiness using baseline-relative performance and history. A simplified visual explanation of baseline-relative measurement is available here.

2) Workplace safety: readiness for safety-critical roles

Many roles depend on stable execution: transport, construction, logistics, healthcare, and industrial work. A baseline-relative tool can support questions such as:

  • “Am I stable enough for a safety-critical shift today?”
  • “Is my performance noticeably reduced compared to my normal range?”
  • “Is there a trend in my performance over weeks?”

This framing focuses on observable performance and repeatable measurement, not inferred causes.

3) NAV / arbeidsevne: functional documentation without labels

Work capacity discussions can become locked into categories: diagnosis vs not-diagnosis, “sick” vs “not sick”. FCE can provide a complementary data layer:

  • Track functional performance over time during rehabilitation
  • Support graded return-to-work planning with repeatable measures
  • Document stability/variability under consistent testing conditions
  • Support dialogue about job demands (high-focus vs low-focus execution)

Boundary: FCE does not diagnose and must not be used as an automated gatekeeper.

Responsible exploration (pilot framing)

If FCE is ever explored in pilots, a cautious approach reduces misuse risk:

  • Voluntary participation with clear consent
  • Device consistency (baseline and checks on the same device/input method)
  • Minimum baseline before interpretation
  • History-first interpretation (trend > one-off)
  • Clear refusal rules (low-quality data should not be forced into decisions)
  • Independent review of claims, thresholds, and error rates

The goal of a pilot is to test validity, reliability, usability, and human impact — not to produce automatic decisions.

Privacy and data ownership

FCE is designed to work offline and store session history locally by default. Any institutional layer should remain explicit and separable from the instrument.

  • No accounts
  • No tracking
  • No server upload by default
  • Manual export (optional, user-initiated)

Trust and legitimacy depend on transparency and clear boundaries.