> 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/exams/create-and-manage-exams/2.-build-exam/exam-sections.md).

# Exam sections

Creating sectioned exams, strict vs soft sections

Sections help you organise an exam into structured parts, allowing you to group related questions and control how candidates progress through an assessment. By default, sections are used for organisation and reporting, but they can also support more advanced assessment models such as section-level grading or additional pass requirements.

Sections let you split up questions in to distinct parts of an exam, key features for sections are:&#x20;

1. Once a section has been submitted, users **cannot** go back to the section to change their responses.
2. EMQ Groups **cannot** be split across sections&#x20;

There are two types of sections on quizzes and exams on Synap which can be configured from the experience page. If you're creating a static exam, titles, timers, instructions and instruction timers will be copied over from the source quiz but can all be modified in the exam

See our detailed guides below on how to build and use sections, grades and advanced grading criteria&#x20;

{% content-ref url="/pages/B5Idpot7Ag70R02B4CBy" %}
[Sections](/docs/quizzes/creating-a-quiz/sections-1.md)
{% endcontent-ref %}

{% content-ref url="/pages/nWwuLsNb9NBdwGUWsE1Z" %}
[Exam grades](/docs/exams/create-and-manage-exams/2.-build-exam/exam-grades.md)
{% endcontent-ref %}

{% hint style="info" %}
See the Dynamic exams page for information on [sections in Dynamic exams](https://academy.synap.ac/doc/exams/create-and-manage-exams/creating-an-exam/dynamic-exams#sections-in-dynamic-exams).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://synap.ac/docs/exams/create-and-manage-exams/2.-build-exam/exam-sections.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
