Remote Exam Recovery
Design a fair recovery flow for a remotely proctored exam interrupted by a network or device failure.
The brief
Understand the problem
Background
Remote exams can fail because of bandwidth, camera, power, or proctor connection issues. Students need reassurance and evidence capture, while institutions need exam integrity without treating technical failure as misconduct.
User context
Nabila loses network access twenty minutes into a timed certification exam. Her answers are locally saved, and she needs to know whether the timer stopped and how to contact the proctor from her phone.
Product problem
Recovery must preserve work, timing, privacy, and a reviewable record without granting an unfair extension or forcing the student to restart blindly.
Objective
Design interruption detection, secure resume, alternate contact, and post-exam incident review for a remote assessment.
What to design
Define the experience
Required experience
- Recognize the failure and saved-work status
- Follow offline recovery guidance
- Reconnect to the same attempt or contact a proctor
- Review the incident record and resulting exam status
Screens and states
- Exam interruption
- Offline recovery
- Secure re-entry
- Incident outcome
Core user flow
Follow the critical path
- 01
Nabila's connection drops and the exam confirms local save time
- 02
The interface shows that the timer is paused under policy
- 03
She reconnects, verifies identity with the approved method, and resumes
- 04
After submission she sees the interruption record and review timeline
Product rules
Requirements and constraints
Requirements
- Preserve encrypted answers and expose the last confirmed save
- State timer behavior and permitted recovery steps before the exam
- Offer an accessible secondary contact route
- Separate technical incident review from misconduct review
Constraints
- Recovery cannot silently increase exam access or duration
- Monitoring data collection must follow disclosed limits
- Accommodation settings must survive reconnection
Reality check
States worth considering
Finish line
What to deliver
- Four desktop screens plus a state diagram for pause, reconnect, and manual review
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Yeseva One & Merriweather
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Yeseva One & Merriweather
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
