Incident Reporting, Documentation, and Escalation
This domain tests incident reporting, documentation, and escalation: turning an event into a clear, timely, factual record that reaches the right decision-maker without contaminating evidence or privacy.
Core rules
- Report promptly under the sponsor's timeline. Late reports weaken the record even when the underlying event was handled well.
- Write objectively: who, what, when, where, how, and what was said or observed. Quote exact words when relevant; avoid labels such as “cheater” or “difficult.”
- Separate observation from inference. “Candidate looked at neighbor's screen three times” is observable; “candidate intended to cheat” is a conclusion.
- Preserve evidence: device, notes, CCTV segment, system logs, seating chart. Log every transfer.
- Escalate by severity and role: center manager, test sponsor, security, or compliance. Share only with those who need to know.
Worked example
A candidate reports that another candidate is looking at her screen. The proctor sees the second candidate's head turn but not the screen content. The report should state the observation, time, seating positions, action taken, and video preservation-not “confirmed cheating.” Escalation follows the sponsor's irregularity process. Reasoning: the reviewer needs facts sufficient to judge, not a verdict from the proctor.
Traps that cost marks
- Subjective language and speculation.
- Editing a submitted report without an addendum.
- Delaying escalation to “see if it resolves.”
- Discussing candidate details in public areas or on social media.