On an event that uses RSVP, every player is in, out, waitlisted, or hasn't responded. Players set their own status; a commish or admin can also set it for anyone from the event page's roster panel, which groups players by status. Saying "in" confirms a player is playing — it does not by itself put them in a tee-time group unless the round's Seat players as they RSVP setting is on (see below).
To change someone's status, tick the checkbox beside their name. An action bar appears at the bottom of the screen offering Move in, Waitlist, and Mark out — tick several names to apply the same change to all of them at once. The bar shows only the actions that would change something, so a player who is already in is not offered "Move in".
The four RSVP statuses
- In — the player is playing. Whether they also land in a group depends on the round's Seat players as they RSVP setting; otherwise you seat them yourself.
- Out — the player isn't playing.
- Waitlist — the player wanted in, but the event was full when they responded. They hold a place in line in case a spot opens.
- No response — the player hasn't answered yet. On a fresh event this is everyone.
How capacity works
Capacity is one optional number for the whole event, set in the event's settings. Leave it blank and there is no limit. Tee times play no part: the number of groups you build doesn't cap the field, and the cap is the same however many rounds the event has.
When the number of players who are in reaches the capacity, what happens to the next player who tries to RSVP in depends on the Enable waitlist setting, which only matters once a capacity is set:
- Waitlist off (the default) — the RSVP is refused with an "event is full" message and the player's status doesn't change. Raise the capacity, or move someone out, to make room.
- Waitlist on — the player is placed on the waitlist instead, in the order they responded.
Capacity is enforced only while the event is open for RSVPs (before it's locked). Managers moving players in from the roster panel go through the same check.
Seating players as they RSVP
Each round has a Seat players as they RSVP setting. When it's on, anyone who becomes in is placed in the earliest tee-time group that still has room (fewer than the round's group size), and players already seated are never moved. This covers a player's own RSVP, you marking someone in, a waitlisted player being promoted, and someone joining through the public page. If every group is full, or the round has no tee times yet, the player simply stays in but unassigned — you'll see them in the round page's "unassigned players" warning and can seat them by hand.
New rounds created in the app have the setting on by default; you can change it per round, and the creation wizard has a single checkbox that applies to every round it makes. It only exists on events that use RSVP. When it's off, RSVPing never seats anyone and you build the groups yourself. Players see their group as soon as they're seated, even before the event is locked. See Setting up tee times and pairings for the setting and how to move players afterward.
When the waitlist auto-promotes — and when it doesn't
Automatic promotion fires in exactly one situation: a player whose status was in changes to out while the event is still open for RSVPs. The first player on the waitlist (the one who responded earliest) is promoted to in, and the promotion is recorded in the event's activity feed. Promotion only changes their status — it doesn't hand them the vacated spot in a group. If the round's Seat players as they RSVP setting is on, they're seated like any other new "in" player; otherwise seat them yourself.
Promotion does not fire when:
- A waitlisted player is removed or marked out — that shortens the waitlist but frees no spot.
- The event is already locked — after lock, a drop-out frees their place, but nobody is promoted automatically. If you want a waitlisted player in a locked event, move them in from the roster panel.
- The capacity is raised — new room doesn't pull anyone off the waitlist automatically; move waitlisted players in from the roster panel.
What changes when the event is locked
Locking the event (the Lock RSVPs button on the event page) closes the RSVP window and snapshots every in player's handicap index for scoring. From that point on, an RSVP change only updates the player's status — no capacity check runs and no waitlist promotion fires. You manage the field manually: the roster panel controls who's in, and the round page controls who sits in which group (see Setting up tee times and pairings). Seating players as they're marked in continues only for rounds that have the setting on and haven't started.
Events without RSVP
An event can be created with RSVP turned off entirely — chosen in the creation wizard's Players step and permanent once the event is published. On a no-RSVP event there are no statuses, no capacity gate, and no waitlist. Every active league member is enrolled automatically, including members who join the league later, and the organizer seats whoever shows up on the day. Being enrolled doesn't seat anyone: only players actually placed in a tee-time group count for scoring, games, and the leaderboard, so a bigger-than-expected turnout is a seating decision, not an error. On these events the lock button reads Lock the field and still snapshots handicaps.
Related articles
- Choosing the RSVP mode and pre-selecting players at creation: Creating an event
- Building tee times and seating the field: Setting up tee times and pairings