The delivery section ends with a run-sheet, a contingency register, and a security procedure. StudyDrome Exam Manager gives the coordinator three things to run them with. It builds the exam-day pack from the published exam in one pass. It computes every slot time using a single timing model. And it shows a manager the live state of every examiner's station session, with the power to reopen one that was closed too early.
The product page OSCE exam-day documents cover the pack and its guarantee. The wider OSCE model is on OSCE exams in StudyDrome. This page connects the section's decisions to what the exam office and the manager see.
The exam-day pack
The run-sheet counts stations, candidates and examiners against lists. In StudyDrome, those lists come from one reading of the published exam. The manager opens the Exam Documents row action for the exam. There are eight document types: Station List, Candidate List, Examiner List, Examiner Checklists, Doorway Instructions, Rotation Timetable, and Simulated Patient and Observer instruction sheets when the exam has such staff. Every document numbers stations and candidates from the same roster. The doorway sheet and the timetable cannot disagree. The three list documents also export to a spreadsheet. Each document downloads separately, so the office prints for one role at a time.
The timing model
The circuit planning page needs one clock per lap. The exam wizard's Timing step holds it. It sets the station duration, the reading time before each station, and the waiting-room gap between stations. The gap is capped at 999 seconds. A slot is reading time plus station duration. The gap sits only between slots, so the final slot ends when the event window ends. Automatic timing needs a date and a start time on every event. With it off, the documents have no computed start times, and the office keeps its own clock.
The rotation timetable
The Rotation Timetable is a grid of station rotations, with slot times for each event. It models one circuit rotating forward. Candidates move one station per rotation. Examiners stay at their station. Each event has its own grid, so a morning and an afternoon session are two timetables from one exam. The model is one circuit per event. An office that runs parallel circuits keeps its own comparison of them, as the circuit planning page describes.
Warnings before printing
The pack does not come out silently broken. As the builder walks the exam, it collects warnings and returns them with the documents. There are four. The exam has no stations. An event has no date, so its start times cannot be computed. Two candidates share a start station in one event, so only the first is placed in the grid. Some candidates have no event or start station, so they are excluded from the checklists and the timetable. Each warning names the event or the count. The warnings arrive with the pack and do not block it. The office reads them before printing. That is what the go/no-go check is for.
Events on the calendar
Publishing an OSCE places each dated event on the account calendar as a system-managed entry. With automatic timing on, the entry spans the computed window. Otherwise it is an all-day entry on the event's date. Publishing again updates the entries rather than duplicating them. Archiving the exam removes them. Examiners see their own work in the examiner app's Exams list: the exam, its stations and rest stations, each event's date, and their allocation. Until one is set, the list says "Not allocated".
Live monitoring
On the day, the manager opens the exam's row action OSCE Stations. The modal lists every examiner's station session for the active publication. Each has one of four states: Not Started, Active, Paused or Completed. That is the contingency register's view of the circuit. It shows which stations are scoring, which have not opened, and which examiner has finished. OSCE delivery has its own monitoring service, separate from the written-exam monitor. It tracks station sessions rather than answer counts.
A Paused state is something the manager sees. It reports that an examiner's session is paused. It is not a control the manager operates.
Reopening a session
The examiner app page states that an examiner cannot reopen a station once it has finished. The sanctioned recovery is here. A manager with the sessions permission chooses Reopen Station on a completed session and confirms. The confirmation says that the examiner will be able to resume grading all completed candidate assessments. Reopening restores every completed assessment in that session, not one candidate. The examiner then sees the station again and finishes it properly. The log gets the time and the reason from the coordinator, as the register requires.
What stays with people
The pack lists the circuit; the office walks it. The timetable computes the slots; the floor manager runs the bell. The monitor shows a session's state; the assessment lead decides what an incident means. A paper fallback pack still sits sealed at every station, and the marking page explains why. What StudyDrome adds is a single source for every list and a single screen for every session's state. The counts the run-sheet asks for become a glance rather than a pile.