> 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/reservations/seasonal-courts-or-contracted-courts.md).

# Seasonal or Contracted Courts

### Overview

A Seasonal Court or Contracted Court (sometimes called a Timeshare Court) is when a Customer pre-pays for a court on a specific day and time for several weeks or months into the future. Clubs offer these to lock in predictable revenue and let a Customer secure a standing slot that would otherwise be limited by the Booking Horizon.

There are two ways to set this up: an Admin books each week as a standalone Reservation, or an Admin creates a single Event as a Series. The right choice depends on whether the Customer needs to invite different groups of friends to different weeks.

### Admin Books Reservations

An Admin can book as far into the future as needed for a Customer, bypassing the Booking Horizon. Because each booking is a standalone Reservation, the Customer can invite a different group of friends to each one. The Reservation Holder can invite one group to the week 3 Reservation and a different group to the week 4 Reservation.

Use this method when the Customer wants flexibility over who joins each week.

To set it up:

1. Charge the Customer inside their Profile for the total value of the Contracted/Seasonal Courts.
2. Book each Reservation for the Customer using the FREE booking option.
3. Notify the Customer they can invite their friends from inside the App using the `Invite` button.

Once the Reservations are booked, the Reservation Holder invites friends to each one individually through the App.

### Events as a Series

An Admin can book an Event as a Series, creating a single Event with all Sessions connected. The Customer is added to the first Session and populates across every Session in the Series.

The Customer cannot invite different groups of friends to different Sessions. Once a Customer is added to a Series, they populate across all Sessions in it. Everyone who joins the Series appears in every Session.

To set it up:

1. Charge the Customer inside their Profile for the total value of the Contracted/Seasonal Courts.
2. Create an Event as a Series on the preferred day and time.
3. Add Sessions to the Series for as far out as needed.
4. Add the Customer to the Series.
5. Generate a signup link.
6. Send the signup link to the Customer to share with their friends.

Once the Series is booked and the Customer is added as an Attendee, they see every Session in their App. To bring friends, the Customer shares the signup link the Admin provided.

{% hint style="warning" %}
**A Series does not enforce a per-Session player cap.** If the Club allows only 4 players per Session and different groups join the Series, 6 or more people can end up in a Session. The Admin should remind the Reservation Holder to keep each Session within the Club's player limit.
{% endhint %}

### Choosing Between the Two Methods

|                                   | Admin Books Reservations                               | Events as a Series                              |
| --------------------------------- | ------------------------------------------------------ | ----------------------------------------------- |
| Structure                         | Standalone Reservations, one per week                  | One Event with connected Sessions               |
| Invite different friends per week | Yes, each Reservation is invited separately            | No, Attendees populate across all Sessions      |
| How friends are added             | Reservation Holder uses the `Invite` button in the App | Customer shares the Admin-generated signup link |
| Per-Session player cap            | Controlled per Reservation                             | Not enforced, Admin must monitor                |

### Timing of Charge and Discounts

For both methods, charge the Customer inside their Profile for the full value of the Contracted/Seasonal Courts before booking, then use the FREE booking option so they are not charged again.

Whether the Customer receives a discount is entirely the Club's choice. A Club might offer a discount to pull revenue forward into the immediate future. A Club might charge full price because it is already giving the Customer the benefit of bypassing the Booking Horizon to secure a preferred day and time. Either approach is valid.


---

# 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/reservations/seasonal-courts-or-contracted-courts.md?ask=<question>&goal=<endgoal>
```

`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.