Examination depth

Compare the whole examination process.

Some CBT systems focus primarily on creating questions, presenting a student paper and producing an objective score. Testify connects that student experience to the wider school operation.

A question-delivery focus

  1. Question creation
  2. Student examination
  3. Objective scoring

The Testify operations workflow

  1. Preparation
  2. Review and controlled publishing
  3. Student examination
  4. Live monitoring
  5. Autosave and recovery
  6. Theory marking
  7. Examination activity review
  8. Controlled result release

Five areas worth testing in every demo.

A serious comparison should test what happens on an ordinary exam day and what happens when a candidate, paper or result needs attention.

  1. 01

    A connected workflow

    Evaluate what happens from examination preparation through monitoring, marking and controlled result release.

  2. 02

    Security and access control

    Review student eligibility, centrally enforced timing, randomised papers, live monitoring, activity records and recovery of saved answers.

  3. 03

    Operational continuity

    Ask how saved answers recover after a refresh or brief interruption and what the school team can see during an examination.

  4. 04

    Human control

    Confirm who publishes examinations, approves official theory marks and decides when results become visible.

  5. 05

    A realistic deployment plan

    Assess the school server, local network, devices and backup power against the expected number of concurrent candidates.

Clear responsibility

Automation supports the school team.

Testify preserves deliberate approval, marking and release decisions instead of treating every step as an automatic system action.

Administrators govern the process

Trusted school staff manage structure and access, publish prepared examinations, review readiness and control result release.

Teachers remain responsible for academic work

Teachers prepare questions and award official theory marks. Assisted suggestions never replace their final decision.

Students receive a focused examination journey

Eligible students enter scheduled papers, work within centrally enforced timing and see results only when school settings allow.

ICT supports a school-operable environment

The school server, local network, devices, backup power and operating process are assessed before live use.

Monitoring and integrity context

See what needs attention without making automatic accusations.

Authorised staff can follow progress, timing and connection status. Configured activity such as tab changes or fullscreen exits can be recorded for review, but the school decides what the evidence means.

  • Questions and answer options can appear in a different order
  • Eligible students access scheduled examinations
  • The examination clock is enforced centrally
  • Staff can monitor and administrators can intervene when needed
  • Selected browser events create a review trail
Testify live monitoring showing examination progress, recorded events and evidence-review actions
Live monitoring and review context · demonstration records.
Testify result release queue showing readiness checks, review status and controlled release information
Results readiness and controlled release · demonstration records.

Theory and result governance

The workflow continues after objective scoring.

Objective answers can be scored at submission. Theory responses move to teachers for final marks, while administrators can hold work that is incomplete or needs review before releasing results.

  • Teachers retain control of every official theory score.
  • Extended can provide assisted suggestions for teacher review.
  • Administrators decide when appropriate results become visible.

Practical continuity

A refresh can return the student to the same attempt.

Testify restores answers already saved to the server and can retry recent unsent work held by that browser. It does not promise recovery of an answer that was never saved anywhere, so a school-specific network rehearsal remains important.

One in-progress attempt

A returning student resumes the existing active attempt instead of creating a duplicate.

Server-controlled timing

The official examination deadline does not depend on the student device clock.

Administrator intervention

Authorised administrators can pause, resume or extend time under the school’s approved process.

Run Testify on the school’s local examination infrastructure.

The student examination environment does not depend on the public internet during normal local operation. Capacity still depends on the server, network, devices and power available to the school.

Understand deployment

Questions to ask every CBT provider.

Test Testify against your current examination process.

Bring one representative paper and the questions your leadership, examination and ICT teams want answered.

Book a school demonstration