> 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/question-types/question-settings-and-organization/checkpoint-questions.md). # Checkpoint questions

Study type	Availability
Screeners	true
Usability tests	true
Media surveys	true
Intercept studies	true
AI moderated studies	false
Diary studies	true

Checkpoint questions let you show participants a message without asking them to respond. Use a checkpoint to give brief instructions, introduce a group of questions, encourage participants part of the way through, or give notice of an upcoming media question. Participants read the message and continue. Checkpoints don't collect a response.

{% hint style="info" %} **Note:** Checkpoint questions aren't available in AI moderated studies. {% endhint %} ### Checkpoint question settings The settings available on a checkpoint question depend on which type of study you're building. Select your study type below for more information. {% tabs %} {% tab title="Screeners" %} Add a checkpoint to a screener in the **Additional questions** section of the **Screener** tab. | Setting | Description | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Message** | What applicants read. You can format the message with `*bold*`, `_italic_`, and `[link text](http://example.com)`. Type @ to recall a closed-ended response from earlier in your screener. | | **Stimuli** (optional) | Attach up to 5 images for applicants to view. For more information, see [Question stimuli](/study-basics/question-types/question-settings-and-organization/question-stimuli.md). | | **Stimuli randomization** | Presents attached stimuli in a random order to each applicant. This setting appears once the question has more than one stimulus attached. | | **Skip logic** (optional) | Route applicants to a later question or end the screener after they continue. For more information, see [Skip logic in screeners](/study-basics/design-a-study/skip-logic-in-screeners.md). | {% hint style="info" %} **Note:** Checkpoint questions aren't supported in screeners for Partner Panels. For more information, see [Recruit from Partner Panels using a screener](/recruit-participants/partner-panels/recruit-from-partner-panels-using-a-screener.md). {% endhint %} {% endtab %} {% tab title="Usability tests and intercept studies" %} Add checkpoints on the **Usability test** or **Study** tab of your builder. | Setting | Description | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Message** | What participants read. You can format the message with `*bold*`, `_italic_`, and `[link text](http://example.com)`. Type @ to recall a closed-ended response from earlier in your study. | | **Privacy blur** (optional) | Blurs the participant's screen in the recording while they're on this message, to protect their personally identifiable information (PII). For more information, see [Privacy blur](/study-basics/testing-prototypes/privacy-blur.md). | | **Stimuli** (optional) | Attach up to 5 pieces of media for participants to view. For more information, see [Question stimuli](/study-basics/question-types/question-settings-and-organization/question-stimuli.md). | | **Stimuli randomization** | Presents attached stimuli in a random order to each participant. This setting appears once the question has more than one stimulus attached. | | **Skip logic** (optional) | Route participants to a later question, question group, or the end of the study after they continue. For more information, see [Skip logic](/study-basics/design-a-study/skip-logic-in-usability-tests-media-surveys-and-intercept-studies.md). | | {% endtab %} | | {% tab title="Media surveys" %} Add checkpoints on the **Media survey** tab of your builder. | Setting | Description | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Message** | What participants read. You can format the message with `*bold*`, `_italic_`, and `[link text](http://example.com)`. Type @ to recall a closed-ended response from earlier in your study. | | **Stimuli** (optional) | Attach up to 5 pieces of media for participants to view. For more information, see [Question stimuli](/study-basics/question-types/question-settings-and-organization/question-stimuli.md). | | **Stimuli randomization** | Presents attached stimuli in a random order to each participant. This setting appears once the question has more than one stimulus attached. | | **Skip logic** (optional) | Route participants to a later question, question group, or the end of the study after they continue. For more information, see [Skip logic](/study-basics/design-a-study/skip-logic-in-usability-tests-media-surveys-and-intercept-studies.md). | | {% endtab %} | | {% tab title="Diary studies" %} Add checkpoints to a diary study on the **Questions** tab of your builder. | Setting | Description | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Message** | What participants read. You can format the message with `*bold*`, `_italic_`, and `[link text](http://example.com)`. Type @ to recall a closed-ended response from earlier in the same activity. | | **Stimuli** (optional) | Attach up to 5 images for participants to view. For more information, see [Question stimuli](/study-basics/question-types/question-settings-and-organization/question-stimuli.md). | | **Stimuli randomization** | Presents attached stimuli in a random order to each participant. This setting appears once the question has more than one stimulus attached. | | **Skip logic** (optional) | Route participants to a later point in the activity after they continue. For more information, see [Skip logic in diary studies](/study-basics/design-a-study/skip-logic-in-diary-studies.md). | | {% endtab %} | | | {% endtabs %} | | ### Add a checkpoint to a study {% hint style="info" %} **Note:** In a screener, checkpoints go in the **Additional questions** section. They can't be knockout questions, and they aren't available on the screeners of auto-recruit studies, which support only multiple choice questions. For more information, see [Question types in screeners](/recruit-participants/what-are-dscout-screeners/question-types-in-screeners.md). {% endhint %} {% stepper %} {% step %} Navigate to the tab of your builder where you want the checkpoint—**Questions**, **Usability test**, **Study**, **Media survey**, or **Screener**, depending on your study type. {% endstep %} {% step %} Click **+ Add** in the center of the builder or in the left sidebar. (**+ Add question** in diary studies, or **Add additional question** in screeners.) {% endstep %} {% step %} Select **Checkpoint**.

