Federation Reports

A federation-scoped aggregator subscribes to license, member, competition, and umpire events and writes monthly FederationRollup documents per (org_node_id, dimension, month). Membership growth (F10.04.01) is computed from license state transitions: new = first-ever active, renewed = active in two consecutive years, lapsed = active last year and not this year. Club activity reports (F10.04.02) read competition-hosted counts and active-member counts (a member is active if they played at least one ranked match in the period).

Age (F10.04.03) and gender (F10.04.04) distribution are pivots on the player profile, recomputed from the current snapshot at month close so historical reports stay consistent. Geographic distribution heat maps (F10.04.05) bin members by postal code or municipality and join with a GeoJSON layer for the map render. License revenue reports (F10.04.06) sum payment events by license_type and OrgNode, respecting per-tenant license-type configuration.

Umpire activity (F10.04.07) counts assignments and matches officiated. Competition calendar utilization (F10.04.08) compares planned vs realized events per week. Year-over-year comparison (F10.04.09) overlays the current month's rollup against the same month last year, with a delta column.

KPI dashboards per federation level (F10.04.10) compose the relevant tiles for club, district, regional, and national OrgNodes; the layout follows the tenant's configured hierarchy depth, so a flat federation sees one level and a deep federation sees all of them. Sensitive reports (revenue, lapsed members) are capability-gated, and federation administrators can drill from a national tile down to the underlying clubs without leaving the dashboard.