> 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/set-up-lesson-passes.md).
# Set Up Lesson Passes
{% hint style="info" %}
This feature is in development.
{% endhint %}
### Overview
A Lesson Pass covers the Coaching fee on a Lesson, so the Customer is not charged for the Coach's time at checkout. Add Lesson Passes when a Membership should include Lessons, or when you want to sell a pack of Lessons with specific Coaches or a Coach tier.
Lesson Passes can go on two kinds of Package Template:
* **Membership Package Templates**, alongside other pass types
* **Lesson Packages**, purchasable packs that contain only Lesson Passes
Lesson Passes cannot go on Standalone Package Templates. To sell a pack of Lessons, use the `Lessons` tab.
For what the Customer pays and when a Lesson Pass applies at checkout, see How Lesson Passes apply when a Customer books a Lesson.
### Add a Lesson Pass to a Membership
1. Go to **Company Settings** → **Package Templates**.
2. Stay on the `Membership` tab, or open an existing Membership template.
3. Under **Passes**, click **Pass**.
4. Set **Type** to `Lesson Pass`.
5. Fill in the Lesson Pass fields (see Lesson Pass fields).
6. Click **Continue**.
7. Save the template.
### Create a Lesson Package
A Lesson Package is sold to Customers the same way a Standalone Package is.
1. Go to **Company Settings** → **Package Templates**.
2. Open the `Lessons` tab.
3. Click **Lesson Package**.
4. Under **Passes**, add one or more Lesson Passes. Lesson Pass is the only pass type on this tab.
5. Fill in the Lesson Pass fields (see Lesson Pass fields).
6. Set price, locations, available-for-sale, and expiration the same way as for a Standalone Package.
7. Save the template.
8. Grant or sell the Lesson Package like any other purchasable Package.
Under **Price**, PodPlay suggests an amount: the Coach's hourly rate × pass duration in hours × quantity, summed across all Lesson Passes in the Package. You can set any price.
{% hint style="warning" %}
**A Lesson Pass scoped to exactly one Coach must be the only Pass in its Lesson Package.** To add other Passes, remove that Pass or change its scope first. Tier-scoped and multi-Coach Lesson Passes can sit together in one Package.
{% endhint %}
### Lesson Pass fields
| Field | What it does |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Quantity` | How many Lesson Passes the Customer receives. |
| `Duration` | How much Lesson time one Pass covers. The minimum is 1 hour, and you can increase it in 30-minute steps, the same way a Reservation Pass covers court time. |
| `Applies to` | Choose either **Coaches** (one or more current Coaches; the Pass applies to a Lesson with any of them) or **Coach tier** (one current Coach tier; the Pass applies when the Lesson's Coach is in that tier). |
| Club/Coach split | Optional. Enter a percentage or a fixed dollar amount, not both. Leave both blank to use the Coach tier's normal split. See [How Coach payout is calculated](https://docs.podplay.app/coaches/manage-coach-tiers/coach-payments-and-payouts/coach-payouts-when-a-lesson-pass-is-used#how-coach-payout-is-calculated). |
| `Max students` | The number of players whose Coaching rate the Pass covers, including the Reservation Holder. The default is 1 (a solo Lesson). Larger parties can still use the Pass and pay the difference. |
| `Includes court fee` | When on, one Lesson Pass also covers the court fee for the same duration. |
| `Display Name` | The name Customers see in the App. Review it if you rely on auto-generated names (for example, `Hour Lesson Pass`). |
{% hint style="warning" %}
**Coaches and Coach tier cannot combine on the same Pass.** Choose one.
{% endhint %}
### Coach payouts for Lesson Passes
When you set a Club/Coach split on a Lesson Pass, PodPlay uses that split for the Coach's payout each time a Customer redeems the Pass.
PodPlay can also pay a Coach for Lesson Passes the Customer never used. This happens only when both conditions are true:
* The Lesson Pass is scoped to exactly one Coach (not a Coach tier and not multiple Coaches).
* **Pay Coaches for unused Lesson Passes** is on in **Company Settings** → **Booking** → **Lessons**.
When the Package expires, PodPlay pays that Coach for each remaining Lesson Pass, using the same payout rules as a redeemed Pass. Multi-Coach and tier-scoped Lesson Passes do not get an unused-expiry payout.
### Editing a Lesson Pass after Customers have it
Changes to a Lesson Pass on a template do not update Lesson Passes already granted to Customers. Only new grants use the updated settings.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.podplay.app/play-passes/create-and-manage-package-templates/set-up-lesson-passes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
