Reproduce the journey on real devices
Test on a small phone, a large phone and a desktop browser. Begin from a landing page, not from a deep link to the form. Record the number of taps, scroll jumps, keyboard obstructions and state resets needed to select a slot.
Practical checkpoint: assign a named owner, preserve a dated baseline and review a sample of at least ten relevant records where volume permits. Document the expected result, the observed result and any exception before approving the next change. For websites/cro, decisions should follow business outcomes and evidence rather than a single platform metric.
Audit calendar and slot behaviour
Try next-month navigation, backtracking, fully booked days, daylight-saving transitions and a slot that becomes unavailable mid-session. Unavailable dates should be clearly distinguished from selectable ones, with a useful explanation where needed.
Practical checkpoint: assign a named owner, preserve a dated baseline and review a sample of at least ten relevant records where volume permits. Document the expected result, the observed result and any exception before approving the next change. For websites/cro, decisions should follow business outcomes and evidence rather than a single platform metric.
Check accessibility and validation
Ensure labels, focus order, keyboard operation, error messages and touch targets are usable. Never rely on colour alone to indicate availability. When validation fails, preserve previous entries and move focus to an understandable summary or field.
Practical checkpoint: assign a named owner, preserve a dated baseline and review a sample of at least ten relevant records where volume permits. Document the expected result, the observed result and any exception before approving the next change. For websites/cro, decisions should follow business outcomes and evidence rather than a single platform metric.
Review time-zone and inventory rules
Confirm that displayed times match the business time zone and the customer's expectation. The server must revalidate availability at submission; client-side calendars are not inventory locks. Provide a clear alternative when a slot is taken.
Practical checkpoint: assign a named owner, preserve a dated baseline and review a sample of at least ten relevant records where volume permits. Document the expected result, the observed result and any exception before approving the next change. For websites/cro, decisions should follow business outcomes and evidence rather than a single platform metric.
Prioritize fixes with funnel evidence
Measure form start, calendar open, valid date selection, slot selection and confirmed booking with privacy-safe events. Segment by device and browser, and pair event data with moderated task observation. Avoid collecting sensitive form contents in analytics.
Practical checkpoint: assign a named owner, preserve a dated baseline and review a sample of at least ten relevant records where volume permits. Document the expected result, the observed result and any exception before approving the next change. For websites/cro, decisions should follow business outcomes and evidence rather than a single platform metric.
Verify a complete booking
Run automated and manual regression tests against booked, empty and conflicting inventory. Verify confirmation emails and calendar entries use the same time and date. Compare confirmed bookings per eligible form start after the change.
Practical checkpoint: assign a named owner, preserve a dated baseline and review a sample of at least ten relevant records where volume permits. Document the expected result, the observed result and any exception before approving the next change. For websites/cro, decisions should follow business outcomes and evidence rather than a single platform metric.