> 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/media-surveys/what-are-media-surveys-in-dscout/response-scoring-in-media-surveys.md). # Response scoring in media surveys In media surveys, Dscout completes automated quality assessments on responses from members of our Scout Panel (found when auto-recruiting for a study). The results of a Scout’s quality determine whether they get paid for their submission. When scoring responses, Dscout assesses the following: * **Expressiveness:** The quality of open-ended responses, including grammar and response length (unless a character limit has been applied by the researcher). * **Video response quality:** The audibility, clarity, and more of video responses. Additionally, the length of submitted videos compared to the length requested by the researcher. Participant responses that **fail** these assessments are rejected. The participant will not be paid, they will not count toward your participant limit, and their response will not be displayed during analysis. Participant responses that **pass** these assessments are shown on the **Responses** tab of your study. You have seven days from the time the response was received to review it yourself. After those seven days, the participant will be paid. If you suspect a response is low-quality, you may report it. For more information, see [Exclude responses from a media survey](/media-surveys/analyze-a-media-survey/exclude-responses-from-a-media-survey.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 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/media-surveys/what-are-media-surveys-in-dscout/response-scoring-in-media-surveys.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.