# Options Options are a pre-defined list or group of possible responses. Follow the [SF.gov style](https://app.gitbook.com/@sfdigitalservices/s/style-guide/), unless you are using a list of defined options that users are already familiar with, like Types of construction for building permit applications. Use a space between numbers and words. Avoid hyphens. | Do | Do not | | --------------------- | --------------------- | | 27: 1 Family Dwelling | 27: 1-Family Dwelling | ### Other Consider using Other as often as you can when giving users a predetermined list of options. This builds trust with our users. Every time we push users into something that doesn’t fit their situation, we lose their trust. We ask them to lie to us or give us the wrong information. Using Other as an option lets users make the form fit them. It allows them to answer the question without making them lie. Using Other makes data collection messier, but offering it as an option can allow users to tell us their truth. For example, always include more options that just “male” and “female” for gender, so that people who don’t fit those categories are included in the form. --- # 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://sfdigitalservices.gitbook.io/style-guide/how-to-write-forms/options.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.