Homologation

A venue owner submits a homologation request specifying the level they are seeking — club, regional, national, or international. The request creates an inspection workflow that pulls the requirement profile for that level from tenant configuration. Each profile defines the venue capabilities required at that tier: for example, Sweden's international level requires a centercourt with 300+ seats, public address, catering, and first aid; Sweden's regional level requires marked courts, scoring boards, and a secretariat. Profiles are fully tenant-configurable, so France can express its own ligue/comité requirements alongside Norway's flatter model.

An assigned inspector works through the structured checklist covering court dimensions, surface quality, lighting levels, and ancillary facilities, recording pass/fail per item with notes and photos. When the checklist is complete, the system generates a homologation decision — approved, conditionally approved, or rejected — and on approval issues a certificate with a level grade, valid-from date, and expiry. The certificate is stored as an immutable artefact and surfaced on the venue profile, in federation directories, and on competition assignment screens.

The critical integration point is at competition approval time. When a tournament is scheduled and a venue is proposed, the system auto-validates the venue's current homologation against the competition's required level by replaying the requirement profile. A regional competition cannot be assigned to a venue whose homologation has lapsed or whose level is below the tournament tier — the assignment is blocked at approval rather than discovered on tournament day.

Renewal and re-inspection scheduling watches expiry dates and emits reminders to venue managers and federation officers in advance, automatically opening renewal requests when the venue confirms intent. Each renewal cycles through the same checklist, ensuring standards keep pace as the requirement profiles evolve.