> 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/adjust-group-size.md).

# Adjusting Group Size

{% hint style="success" %}
This is the booking flow for the **Per Player pricing model**.
{% endhint %}

### Overview

A few important things to keep in mind for Group size in a Reservation:

***Customers cannot invite more people to a Reservation than the Group size quantity***

* If a Customer booked a private Reservation for 4 people and wants to invite 5 people, that's 6 total people instead of 4. The Customer will NOT be able to invite more people to the Reservation than the Group size is set to.

***Prices per "share" of the Reservation will change based on the Group size***

* If a booking is $40, booked for 4 people, the cost per "share" is $10. If the group size is [chaged by the Customer](https://docs.podplay.app/reservations/customer-books-reservation#edit-reservation-group-size) or by staff in the Dashboard, the cost per "share" is $8. If the group size is changed to 2, the cost per "share" is $20.

***Reservation Holders are on the hook for the cost of each "share"***

* If a booking is $40, booked for 4 people, and only 1 other Customer joins, the Reservation Holder is on the hook for the remaining balance of the booking.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FQJg2An8Xq7UZcYZo5WMR%2FScreenshot%202026-09-30%20at%2022.08.09.png?alt=media&amp;token=19c4840e-812a-4152-a5f1-2d9b31959457" alt=""><figcaption></figcaption></figure>

[***Customers***](https://docs.podplay.app/reservations/customer-books-reservation#edit-reservation-group-size) ***and Admins*** (this article) ***can change the group size***

### Admins Update Player Count

For any Club employee to change the Player count, they can:

1. Click on the Reservation
2. Notice the side panel appear
3. Select the pencil icon next to the player count
4. Choose the new quantity of players in the pop-up window
5. Notice any cost adjustments in the pop-up window
6. Finalize the change by clicking on the `Update reservation` button

At the end of the Reservation, when charges are processes, any new amount changed to the Customers in the Attendee list of the Reservation will be visible in the Purchases tab of the Reservation.

{% @supademo/embed url="<https://app.supademo.com/demo/cmuowcb7r0ra6qmh1f4n332ce>" demoId="cmuowcb7r0ra6qmh1f4n332ce" %}

### Projected Settlement

This section of the Reservation is on the Overview tab and shows Club staff a high-level view of all information as it pertains to the anticipated charges to Customers.

At the top level:

* **Price** — total cost for the booking charged to a card on file minus any discounts
* [**Credits**](https://docs.podplay.app/payments/virtual-credits) — total amount of Credits that will be used to pay for the booking
* **To collect** — total amount that has yet to be collected, with sub-copy showing how much I currently on hold

The table beneath the top level shows

* Customers name
* How much they owe for their "share" of the booking
* How the Customer is paying
* How the Customer will be charged

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2F94ss2iwJbw1cxN3aHYDX%2FScreenshot%202026-09-30%20at%2022.31.13.png?alt=media&amp;token=a5f54121-8c7a-4893-9a88-e66080d60df6" alt=""><figcaption></figcaption></figure>

Further details can be expanded by clicking on the `Show breakdown` hyperlink.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FWO1bPvu3tKGmXY2ZLmTz%2FScreenshot%202026-09-30%20at%2022.32.01.png?alt=media&amp;token=cf1105e8-902c-4668-840b-eb54951457c5" alt=""><figcaption></figcaption></figure>

### Revisions

Anytime there is a change to prices or a change to the amount to be charged to Customers, the Revisions section on the Purchases tab will update.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2F6UkJGwoLjLNlBNjZx2Dv%2FScreenshot%202026-09-30%20at%2022.32.48.png?alt=media&amp;token=7984bec9-a97c-4f96-a99a-484742c3ba8a" alt=""><figcaption></figcaption></figure>

This is similar to [Activity Logs](https://docs.podplay.app/support-and-troubleshooting/customer-activity-log), except that it's always about money movement. The information here will show how a Customer joined a Reservation (if they were added by staff or joined through an invite link sent by the Reservation Holder) and how much money the Reservation Holder will owe at the end of the booking.


---

# 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/reservations/adjust-group-size.md?ask=<question>&goal=<user_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.