> 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/recruit-participants/what-are-dscout-screeners/report-an-applicant-in-a-screener.md). # Report an applicant in a screener Dscout takes pride in the quality of our Scout Panel and Partner Panels. So, if you have concerns about the quality, honesty, or integrity of a screener applicant, you can report them directly from your screener. Reporting sends your concern to Dscout Support for review. ## Report an issue with an applicant or response {% stepper %} {% step %} Navigate to the **Responses** tab of your screener.
{% endstep %} {% step %} Click **Participants** in the left sidebar. Then, select the participant whose response you want to report. The participant’s details are displayed in the right sidebar.
{% endstep %} {% step %} Click the three-dot icon in the right sidebar. Then, select **Report an issue**. A confirmation modal is displayed.
{% endstep %} {% step %} Select from the following issue types, then click **Next**: | Issue type | Possible reason | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Participant** | | | **Technical** | | | {% endstep %} | | {% step %} Select a **Reason**. {% endstep %} {% step %} Enter a description of the issue. {% endstep %} {% step %} Click **Submit**. {% endstep %} {% endstepper %} Now, your report is sent to Dscout Support who will review the participant’s response. {% hint style="info" %} **Note:** Unlike Dscout studies, screeners don’t include refund, exclusion, or backfill options as part of a report. Reporting a response simply sends your concern to Dscout for review. {% endhint %} ## Set an applicant aside You can’t exclude applications from a screener the way you can in Dscout studies. Instead, use the applicant’s **Fit** rating to keep them out of the participants you select for your study. Assigning a `Bad Fit` or `Low Quality` rating removes the applicant from your `Good Fit` picks, while keeping their application accessible if you need it later. For more information on fit ratings, see [Review screener responses](/recruit-participants/what-are-dscout-screeners/review-screener-responses.md#potential-fit). --- # 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/recruit-participants/what-are-dscout-screeners/report-an-applicant-in-a-screener.md?ask=&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.