A form should collect enough information to process a request without making the applicant repeat themselves or guess what a question means.
Plan the questions (link to section)
For each question, identify who uses the answer and what they do with it. Remove questions that have no role in the process.
Group related questions on pages. For a Lakeview event request, contact details, event details, and supporting files may be separate groups.
Write clear labels and help (link to section)
Use a visible label that names the information you need. Put format guidance or an example in help text rather than using a placeholder as the only explanation.
| Instead of | Use |
|---|---|
| Name | Applicant’s full name |
| Details | Describe the activities planned for your event |
| Attachment | Upload your insurance certificate |
Ask one thing at a time. Keep instructions close to the question they explain.
Set required fields carefully (link to section)
A required field prevents the applicant from continuing without an answer. Use it when the answer is needed to process the request, rather than because the information could be useful later.
Choose a question type that matches the answer. For example, use a number question when a booking rule needs to compare attendance with a space’s capacity.
Check conditions and references (link to section)
When a route, booking rule, notification, or document uses an answer, check that it points to the intended question.
Renaming or removing a question can affect the parts of the service that refer to it. Review the whole draft after structural form changes.
For booking forms, questions used to calculate a price must appear before the booking page that reads them. See Create a booking service.
Preview as an applicant (link to section)
Before review, try the form with fictional answers:
- Leave a required question blank and check that the error explains what to do.
- Try each branch or conditional question.
- Use long names and realistic descriptions.
- Check the form on a narrow screen.
- Review file instructions and the service’s privacy wording.
- Confirm the route can use all the answers it expects.
Continue to Review and publish when the form and route agree.