> 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/dscout-scout-panel/programming-insight.md).

# Programming insight

When recruiting participants, it can be useful to see where applicants are most often being disqualified. In screeners, usability tests, and media surveys, you can see exactly how many applicants were disqualified by each of your knockout questions. Then, you can use that data to update your knockout logic to either be more or less inclusive depending on your needs.

{% hint style="info" %}
Programming insight is only available when auto-recruiting from the Dscout Scout panel.
{% endhint %}

Once you launch your screener or study, you'll find programming insights on the **Overview** tab:

![](/files/0c55757a690b20145c31e7f35af01fc9348f1669)

{% hint style="info" %}
If your participant numbers are low and one question is disqualifying most of your applicants, consider whether your requirements for that question can be more flexible.
{% endhint %}


---

# 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/recruit-participants/dscout-scout-panel/programming-insight.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.