Booking Launch Checklist

Use this checklist before opening a booking flow to customers and after changes to schedules, resources, forms, checkout, or customer access.

Prepare a controlled test

Work on staging where possible, use an inbox you control, and use gateway test/sandbox credentials for online payments. Check active notification recipients before creating a reservation. Keep a record of test booking references so they can be cleaned up or cancelled deliberately.

Offering and availability

• Confirm the offering is published with the intended public title, content, and timezone.
• Check at least one future session and verify recurrence in the preview.
• Confirm ticket/service price, quantity, and booking method.
• For resource-based services, test assignment, working hours, exceptions, capacity, and buffers using the availability guide.
• Check the generated offering page and any separate embedded booking page; they are different presentation paths.

Customer journey

1. Open a private browser window and choose a session and option.
2. Complete required booking and participant fields. Test a missing required answer and both branches of a conditional field.
3. Check the displayed total, coupon behavior if used, and intended payment route.
4. Submit a free/offline reservation or complete a sandbox payment.
5. Record the booking reference and check the completion page.
6. Verify the customer can reach the configured portal and only their authorized booking data.

Administrator journey

Open DayTidy → Bookings and reconcile the saved session, quantities, customer answers, resource, total, and both statuses. Confirm the resulting capacity behavior with a second controlled request. Do not assume a payment is collected merely because a reservation is confirmed.

If operationally relevant, test rescheduling and cancellation on the test booking. Treat refunds as a separate action. Inspect intended message recipients and, with Pro operations enabled, delivery logs and reminder jobs; accepted mail is not proof of inbox delivery.

Release the configuration

Resolve essential failures before accepting customers. Remove unintended test content, restore any deliberately changed test settings, and switch payment configuration to live only when the business is ready. Recheck public pages after deployment, caching changes, or domain changes. Keep a current backup and follow update and recovery guidance for later maintenance.