The specialized domains
The other twelve domains, fast — what they do and when they apply.
What this block is about
After the spine, the rest of the platform is easier — each remaining domain has a clear scope and integrates with the spine in predictable ways. Read the domain overview pages to know what is in each, then drill into specific subsystems whenever a stakeholder ticket touches one. You do not need to know every subsystem cold; you need to know which domain it lives in and what its overall purpose is, so you can find the answer quickly.
The point of this block is "I know it exists and where to look", not "I have memorized every detail".
Reading list
Work through these in order. Click each card to open the page in a new tab — your progress is remembered between visits.
- 1
Officials & Judiciary (F05)
Core ~25 minUmpire registry, jury workflow, disciplinary cases, training pipeline.
- 2
Coaching & Education (F06)
Core ~25 minCoach certification, training programs, e-learning, talent pipeline, mentorship.
- 3
Venues & Facilities (F07)
Core ~20 minBoulodrome registry, court management, public discovery, accessibility metadata.
- 4
Communication & Media (F09)
Core ~25 minNotifications hub, newsletter engine, social publishing, broadcast support.
- 5
Statistics & Analytics (F10)
Core ~25 minPlayer stats, federation reports, FIPJP global analytics, data visualisation.
- 6
Commercial & Marketplace (F11)
Core ~20 minEquipment catalog, marketplace, sponsor management, homologation registry.
- 7
Anti-Doping & Medical (F12)
Core ~20 minWADA compliance, ADAMS integration, TUE workflow, medical records.
- 8
Events & Tourism (F13)
Core ~20 minMajor events, ticketing, tourism integration, corporate events, heritage sites.
- 9
Integration & API (F14)
Core ~25 minPublic API, webhooks, third-party integrations, data export, embedding.
- 10
Mobile & Fan Experience (F15)
Core ~25 minThe player-facing app — community, gamification, accessibility, native features.
- 11
Safeguarding, Welfare & Integrity (F17)
Core ~20 minChild protection, medical safety, sport integrity, dispute resolution, whistleblower.
- 12
Chain-Venue Booking Platform (F22)
Core ~30 minThe full commercial chain-venue stack — bookings, POS, F&B, staff, loyalty, marketing.
After this block you should be able to
Read these out loud. If any feel uncertain, revisit the relevant resource above before moving on.
- 1 Given any operator question, name the domain that owns it and the closest subsystem.
- 2 Explain why F22 (chain-venue) is its own domain and not part of F07 (venues).
- 3 Describe the difference between F09 (general communications) and F22.14 (chain-venue notifications).
- 4 List which domains are most likely to need API integration with external systems.