> ## Documentation Index
> Fetch the complete documentation index at: https://docs.witt-play.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule a recurring game series on Witt & Play

> Create weekly, biweekly, or monthly game series in one step. Each session is independent with its own roster, chat, and RSVPs — up to 12 per series.

A recurring game series lets you schedule multiple sessions of the same game in one form submission. Instead of creating each session manually, you set a start date, a repeat interval, and a session count — and Witt & Play generates all the sessions at once. Each session is fully independent, so players RSVP separately to each one and hosts manage each roster on its own.

## Setting up recurrence

Recurrence is configured in the **Make this a recurring game?** section of the game creation form. It is off by default.

<Steps>
  <Step title="Choose a repeat interval">
    Select how often the sessions repeat:

    | Option        | Interval                |
    | ------------- | ----------------------- |
    | One-time only | No recurrence (default) |
    | Weekly        | Every 7 days            |
    | Every 2 weeks | Every 14 days           |
    | Monthly       | Every 30 days           |

    The repeat interval is applied from the start date you set. For example, if you pick **Weekly** and set the start to Saturday at 10:00 AM, the sessions fall on consecutive Saturdays at the same time.
  </Step>

  <Step title="Set the number of sessions">
    When any repeat option other than **One-time only** is selected, a **Number of sessions** field appears. Enter a number from **2 to 12**. This is the total count including the first session — if you enter 4, you get sessions on weeks 1, 2, 3, and 4.

    <Note>
      The maximum is 12 sessions per series. If you need more, create a second series when the first one ends.
    </Note>
  </Step>

  <Step title="Submit">
    Click **Post the game**. All sessions are created at once. You are redirected to the first session's game detail page. A success toast confirms: *"Created X sessions! Time to round up players."*
  </Step>
</Steps>

***

## How sessions are structured

### Independent game records

Each session in a series gets its own unique game ID. This means:

* Players must **RSVP to each session individually** — approval for one session does not carry over to others
* Each session has its own **chat thread** with its own message history
* Each session has its own **roster** of approved, pending, and waitlisted players
* You can **edit or cancel a session** without affecting the others

### Series grouping

All sessions created together are linked as a series. This grouping is used to connect related sessions in the platform — you don't interact with it directly, but it's what ties recurring sessions together.

### What is shared across the series

All sessions in a series inherit the same values from the form at creation time:

* Title
* Description
* Sport and category
* Location
* Skill level
* Accessibility tags
* Max players
* Reimbursement per player
* Privacy setting
* Notes

You can edit any of these per-session after creation using the **Edit** button on the game detail page.

***

## Player RSVPs per session

Because each session is a separate game record, players must request to join each session independently. There is no "subscribe to series" feature — a player approved for session 1 is not automatically included in session 2.

<Info>
  This design keeps each session's roster fresh. Players opt in to the specific sessions they can make, which gives you an accurate headcount per session rather than a stale sign-up from weeks ago.
</Info>

When you approve a player for a session, they receive notifications for that session only. If the same player requests every session, you will see a separate pending request per session in the Host Console.

***

## Managing a series

There is no bulk-edit tool for a series. To update all sessions — for example, to change the location or time — you need to edit each session individually using the **Edit** button.

To end a series early, cancel the sessions you no longer want to run. Cancelling one session does not affect the others.
