Creating an Event, Step by Step
7 min read
The four-step wizard from the organiser's side — type, schedule, participation, review — and the three settings that quietly decide how the session runs.
Creating an event takes about five minutes, and three of the settings inside it decide most of what happens afterwards: which courts it occupies, who may join, and what the match rules are. This guide walks the wizard and flags those three as they come.
Step 1 — Type
The event type is the format: open play, a league, a ladder, and so on. It is not cosmetic — the type decides which scheduling tools you get later, how standings are computed and what the browse card says about the event.
Pick the type from what the evening actually is. A social night with rotating partners is open play; a season with a fixed roster and a table is a league. If you are unsure, choosing the right format compares them side by side.
Open play events also carry a play format — the rotation the evening runs on. That choice is advertised on the event card, so players know before they arrive whether they are playing Americano or a paddle queue.
Step 2 — Schedule
Here you set whether the event happens once or repeats, on which day, and between which times.
- One-off — a single date. A one-off can never gain a second session later; if you might repeat it, make it repeating now.
- Repeating — weekly or monthly, with a start date and an optional end date. Leave the end date open for an ongoing club night.
- Start and end time — you enter both. The duration is derived, and a session that crosses midnight is handled.
Step 3 — Participation
This is the step that matters most, and it holds the three settings worth pausing on.
Courts
Select the courts the event uses. This is what stops a member booking the court your session is played on: an event with no courts declared occupies nothing on the calendar and blocks no booking.
If your facility genuinely floats across whatever court is free — a clinic, a social night — you can continue without selecting courts, and the wizard says what that costs. What it must never be is the silent default.
Capacity and joining
- Capacity — the number of confirmed players. Beyond it, joiners go to the waitlist automatically.
- Approval required — join requests wait for you instead of confirming instantly.
- Members only — restricts registration to facility members, while the event stays visible to everyone. Visibility and registration are separate on purpose: hiding the card would hide your club's own advertising.
- Level gates — a DUPR range, if the session is level-specific.
- Who can see it — public, unlisted or invite-only. See who can see your event.
- Registration window — how many days before each session registration opens, and when it closes. See registration windows.
Match rules
Scoring system, target score and format. These are the numbers the app will use for score entry and, where relevant, for what it sends to DUPR — so they are worth setting deliberately rather than accepting.
Step 4 — Review, then publish
The summary shows the event as a player will see it. Publish when it is right; a draft is visible only to you and your facility team.
What happens after publishing
- Players join, and the waitlist fills behind the capacity.
- Before the session, you take attendance — the roster the schedule is built from.
- You generate the round, play it, enter scores, and generate the next one.
- Standings update as scores land; the session's champion is decided by the table, not by you.
Scheduling is deliberately not part of creating the event. The roster changes between now and the first serve — people join late, others leave early — so the schedule is built on the night, from whoever is actually there.