When you’re gearing up for your next round of proctored exam deliveries, and a handful of students can’t use a webcam, how do you keep standards high and fairness intact?
Running a proctored exam without webcam can feel like walking a tightrope, but you’ve got options to secure identity checks and deter cheating.
By the end you’ll know exactly how to verify identity, design fair questions, and monitor performance without webcams.
Start by scanning your institution’s academic integrity rules. Make sure you know which devices (smartphones, tablets) and authentication methods are approved. Look for any clauses on remote checks, acceptable use of personal data, and accommodations for disabilities.
Outline the level of security your exam demands. High-stakes finals need stricter measures than weekly quizzes. Decide if you require full-screen lockdown software, keystroke analysis, or simple ID checks. Rank these features by importance and feasibility.
Ask students to upload a clear scan or photo of a government-issued ID. Provide specs on resolution, file type, and upload deadline. Use an encrypted portal or your LMS to protect personal data. You can verify details manually or leverage vendor tools.
Schedule a brief audio call before the exam window opens. Have students confirm their name, student ID, and read a random phrase aloud. Log the call time and notes for your records to build an audit trail.
Include a few short prompts that only the registered student can answer. Cover topics like previous assignment details or course policies. Rotate questions across sessions to keep things fresh without adding tech overhead.
Use software that restricts website access, copying, and file downloads. Look for platforms that work without a camera but still require full-screen mode or block new tabs. Test your chosen tool before exam day to avoid surprises.
Offer a 12–24-hour window instead of a strict start time. It eases tech hiccups and reduces stress. Track login times in your LMS to spot any odd patterns.
Build question banks and pull random sets for each student. This mix-and-match style makes sharing answers much harder. Label and categorize questions to simplify future updates.
Switch from recall-based questions to application or problem-solving prompts. These require critical thinking and can’t easily be googled. You’ll get deeper insights into each student’s understanding.
Send a detailed email with requirements, deadlines, and step-by-step login directions. Include links to system checks, document upload portals, and any scheduled audio calls. Remind students to test their mic and internet ahead of time.
List contact details for your IT help desk or support team. Set office hours for exam-day troubleshooting. Consider hosting a quick Q&A session a few days before the test to address last-minute questions.
Mid-exam, ping students via chat or a quick audio call. Ask them to confirm their status and ID details again. It’s like a surprise roll call that helps deter off-task behavior.
Review access logs for unusual patterns, such as rapid question changes or multiple IP addresses. Use vendor reports on time per question or backtracking. Highlight anomalies that fall outside expected norms.
Check timestamps, browser logs, and file metadata for signs of tampering. Archive these records in case you need to investigate later.
Compile any flagged issues—ID mismatches, suspicious logs, audio irregularities. Consult your academic integrity office if patterns emerge. Update your policy and verification mix based on these insights.
Send a short survey about the clarity of instructions, tech hurdles, and overall experience. Mix rating-scale and open-ended questions. Students will appreciate being heard and you’ll spot areas to improve.
Try one tweak next time you set up a camera-free exam, like adding an ID upload step or randomized questions.
