> For the complete documentation index, see [llms.txt](https://participanthelp.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://participanthelp.dscout.com/getting-started/dscout-overview/best-practices-for-applying-to-studies.md). # Best practices for applying to studies Below is a list of best practices that we recommend when applying to studies. Although we can’t guarantee that these best practices will always result in getting selected to participate in a study, they’ll definitely help improve your chances! ### Be selective, and don’t apply to everything In general, we recommend that you only apply to studies that really interest you or pertain to you. By doing so, you’ll be able to submit more thoughtful answers, which make for better applications overall. **Example**: Don't apply to a study about cats if you don't own a cat! ### Provide structured and thoughtful answers If you only apply to studies that truly interest you, you’ll be able to provide more thoughtful and authentic answers. We score applications in a number of different ways, but organized, well thought-out responses are definitely better than one-word responses and incomplete thoughts. **Example:** A study asks you to describe your cat. A response like “My cat’s name is Boots. He is an American Shorthair. We named him Boots because all four of his paws are black, but the rest of his coat is gray. He has brown eyes and is still very active in spite of his old age” is a far better response than “My cat is old.” ### Follow the directions For each question, please make sure to follow the directions and stay on target. For video and image questions, you’ll be able to view the prompt by tapping View Instructions if you forget what the question is asking. **Example**: In the same study about cats, if asked to take a video of you playing with your cat, be sure you take a video with your cat instead of submitting a selfie-style video where you describe play time to us. ### Be a good camera operator We often ask scouts to provide picture and video responses in applications to studies. If an application to a study includes a media question, making sure that we can see the subject (whether that’s you or something else) and hear you clearly (if it’s a video question) is very important. In general, it’s good to follow these guidelines when using your mobile device’s camera to answer a question: * **Hold your phone steady.** Try not to simulate earthquake conditions. * **Ensure you are well lit and in frame.** We want to see your beautiful face, not just your nose. * **Speak clearly.** A video’s no good if we don’t understand what you’re saying. * **Let your passion show.** If you’re bright-eyed and excited, we’re excited! * **Keep your shirt on.** ***Please.*** * **Don't Dscout and drive**. We're not your mom or anything, but for your own safety and the safety of others, please refrain from recording videos and taking pictures while on the road. We know that recording videos takes more effort and planning than just taking pictures or answering questions. And that's okay! Take the time you need to get settled, collect your thoughts, and answer away! --- # 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://participanthelp.dscout.com/getting-started/dscout-overview/best-practices-for-applying-to-studies.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.