> 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/media-surveys/create-a-media-survey/media-survey-checklist.md).

# Media survey checklist

Before you launch your media survey, 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 mission prior to launch.

{% hint style="info" %}
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 mission. If the button is green, you’ve met all the requirements!
{% endhint %}

## Mission settings

Before launching, verify your mission 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)

If you’re auto-recruiting participants (either from the Dscout Scout Panel or from Partner Panels), your mission will have a dedicated **Screener** tab. Here, verify your mission 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).

## Mission questions

To double-check the rest of your mission, here’s a list of questions to ask yourself about your mission 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-mission/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?
* Will participants have enough time to respond to any video questions within the time limit you’ve set?

{% hint style="info" %}
For good measure, we recommend testing your mission prior to launch. For more information, see [Test a media survey](/media-surveys/create-a-media-survey/test-a-media-survey.md). You can also have your mission reviewed by a Dscout Research Advisor. For more information, see [Optional pre-launch review](/study-basics/design-a-mission/optional-pre-launch-review-for-screeners-and-missions.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 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/media-surveys/create-a-media-survey/media-survey-checklist.md?ask=<question>&goal=<endgoal>
```

`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.