Pickleball court scheduling: players in multiple brackets, and rest between matches

Court scheduling is the hardest computation in a pickleball tournament and the one most software does worst. It is a constraint problem: courts are limited, players appear in several brackets, and everyone needs rest between matches.

The three constraints

Everything else is detail. First, a court holds one match at a time. Second, a person cannot be on two courts at once - and in amateur pickleball, entering two or three brackets is normal, so this collides constantly. Third, a person who just finished needs rest before starting again, or your event is quietly punishing whoever is winning most.

Court capacity: one match per court per slot
Player exclusivity: across every bracket, not just within one
Minimum rest: typically 15–30 minutes between a player's matches
Dependencies: a bracket match can't start before the matches feeding it finish

Why round-order scheduling breaks

The naive approach - run bracket A's round 1, then bracket B's round 1 - produces a schedule where a player in both brackets is double-booked, or ends up playing four straight matches while another player waits two hours. It looks orderly on the printout and fails on the ground.

The fix is to schedule across all brackets at once, slot by slot: at each time slot, fill the available courts with matches whose players are all free and rested. That is what a good director does by hand, and it's mechanizable.

Court utilization is the number to watch

Utilization is the share of court-slots that actually held a match. A tight event runs high; a poorly scheduled one leaves courts empty while players sit resting. Watching it tells you whether to add courts, shorten the format, or tighten your rest minimum - long before the day itself.

Publish it, and keep it stable

Once a schedule is printed and taped to a wall, a reprint has to match it. A scheduler that produces a different answer each time it runs is unusable, no matter how good the answer is. Deterministic output - same input, same schedule - is a hard requirement, not a nice-to-have.

DinkBoard's scheduler is a deterministic pass over time slots that takes court count, match length, and minimum rest as inputs, honors bracket dependencies, and reports utilization for the day it produced.

Then tell the players

A schedule nobody can see is a schedule your desk has to read aloud all day. Put next-match-and-court on each player's phone and on a venue TV board, and the printed bracket on the wall becomes a backup rather than the interface.

Full guide: Pickleball tournament software: what to look for in 2026

Frequently asked questions

How much rest should players get between matches?

15 to 30 minutes is typical. Less than 15 and back-to-back matches become a fitness test rather than a skill test - especially for players deep in a losers bracket.

How do you handle a player entered in three brackets?

Schedule across all brackets at once rather than bracket by bracket. Their matches must be serialized with rest between them, which means the brackets they're in can't be run independently.

How many matches can one court run in a day?

About two per hour for a single game to 11 with win-by-2, including warm-up and changeover - so roughly 16 to 20 in a full day.