Remote examination integrity is created by coordinated controls before, during and after the administration. This note provides a lifecycle model and a practical set of operational indicators so organizations can monitor identity exceptions, technology interruptions, security events, accommodation delivery and proctor competence.
1. Remote examination integrity is a system
No single control — secure browser, webcam, ID check or proctor — establishes integrity by itself. A defensible remote-examination program links identity, environment, technology, proctoring, accommodations, incident response, privacy and vendor oversight into one monitored operating system.
2. Control lifecycle
Eligibility, identity proofing, authentication, device/system check, candidate rules, accommodation planning.
Session authentication, environment controls, proctor competence, secure delivery, breaks, interruptions and event logging.
Incident adjudication, evidence preservation, candidate due process, trend monitoring, vendor review and corrective action.
3. High-priority control areas
4. Suggested operational measure set
| Measure | Formula | Interpretation |
|---|---|---|
| Identity verification exception rate | Identity exceptions ÷ completed administrations × 1,000 | Tracks friction and possible identity-control weaknesses. |
| Technology interruption rate | Material technology interruptions ÷ completed administrations × 1,000 | Separates platform reliability from candidate performance. |
| Confirmed material security event rate | Confirmed material events ÷ completed administrations × 1,000 | Low-frequency but high-consequence indicator. |
| Accommodation delivery conformance | Administrations delivered as approved ÷ administrations requiring accommodation × 100 | Tests operational execution of approved accommodations. |
| Proctor competency currency | Authorized proctors current on required competency ÷ active authorized proctors × 100 | Workforce-control indicator. |
| Incident closure time | Median calendar days from incident opening to documented closure | Measures timeliness; severity should be stratified. |
These values form a worked calculation example. They demonstrate the metric definitions and do not represent reported organizational performance or an empirical benchmark.
5. Escalation logic
Rate measures should not hide severe events. A single confirmed impersonation, major content exposure, systemic accommodation failure or significant vendor outage may warrant immediate investigation even if an annual rate appears low. Organizations should define severity-based escalation in addition to aggregate metrics.
6. Privacy and evidence retention
Remote-proctoring evidence can be highly sensitive. The organization should document the lawful/business basis for collection, minimize unnecessary data, define retention and access, protect recordings/logs, and make candidate-facing disclosures consistent with the actual workflow.
CHSPS references
Accreditation requirements are stated exclusively in the published, version-controlled CHSPS standards. This note explains method, risk and good practice; it creates no requirement and changes none.
- CHSPS Standards LibraryThe controlled Edition 2026.1 standards for all 16 active CHSPS program codes.
- CHSPS Standards InterpretationsFormal interpretations issued under document control when a requirement needs clarification.
- CHSPS Technical ReportsPublished CHSPS methods and analyses supporting evidence quality, assessment integrity and performance measurement.