# 4.3.8 Asking users for information Clearly state why you need the information and how it will be used. For instance, you might need users' information so that you can provide a service, register them for a service, or tailor an experience to meet their needs. Consider whether you need to ask for the information or whether you can use integrations to get that data from internal or external sources. Check whether you need to ask for [consent](https://docs.google.com/document/d/1kjLic18ifk_MpcGdHBFBhKA0OlYCLrynF23-9qr7s-U/edit#heading=h.vyy08tdvrne0) to ask the questions. You can use a [question protocol](https://www.uxmatters.com/mt/archives/2010/06/the-question-protocol-how-to-make-sure-every-form-field-is-necessary.php) to help you figure out what you need to ask.\ \ If you ask people for optional information, add ‘(optional)’ to the question. Do not mark mandatory questions with asterisks as these are not accessible. #### Question page

**Backlink** A question page should have a backlink to help users who may want to go back to the previous question to make any changes. **Question or question heading** When asking people for information, ask for one thing at a time. Helps users focus on one specific thing at a time and provide its answers without overwhelming them with too many demands at once. This can be one question per page or group-related questions together, for example, contact details. Grouping related questions together can help users understand the context of each question and make it easier to provide accurate responses. When you group related questions together, you will have a ‘question heading’ that will help people understand what is needed for the set of questions. **Hint text** Provide clear instructions to help users understand what is expected of them on each question. **Question field** Use the appropriate question field for the different question types. **Other ways to provide information** Always provide other alternative mechanisms for users to identify themselves or provide their information so that they can access your service.\ Provide clear instructions on what to do if they encounter any problems. --- # Agent Instructions: 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: ``` GET https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.12-asking-users-for-information.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.