> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/exams/exam-setup.md). # Exam setup An exam combines questions with the rules for delivering them to students. The first choices you make—particularly the exam type and registration method—shape the pages and settings that are available later. ### Core setup fields | Field | What it is | What to bear in mind | | --------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | Name | The name shown to admins and students | Make it specific enough to distinguish it from similar exams, for example “Biology mock exam – September” | | Description | A short explanation of the exam | Use Instructions for anything students must read before starting | | Image | The image used to identify the exam | Use a clear image that still makes sense when displayed at a small size | | Owner | The person responsible for the exam in Synap | Choose someone who will continue to have access to manage it | | User group or direct registration | How students are associated with the exam | Use a group for an existing class; use direct registration when you want to choose individuals | | Custom attributes | Organisation-specific metadata | Apply reporting fields before delivery so exports and filters are consistent | ### Exam type The type is selected during creation and is normally locked once the exam exists. | Type | Question selection | Useful when | What to bear in mind | | ------- | ---------------------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | Static | Every attempt uses the configured question set | Everyone should receive the same paper, or your question bank is small | Students see the same content unless you create another version | | Dynamic | Each attempt is generated from filter rules | You have a large question bank or expect repeated sittings | Questions must be tagged consistently and students may receive different papers | {% hint style="warning" %} You cannot normally change the type after creating the exam. If you later need the other type, create a new exam so that the earlier attempts remain easy to understand. {% endhint %} ### Source quiz The source quiz supplies questions, answers, question-level marks, feedback, tags and Extended Matching Question (EMQ) groups. Exam settings can override delivery behaviour, but they do not replace the need for a well-formed source. Before selecting a source: * confirm all questions are published and usable; * verify correct answers and manual-marking requirements; * check question timers if the exam will infer its duration from questions; * validate tags and tag sets for dynamic selection or reporting; * check embedded files and media using the devices candidates will use. Changing content after an exam has attempts requires version awareness. Existing attempts remain associated with the version from which they were generated; a later version can be prepared without rewriting completed delivery history. ### Registration model #### User group The exam is connected to a user group, such as a class. This is useful when you already organise your students into groups. Check the group's membership before registering attempts so that nobody is included or missed by mistake. #### Direct registration Admins select students directly on the exam. This is useful for a one-off sitting or when the students come from several groups. The exam still creates a separate attempt for each person, so registration dates matter when a relative deadline is used. ### Versions and publishing An exam can have a draft configuration alongside a published version. Draft settings are the working copy; publishing turns them into the next delivery version. | Action | Effect | | ------------------- | ------------------------------------------------------------------------- | | Edit draft | Changes the configuration being prepared | | Publish | Creates a delivery version used by new attempts | | Start another draft | Prepares future changes without altering the historical version | | Archive | Removes the exam from normal active workflows while retaining its records | Some settings warn that saving applies to all unstarted attempts. Read these warnings literally: a candidate who is registered but has not started may receive updated instructions or workflow settings, while an in-progress or submitted attempt remains governed by its established state. ### Recommended setup sequence 1. Choose static or dynamic based on comparability and item-bank strategy. 2. Select and quality-assure the source quiz. 3. Choose group or direct registration. 4. Configure questions, scores and grades. 5. Configure what students will see and how the exam will run. 6. Publish, register test users and complete a rehearsal. 7. Register your students and enable emails when you are ready for them to receive access. ### What can safely change later? Do not judge this only by whether the editor permits a change. Ask which attempt population should receive it. | Candidate state | What to assume | | -------------------------- | -------------------------------------------------------------------------------------------------------------------- | | Not registered | Receives the version and schedule current when later registered | | Registered but not started | Some saved changes may apply; read the warning shown by the relevant setting | | In progress | Avoid changing the shared setup unless you are correcting a problem; use attempt-specific controls where appropriate | | Submitted or finalised | The attempt is historical evidence and should remain associated with its delivered version | If you need to correct a problem, first check which version and students are affected. Use a new version for changes to questions or the shared exam setup. If only one student needs a different closing time or extra time, change that student’s attempt instead. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://synap.ac/docs/platform/exams/exam-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.