Every exam failure has a paper trail — a setting that was not confirmed, a link that went out late, an integrity control that was left off. This online exam checklist is designed to be run before every live session, no matter how many times you have run exams on the same platform. Think of it as a pre-flight. Pilots with thousands of hours still use checklists because the cost of skipping one step is too high. For institute administrators and HR coordinators running exams that affect grades, placements, and certifications, the same logic applies. Use this checklist as a template, adapt it to your workflow, and save it somewhere your whole team can access.
When exam administration relies on one person remembering the correct settings, one sick day or one new team member creates risk. A written checklist transfers knowledge from an individual into a process. It also makes auditing possible: if something goes wrong, you can look at the checklist and see which step was done or skipped. For schools and institutes running exams across multiple subjects and departments, a shared checklist reduces configuration inconsistencies between coordinators.
Check the attempt count in the admin panel within the first five minutes of the window opening. If attempt count is significantly lower than expected, the link may have an issue or the invite may not have reached all candidates. Respond to technical issues within five minutes during the live window — most issues are login or browser compatibility problems that resolve quickly with guidance.
Even with a thorough checklist, things go wrong. The key is having a response tree ready before the exam, not improvising under pressure. The three most common failure scenarios: the candidate link does not work for a subset of candidates (check if the link was changed after sending; re-send from the dashboard), the platform is unresponsive mid-exam (switch to WhatsApp for candidate communication and document the incident for the vendor), or a candidate submits but does not see their score (check the admin panel — the submission may have registered even if the candidate's UI did not refresh).
Keep a short incident response card alongside this checklist. It should have: the vendor support number and SLA for live exam emergencies, the escalation path in your own organisation (who decides whether to postpone or proceed), and the template for communicating a delay or incident to candidates. A calm, factual message sent within ten minutes of a problem being identified is far better than silence for thirty minutes.
For exams that repeat on a schedule — monthly compliance checks, weekly quizzes, quarterly assessments — add two steps to the start of the planning checklist. First: review the question bank and retire any item flagged from the previous cycle. Second: confirm that the invite list reflects the current cohort, not a stale roster from last term. Both steps take under ten minutes but prevent the most common recurring errors.
A five-question formative quiz does not need the same checklist depth as a semester final. For quick formative checks, use a shortened version: confirm the question set, enable shuffle, share the link. For high-stakes exams, run the full checklist. For hiring screens, add candidate batch verification and a score export format check for the HR system.
Keep the checklist in a shared document that every exam coordinator can access. Version-control it — when your process changes, update the document so everyone runs the current version. Add a "last updated by" and date field so it is clear whose changes are current. A Google Doc, Notion page, or even a printed laminated sheet works. The format matters less than the habit of using it.
