> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/events/event-series.md). # Create a Series ### Series A Series is an Event that spans multiple days. When a Customer signs up for a Series, they sign up for all sessions at once and pay for the entire Series upfront. This is different from copying an Event — copies are independent, while a Series links all sessions together. Use a Series for Leagues, multi-session Clinics, or any programming where you want Customers committed to the full run. #### Create a Series 1. In the Dashboard, highlight the time slot and court for the first session 2. Create an Event and select the Event type 3. Click **Create a Series** at the top right of the side panel 4. Fill in all Event details (name, picture, description, pricing) 5. Click the blue **Book as Draft** or **Book & Publish** button 6. In the new side panel that appears, click **+ Sessions** 7. Add all remaining sessions to the Series 8. Click **Save** The Series icon (triple square) will appear on the Dashboard Overview once saved. #### Edit a Series Click into any session in the Series to open the Series editor. Editable fields include: * Name, picture, and description * Capacity * Courts and tables * Members-only toggle * Member and Non-member pricing * Prorated pricing and late-join window * Scheduling / visibility settings #### Capacity in a Series To change the number of Customers allowed to sign up: 1. Open the Series 2. Go to the **Settings** tab 3. Update the **Total Teams** quantity 4. Click **Save** 5. Select **Apply to all events** in the Series 6. Click **Save** in the pop-up, then **Save** in the side panel Avoid editing capacity after a Series has been published with Customers already signed up. #### Team signup for a Series A team Series lets Customers sign up as a team (for example doubles or a squad) rather than individually. It works the same way as team signup for a single Event, but a teammate who joins is added to the team for **every** session in the Series at once. Setting it up: 1. When creating the Series, open the **Settings** tab on the first Event 2. Set the **Team Size** (players per team, e.g. 2 for doubles) 3. Set **Total Teams** — for a team Series this is the number of **teams** that can join, not the number of players 4. Use **Apply to all events** so every session shares the same team size and total teams Key points: * **Capacity counts teams, not players.** Total Teams of 8 with a Team Size of 2 means up to 8 teams (16 players). * **Team size and total teams are set at the Series level.** Once a team Series exists, these fields are read-only when editing a single session — change them through the Series, not per session. * **The team leader signs up and pays for the team's spots up front**, then invites teammates. A teammate's invitation covers the whole Series. * **Split payment** (if enabled for your venue) lets each teammate pay their own share at the Series rate. The team leader is refunded for that share when the teammate accepts. * If a teammate declines or cancels, their spot is removed from every session and freed for the team. * Team signup for a Series must be enabled for your account — contact your PodPlay CSM if you don't see Team Size on a Series. #### Schedule a Series to publish to Members before Non-members 1. Create the first Event in the Series 2. Click **Create a Series** at the top right 3. Fill in all details 4. Click the **Visibility options** drawer 5. Select **Scheduled** 6. Set the number of days in advance for Members and Non-members separately 7. Review the calculated publish dates 8. Click **Publish**, then **Book and Publish** 9. Add remaining sessions #### Series pricing Set the Series price as the total for all sessions combined. For example, a three-session Series at $10 per session should be priced at $30 — the per-session pricing adjusts automatically. **Unit pricing** (price per individual session) is also available and is useful for discouraging late signups. Set the unit price higher than the per-session breakdown of the full Series price: * A four-session Series costs $40 total ($10/session) * Unit price: $12/session * A Customer who joins after the Series has started pays $12 for each remaining session rather than $10 **Prorated pricing** lets Customers join a Series after it has started at a different price than the full Series cost. Set the prorated per-session rate and optionally set a cutoff date after which no new signups are accepted. #### Non-participants in a Series Normally, adding a Customer to a Series enrolls them in all sessions. Non-participants are the exception — adding a Customer as a Non-participant to a single session of a Series adds them only to that session, not the full Series. This is also how to add a Customer to one session of a Series for a separate charge: 1. Open the specific session 2. Click **Add** in the Attendees section 3. Select **Non-participant** 4. Find and select the Customer 5. Click **Add** Once added, the Customer's name appears in the **Purchases** tab of that session, where they can be charged individually. #### Series FAQs **Can I add a session to a Series after Customers have signed up?** Avoid this where possible. Adding sessions post-publish can cause unexpected errors. Where possible, build the full Series before publishing. **Can an Admin add a Customer to a Series manually?** Yes. Ensure there is space in the Series, then add the Customer as a Regular participant from the Dashboard. The system may take a moment to sync the Customer across all sessions — this is normal. **Why isn't a manually added Customer showing up immediately in all sessions?** The system runs a background propagation job when Customers are added or removed. It takes a few seconds to complete. **A Customer has a confirmation but isn't showing in the Dashboard — what happened?** This is likely a bug. Contact your PodPlay CSM. If a Series was edited after Customers signed up, that may also cause this — let your CSM know either way. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/events/event-series.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.