{% endstep %} {% step %} Enter your **Message**.

{% endstep %} {% step %} Configure the remaining settings. For details, see [Checkpoint question settings](#checkpoint-question-settings) above. {% endstep %} {% step %} Click **Done**. {% endstep %} {% endstepper %} #### Group and randomize checkpoints Checkpoints work with Dscout's question-organization features: * [**Question groups**](/study-basics/question-types/question-settings-and-organization/question-groups.md) keep related questions together and can randomize the order they're presented in. * [**Multi-variate testing**](/study-basics/question-types/question-settings-and-organization/multi-variate-testing.md) presents different concepts or design variants to different participants. * [**Question banks**](/study-basics/question-types/question-settings-and-organization/question-banks.md) let you save a checkpoint and reuse it in other studies. ### Analyze a checkpoint Checkpoints don’t collect a response, so there’s nothing to analyze. In the **Questions** view, a checkpoint appears as a card that shows its message, with no responses below it. A checkpoint doesn’t appear as a column in your study’s CSV export.

In diary studies, a checkpoint appears in an entry as a divider labeled **Checkpoint** between the participant's responses.

### Frequently asked questions

Do checkpoints count toward question limits?

It depends on the study type. Checkpoints don't count toward a screener's question limit. In a diary study, they count toward the 15 questions in an activity that Dscout recommends staying under. Media surveys, usability tests, and intercept studies don't have a total question limit.

Can a study contain only checkpoints?

No. A screener, study, or diary activity needs at least one question that isn't a checkpoint. If it contains only checkpoints, Dscout asks you to add another question before you can launch or submit it.

Can I add a page break or section between questions?

Every question appears on its own screen, including checkpoints. [Question groups](/study-basics/question-types/question-settings-and-organization/question-groups.md) only organize your questions in the builder, so they don't create sections that participants can see. To separate parts of your study, add a checkpoint between them with a short message, such as an introduction to the next set of questions.

Can I use a checkpoint to route participants?

Yes. You can set skip logic on a checkpoint, and you can skip participants to one. This helps when you want some participants to skip past a question but can't set that skip directly. For example, in a multi-variate question that shows one variant, participants who finish a variant move on to the next question after the block. To send some of them past that question, add a checkpoint right after the block and set its skip logic to the question you want them to reach. Participants see the checkpoint's message before they continue, so write a message that makes sense for everyone who reaches it, such as a short transition. For more information, see [Multi-variate testing](/study-basics/question-types/question-settings-and-organization/multi-variate-testing.md).

Can I change a question to a checkpoint, or a checkpoint to another type?

Yes, in usability tests, intercept studies, media surveys, and screeners. Open the question in the builder and use the **Type** dropdown, which lists the question types available for your study type. If something won't carry over to the new type, such as answer choices or skip logic, Dscout shows a warning before you confirm the change. After you change a question's type, double-check settings like stimuli and skip logic to be sure they're what you expect.

Can I add a checkpoint in the middle of a task?

No. A checkpoint is its own question type, so it can't appear inside a [Task question](/study-basics/question-types/activity-questions/task-questions.md). To give participants a pause partway through, split the work into two Task questions and add a checkpoint between them.

Why can't I add a checkpoint to my AI moderated study?

Checkpoint questions aren't available in AI moderated studies. For the question types available, see [Question types in AI moderated studies](/ai-moderated-studies/what-are-ai-moderated-studies/question-types-in-ai-moderated-studies.md).

Why can't I add a checkpoint to my Partner Panels screener?

Screeners for Partner Panels don't support checkpoint questions. You can include a checkpoint in your study itself. For more information, see [Recruit from Partner Panels using a screener](/recruit-participants/partner-panels/recruit-from-partner-panels-using-a-screener.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/question-types/question-settings-and-organization/checkpoint-questions.md?ask=&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.