> 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-mission/optional-pre-launch-review-for-screeners-and-missions.md).
# Optional pre launch review for screeners and missions
| Study type | Availability |
|---|
| Screeners | true |
| Usability tests | true |
| Media surveys | true |
| Intercept studies | true |
When building a screener, usability test, or media survey, you have the option of submitting them for review by a Dscout Research Advisor prior to launch. Having your screeners and missions reviewed before opening them to participants can help ensure you get the most effective responses and that your participants have the best experience.
{% hint style="info" %}
**Note:** Screeners should be just long enough to determine whether an applicant is a fit for your study. So, screeners that present applicants with more than 20 questions cannot be launched without being submitted for a pre-launch review.
{% endhint %}
Reviews can take up to two business days. However, we understand different projects call for different timelines, so these reviews are optional in many cases. If you don’t see the option to skip this review, it may not be available in your organization’s Dscout account. Contact your Dscout administrator or account manager for more information.
{% hint style="success" %}
**Tip:** If you choose to launch your screener or mission without submitting it for review, refer to our our [Screener review checklist](https://help.dscout.com/hc/en-us/articles/13167502742548) and [Project review checklist](https://help.dscout.com/hc/en-us/articles/360038414832) to make sure you’ve covered all the essentials.
{% endhint %}
**To submit a screener or mission for review:**
{% stepper %}
{% step %}
In the builder, click **Launch** in the top-right corner. A modal opens displaying your review options.
{% endstep %}
{% step %}
Select **Submit for review**.
{% endstep %}
{% step %}
Click **Continue.** A modal opens requesting a few more details about your screener or mission.
{% endstep %}
{% step %}
Enter your intended **launch date**. This must be at least one business day from the date you’re submitting. And keep in mind that your selection here will not guarantee a faster review.
{% endstep %}
{% step %}
Enter a sentence or two into the provided text box. Let our Research Advisors know about your project goals or anything you want specific feedback on.
{% endstep %}
{% step %}
Click **Submit**.
{% endstep %}
{% endstepper %}
Next, a Research Advisor will review your screener or mission as soon as possible—within two business days at the very latest. You’ll receive an email once the review is complete and find the Research Advisor’s feedback via comments in the builder.
Once you’ve resolved any issues, give your screener or mission one last glance. Then, click **Launch** in the top-right corner of the builder to open it to participants.
For information on selecting participants based on screener responses, see [Viewing applications and selecting participants](/recruit-participants/dscout-scout-panel/view-applications-and-select-participants.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/study-basics/design-a-mission/optional-pre-launch-review-for-screeners-and-missions.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.