Online exam administration: four decisions before exam day
Online exam administration comes down to four decisions — who sits, under which rules, on which paper, by which route — configured once, before exam day.
Online exam administration is the set of decisions an exam officer makes before anyone sits the exam: who sits it, under which rules, on which version of the paper and by which route. When exam day goes wrong, the cause is often one of those decisions made late, made by hand or not made at all. This guide takes the four decisions in order, with NUADU's Assign pillar as the worked example. The one thing to remember: a decision written into configuration once is applied to every candidate in the cohort, and the record shows it.
How do you administer an online exam?
You administer an online exam by settling four questions before the window opens and writing each answer into configuration rather than into an email thread. Whether your institution calls it online exam administration or online test administration, the questions are the same:
- Who sits it — the cohort, imported or built by hand.
- Under which rules — window, duration, access, attempts, retakes, late work.
- On which paper — randomised order or a parallel form.
- By which route — the device, the notifications, the reminders.
The order is not arbitrary. The Assign page names three failures exam officers have lived through: "a learner with an accommodation who didn't get the extra time, a cohort that got the wrong variant, a candidate who was locked out of an exam window". None of them is an integrity problem or a marking problem. Map them onto the list and each is a step left until the morning: the missing extra time and the locked-out candidate are rules, the wrong variant is the paper. The page draws the conclusion this guide is built on: "Reliable delivery should not require an operations team. It should be configuration."
Time windows, cohorts, variants, accommodations. Boring on purpose.
Who sits the exam, and under which rules?
The cohort comes first, because every rule attaches to it. On NUADU a cohort can be individuals, classes, cohorts or whole programmes. It can be imported from your LMS, SIS or HRIS via LTI, API or SSO, built manually where a list is all there is, and targeted by region and department. Assignments appear where learners already work.
The rules come next: time windows, duration, access controls, attempt rules and late-submission policies. Cohorts do not have to share them — different windows, attempt rules and access settings can be set per cohort, so a distance-learning cohort and a campus cohort can sit the same assessment under rules that suit each. Windows are time-zone-aware, and IP and device restrictions are available where required. The full rule set sits under exam scheduling and access control on NUADU.
Three rules cause many of the arguments at the door, so write them down first:
- Attempts: how many a candidate may have.
- Retakes: whether one is allowed under your policy, and the cooldown before it.
- Late work: what happens to a submission still open when the window closes.
Each is a policy the programme already has. NUADU does not supply the policy; it applies yours. Retakes follow your policy, with cooldowns, and the late-submission rule is fixed before the window opens rather than argued over after it closes. A rule held in configuration is applied to every candidate in the cohort. A rule held in an email thread is the one that goes wrong on the day.
Accommodations belong to this step as well. They are applied automatically per learner, which makes the extra time part of the setup rather than something a colleague has to remember — extra time accommodations that follow the learner sets out how.
Which paper, and by which route?
Choose the variant before the window opens. Randomised item and option order is the default and suits lower stakes; for higher stakes, parallel forms are drawn from item banking with calibration statistics, with equating logic to keep difficulty comparable across forms. Because the choice is configurable per assessment, a weekly quiz and a certification sitting do not carry the same machinery. Different forms can go to different cohorts where appropriate, and the reason a reordered paper and an equated form are different things is set out in parallel forms, which are not shuffled questions.
The route in is deliberately plain. Delivery is browser-based, with no installation, on the devices students already own. Notifications go out by email and in-app, localised, with reminder cadences configurable per cohort, and reminders then go out automatically. A corporate compliance rollout, to take one of the site's illustrative cases, might pair localised notifications with time-zone-aware deadlines and participation status visible to people-managers.
The same four decisions hold at the other end of the scale. The site's illustrative national certification exam runs at the scale of the session plan, across multiple centres, with identity verification at exam start and a full audit trail for candidate due process — heavier settings, not a different method.
What happens inside the session is a separate set of choices. Identity verification at exam start and the lockdown browser are the defaults; every further integrity layer is an explicit choice per assessment. Those belong to exam delivery and invigilation, not to administration. Administration has done its job when the right candidate reaches the right session with the right rules applied.
Where does online exam administration end?
Online exam administration ends where monitoring begins: once the window opens, the exam officer watches and adjusts rather than configures. The live participation dashboard shows who received, started and submitted the assessment, with per-learner status, and the exam officer can pause, extend or accommodate mid-session without disrupting anyone already writing. Live support is there during every exam session.
Every operational action is logged, and the choices made beforehand are on record in the configuration itself, because each one was configured rather than improvised. That record is not a separate file: Assign shares the same rubric, the same framework and the same audit trail as the rest of the lifecycle, from authoring to certification. How a single exam day plays out across several campuses — local windows, a form per site, adjustments on the record — is the subject of exam time zones.
Frequently asked questions
What is an exam window?
An exam window is the period in which candidates can start and submit an assessment; the duration is how long each candidate has once they start. On NUADU each cohort can have its own window, windows are time-zone-aware, and the late-submission policy decides what happens at the close. A programme might run a weekly quiz that auto-submits at 3:15 PM, with marking beginning as soon as the window closes.
What is a test retake policy?
A test retake policy says whether a candidate may sit an exam again, how many attempts are allowed and how long they must wait in between; in British usage it is often called an exam resit policy. The platform should apply the policy, not invent one. On NUADU retakes are allowed per your policy, with cooldowns, and attempt rules can differ per cohort where the programme needs them to.
How do you set up an online exam?
Set it up in the order above — cohort, rules, paper, route — and check the configuration against your current exam-day checklist, because much of that checklist is configuration. On NUADU a single module goes live in max 2 days; a first full deployment takes 2–3 weeks and depends on integration with your LMS, SSO and learner records.