01Where does the policy appear?
Map the places a visitor can book: a service page, a team member's profile or a final booking button. A summary only on Home may be missed by someone arriving on a service link. Place the same approved summary beside the relevant action and link to one readable full version, rather than copying different paragraphs across the site.
In the quoteList the agreed booking-entry pages and summary placements. Your booking platform's settings remain yours; provider configuration is not assumed in website scope.
02Does the site match the booking platform?
Check the same example through both paths: a customer cancels, arrives late or wants to change a session. The website, provider screen and reschedule instructions should describe the owner's existing terms consistently. Record who can approve a change and which version is authoritative before publishing it.
In the quoteSupply the approved wording and current provider links. The brief identifies a single content owner; drafting terms, enforcing fees and changing payment settings are not included.
03Can someone reschedule without booking again?
A returning customer has a different task from a first-time visitor. Show the existing provider's change-booking route or the business's approved contact method. If an exception requires a conversation, say who to contact instead of suggesting the website can grant a refund, waive a fee or alter a booking.
In the quoteAgree the supplied rescheduling instructions and exception contact. Copy presentation and any later policy updates are defined in writing; no reminder, refund or booking automation is implied.