Eligibility rules
Age, squad size, required documents and cross-event limits — block or warn, with logged overrides.
Eligibility rules stop ineligible players from being entered, so problems are caught at registration rather than on match day. There is no separate screen for them — they're set in two places:
- Per event: on the event form, in the Eligibility rules card.
- Tournament-wide: on the tournament form, in the Cross-event eligibility card.
The rules
| Rule | Where | What it checks |
|---|---|---|
| Age | Event | Min/max age on the Age as of date, using each player's date of birth. |
| Squad size | Event | Min/max players per team. |
| Required documents | Event | Whether each player must have an ID proof and/or photo uploaded. |
| Max events per player | Tournament | How many events one player may enter in this tournament. |
| One player, one institute | Tournament | Flags the same roll / admission number appearing under two different institutes. |
Block or warn
Each rule has a Severity:
- Block — the player can't be saved, and the draw can't be generated while any player breaks the rule.
- Warn — the problem is shown with a ⚠ badge on the roster, but nothing is stopped.
Overriding a block
Only the org admin or the tournament's host can override, and only with a written reason:
- When saving a player: the blocked form shows the problems and a Reason box. Fill it in and save again.
- When generating a draw: the draw page lists the problems. Tick the override box and give a reason.
Every override is stored with who did it and when, and written to the audit trail. An institute that isn't the host can't override; it has to fix the player's details or ask the host.
Tightening a rule later doesn't remove anyone already saved. Existing players who now break the rule are flagged on the roster and draw pages, so you can decide what to do.
Bulk upload (Excel/CSV) doesn't check these rules row by row. After an import, check the roster page for ⚠ badges.