> 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/create-a-usability-test/usability-test-checklist.md).

# Usability test checklist

***

Before you launch your usability test, it’s good to take a minute to make sure everything is in order. This leads to a more seamless experience for your participants, but it can also make analysis easier on your end once you’ve received responses. Use the following sections (organized by category) to double-check your study prior to launch.

{% hint style="info" %}
**Note:** Some things are required to launch your usability test. To view any unmet requirements, click the purple **Launch** button in the top right corner of your study. If the button is green, you’ve met all the requirements!
{% endhint %}

### Study settings <a href="#h_01k8bbjjvgy19e4y0hve97ekph" id="h_01k8bbjjvgy19e4y0hve97ekph"></a>

Before launching, verify your study has:

* A clear and engaging **title** and **description**.
* An accurate **participant limit** and **incentive**.
* Any applicable **custom informed consent** enabled. For more information, see [Custom informed consent](/getting-started/research-basics/custom-informed-consent.md).

### Screener questions (auto-recruit only) <a href="#h_01k8bbjjvgddpy0czn83j897n3" id="h_01k8bbjjvgddpy0czn83j897n3"></a>

If you’re auto-recruiting participants (either from the Dscout Scout Panel or from Partner Panels), your study will have a dedicated **Screener** tab. Here, verify your study has:

* Specific (but not too exclusive) **targeting attributes**. For more information, see [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes.md).
* Questions with **knockout logic**. For more information, see [Knockout questions](/recruit-participants/dscout-scout-panel/knockout-questions.md).

### Study questions <a href="#h_01k8bbjjvgqz8fd557xzrmpgqm" id="h_01k8bbjjvgqz8fd557xzrmpgqm"></a>

To double-check the rest of your study, here’s a list of questions to ask yourself about your study questions:

* Are question prompts clear? For a little help, see [Refine your questions](/dscout-ai/built-in-ai-features/refine-your-questions.md).
* Is skip logic applied correctly? For more information, see [Skip logic](/study-basics/design-a-study/skip-logic-in-usability-tests-media-surveys-and-intercept-studies.md).
* Are multiple choice questions correctly set as single- or multi-select?
* Are response choices for single-select questions clear and mutually exclusive?
* Do open-ended questions have character limits when needed?
* Do task questions include the necessary website or prototype URLs? For more information, see [Task questions](/study-basics/question-types/activity-questions/task-questions.md).

{% hint style="success" %}
**Tip:** For good measure, we recommend testing your study prior to launch. For more information, see [Test a usability test study](/usability-tests/create-a-usability-test/test-a-usability-test.md). You can also have your study reviewed by a Dscout Research Advisor. For more information, see [Optional pre-launch review](/study-basics/design-a-study/optional-pre-launch-review-for-screeners-and-studies.md).
{% 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/usability-tests/create-a-usability-test/usability-test-checklist.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.