Court Management

Each court is created under a parent venue with a stable number, dimensions, and surface type, then enriched with attributes such as indoor/outdoor classification and lighting from the venue registry. Configuration follows FIPJP norms but is editable per tenant so federations with non-standard dimensions can still represent their facilities accurately.

Real-time status is exposed through the /venues/{id}/courts/status endpoint, which combines three signals into a single answer per court: active bookings from the reservation system, competition allocations from the tournament module, and open maintenance windows. Conflicts are resolved deterministically — a maintenance lock-out always wins, then competition allocations, then regular bookings — so the booking calendar and the public real-time availability feed never offer a court that operations has taken offline.

During competitions, the allocation workflow lets tournament directors reserve sets of courts for specific sessions. Allocations move through allocate, confirm, and release states, and confirmed allocations automatically block overlapping reservations and recurring booking series. When the session ends, releasing the courts returns them to the booking pool without manual cleanup.

Condition reporting is built for the people on the ground. Players, referees, and venue staff file reports with severity, category, free-text notes, and image attachments. Reports remain open until a maintenance task resolves them, and resolution is logged against the originating report so the history is fully auditable. Maintenance scheduling itself is a full lifecycle workflow: tasks move through scheduled, in_progress, and completed states with cost tracking on labour and materials, generating a per-court maintenance ledger that feeds homologation renewals and budgeting reports.

Because every state transition emits events, downstream surfaces — the booking calendar, tournament software, the public availability map, and the venue feed in the player app — all stay synchronised without polling.