A request form is not a confirmed appointment. Design the page, message and staff handover around that distinction so a patient knows what has happened and the clinic knows what to do next.
Start with the workflow, not the fields.
Write down where a request goes, which team reviews it and how a time is agreed. If a receptionist contacts the patient later, the button should say "Request an appointment", not imply a confirmed slot. A live booking system can confirm a time only when that is what it actually does.
Choose one clear route for each branch. If all requests go to central reception, say so. If the visitor must select a branch, use names a patient recognises and keep that choice near the start. Do not make staff infer the branch from a free-text message.
Ask for the minimum needed.
W3C recommends short, simple forms and asking only for information needed to complete the process. Have the clinic decide which contact details and scheduling preferences it genuinely needs. Do not copy a full medical intake form into a marketing page just because a template includes one.
Put a reason beside every proposed field: who uses it, when and what happens if it is missing. Remove fields with no clear purpose. Arrange appropriate privacy and security review for collection, storage and the services receiving the information. This checklist does not establish legal compliance.
Make labels and errors usable.
Use visible labels that remain after typing starts. Explain required fields and format rules before submission. W3C describes associating labels with controls, giving instructions and providing feedback. Placeholder text alone disappears when the person starts typing.
If a contact detail is rejected, name the field and explain how to fix it. Do not rely only on a red border. Preserve other entries where safe. Ask the developer to demonstrate keyboard operation and how assistive technology is informed of errors.
Write an honest confirmation.
State whether a request was received and what happens next. Agree any published response expectation with reception; do not invent a promise on their behalf. A message should not say an appointment is confirmed unless a time has actually been booked.
Example wording for clinic review: "Your appointment request has been received. Our reception team will contact you to agree a time. Your appointment is not confirmed yet." Add only approved service instructions and verified contact details. Do not use an ordinary enquiry form for urgent clinical advice.
Test receipt, not only the green message.
A page can show success while a notification reaches an unused inbox. Test the complete route in staging or with a clinic-approved labelled test. Do not submit invented patient symptoms into live intake. Verify who received it, whether the branch choice survived and whether staff can follow up.
Check an empty required field, an invalid contact detail, a valid request and a server failure. Agree how duplicate clicks are handled. Test both what the patient sees and what reception receives. Our mobile contact checklist covers the wider contact journey.
Appointment-request acceptance record
- Record the exact page URL, branch and intended reception team.
- List required fields and the reason for each.
- Check keyboard access, persistent labels and useful correction messages.
- Record the approved test identifier, confirmation and receiving system.
- Confirm failed submissions do not falsely claim receipt.
- Name who approves privacy handling, wording and staff response.
Source notes
Platform guidance checked 18 October 2026. Checklists are Wellfront recommendations, not ranking, booking, clinical or legal guarantees.