> For the complete documentation index, see [llms.txt](https://loggix.gitbook.io/indephr-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://loggix.gitbook.io/indephr-docs/publishing-and-sharing-structure/best-practices-for-distribution.md). # Best Practices for Distribution ### Overview How you distribute your survey plays a critical role in determining response rates and the quality of feedback you receive. Even a well-designed survey may perform poorly if it is not shared effectively. This page outlines practical best practices to help you reach the right audience, encourage participation, and collect meaningful responses. *** ### Choose the right audience Ensure that your survey is shared with people who are relevant to your objective. * Target respondents who have the experience or knowledge needed * Avoid sending surveys to a broad but unrelated audience * Use recipient management when specific targeting is required Relevance improves both response quality and engagement. *** ### Provide clear context Before sharing your survey, explain its purpose clearly. * Tell respondents why the survey is being conducted * Explain how their feedback will be used * Set expectations about the outcome When respondents understand the purpose, they are more likely to participate. *** ### Keep communication simple and direct When sharing your survey: * Use a short and clear message * Avoid unnecessary or complex explanations * Include only essential information A simple message increases the chances of engagement. *** ### Set expectations for time Let respondents know how long the survey will take. * Short surveys (2–5 minutes) tend to have higher completion rates * Clearly communicating time helps respondents decide quickly This reduces drop-offs and incomplete responses. *** ### Share at the right time Timing can significantly impact response rates. * Choose a time when your audience is most likely to engage * Avoid sending surveys during busy or irrelevant periods * For professional audiences, consider working hours Proper timing increases visibility and participation. *** ### Follow up when needed Not all recipients will respond immediately. * Send reminders to those who have not completed the survey * Keep follow-up messages polite and concise * Avoid sending too many reminders Thoughtful follow-ups can significantly improve response rates. *** ### Build trust with transparency Indephr allows you to share summaries and action plans with respondents. Use this to build trust. * Inform respondents that their feedback will lead to actions * Share outcomes after analysis * Show that their input has value This encourages future participation and engagement. *** ### Avoid over-surveying Sending too many surveys can reduce engagement. * Limit the frequency of surveys * Ensure each survey has a clear purpose * Respect respondents’ time A focused approach leads to better quality responses. *** ### Monitor and improve After sharing your survey: * Track response rates * Identify patterns in participation * Adjust your approach based on results Continuous improvement helps you get better outcomes over time. --- # 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://loggix.gitbook.io/indephr-docs/publishing-and-sharing-structure/best-practices-for-distribution.md?ask=&goal= ``` `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.