> 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/question-types/question-settings-and-organization/using-question-quotas.md).

# Using question quotas

**Quotas can be set on both single-select and multi-select questions**. This feature is available in screeners, usability tests, and media surveys.

**You have the option to set either “equal to” or “at most/at least” quotas.** For “equal to” quotas, you’ll indicate the exact number of responses you’d like for a given choice. Use on single-select questions when you’d like to ensure a specific number of responses for either one choice, or for multiple choices. If a participant's selection is above your set quota for that question, they'll be excused as a potential participant, saving you time.

Use “at most/at least” when your recruit criteria is more flexible, but you want to ensure that at least a few participants pick a certain choice, or that too many participants don’t pick another choice.

* When using “equal to” quotas, any response option that does have a quota will accept submissions that select that option until the quota is met and then the selection will become a knockout for participants. Any response option that does not have a quota set will be an automatic knockout.
* When using “at most/at least” quotas, responses will either be reserved until at least a minimum number of a specific response is collected, or it will ensure that no more than a certain amount of responses are collected for a given condition. You can use just “at least” or “at most”, or use both in the same question.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/37BxIvW1mTueZgEr4G0U/33671395021332)


---

# 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/study-basics/question-types/question-settings-and-organization/using-question-quotas.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.