WEBSITE PLANNING

Plan Cancellations and Rescheduling Clearly

Map cancellation and rescheduling states without inventing fees, refund terms or promises your business has not approved.

Start with the owner’s actual decisions

Before designing buttons, ask who can cancel, who can reschedule, which requests need staff approval and what happens to a reserved slot. Any cutoff, fee, deposit or refund term must come from the business and receive appropriate review. This page is a workflow brief, not a cancellation policy. A developer should not fill those decisions with convenient defaults and publish them as if the owner had approved them.

Map a fictional rescheduling request

A fictional customer has a confirmed appointment and requests another time. The worksheet first records reschedule requested, then checks the alternative. If it is unavailable, the original appointment should behave according to an explicit rule agreed by the owner. It must not silently disappear just because the customer opened the change screen. The example does not choose a fee or promise that every request will be accepted.

Keep state changes and notifications separate

For each transition, write the old state, permitted actor, required checks, new state, calendar effect and message to send. Add a repeated-click case: the same cancellation should not generate multiple refunds or conflicting messages. Add an expired-link case with a clear way to request help. Notification failure also needs an owner, because a calendar change and a delivered email are different outcomes.

Review one complete journey

Walk through request, confirmation, change request, approved change and cancellation using synthetic appointments in a staging calendar. Confirm the displayed dates and zones at every step. Google Calendar’s event reference documents its event states and fields; other platforms have their own rules. Bring approved business decisions and the state worksheet to a workflow review rather than asking the website to invent policy.