> 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-diary-studies.md).

# Skip logic in diary studies

With skip logic, you can jump scouts to a particular question based on their response choice.

In the example question below, only scouts who choose "in the water" will see the relevant short response question that comes next.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/p05MqQE5OqV74EEmQZOp/360048963331)

When editing a question with skip logic, just click the grey arrow next to individual answers (or the question prompt!) to direct scouts to the question they should see next.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/mf8KrGaBxlYF7Smc4e4m/360048834572)

* Skip logic can be applied to all question types.
* Multiple select questions **can not** skip to different question paths (i.e., if option A skips to question 3, option B **can not** skip to question 5). This is because the platform won't know what to prioritize if a scout chooses multiple options that skip to different questions.
* Write all your questions first, *then* define your skip logic afterwards. Moving questions around after defining your skip logic will cause the skip logic to break (disappear), and you'll have to define it again. And we don't want that.
* You're **not** able to program skip logic on the last question in a study. To activate skip logic on a question you just created, move it up in the question script.


---

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