> 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/coaches/how-does-the-coach-club-split-work-for-an-event.md). # Coach on Events ### Overview When an Event is created, a Coach can be added to the Event. If the Event type is a Class or Clinic, you will see an option for a Coach rate during the Event creation.
If the Event type is an Open Play, Tournament, League, or Party, you will not see an option for a Coach rate during the Event creation. Once the Event is published, you will see in the side panel a button to `+ Coach`.
After this button is clicked, a pop-up window will appear where you can choose which Coach to add to the Event and set their rate at the bottom. ### Event Payments for a Coach There are two types of Coach payments for an Event: 1. Coach is paid a **$value** 2. Coach is paid a **%value** of Event revenue
When a Coach is added to an Event, staff will set the Coach's rate during that process. The flow of money is: * `Customer signup payment` :arrow-right: sent to `Club` * `Club payment` :arrow-right: `Coach` The money movement in these bullets are separate and do not rely on each other at all. When a Coach is added to an Event, staff should verify the Coach has an `Accepted` status flag next to their name.
### Coach is paid a $value The rate is static. If the Coach rate is set at $50, the Coach receives $50 for the Event. The rate does not change based on Event length (1 hour vs. 2 hours). The rate does not change based on the number of Customers who join the Event (4 Customers or 10 Customers — the Coach rate is fixed). The Club sets the Customer-facing price for the Event and receives all Customer funds, regardless of attendance. The Coach is paid from the Club's Stripe account. **Payout flow:** the L shape. Funds move from the Customer to the Club, and the Club pays the Coach. ### Coach is paid a %value of Event revenue The rate is dynamic. The way this will work is that the Coach payment is a **%value** of the revenue captured for the Event. In an example: * 6 Customers sign up for the Event * 3 Customers pay $10 * 2 Customers pay $5 * 1 Customer pays $10 in Credits * $50 in revenue is generated * The Coach's **%value** = 50% * Coach is paid $25 (50% of the $50) Total revenue from the Event includes: * Cards * Credits * Cash (if used) If coupons are used (Promo Code or Passes), this is not money movement and thus is not added to the sum from which the Coach **%value** is split.
What if the Event generates $0? **With the $value option**: The Coach is paid $n at the end of the Event. If $50 is added here and the Event generates $0, the Coach is still paid $50 (this is how the system works today) **With the %value option**: The Coach is paid n% of $0, which is $0. If the Coach is supposed to be paid more than $0, [an ad-hoc payment](https://help.podplay.app/en/articles/2095233) can be made to the Coach.
How do cancellation fees work? **With the $value option**: The Coach is paid the rate entered. **With the %value option**: The Coach is only paid a **%value** of the attendees, not any revenue generated from cancellations.
What if multiple Coaches are added to an Event? **With the $value option**: Each of the Coaches are paid their rate. **With the %value option**: If there are 2 Coaches added to the Event with 50% each, then 100% of the Event's revenue is sent to the Coaches. If there are 2 Coaches added to an Event with 25% each, then 50% of the Event's revenue is sent to the Coaches. If there are 2 Coaches added to the Event with 60% each, a 120% value of the Event's revenue is not possible, thus no Coaches are paid
How does this work on a Series? **With the $value option**: This is the only Coach payment option on a Series. **With the %value option**: The %value option is NOT AVAILABLE on a Series.
--- # 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/coaches/how-does-the-coach-club-split-work-for-an-event.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.