How exams work
Exams are on the Pro plan. Attendance and coursework are on every plan.
An exam is an assessment that students sit inside Quorum, on their own devices, against a timer.
Exams are for owners only. A TA can create the quiz or midterm as coursework, but cannot open its exam setup, write its questions or review its attempts — they are told Only owners can manage exams.
Assessment → Exam config → Questions → Publish → Attempts → Scores
The four stages
1. An assessment. Exams are not a separate object. You create an assessment as normal — title, type, max score — and then turn on its exam. The type must be Quiz, Midterm or Final Exam; only those rows have Exam Setup.
2. Configuration. When students may enter, how long they get, how many attempts, whether a code is needed at the door, and which integrity rules apply. See Set up an exam.
3. Questions. Multiple choice and true/false, each worth points. See Write questions.
4. Attempts. A student opens the link, identifies themselves, and works through the questions until they submit or time runs out. Marking is automatic.
Enabled and published are different
Two separate switches, and both must be on before a student can sit anything:
| Means | |
|---|---|
| Enabled | The exam exists and access checks apply |
| Published | Students can actually see it |
Students will not see the exam until it is published. This is what lets you build the whole thing — questions, timing, rules — in the open without anyone stumbling into a half-finished paper.
Everything marks itself
Both question types are objective, so Quorum scores every attempt on submission. There is no marking queue to work through and no written answers to read.
That has a design consequence worth taking seriously: an exam can only ask what a multiple-choice or true/false question can ask. If your assessment needs prose, run it outside Quorum and record the mark as ordinary coursework.
How students are identified
By university ID, exactly as with attendance — not by logging in. Students have no accounts.
Each attempt gets its own access token, so a student's attempt is theirs and cannot be resumed by someone else with the same link.
Optionally you can require an access code as well, and require that the student attended the linked session. See Give students access.
What the scores become
An attempt produces a score against the assessment's max score, which is a coursework grade like any other. It flows into the breakdown through whichever category the assessment's kind belongs to, and appears in exports.
Whether students see their own score is a separate decision — see Release results.