A form is a set of fields and controls that collects information or lets someone complete a task. It can be a single search box or a multi-step application. A useful form asks only for information needed for the next decision, explains what to enter, and gives a clear way to submit.
Think of a form like a short conversation at a service desk: each question should help complete the request, and the person should understand what happens next.
Plan for the task
Start with the user’s goal and the data the service actually needs. Group related questions, order them in the sequence people can answer, and defer optional details. A delivery address should not be requested before a user has chosen delivery.
Make controls understandable
Give every field a clear label and place format hints before they are needed. Group related options under a shared heading. If the form has multiple steps, show progress in a way that remains accurate when a step is skipped or added.
Validate without blame
Check input when it can help, but explain a problem in plain language and say how to fix it. Keep valid answers when another field fails. A checkout should not erase a correctly entered address because a postal-code field needs attention.
Confirm the result
After submission, say whether the task succeeded and what happens next. For a request that needs review, say it was received rather than implying it was approved. Keep a reference number or a way to return to the task when follow-up matters. For example, a support request can ask for the issue and a reply address, then request a screenshot only if it is needed. The form should distinguish required details from optional context. On a small screen, keep labels and entered answers visible while the keyboard is open, and make the submit action easy to find without hiding error messages.
Frequently asked questions
Key takeaways
- Ask only for information the task needs.
- Use labels and instructions before a person enters an answer.
- Keep answers when validation finds an error.
- Confirm what happened after submission.