1. List common tasks before a visit
Collect questions people ask before contacting the clinic: which services are available, where it is, how a visit is requested and what to know beforehand. Confirm answers with the clinic instead of inferring them from old pages.
Separate general information from questions requiring an individual assessment. The website can point to the right contact without assessing someone’s health itself.
2. Assign an owner to each claim
Create a register with the topic, reviewer, last approval date and event that triggers another review. Clinical information needs a named role able to confirm it.
Remove wording that implies guaranteed results or universal suitability unless it is supported and approved. Do not turn a possible outcome into a promise.
3. Review forms and booking journeys
Map what a visitor sees before and after sending a message. Verify the recipient and confirmation for both inquiries and appointment requests.
Before collecting health details, the clinic should assess purpose, data minimisation, channel, access and retention. If that review has not happened, ask for less and show an approved contact route.
4. Test real visitor tasks
Ask someone outside the clinic to find a relevant service, understand how to request a visit and locate the contact for a practical question. Repeat on mobile and using a keyboard.
Then have the clinic’s owners review facts, accessibility and links. Record decisions and open questions so future edits start from a reliable baseline.
| Content | Responsible check |
|---|---|
| Service description | Clinic confirms scope and clinical wording |
| Booking | Owner checks recipient and status |
| Visit information | Named owner confirms location, hours and instructions |
| Form | Clinic assesses data, access and retention |