PRACXASecurity begins before the start button
Communicate permitted materials, device requirements and recovery rules in advance. A system check reduces avoidable exam-day failures.
Use controls proportionately
Choose browser, camera, screen and evidence options based on the risk of the assessment. Browser controls cannot prevent every off-device action.
Review events in context
Treat alerts as signals for review, not automatic proof. Keep an audit trail and give authorised staff a consistent review workflow.
Assign clear exam-day responsibilities
Name the people responsible for candidate support, live monitoring, recovery and security review. Give each role only the access it needs. A documented escalation path keeps assistance consistent when several candidates report problems.
Protect evidence throughout its lifecycle
Record why evidence is collected, who may review it, when downloads are allowed and when records are removed. Store decisions separately from raw observations. A security event is a signal requiring context, not an automatic verdict.
Close the operation deliberately
Resolve interrupted attempts, complete authorised reviews and confirm result-release rules. Capture lessons about instructions, device checks and support volume. Use those findings to improve the next exam instead of adding controls without evidence that they help.
Continue with Pracxa online exam software, explore platform features, or compare plans and credits.