Competition Calendar

The calendar treats every sanctioned event as a first-class object scoped to one of five levels — world, continental, national, regional, or club — and tagged with an event type (championship, open, league, friendly, training). When a club or district drafts an event, the system pulls the active season definition for the tenant, validates the dates against existing entries at the same and neighbouring levels, and surfaces any collision (overlapping championship, blackout window, parallel-event quota breach) before submission. Approval flows through a configurable regional > national > continental chain, with each authority signing off only on events within its remit and the next level inheriting the locked dates.

Once published, the event becomes visible in the public calendar view, where filters cut by level, region, discipline, and format. Subscribers consume the calendar through a paginated cursor API, an iCal export, or a webcal:// feed; the endpoint honours ETag and If-Modified-Since (PL-T074) so calendar clients only refetch when something actually changed, keeping millions of devices in sync without hammering the backend. Season definition runs underneath the surface — the federation declares a season window (start, end, optional sub-windows for indoor/outdoor or summer/winter) and every event must belong to one.

This makes ranking windows, qualification deadlines, and league fixtures coherent. Notifications and reminders fan out from the same source: players who follow an event, a region, or a club get push and email alerts on publication, schedule changes, and X days/hours before kick-off. Calendar events are the spine that the rest of competition management hangs from — registration windows, draws, scoring sessions, ranking recomputes, and external event proxying all key off the same canonical event record.