> 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/guides/recruiting-with-confidence/designing-strong-screeners.md). # Designing strong screeners A screener helps you recruit the right participants for your study by combining targeting attributes with screening questions. This lesson walks you through the logic available when designing screeners as well as several best practices to keep in mind. For a step-by-step guide on how to create a screener in Dscout, see [Set up a screener](/recruit-participants/what-are-dscout-screeners/set-up-a-screener.md). ### Screener logic Dscout offers three types of screener logic that can dynamically change a participant's experience. For example, you can skip participants to specific questions based on their answers. Or, you can automatically disqualify participants based on answers they provide. Here's a breakdown of the three types of screener logic available in Dscout: | Logic type | Description | Availability | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | | Knockout logic | Commonly called “termination” logic, knockout logic disqualifies participants if they select certain answers to a question. For more information, see [Knockout questions](/recruit-participants/dscout-scout-panel/knockout-questions.md). | Only available when using auto-recruitment | | Must-select logic | Similar to knockout logic, must-select logic disqualifies participants if they do not select a required answer to a question. For more information, see [Knockout questions](/recruit-participants/dscout-scout-panel/knockout-questions.md). | Only available when using auto-recruitment | | Skip logic | Skip logic sends participants to a specific question later in your screener based on answers they provide. This is similar to branching logic and allows you to skip participants past parts of your screener if those parts do not apply to them. | Available on all recruitment approaches | ### Best practices Here are some best practices to keep in mind when designing a screener: * **Keep titles scout-facing:** Avoid revealing your core recruitment criteria in the screener's title. Doing so can lead applicants to overemphasize related experience just to earn a spot. Instead of `Calling heavy users of Amazon Alexa`, try something like `Smart home tech and you`. * **Use the internal title name feature:** Keep your workspace organized by adding internal titles that are only visible to you and your collaborators. This is great for iterative research (like labeling waves) or for distinguishing screeners aimed at different recruits. * **Lean on targeting attributes to shorten your screener:** Members of the Dscout Scout Panel and our Partner Panels share data like age and income as part of their profile, so you can filter who receives your screener instead of asking. Participants who don't meet your targeting attributes are automatically disqualified and won't be able to participate. (Targeting attributes are not available when screening bring-your-own (BYO) participants.) * **Use logic to create a smooth participant experience:** If certain questions only apply to certain participants, use skip logic to keep participants moving along efficiently. Similarly, when utilizing auto-recruitment, use knockout and must-select logic to disqualify applicants as early as possible. * **Submit for review:** Before launching, you can request feedback from a Dscout research advisor, typically within two business days. Reviewing your screener before it opens to participants helps you get more effective responses and confirms everything is set up correctly. * **Save time with templates:** Save proven screener and study formats as templates to reduce repetitive setup and keep studies consistent across your team. (Only certain user types can create screeners, but most can use them.) Now that you're familiar with how to go about designing a screener, let's look at how to write your questions in lesson four: [Writing smart screener questions](/guides/recruiting-with-confidence/writing-smart-screener-questions.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/guides/recruiting-with-confidence/designing-strong-screeners.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.