> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/study-basics/design-a-study/skip-logic-in-single-session-studies.md).

# Skip logic in single-session studies

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr><tr><td><strong>AI moderated studies</strong></td><td>true</td></tr></tbody></table>

With skip logic in studies, you can jump participants to different questions based on their answers to a previous question.

In the example question below, only participants who select "Outside of my bedroom" will see Question 2, the relevant open-ended question that comes next. Those who do not will skip to Question 3.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/xlwwOIkW8A328IS5W2FS/18354226977044)

If including skip logic to an answer option, click the skip logic icon next to the individual answer option to apply skip logic. If include skip logic at the question level, click the skip logic icon above the question prompt to direct participants to the question they should see next.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/iekIKK7p22OMEZn68kgb/18354194118932)

Skip logic can be applied to any question type in a usability test, media survey, intercept study, or AI moderated study. Multi-select questions can not include multiple skip-logic paths. In AI moderated studies, how skip logic works depends on the question type. For more information, see [AI moderated studies](#ai-moderated-studies).

### AI moderated studies

In AI moderated studies, skip logic works as follows for each question type:

| Question type   | Skip logic                                                                                                   |
| --------------- | ------------------------------------------------------------------------------------------------------------ |
| Multiple choice | Add skip logic to individual answer options. Multi-select questions can't include multiple skip-logic paths. |
| Scale           | Add skip logic at the question level. Every participant who answers goes to the same next question.          |
| Talk out loud   | Add skip logic at the question level. Every participant goes to the same next question.                      |
| Task            | Add skip logic at the question level. Every participant goes to the same next question.                      |

Skip logic can send participants to a later question, a question group, or the end of the study.

{% hint style="success" %}
**Tip:** Question-level skip logic is useful for bringing branches back together. For example, if a multiple choice question sends some participants to one Talk out loud question and the rest to another, add skip logic to the first Talk out loud question so those participants jump past the second one.
{% endhint %}

#### Follow-up questions and skip logic

If a multiple choice or scale question has follow-up questions turned on, the AI moderator asks those follow-ups **before** moving the participant to the next question. Skip logic is based only on the answer the participant selected on screen. Nothing they say during the follow-ups changes where they go next.

If the **Follow-up questions** toggle is off, the participant moves on as soon as they make a selection.

{% hint style="info" %}
If your study runs in a language other than English, skip logic still works. The participant's selection is matched to the answer options you wrote.
{% 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://help.dscout.com/study-basics/design-a-study/skip-logic-in-single-session-studies.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.
