Skip to content

Suggested

Language: English. French, Portuguese and Arabic are in preparation.

Discuss your project

The person who earned the result should be provable.

Fixiam connects registration, exam access and result evidence to the same verified person without requiring you to replace the assessment engine, question bank or scoring system.
Exam centre check-in
Sitting ·B

Candidate ·0412

Registered identity on file

Registration identityBound at enrolment
Authentication at check-inSame person
Exception pathAssisted review available
EvidenceRetained with the sitting

Illustrative interface · masked data

Register → Authenticate → Sit → Record → Credential.

  1. 01

    Register

    Identity bound at enrolment

    !Risk entry pointControl point
  2. 02

    Authenticate

    Same person at check-in

    !Risk entry pointControl point
  3. 03

    Sit

    The assessment itself

    !Risk entry point
  4. 04

    Record

    Evidence retained with the sitting

    Control point
  5. 05

    Credential

    Result tied to the verified person

    Control point
!Impersonation entry pointIdentity re-established
Exception paths remain human-operable; the goal is assurance, not candidate exclusion.

What the pilot should prove.

  • Enrolment completion
  • Authentication success
  • Exception/manual-review rate
  • Impersonation or mismatch events
  • Impact on check-in time
  • Evidence retained with the sitting
  • Centre operating behaviour

What if biometrics fail?

Every pilot must define an exception and assisted-review path so an identity-control failure does not automatically become an unfair candidate outcome. Exact fallback design is programme-specific.