A person arranging a first appointment may have practical questions before they can choose a time. They might need step-free access, prefer a quieter part of the day or be unsure whether the request will actually reserve an appointment.
We designed our first-consultation website around that uncertainty. The explanatory page and the appointment request are separate, so someone can understand the process before beginning the form.
This article concerns that administrative experience. The practice's clinical team must decide the care information, instructions and handling requirements that a live website uses.
Explain the visit before collecting the details
The first-visit page follows three stages: before arrival, at the practice and after the conversation. Each answers a practical question at the point the visitor is likely to ask it.
Before arrival, the page explains that the practice would confirm availability and tell the person what to bring. It invites access and communication preferences. The later sections explain that questions and proposed next steps can be discussed at the practice.
That content has a different job from the form. Moving it all into introductory text above the first input would make the request longer without necessarily making it easier to understand. A separate page lets someone read and return when they are ready.
Ask for a preference without presenting it as a promise
The appointment request offers a first available practitioner as well as a named preference. One practitioner is explicitly unavailable in the example week. The form explains the limitation beside the choice and suggests selecting first available or mentioning a later date.
This is a small but meaningful interaction. The visitor does not have to submit a request before discovering that their preferred option cannot work. They can make an informed choice while keeping the request open for staff review.
Ask for preferences without implying a booking
Preferred day and morning, afternoon or flexible timing serve the same purpose. They help the practice discuss a suitable appointment; they do not create a reservation.
Give practical needs a clear place
The sample request mentions a quieter appointment time and step-free access. Those details are relevant to arranging the visit. They should not be hidden in a field labelled as a clinical history, nor should the design ask for extensive sensitive information without an agreed reason.
For each field, the practice should be able to identify who needs the answer and what they will do with it. That exercise often separates information needed for the initial request from information collected later through the appropriate care process.
Use persistent labels and explain corrections near the relevant field. W3C's form-label guidance covers those accessibility foundations.
Keep administrative readiness separate from clinical judgment
Our referral completeness workspace deals with records and outstanding paperwork. Its register helps a team inspect the handover; it does not determine clinical priority.
The distinction is easy to blur with a green completion indicator. A person may have supplied every requested item while a professional assessment is still required. The document collection guide explains why the next stage should be named rather than implied by a tick.
Before the appointment
- 01ExplainLet the person read the approved visit information.
- 02RequestCollect only the agreed administrative details.
- 03RespondState the actual next step without implying a clinical decision.
Describe who responds and what happens next
The consultation form finishes with a short sequence: the team reviews the request, discusses a suitable appointment and confirms the details before the visit. This answers a more useful question than a generic ?thank you?: what has the submission started?
For a live service, agree the wording with the receiving team. The channel's purpose, monitoring and alternative contact instructions must match its actual operation. Do not use a confirmation message to suggest a booking or assessment that has not occurred.
Our enquiry handoff article follows the operational side of that process. The lead follow-up guide covers assignment and later contact, which need the practice's approved communication rules here.
Explain the first visit before starting the form
We scope this work through web engineering, reviewing the explanatory content, form and staff destination together. The practical aim is to help someone ask for an appointment without being left to guess what they have committed to or what the practice needs from them next.
Sources and calculation notes
The project observations come from our original page files, project records and anonymised screenshots. Recommendations describe how we would scope and review the workflow; they are not claims of deployed integrations or measured business outcomes. No numerical benefit is asserted.
- Our practice and first consultation project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- Our referral completeness workspace project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- W3C form labels. Supports visible, associated labels for form controls.
External references checked on 31 October 2026.