Invigilare.
YOUR ROLE, YOUR WORKFLOW

Invigilator guide

Check in candidates, supervise live exams, monitor recording health and record a considered human review.

What this role can do

Guides describe access; opening a guide does not grant a role. Use the current organisation and your individual account.

Sign in and accept your invitation

Each person uses their own invited email address. Support contact details do not change an account’s sign-in address.

  1. Open the sign-in page and enter the address invited to the organisation. Request your personal sign-in link.
  2. Open the newest email within 10 minutes, then choose Confirm sign-in. A link works once. Request a fresh link if it has expired or was already used.
  3. In Account & organisation, accept any pending organisation invitation. Open the workspace for your role. If you belong to several organisations, choose the intended one first.
  4. Never forward a sign-in link, share an account or paste its token into a support message. Sign out on shared computers. You can revoke other browser sessions from Account & organisation.

During the free pilot a new email recipient needs one-time Cloudflare delivery verification, arranged by the organiser. Check Spam, but do not assume an invitation or neutral sign-in response proves email delivery.

Read service policy and your training record

Invigilators can read the published policy and their own recorded training; an owner or administrator manages changes.

  1. Open Service & safeguards to read the published operating policy, recording retention and contacts.
  2. Check the training/briefing records shown for your membership. Ask an owner/admin to correct missing or expired evidence.
  3. Use the notice saved with each room. A later organisation policy update does not replace an existing room’s version.
  4. Ask an owner/admin to change modes, invitations, retention holds or policy publication; your invigilator role does not grant those controls.

Check in and supervise a candidate

Human and hybrid modes require an invigilator to admit the candidate.

  1. Open Session dashboard and the booked or assigned room. The candidate signs into their own account and opens the same booking. Ask them to use headphones and complete webcam, microphone, screen and connection checks.
  2. Wait for the recording notice and, for AI modes, separate AI acknowledgement to be accepted. Confirm both intended live feeds are visible. Use the agreed manual identity check; the pilot does not request an ID upload.
  3. In Invigilator controls, choose the agreed manual identity method and confirm identity. Save the environment, permitted-materials and instructions review; this is required for admission when enabled on the assessment. Then choose Admit & start cloud recording. Candidate devices begin capture after admission; check that both cloud uploads appear. The first segments normally arrive after about 20 seconds.
  4. Monitor live feeds and recording health. Use messages for communication and notes/incidents for objective observations. A tab switch or connection change alone does not establish misconduct.
  5. If a feed ends or recording fails, tell the candidate and follow the agreed pause/recovery/escalation procedure. Use Invigilator controls to pause with a reason during an interruption. The server clock stops and answers are locked; sharing and recording continue. Resume when ready. Leaving or refreshing alone never pauses the exam.
  6. End the session when appropriate or wait for submission/time expiry. Ask the candidate to keep their tab open until uploads finish, then review the cloud evidence.

The initial pilot allows one concurrent human/hybrid exam per assigned invigilator (unassigned legacy rooms reserve the organisation’s shared capacity) and one candidate per human slot. A role does not prove training or exam-body approval; complete the actual briefing first.

Mark answers and preserve context

Assessment scoring and proctoring observations are separate.

  1. After completion, open Results & reports and search for the candidate, assessment or booking reference. Open the assessment report even after short-lived room access closes, while evidence remains retained. Choice answers are scored against the saved answer key; enter marks for written questions within their available points.
  2. Save objective notes about irregularities, technical issues and the candidate’s explanation. Do not treat an AI code or tab switch as an automatic failure.
  3. Use Results & reports for section/question scores, approximate foreground question timings, actor-attributed checks and the audit trail. Export filtered CSV or print an individual report to PDF. Open its recordings/evidence link for human review. Room access has a shorter window; cloud evidence follows the snapshotted retention policy.
  4. Escalate a needed retention hold or deletion to an owner/admin before evidence expires. Do not store uncontrolled copies on a personal device.

Find participants and review results

Results and proctoring evidence serve different purposes. A low score or a system observation alone is not a misconduct finding.

  1. Open Results & reports to search by candidate, assessment or booking reference, then filter by assessment, operational status or human review outcome. Disconnected means no recent heartbeat, not a confirmed withdrawal.
  2. Open a report for overall/section marks, selected and correct choice answers, written marking, manual identity method and pre-exam checks. Approximate question timings exclude hidden tabs, pauses and gaps over 20 seconds; older sessions have no backfilled timing.
  3. Save written marks within each question’s available marks. Changes record the reviewer in the chronological audit trail. Marks remain separate from the evidence-review outcome.
  4. Use Invigilator controls → Stop an assessment with a reason when an exam cannot continue. Its stopped status has no automatic pass/fail result. Pause is for a session expected to resume.
  5. Use the report link to open cloud recordings and review contextual evidence. Retention expiry and deletion apply to reports too; documented holds preserve access.
  6. Export the filtered participant list to CSV or print an individual assessment report to PDF. These downloaded copies need the organisation’s own access and deletion controls.

