Most university exam software evaluations go wrong the same way. The demo looks fine, the contract gets signed, and the problems arrive at scale: accommodations that need a workaround, an item bank you cannot export, and statistics nobody can explain to an appeals panel. This guide covers the seven things that actually differ between systems, and how to test each one before you sign.
Start with the things that are expensive to fix later. Feature checklists are cheap. Migration, accessibility and defensibility are not.
- Exam integrity is a policy choice, not a feature score.
- Item-bank portability decides whether your next procurement is free or captive.
- Accommodations must be a workflow, not a support ticket.
- Statistics must be named, not implied.
- Integration cost usually exceeds licence cost in year one.