Reliability
Exams don't wait for IT.
Things go wrong on exam mornings. Choose a problem to see what the candidate sees and what your staff do.
Pick your problem
The candidate keeps typing.
- Straight away. Their work keeps saving to the laptop, encrypted, about once a minute.
- While it's down. The exam stays open, with nothing for the candidate to do.
- When it's back. Unsent work goes up to the server automatically.
Exams can still start.
- Beforehand. Laptops keep an encrypted offline pack, including papers for the week ahead.
- On the day. A member of staff enters the emergency admin code, then the candidate's number.
- If a paper's missing. The laptop says so plainly, so they can use a printed copy.
Live exams reopen by themselves.
- Immediately. The launcher notices and covers the screen, so the desktop isn't left exposed.
- Seconds later. The exam reopens with the candidate's work, and the event is logged.
- Repeated crashes. After five reopens, it stops trying and a person takes over.
A hang is treated like a crash.
- After 15 seconds. If Windows reports the live exam window has stopped responding, it's closed.
- Then. It reopens the same way as after a crash, with the work reloaded.
Move the candidate.
- On the new laptop. They type their number. It says the code is in use elsewhere and offers to ask for a move.
- Staff. Someone approves the move on the server.
- Their work. The last copy saved to the server opens. They may lose about a minute of typing. Rescue mode can pull unsent work from the old laptop if it starts again.
There's always a way out.
- Admin unlock. It's on the sign-in screen, whatever's typed there. The emergency admin code closes the app.
- Windows. Signing out through Ctrl+Alt+Del also ends the lock.
- Wrong codes. Repeated wrong codes make the next attempt wait.
Try it in your school.
We're looking for UK schools to run Arrangely alongside what they use today, starting with mock exams.