Work through the review queue

AI-assisted recorded exams require an accountable human reviewer. Agree who supplies the reviewer before each pilot. The same workflow can support recruitment skills exercises, education and training; observations never rank applicants or decide whether to hire.

  1. Open Review queue. Filter by candidate/exam, mode, state or Assigned to me. The queue prioritises changed evidence, follow-up and retention deadlines, with 25 sessions per page. Follow-up outcomes remain in Needs attention until reopened and resolved.
  2. Open a session and choose Take this review. Owners/administrators can assign a current staff reviewer. One account owns saved changes; other staff can inspect the evidence. Release ownership for a handover. Refresh before retrying a concurrent-change warning; unsaved notes stay on screen.
  3. Check the exam window and both recording coverage bars. Green is clip metadata, amber marks gaps over two seconds; it does not prove actual playback is complete. Open the footage and inspect partial clips, recording errors and missing intervals. AI sampling coverage is separate and approximate.
  4. Use the linked player to navigate webcam/microphone and screen on the same exam timeline. Play both, change speed or jump from a worklist timestamp or gap. Synchronisation uses approximate recording timestamps. Restarts appear as separate clips under All recordings; gaps do not become playable footage.
  5. Review every grouped observation, analysis error and flagged activity item. Nearby samples of the same kind form an episode; they do not show continuous behaviour. Inspect the samples and surrounding recordings, then choose Explained / permitted, Needs follow-up or Unable to resolve, with meaningful notes. A changed episode needs a new resolution.
  6. Start the review timer to measure approximate focused review effort. Timing pauses on tab/window inactivity, excludes long heartbeat gaps and uses a single token across tabs. Resume when you return. Saved time is operational evidence, not proof of attention or a payroll record.
  7. Read the agreed instructions, rules, accommodations and available candidate explanation. Save a draft if needed. Complete review only after the exam ends, uploads/analysis finish and every worklist item has a resolution; confirm coverage and context and record final notes. Incomplete footage cannot receive No concern identified by reviewer.
  8. Choose a human outcome: No concern identified by reviewer, Follow-up needed or Insufficient evidence. This does not change marks, establish misconduct or make an employment decision. Reopen with a reason when more review is needed. New evidence automatically marks a previous outcome as requiring review again, including in Results & reports.
  9. Export review evidence for a dated JSON snapshot containing current coverage, resolutions and the latest 100 review-history changes. Owners/administrators can also assemble the analysis/usage report. Videos are separate authorised downloads. Reports may become stale when new evidence arrives.

Cloud evidence and review notes follow the session retention policy, including holds and deletion. Downloaded copies require separate approved storage. Current AI uses intermittent images, can be wrong or absent, and does not analyse audio, verify identity, infer intent or replace a human decision. Recruitment pilots should use adult volunteers and practice material, not live hiring decisions, until the client has accepted the process.

Resolve common problems

Keep the session or upload tab open while investigating a problem.

  1. No sign-in email: check the invited address, Spam and the newest message. Ask the organiser about one-time recipient verification; avoid repeatedly requesting links because requests are rate-limited.
  2. Camera or microphone blocked: check the browser’s site permissions and operating-system privacy settings; close other apps using the device. Use HTTPS and current desktop Chrome or Edge.
  3. Screen share stopped: select Share screen again, confirm the preview and tell the invigilator. A capture interruption needs review even if sharing resumes.
  4. Live feeds cannot connect: retry Connect / retry with the invigilator. Restrictive networks may block the current peer connection. Cloud upload is separate; a live human exam should not begin without the required live feeds.
  5. Upload error: keep the candidate tab open and reconnect. Use Recover / retry recording in the room or Recover uploads on the candidate workspace. Do not clear site data or start another recording while previous segments need recovery.
  6. Access changed or session expired: sign in again using the right organisation and role. Do not use another person’s room link. Contact support if you were removed or the room has expired.

For the Kennedy Advisory pilot, contact michael@kennedyadvisory.co. Include the booking reference or session ID, time, browser and error text. Do not email identity documents, passwords, sign-in tokens or recordings unless an authorised secure handover has been agreed.