Below is a checklist of the things we recommend you check in the run up to your exams
Order of preparing an exam
3 MONTHS BEFORE EXAM
- Contact Practique Team to notify of exam dates and student numbers
- If on-site support is required from the Practique team, notify the team
1 MONTH BEFORE EXAM
-
- Check that all Items have been tagged correctly (blueprinting)
- For OSCE, check the marksheets marksheet for fields that are marked as feedback are correct
-
- Check the Known Issues page on the Knowledge Base
- Review your local on-the-day escalation plan in the event of an unplanned issue
- Notify your local IT team that may need assistance on your exam day
- If running on paper, create and download papers from Practique
- Check you have the most up to date iPad application and Practique server version
2 WEEKS BEFORE THE EXAM
- Finalise the Item Setsitem sets. Ensure that each item in the set is using the latest version before sending for senior review and approval.
- Check that the Items in the Items Item Sets are in the correct order
- Create the Exam in Practique
- Finalise Exam allocation and rotation
- Upload candidates to Exam
- For OSCE, upload examiners and marshals to Exam
- Ensure you have all devices (iPads, computers) that you will need, including marshal and spare iPads.
1 WEEK BEFORE THE EXAM
- For OSCE, check the rotation of all of the sessions
- For OSCE, check that examiners have been allocated to the correct rooms
- Sync exam to the devices and test the exam
- Check that all items appear correctly on the devices
- Check that resources correctly load on the device
- For OSCE, check that candidates rotate in the correct way
-
- Check again the Known Issues page on the Knowledge Base
- For OSCE, ensure that 1 sessions worth of spare paper marksheets are available.
1 DAY BEFORE THE EXAM
- Reset Exam and open sessions that will be used on the day
- For OSCE, print or provide for onscreen use, QR codes for examiners
DAY OF THE EXAM
-
- For OSCE, mark students as not attending as necessary, by marking them DNA
{"serverDuration": 257, "requestCorrelationId": "ad3373f47d1840199066797683b450d8"}