> 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-screeners.md).

# Skip logic in screeners

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

In the example question below, the question workflow will work as follows:

* Participants who select "Always" or "Often" will be skipped to Q4
* Participants who select "Sometimes" will be skipped to Q7
* Participants who select "Rarely" or "Never" will move on to the next question (Q3)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/zkVXO5JTlt8v9bcRQqZc/21709631260180)

To add or edit skip logic, click the curved grey arrow next to the answer(s) to direct participants to the question they should see next:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/czg5cFNSpK8CRf3jK8ow/21709654645524)

{% hint style="info" %}
**Note:** Selecting "End" on Skip logic does not operate as a knockout question. Skip to End should be used when a participant, based on that response, does not need to answer the remaining questions in the study or screener. This means the participant qualifies and their application is considered complete if they're skipped to the end. In diary studies, usability tests, and media surveys, this is a way to build in "optional" questions.
{% endhint %}

Skip logic can be applied to any [question type](/recruit-participants/what-are-dscout-screeners/question-types-in-screeners.md).


---

# 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-screeners.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.