INTRODUCTION
Feature Summary: CourtReserve supports creating team-based events, allowing a player to sign up for an event with a designated partner.
Use Cases:
Doubles & Partner-Based Events: Perfect for pickleball or tennis doubles, where players register as a team.
Split Payments Between Partners: Players can register and pay only their share.
Guest Participation: If allowed by the Club, players can register with a guest partner without requiring full membership access and guest can pay customized amount.
Admin-Controlled Registrations: Admins can register partners manually and process payments for each player directly from the admin panel, streamlining event management.
Team-Based Registration is in Open Beta
We’re excited to introduce our new Teams-based registration feature, now available to all customers in Open Beta. This means the feature is fully functional but still being refined based on real-world use and your feedback.
We’d love to hear your thoughts! If you run into any issues or have suggestions, please contact our Customer Success Team.
In This Article
Setting Up a Team-Based Event
OVERVIEW
CourtReserve’s team-based registration feature allows players to register for events alongside a designated partner—ideal for doubles formats and partner-based competitions. This flexible system enhances the registration experience for both players and administrators by supporting shared sign-ups, split payments, and guest participation. In CourtReserve, a team is a two-person partnership.
Before you get started, be sure to check out the article Team-Based Events: FAQs.
SETUP REQUIREMENTS
To create a team-based event:
Setting Up a Team-Based Event
When creating an event with team-based registration, the following fields are specific to registering partners together. For a detailed explanation of all fields on the Create an Event page, refer to this article.
Register as a Team: Check to enable team-based registration, allowing players to sign up with a designated partner. When registering through the CourtReserve Member Portal or mobile app, one player will complete the registration and add their partner during the process. Admins can register partners manually through the admin panel.
Max Teams: Sets the total number of teams that can register for the event. For example, if two pickleball courts are available, setting Max Teams to four ensures all courts are in use with no teams waiting to play.
Maximum Registrants Per Team: Defines how many players can be on each team. This defaults to two and cannot be changed.
If your club uses the Organized Play event functionality, please be aware that a Team Event cannot be designated as an Organized Play event — and vice versa.
Minimum Participation for Teams
For team-based events, if a minimum participation requirement is enabled, you must specify the minimum number of teams required for the event to proceed.
Require Minimum Participation for this Event to Occur: When checked, the system will monitor registrations to ensure a minimum number of teams are signed up.
Minimum Team Participation: Specifies the minimum number of teams required for the event to take place. For example, if set to “2,” at least two teams must be registered to avoid cancellation.
Waitlists for Team-Based Events
When creating an event, system users can choose to Allow Waitlists. It’s important to understand how waitlists function for team-based events.
When a team joins the waitlist and Auto Register from Waitlist is enabled, the team will be automatically registered once a team spot becomes available. Teams will be automatically added to the event from the waitlist regardless of if the team is full or not. For example, if Team 5 has only one confirmed player, the team will still be added to the event from the waitlist when a spot opens up.
If Auto Register from Waitlist is not enabled, it becomes the admin’s responsibility to monitor the event and manage registrations manually. CourtReserve handles the following scenarios:
If one player from a team withdraws, the admin can either add a replacement player or choose to notify and withdraw the entire team.
If an entire team withdraws, the admin has the flexibility to add either an individual player or a new two-person team.
This setup gives admins full control over how spots are filled in team-based events.
Custom Fields
Custom Fields: If needed, add a Custom Field to your team-based event. This field will collect the specified information for both partners during the registration process though only the registering player's information will be required.
In this example, a custom field for T-shirt size has been added. The registering player is required to provide their own information (indicated by the red asterisk) and may also enter their partner’s information if available.
Pricing for Team-Based Events
For team-based events, there is no full registration fee—only drop-in pricing applies. On the Event Setup tab, pricing is set as Drop-In Price Per Player, not per team.
For example, if you want to charge $20 per team, you would set the drop-in price per player to $10.
Payment Process
The registering player pays their portion at the time of registration.
Their partner receives an email with a link to pay their share separately.
Depending on your Club’s settings, the partner can be either:
Another member (or existing CourtReserve account holder), or
A guest (non-member or new participant).
If a guest is selected as the partner, the registering player pays both portions up front.
Admins can track unpaid fees and process payments directly from the admin panel at any time.
Optional: No Up-Front Payment
If your Club allows registration without requiring immediate payment, admins can process payments in the admin dashboard. This offers flexibility in how and when team partners are billed.
Registration Restrictions - Rating Restrictions
Under Apply Rating Restriction To, you can control whether rating restrictions apply to:
All Players Registering
The system checks the ratings for both players on the team during registration based on your settings.Only the Registering Player
The system checks only the registering player's rating. Important exception: If a DUPR Max restriction is set, it always applies to both players, regardless of this setting. This ensures competitive integrity.
These restrictions apply whether you are using Custom Ratings or have DUPR integration enabled.
Custom Ratings
Under Allowed Rating Categories, you can use any Custom Ratings you’ve set up, or take advantage of DUPR integration if it is enabled on your account.
If you use Custom Ratings, you can select the Allowed Ratings for your registrants.
Example Scenario:
A Pickleball Doubles Event requires players to have a Custom Rating of 3.0 or 3.5 to participate.
If the Event is set up as "All Players Registering"
The system checks the Custom Rating for both players when registering the team. Both must have a valid Custom Rating of either 3.0 or 3.5 saved to their profiles (if both are members). Note: Custom Ratings do not apply to Guests.
Example:
Jamie is registering their team.
Jamie's Custom Rating = 3.5
Their partner, Taylor, has a Custom Rating = 3.0
The team is allowed to register
If the Event is set up as "Only the Registering Player"
The system checks the rating of only the registering player. The partner's rating is not checked, so they can register even if the partner's Custom Rating is missing or outside the allowed range.
Example:
Jamie is registering their team.
Jamie's Custom Rating = 3.5
Their partner, Taylor, has no Custom Rating or has a different rating outside the allowed list (e.g., 2.5)
Team is allowed to register
DUPR Ratings Integration
If your Club has DUPR integration enabled, team-based events include a way to apply the dynamic DUPR rating in the Rating Restrictions.
DUPR Rating Filters (Individual and Combined)
These filters determine which players (or player pairs) are eligible to register based on their dynamic DUPR rating(s). Admins can use either or both sets of filters. If both checkboxes are selected, the team must meet the criteria for both if validating "all players."
Individual DUPR Filters
DUPR Doubles Rating: Enables filtering based on the individual player's doubles DUPR rating.
DUPR Min Doubles: The minimum allowable individual doubles DUPR rating.
Example: A player must have a rating of at least 2.500 to be eligible.DUPR Max Doubles: The maximum allowable individual doubles DUPR rating.
Example: A player must not exceed a rating of 4.000 to be eligible.
Use Case: Ensures that each player individually falls within a certain skill range.
Combined Partner DUPR Filters
DUPR Doubles Combined: Enables filtering based on the combined DUPR rating of both partners.
DUPR Min Doubles Combined: The minimum allowable total when both partners’ doubles DUPR ratings are added together.
Example: A team's combined score must be at least 5.000.DUPR Max Doubles Combined: The maximum allowable combined total for a team. Example: A team’s total rating must not exceed 8.000.
Use Case: Controls the overall team strength, regardless of individual ratings.
If both checkboxes are selected:
Each individual player must meet the individual DUPR range,
andTheir combined rating as a team must also fall within the combined DUPR range.
Example:
If Min Doubles is 2.5 and Max Doubles is 4.0, and Combined Min is 5.0 and Max is 8.0:
A player rated 2.4 would be ineligible (too low individually).
A team rated 4.0 + 4.2 = 8.2 would be ineligible (combined too high).
If DUPR restrictions are set up and a player is registering a Guest when validating "all players" when registering, the Guest’s DUPR information will also be validated during the registration process. The player must know their partner’s DUPR ID and ensure their first and last name match exactly as listed in DUPR.
The registering player is only required to know their partner’s DUPR ID when registering a Guest. However, in this example, if instead the partner is a member of the organization but does not have a DUPR ID saved in their profile, the player will not be able to register that partner to their team.
In Summary:
When validating "all players" with DUPR restrictions, Guests and members alike must meet DUPR requirements and have correct DUPR details entered (for guests) or saved to their member profile (for club members).
When validating "only the registering player," the system will check the DUPR information for the registering player only. Partners are not required to meet the restriction or have DUPR information — unless a DUPR Max is set, which always applies to both players.
Note: A player with an "NR" (Not Rated) status can register as long as the event’s minimum rating is set to 0.00 in the event setup.
If the Player doesn't meet the restriction, they will see the following:
Player view when registering a partner:
Admins will see Ineligible tags along with a pop-up message detailing which registration requirements were not met. However, admins can still save the partnership, even if it does not meet the specified restrictions.
Example:
Allowing Guests as a Partner
On the Create an Event page, at the bottom under the Guest Setup tab, you’ll find the Allow Guests as a Partner checkbox. When enabled, this allows players to register with a guest as their partner—even if that guest does not have a CourtReserve account. This is ideal for clubs that welcome non-members or first-time visitors to participate in team-based events.
As with other guest settings, system users can limit the number of guests allowed per event occurrence. Additionally, a drop-in price can be set for guest participants and customized based on membership type.
ADMIN PERSPECTIVE
On the Scheduler, the event will display the number of Teams in relation to the spots available.
On the Event List, any Team event will have an icon as follows:
USER PERSPECTIVE
Team-based events display “team spots” to show how many team registrations are available. In this example, a “Team” tag was also added to clearly indicate that the event is team-based.
Players select the drop-in dates they wish to register their team for:
For more examples of team registration, see the detailed article here.
RELATED ARTICLES