Exam time zones: one exam, four campuses, three time zones, one record
Exam time zones from the institution's side: a local window and parallel form per campus, a live dashboard on exam day, and every change logged.
Exam time zones exist because one exam cannot start at the same moment everywhere without someone sitting it in the middle of the night, so each group of candidates gets a local start time — and often its own version of the paper. Running your own exam that way is configuration, not improvisation. Picture one midterm, four campuses, three time zones: the numbers are illustrative, the shape of the day is not. Here it is end to end on NUADU, for the exam officer who delivers it and the programme director who answers for it.
Why do exam time zones exist?
Exams run in time zones because a single global start would put some candidates in the hall at dawn and others at midnight. Large sessions therefore group centres into zones with local start times, and because those zones sit hours apart, each one often gets a different version of the paper, so that questions seen early cannot travel to candidates who sit later.
That is two decisions, not one: when each group sits, and what each group sits. An institution running its own exam across campuses has to make both, and has to be able to show afterwards how it made them. The rest of this post follows one illustrative day through both decisions and into the record.
How do you run one exam across time zones?
You run one exam across time zones by giving each site its own cohort, its own local window and, where the stakes justify it, its own form — all configured before the day. On NUADU windows are time-zone-aware and can differ per cohort, so each campus's window is set for its own hours instead of being translated by hand from head office.
For the illustrative midterm that means four cohorts, one per campus, each with its own reminders — email and in-app, localised, on a cadence configured per cohort and sent automatically. The settings sit under exam scheduling on NUADU, and most of them are ordinary pre-exam work — rules, notifications, the route in — covered in how to administer an online exam. In multi-site testing the sites often differ in room type, so it helps that access settings can differ per cohort as well: IP and device restrictions where required for a campus sitting in a supervised computer room, none for one sitting on the devices students already own.
Two choices are specific to a day like this one:
- The paper. Each campus gets a parallel form rather than a reordered copy of one paper; how parallel test forms differ from a shuffled paper is a subject of its own.
- The integrity layer. The defaults are an identity check at exam start and the lockdown browser, and anything beyond them is an explicit choice per assessment — a separate decision from the clock, and the subject of which type of online proctoring an exam needs.
Configuration before. Monitoring during. One programme view after.
What does the exam officer see on the day?
The exam officer sees status, not inboxes. With three time zones, the exam day schedule is a sequence of local windows rather than one start time: the easternmost campus is writing while the others are still asleep, and by the time the westernmost campus opens, the first window may already have closed. The live participation dashboard follows all of it — who received, started and submitted, with per-learner status: who started, who finished, who hasn't opened the assessment.
Three things happen on our illustrative day. Each is a configuration action, not a crisis.
- On the first campus, a learner has not opened the assessment well into the window. A reminder has already gone out on the cadence set in advance, and the dashboard shows the status instead of leaving it to a guess.
- On the second campus, word of a learner's accommodation arrives once the window is already open. The exam officer accommodates the learner mid-session; how extra time follows the learner covers the accommodation itself.
- On the third campus, a fire alarm empties a hall. The exam officer extends that cohort's window, without disrupting candidates already in progress elsewhere.
Every one of those actions is logged. The adjustment and the record arrive together: the exam officer acts in real time, and the programme director can read afterwards what was done. Nor does the exam officer act alone. Live support during every exam session is part of the delivery, not a ticket raised afterwards — in the Certification path's words, the highest-stakes hour is not one you spend alone.
What happens after the windows close?
After the windows close, four sets of results become one programme view, and the record keeps the day. Each cohort's window closes in its own local time, and the late-submission policy set in advance decides what happens to anyone still writing, so nobody decides it under pressure. Marking starts, with your rubric applied across the cohort.
The programme director's half of the day is in Report, which gives two views of it: a programme view with cohort comparisons and accreditation-ready exports, and an institutional view with faculty- and site-level aggregates. The four campuses can be compared as cohorts — whether the same rubric criterion or standard landed differently on different sites — and individual signals go to a tutor, never onto a label. The exam results reporting page describes the three views.
When someone asks, a term later, why one campus's results look different, the answer is not a recollection. The configuration shows which cohort was given which form and which windows were set; the log shows what was extended or accommodated during the session. Four campuses is the illustration, not the limit. Scale, on the Assign page's own terms, does not require an operations team: 500,000+ users, the same configuration model as a single course.
Frequently asked questions
Do exams start at the same time in every time zone?
Not usually. Large sessions set local start times by zone, and on NUADU a window can be set per cohort and is time-zone-aware, so each site sits in its own local hours. What has to stay the same is the standard of the exam, which is why the question of the paper matters as much as the clock.
Are there multiple versions of an exam for different time zones?
Often, yes: zones that sit hours apart are commonly given different versions so that questions cannot travel ahead of the clock. On NUADU that is a per-assessment choice — item and option order randomised by default, or a parallel form per campus where the stakes justify it.
What should an exam contingency plan include?
An exam contingency plan sets out what happens when something disrupts a sitting: who decides, what may change, and how the change is recorded. For the platform's part, NUADU lets the exam officer pause, extend or accommodate without disrupting candidates already in progress, logs every operational action, and provides live support during every exam session. People, rooms and alternative arrangements stay in your own plan.