> 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/play-passes/create-and-manage-package-templates/pass-duration-and-court-booking-limits.md).

# Pass Duration and Court Booking Limits

## Overview

When you configure a **Reservation Pass** or **Guest Pass**, the **Duration** dropdown limits how long one pass covers for a private reservation. If the pass is scoped to specific **courts** or **areas**, the maximum duration follows those courts' booking limits—not only the company-wide **Max Hours per Reservation** setting.

Use this when one location allows longer reservations than others (for example, a 2-hour court cap at one club while the company default is 1 hour).

### How court limits affect the Duration dropdown

* **No court or area selected** — The dropdown follows **Company Settings → Max Hours per Reservation**. If that limit is not set, durations up to **4 hours** are available.
* **Specific courts selected** — The dropdown uses the **lowest** max booking time among those courts. You can offer a longer pass only when every selected court allows it.
* **Areas selected (without picking courts)** — The same rule applies to all courts in those areas.

{% hint style="info" %}
**Example:** Company max is **1 hour**, but Tigard courts are overridden to **2 hours**. After you select only Tigard courts on the pass, **2 hours** appears in the Duration dropdown and the template saves successfully.
{% endhint %}

### Mixed court limits

If you select courts with different limits (for example, one court at 1 hour and another at 2 hours), the dropdown caps at the **strictest** court—**1 hour** in that example. Narrow the court list or align court overrides before offering a longer pass.

### Validation messages

If the duration does not meet the rules, saving the template may show:

* **Pass duration must be at least 60 minutes and in 30-minute increments** — Duration is under 1 hour or not on a 30-minute step.
* **Pass duration exceeds the maximum booking duration of X hours for the selected courts** — Duration is longer than allowed for the courts (or areas) on that pass.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FF4WkwgCqr1rCr7YBr0eA%2FScreenshot%202026-09-02%20at%2022.29.25.png?alt=media&amp;token=497f59db-bd6d-4389-b032-331228a5b10b" alt=""><figcaption></figcaption></figure>

### Related settings

Company-wide defaults live under **Company Settings → Booking** ([**Max Hours per Reservation**](https://docs.podplay.app/system-restrictions/general-restrictions/reservation-and-event-restrictions#max.-hours-per-reservation) and/or [**Maximum Hour Reservation Play Passes (daily)**](https://docs.podplay.app/system-restrictions/general-restrictions/reservation-and-event-restrictions#max.-daily-reservations-using-play-passes)).


---

# 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/play-passes/create-and-manage-package-templates/pass-duration-and-court-booking-limits.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.
