Organizers

Events and priority windows

Create events, set capacity rules, and understand when staged access matters versus when the event type bypasses those tools entirely.

Event structure and staged access rules determine how openings are offered and filled.Guide step 3 of 7

Open admin

Back to organizer guide All guides

Create and edit events

Set the date, time, location, and RSVP limit.
Use male/female slots for co-ed balance when needed.
Configure skill and age requirements.
Edit events any time, with optional update notifications.

Capacity

Runnit enforces your slot limits automatically so you never overbook.

Priority windows

Priority windows let you open RSVPs in stages. Season roster members can get first access, followed by league members, then the broader player pool.

Season roster priority: reserve spots for paid roster players.
League priority: give league members first access.
After windows close: continue filling with invites or sub requests.

Automation

You can use automation to keep events moving after priority windows, including invites and sub-request support when you are short.

Business drop-in exception

Business drop-ins do not use priority windows and do not generate sub requests. Those events use the drop-in flow instead of the standard staged-access model.

Waitlist types

Choose how you want waitlists to behave when events fill up.

Queued: players are invited one at a time, in order, until someone accepts and fills the open spot.
Pooled: all waitlisted players are notified and the first person to claim the opening gets it.

When to use each

Choose queued for orderly, turn-based offers. Choose pooled when speed matters most.