> 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/creating-surveys/structuring-your-survey.md). # Structuring Your Survey ### Overview Structuring your survey is an important step in ensuring that respondents can easily understand and complete it. A well-structured survey improves response rates, reduces confusion, and results in more reliable data. In Indephr, organizing your questions thoughtfully helps create a smooth and engaging experience for respondents. *** ### Why survey structure matters A poorly structured survey can lead to: * Confused or incomplete responses * Lower completion rates * Inconsistent or inaccurate data A well-structured survey, on the other hand, helps respondents move through questions naturally and confidently. *** ### How to structure your survey effectively To create a clear and logical survey, follow these guidelines: *** #### Start with simple and general questions Begin your survey with easy-to-answer questions. This helps respondents feel comfortable and encourages them to continue. Avoid starting with complex or sensitive questions. *** #### Maintain a logical flow Arrange your questions in a sequence that makes sense. * Group related questions together * Follow a natural progression of topics * Ensure each question connects logically to the next This creates a smooth experience for respondents. *** #### Move from general to specific Start with broader questions and gradually move toward more detailed or specific ones. This helps respondents build context before answering more complex questions. *** #### Keep similar question types together Avoid frequently switching between different question formats. Grouping similar types of questions helps maintain consistency and reduces cognitive effort for respondents. *** #### Limit survey length Keep your survey focused and avoid adding unnecessary questions. A shorter and more relevant survey: * Increases completion rates * Improves response quality *** #### Avoid repetitive questions Ensure that each question adds value. Repeating similar questions can frustrate respondents and reduce engagement. *** #### Place sensitive questions carefully If your survey includes sensitive or personal questions, place them later in the survey after trust has been established. *** ### Organizing sections (if applicable) If your survey is longer, consider dividing it into sections based on topics. This helps respondents: * Understand the structure of the survey * Stay focused on one topic at a time *** ### Reviewing your survey Before publishing your survey: * Read through all questions in order * Check for logical flow and clarity * Ensure there are no duplicate or unnecessary questions * Confirm that the survey aligns with your objective A final review helps identify issues before sharing the survey. --- # 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/creating-surveys/structuring-your-survey.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.