Booking forms · Australian checklist
What should an online booking form ask?
Ask for enough detail to make the booking useful. Do not turn the first step into a long intake form.
Short answer: most local service booking forms need a name, one reliable contact method, the service or job type, a preferred time, and only the location or notes needed to do the work. Every extra field needs a clear reason. Keep sensitive details, marketing permission and long intake questions out of the basic booking unless they are genuinely required.
A booking form has one main job: help a customer ask for the right service at a time the business can handle. A shorter form is not always better. A form that leaves out the address for an on-site job can create a phone call and a delay. The aim is to collect the smallest useful set of details.
This guide gives a practical starting point for Australian local service businesses. It is general information, not legal advice. Privacy Act coverage can depend on your turnover, industry and activities, so check the current guidance for your business.
The essential booking form fields
Start with the booking outcome. What must the team know to confirm the time, find the customer and deliver the service? The answer will differ for a salon chair, a home visit and a quote request.
| Field | Why it may be needed | Good form rule |
|---|---|---|
| Name | Identifies the booking and lets staff greet the customer. | Ask for the name the team will use. A title or middle name is rarely needed. |
| Phone or email | Lets the business confirm a change or send booking details. | Choose one main contact method. Do not force both unless the workflow needs both. |
| Service or job type | Sets the likely duration, price path, staff skill or next step. | Use clear customer words. Separate a firm booking from a quote request. |
| Date and time | Shows when the customer wants the work. | Offer only real times, or label the choice as a request that still needs confirmation. |
| Location | Needed for mobile or on-site services. | Skip it for work at your premises. Ask for a suburb first if that is enough to check the service area. |
| Short job note | Helps the team bring the right tools or understand the request. | Explain what to include. Set a sensible length and do not invite sensitive detail. |
Use required fields only for facts that block the booking if they are missing. Everything else can be optional, asked later, or handled during a short follow-up.
Fields to make optional or avoid
Extra fields feel harmless because each one takes only a few seconds. Together, they make the form harder to scan and create more personal information for the business to protect.
- Date of birth: ask only when age affects the service, eligibility or safety.
- Gender or title: do not ask by habit. Use it only when it serves a clear booking purpose.
- Full street address: make it conditional for on-site work. A premises booking may not need it.
- Detailed health or financial notes: move genuine intake needs to a suitable later step with the right controls.
- How did you hear about us? keep this optional and place it after the booking details.
- Marketing opt-in: keep it separate from booking consent. Do not pre-tick it.
- Account password: do not force an account when a guest booking will do the job.
What should the privacy notice say?
Put a short notice near the submit button or the point where information is collected. Do not hide the only explanation in a long policy link.
In plain language, tell the customer:
- which business is collecting the details;
- why the details are needed;
- what may happen if required information is not provided;
- who the information may be shared with, such as a booking platform or payment provider;
- how to read the privacy policy or ask a privacy question; and
- whether information is likely to be disclosed overseas, where that is relevant.
APP 5 sets notification duties for organisations covered by the Australian Privacy Principles. The exact notice depends on the collection and the business. A one-line notice can point to a full policy, but the line still needs to make the purpose clear.
Make the form easy to complete
A good field list can still fail if people cannot tell what each box means. W3C guidance says forms should provide labels or instructions when user input is required. It also says a detected error must identify the item and describe the problem in text.
Accessible form checklist
- Use visible labels. A placeholder is an example, not a lasting label.
- Mark required fields in text, not by colour alone.
- Show the expected format before an error, such as 04xx xxx xxx.
- Name the field in each error and explain the fix. Use “Enter a mobile number with 10 digits”, not “Invalid”.
- Keep keyboard focus visible and the reading order logical.
- Let the page reflow at phone width without a sideways scroll.
- Show a clear success message and repeat the booking details after submission.
Test the form before it goes live
- Book from a phone. Use mobile data and one hand. Note any field that feels hard to reach or understand.
- Leave each required field blank. Check that the error names the field and tells the customer what to do.
- Enter realistic formats. Test an Australian mobile number, a long suburb name, an apartment address and an email with a plus sign.
- Use only a keyboard. Tab through the form and make sure the focus order follows the page.
- Read the collection notice. Confirm it matches what the form actually sends and stores.
- Check the business diary. Make sure the booking appears once, under the right customer, service, time and staff member.
- Change and cancel the test booking. Check that the customer and team see the same current truth.
Where Alice fits
Alice Booking Diary keeps bookings, customer records and staff time in one working view. Alice can also answer website chat and phone enquiries and offer real available times. The business owner remains responsible for checking the booking, availability, price and customer message before relying on it.
Alice is not a reason to collect more. The same rule applies: ask for the details needed to handle the enquiry and booking, then keep the record clear. See the booking diary guide for the wider workflow. If payment is part of confirmation, use the booking deposit decision guide before adding fields or terms.
Frequently asked questions
Should a booking form ask for phone and email?
Not always. Ask for the contact method needed to confirm and manage the booking. If email sends a receipt and phone handles urgent changes, explain why both are required. Otherwise, let the customer choose one.
Should marketing consent be part of the booking?
Keep it separate. A person may agree to booking messages without asking for promotions. Use an optional, unticked marketing choice with clear wording.
Is a preferred time a confirmed booking?
Only if the system checks real availability and confirms it. If a staff member must review the request, label the time as preferred and tell the customer when confirmation will arrive.
Does this checklist make a form Privacy Act compliant?
No. It is a design checklist, not legal advice. Privacy Act coverage and the right notice depend on the business, the information and how it is handled. Check the OAIC guidance and get advice for your situation.
See the booking flow.
Open the Alice demo. Try the diary and booking screens without creating an account.
Try Alice now