> 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/usability-tests/what-are-usability-tests-in-dscout/question-types-in-usability-tests.md). # Question types in usability tests Usability tests let you ask participants to perform specific tasks related to concepts, prototypes, and more. Responses are continuously recorded, and you can combine many different question types in your study to collect the information you need. The table below outlines which Dscout question types you can use in a usability test: {% hint style="info" %} **Note:** The following question types can be combined in the usability test portion of your mission (on the **Usability test** tab). However, only multiple choice questions can be used in the screener portion (on the **Screener** tab) when auto-recruiting participants. {% endhint %} | Question type | Description | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Multiple choice** |

Provide participants with a list of options to choose from.

Tip: Knockout logic can be applied to multiple choice questions to disqualify applicants during the screener portion of your mission. For more information, see Knockout questions.

| | **Typed response** | Allow participants to provide a written response. You can limit responses to 140 characters or apply no limit. | | **Checkpoint** | Provide additional context or instructions to participants without asking a question or requiring a response. | | **Scale** | Have participants rate how they feel about a statement or stimuli on a predefined scale. You can customize the **Start value** and **End value** with your own labels. | | **Ranking** |

Have participants rank a list of options in comparison to one another. For example, “Rank the following pizza toppings from best (1) to worst (6).”


For more information, see Ranking questions.

| | **Number** | Have participants provide a number up to nine digits in length. | | **Card sort** |

Provide participants with a set of items (cards) to sort into different categories.

For more information, see Card sort questions.

| | **Tree testing** | Have participants show you how they would navigate an organizational structure to find a specific item or complete a specific task. For more information, see Tree testing questions. | | **Task (up to 15 per mission)** |

Prompt participants to complete a specific action or activity on an attached website or prototype. For more information, see Task questions.


Note: It’s important to maintain participants’ privacy, including when capturing task screen recordings. For more information, see Privacy blur.

| | **Talk out loud** | Allow participants to provide a verbal answer that will be transcribed as part of their recorded response. | | **Question groups** | Organize related questions in the builder for easier mission design or to randomize the way they are presented to participants. For more information, see [Question groups](/study-basics/question-types/question-groups.md). | | **Multi-variate** | Organize questions by concept or design variants and randomize how they are presented to participants. For more information, see [Multi-variate testing](/study-basics/question-types/multi-variate-testing.md). | To learn more about adding questions to your mission, see [Add questions to a usability test](/usability-tests/create-a-usability-test/add-questions-to-a-usability-test.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.dscout.com/usability-tests/what-are-usability-tests-in-dscout/question-types-in-usability-tests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.