Plan the weekly timetable

This guide is for the person who plans the week's sessions and wants them well used. It describes a weekly cycle in four steps — review last week, build next week, release it, and adjust it as bookings come in — and the limits to plan around. The setup of a calendar and the Generate dialog itself are described in Schedule appointments and generate sessions and Generate sessions.

The examples use an invented studio: a room calendar Studio 1, and two sessions linked to it, Morning flow (60 minutes, 14 places) and Yin evening (75 minutes, 12 places). Each level or format you offer — for example a beginners' and an advanced class — is its own session with its own length, places and price; its name is how the level shows in the scheduler, on the booking site and in Analytics.

Before you start

• Each session is linked through Dependencies to the calendar it runs on, and that calendar is selected in the scheduler — see Prepare a calendar for group sessions.
• Your user has Configuration & settings set to Manage (to generate sessions, change a session's capacity and visibility, cancel sessions and mark no-shows) and either Organisation set to Manage or Manage on the calendar's resource under Resources (to save sessions on that calendar). For the review step you also need Analytics set to View. Without Organisation: Manage or Manage on the calendar's resource, the next sync is refused, go flow signs you out and the changes not yet synced on this device are lost — see What each right opens.
• You know the session settings each generated session copies or uses: Slot capacity, Slot duration (minutes), Slot price, Min capacity and Reservations possible — see Resource details.

1. Review last week

In the scheduler. Select the calendar, choose Week and go back one week. Switch on the Occupancy heatmap: sessions at the open end of the colour scale had places left, sessions at the full end sold out. An hourglass with a number on a session shows clients who were still waiting for a place — demand beyond the capacity you offered. The heatmap reflects the sessions as they are now: cancelled bookings, waitlist entries and participants you marked as no-show do not count as booked.

In Analytics. Open Analytics > Overview and choose last month as both Start date and End date. Each row is one booking, named "calendar - session" (for example "Studio 1 - Morning flow"), with the places booked (Actual) and the session's Capacity. Filter by resource and use Export to Excel to compare weekdays, start times and formats — go flow has no built-in report by weekday, time or format. Over a longer period the rows become monthly totals per calendar and session. Keep in mind:

• Only active bookings in active sessions count; cancelled bookings, waitlist entries and no-shows are left out.
• A session without any booking does not appear at all, so its places are missing from Capacity and Actual against Capacity overstates utilisation. Look up empty sessions in the scheduler.
• In the single-month list, the session's capacity repeats on every booking row of that session; count it once per session.
• Analytics does not tell private classes from public ones: a class reserved for a group counts like any other. Note the classes with the Private badge in the scheduler's Week view and judge them separately.
• Time without a class has no figures, and go flow records no enquiries or group requests apart from the waitlist. Keep those in your own notes and count them as separate evidence.

How to read these figures is explained in Analytics.

2. Build next week

1. In the scheduler, select only the calendar you are planning, choose Week (or Work week) and move to next week. In Set status display, keep Created and Active ticked, and keep Waitlisted only off — Generate only recognises the sessions the calendar shows.
2. Click Generate, choose the first session (for example Morning flow) and set Visibility & bookability. For a weekly series, Bookable days before is the usual choice: with 14, each class opens two weeks before its own date.
3. Add one schedule row per start time and tick its days — for example Monday to Friday at 07:00, and Saturday at 09:00 in a second row. Untick days that have already passed. Save.
4. Repeat steps 2 and 3 for each other session (for example Yin evening). One run creates one session for one week; there is no copy-week or term function.
5. Check the result. The new classes are Planned (dashed outline). A slot that already held a session on this calendar was skipped without a message, so compare the calendar with your plan. Add a single extra class by dragging the session's chip onto the grid, move a class by dragging it, and remove one with the cross.

To prepare several weeks, move to the following week and repeat. A planned class cannot be opened, so its own capacity can only be changed once it is active; its visibility and bookability can be changed before that with Apply to selected in the Generate dialog. A class that opens on a later date cannot be booked before then, so after activating it you can still adjust it in Edit a session.

Early access and closed groups. To let members book before everyone else, generate with Restricted, the Eligible groups and a later opening date, and add early-access tiers (Promotions module) — see Session visibility & bookability. For a class reserved for a private or corporate group, see Run a group or corporate class.

3. Release the week

1. Click Activate all. It activates the planned sessions currently shown; to release several prepared weeks at once, switch to Month first.
2. Check what clients see. On the booking site, a Public class that is Bookable now can be booked at once; a class that opens on a later date is listed as coming soon with its opening date, and eligible early-access members can book it ahead; Hidden classes are never listed, and Private or non-eligible Restricted classes show as locked cards. Classes further ahead than the session's Reservations possible are not listed yet.
3. Open the booking template's customer page, go to the released week and open a class to check its date, time, price and free places. An empty week usually means the classes are still planned, lie beyond the booking horizon, or the template does not include the session — see Set up online booking.
4. Brief the team: print the week from the Week view, or use Agenda for the participants (Print prints the current view).

4. Adjust as bookings develop

Look at the coming days with the heatmap, the hourglass counts and Waitlisted only; the Agenda view shows who is booked and who is waiting.

• Full with a waitlist. Raise the class's Slot capacity in Edit a session — places freed or added are offered to waiting clients first, automatically — or add another class with a chip or Generate.
• Weak uptake. Lower the capacity (never below the places already booked), move the class to a better time by dragging it, or run a last-minute pricing rule — see Run a promotion or discount code. An unbooked class can be removed with the cross.
• Moving a booked class. Its participants, capacity and settings move with it and their reminders follow the new time, but no message is sent; tell them with Message clients in the participant list.
• A different level or length. A class keeps its session — its name, length and price — and cannot be switched to another session or resized. Add a class of the other session with its chip or Generate. Remove the old class with the cross once nobody is booked in it; move booked participants one at a time first, see Move a client to another session.
• Below min capacity. A warning dot appears while bookings are under the session's Min capacity. It is information only — go flow does not cancel the class; you decide.
• A class cannot run. Follow Handle a disruption before you change or cancel anything.

Judge a change afterwards. go flow keeps no planning notes and no record of how a class filled up over time, so write down what you changed, when, and the result you expect. The participant list's Created column shows when each place was booked: count the places booked before and after the change, or compare how early two classes filled. Account > My activity shows when you changed a class.

Limits to plan around

• One week, one session per run. Generate covers the week shown and one session; there is no copy week, no term and no series that continues on its own.
• Planned is the only draft. There are no saved alternative layouts to compare. Planned sessions are visible to your colleagues in the scheduler (never to clients), and an activated session cannot be returned to Planned. go flow makes no demand forecast: the heatmap, the waitlist counts and Analytics show bookings only, so keep your own estimates apart from them.
• No teacher on a dated class. A class belongs to one calendar — the resource it was generated on. go flow records no second resource on it, such as a teacher or equipment, so who teaches is planned outside go flow, or you use the teacher's own calendar as the class calendar. go flow has no staff rota either: who covers the desk, the classes and other duties on a day is planned outside go flow.
• No room or staff conflict check. Generate only skips slots that already hold a session on the same calendar. Dropping a chip or dragging a class is not checked, one-to-one appointments in the slot do not block a class, other calendars are not compared, and there are no changeover buffers. Dependencies only links a session to its calendar. To spot clashes yourself, select the calendars involved and use Group resources (desktop) to see them side by side; select only the class calendar again before you generate. Out-of-office on a resource does not stop Generate or the booking of classes on its calendar: while a room or piece of equipment is unavailable, do not generate there, and set classes already generated to Not bookable or Hidden.
• No price per class. Every class is charged the session's Slot price; a change applies to all its classes for new bookings. Use pricing promotions for cheaper times.
• Moving a class keeps its capacity. Moving it to another room's column does not adopt that room's size; change the capacity in Edit Session.

If the result is not what you expected

What you see	What to check
Generate is missing or disabled	The calendar prerequisites, and the Week or Work week view.
Generate created nothing or too little	The slots already held sessions on that calendar, or the days lie outside the week shown (in Work week, before your first or after your last working day).
Classes appear twice	Sessions were hidden by Set status display or Waitlisted only while you generated. Remove the extra unbooked classes with the cross.
Classes missing on the booking site	Still Planned, Hidden, beyond Reservations possible, or the template does not offer the session.
Nobody can book	The class is Not bookable or Private, its opening date lies ahead or was left empty, or it is Restricted to groups the client is not in.
You were interrupted and are not sure what you already did	Account > My activity lists your own saves, newest first; sessions generated together show as one row with a count. Changes still waiting on this device (cloud icon with "!") are not listed yet. Dashed classes in the scheduler are still Planned.