> 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/writing-smart-screener-questions.md).

# Writing smart screener questions

Well-written screener questions are clear, specific, and hard to game. This lesson shows you how through several examples.

{% hint style="success" %}
**Tip:** Dscout AI can help you write research questions directly in the build on most study types, getting you from idea to launch faster. For more information, see [Refine your questions](/dscout-ai/built-in-ai-features/refine-your-questions.md).
{% endhint %}

### Example one: Avoid the "yes" or "no"

Offering yes or no questions as a form of qualification makes it evident to applicants what you're looking for in a participant. Most of the time, a "yes" answer will keep them moving through the screener, while a "no" answer will disqualify them.

Instead of asking <mark style="color:red;">`Did you buy a home in the last six months?`</mark> try asking the same question in a multi-select format: <mark style="color:green;">`Which of the following have you done in the last six months?`</mark>

The second format allows you to include decoy answer choices that prevent the participant from guessing what you're looking for. Include answer choices like `Bought a home`, `Attended a concert`, `Traveled domestically`, and `Started a new job` that use knockout logic. The participant has no idea which of these will qualify them, keeping them honest as they apply.

### Example two: Avoid making assumptions

When writing screener questions, it's an easy mistake to write them specifically for your target audience. However, it's important to avoid making assumptions about the applicants completing your screener.

Instead of asking <mark style="color:red;">`Which bathrooms will you be renovating this year?`</mark> try asking the question more generally first: <mark style="color:green;">`Which of the following home renovations do you plan to complete this year?`</mark>

The second format removes the assumption that all applicants will, in fact, be renovating at least one bathroom this year. You can offer a `None of the above` option for applicants who don't plan to renovate anything, while also making the question multi-select in case applicants plan to renovate more than just a bathroom. (But if the bathroom renovations are all that's important to your screener, you can still apply must-select logic to knock out those who do not choose that as an answer.)

### Example three: Get specific when needed

Following the theme from above, let's say you get to a point in your screener when applicants who do not plan to renovate a bathroom have been knocked out. Now, you want to ask questions specifically about the applicant's intended bathroom renovation. At this point, it's okay to get specific so they still know what you're talking about.

Instead of asking <mark style="color:red;">`What's your budget?`</mark> try homing in on the bathroom renovation specifically by asking <mark style="color:green;">`For your planned bathroom renovation, what budget do you intend to work with?`</mark>

The second format makes it clear to applicants that you're now exclusively asking about the bathroom renovation, even if they may have chosen multiple renovation projects as an answer to a previous question.

Now that we've covered some examples of how to write smart screener questions, let's wrap things up by looking at how you actually go about selecting participants from your eligible screener applicants in lesson five: [Selecting the right participants](/guides/recruiting-with-confidence/selecting-the-right-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/guides/recruiting-with-confidence/writing-smart-screener-questions.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.