Candidates should arrive knowing everything except the station content. That means the format and the timing. The rules that decide a pass. How adjustments are requested. And what happens when something goes wrong. Publishing it is not a courtesy. A candidate who did not know a rule can argue it was applied unfairly. The file has to show otherwise.
Why unfamiliarity is a design problem
An OSCE tests clinical performance. A candidate who has never seen a circuit spends the first station learning the format instead. That is measurement error, and it falls hardest on people meeting the method for the first time.
The point is not hypothetical. A study of OSCE implementation in Tunisia surveyed 131 students and 33 educators across four specialties. It named student unfamiliarity with the format as one of three main barriers. The others were institutional tradition and educator capability. Its recommendation was to run formative OSCEs first, which is the subject of the mock and formative page.
Briefing is the cheap half of that fix. It cannot teach the skill, but it removes the surprise.
What the handbook contains
Publish this as one document, dated and versioned, and link it from wherever candidates look for exam information.
Two rows cause most disputes when they are missing. The pass rules are the first. Say a candidate learns only after failing that they also needed to pass nine stations. That is a real grievance. The conduct rules are the second, because misconduct decisions rest entirely on what the candidate was told.
The rules themselves come from the regulations and the conjunctive rules the committee already decided. This page is about publishing them, not choosing them.
How far ahead?
Three horizons work better than one deadline.
At the start of the year or module, publish four things. The format, the blueprint level, the assessment rules, and the adjustment process. This is the version candidates plan against, and the adjustment deadline depends on it.
Two to four weeks in advance, publish the practical details: dates, reporting time, venue, what to bring, dress code and equipment, and the identification you will ask for.
On the day, brief in person. The AMEE guide on OSCE organization treats this as one of three separate briefings. The others are for examiners and for simulated patients. Separate is the operative word. Candidates hear a different script from examiners, and running them together leaks.
What the exam-day briefing says
Keep it short, fixed, and delivered by the same person to every session. Five things and no more.
The sequence: where to wait, how the rotation works, what the signals mean, what happens at the end. The clock: reading time, station time, and that a bell or announcement ends the station, whatever is happening. The rules: no phones, no discussing stations with anyone until the whole cohort has finished, stay with your marshal. The exceptions: what to do if you feel unwell, if equipment fails, or if a station went wrong. Say plainly that raising it does not count against you. And the close: when results come, in what form, and where the feedback will be.
Write the script once and keep it with the run-sheet. A briefing that varies between morning and afternoon is a defect in the exam. The two cohorts were told different things.
What candidates must not be given
The line is between the format and the content. Everything about how the exam works is publishable. Anything that narrows the guess about what is in it is not.
That rules out the station list, the cases used, the checklists, and any previous stations still in the bank. It also rules out a count per domain, where the count effectively names the domain. Past candidates talking to future ones is a security matter. Quarantine and the bank's rotation cover it; a handbook cannot.
Two revision posts for candidates already sit on this site: preparing for OSCE exams and the exam itself. They are candidate-facing by design. Pointing students at general advice is safer than writing hints about your own stations.
Limits
A handbook does not make a process fair; it makes it knowable. Publish an unfair adjustment process clearly, and you have an unfair, well-documented process.
Publication also has to be traceable. Keep the dated version. An appeal a year later asks what candidates were told at the time, and a quietly edited page cannot answer that.
Frequently asked questions
What should an OSCE candidate handbook contain?
The format and timing, the blueprint at domain level, what is assessed at a station, how a pass is decided, including any minimum stations passed and must-pass rules, the adjustment process and its deadline, the conduct rules, what happens if something goes wrong, when results and feedback arrive, and the appeal grounds and deadline.
How far in advance should OSCE information be published?
In three stages. Format, blueprint level, pass rules, and the adjustment process at the start of the year. Practical details such as dates, reporting time, and venue should be communicated two to four weeks in advance. The spoken briefing on the day itself.
What can candidates be told about station content?
Nothing that narrows the guess. The blueprint at the domain level is publishable; the station list, the cases, the checklists, and previous stations still in the bank are not. Everything about how the exam works can and should be published.
What goes in the exam-day briefing?
The sequence and signals, the clock, the conduct rules, what to do if unwell or if a station goes wrong, that raising it carries no penalty, and when results arrive. Use one written script delivered the same way to every session, kept with the run-sheet.
Should candidates be briefed by examiners?
No. The AMEE guide treats candidate, examiner, and simulated patient briefings as three separate events. The scripts differ, and combining them leaks information to the group that should not have it.