Block Booking Worked Scenarios in Go Operator

Problem

Staff need to know which create, edit or cancel option to use for common block booking requests in Go Operator, such as term-time bookings, price rises or a customer stopping early.

Resolution

1. Find the scenario and apply its set-up

   Scenario	Set-up
   Same coach every Tuesday for 10 weeks	Weekly → Tuesday, 10 occurrences, per-session price, Whole Reservation (one invoice).
   Community group, first Monday and third Wednesday each month	Monthly → Specific Day → First Monday, Third Wednesday; end at financial year end; Reservation ID for example COMM-GRP-001 for reporting.
   School pool every Friday in term, not half term	Weekly → Friday across the term, then Exclude Date on the half-term week (not a single-date edit).
   Price rise from next month; earlier (including invoiced) dates unchanged	Edit selected date and all future, anchored on the first date at the new rate. Not Edit all bookings in the series.
   Customer stops after a date	Selected date and all future, anchored on the first date to cancel. If any affected date is invoiced, cancel those individually first.
   Moving a whole Tuesday series an hour when Jan–Feb are invoiced and paid	Edit each invoiced date individually (invoiced-occurrence edit), then Edit selected date and all future from the first March date.
   Booked against the wrong contact	No edit path. Cancel (with a reason) and recreate against the right contact; re-enter products, prices and invoicing options.
   Customer wants "no record of it at all"	Cancelling removes current and future dates only; past sessions stay on record. Invoiced dates must be cancelled one at a time first. No undo.

Notes

• Creating: Creating a Block Booking in Go Operator.
• Editing scopes: Editing a Block Booking in Go Operator.
• Cancelling scopes: Cancelling a Block Booking in Go Operator.

This page as markdown · All pages · llms.txt