# Why forms? We use forms when we need to gather information from users to help them get a service or complete a task. A form helps City staff do their jobs by collecting information from users in a structured way that can be delivered electronically. This guide is based on the [US Web Design System](https://designsystem.digital.gov/components/form-controls/). It is a work in progress and will be updated with more examples and guidance. ### User needs focus on what the form filler wants to do. Define the need for the resident or customer. Also define the need for City staff or people who will process the data that comes in from the form (the consumption end point). *As a contractor in San Francisco*\ *I want to get a building permit*\ *So that I can do construction.* *As a permit tech for the Department of Building Inspection*\ *I want to review and approve a permit*\ *So that I meet my deadlines and keep the City building* *As a program manager for the City and County of San Francisco*\ *I want to approve business owners for sick leave reimbursement*\ *So that I can disburse the grants.* --- # 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/why-forms.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.