Real-time court scheduling: lessons from Court & Yard’s match engine
A booking system becomes a community system when it helps people find the game, fill the empty seat and keep the day moving.
The schedule was only half the problem.
A venue can be full at the obvious hours and still have empty time everywhere else. The desk receives calls during the rush while the quiet slots remain invisible to the people who would use them.
Then there is the social work around a booking: finding players, confirming a share and handling the moment someone drops out.
We treated the booking as a living object.
A useful court system has to know more than whether a slot is technically free. It has to make availability understandable, let people join with confidence and keep the state of the session visible to everyone involved.
The product grew from reservation into discovery, matchmaking and community because the real job was never just taking a booking. It was helping a game happen.
The lesson was to design for the empty space.
Peak demand tells you that people already know where to go. Off-peak demand tells you whether the product is creating new behaviour.
The quiet hours became the measure of the system: fewer calls, more filled sessions and less operational memory required from the venue team.