Participants and teams

Set these up in this order. Each one builds on the one before.

1. Teams (houses)

Participants → Teams. The houses or teams that compete, with colours and logos. On an inter-institution fest a team can be an institution.

2. Categories

Participants → Categories. Age or class bands, such as Junior, Senior or Kulliyya. Each category:

• is mapped to classes from one or more participating institutions. The mapping decides which students fall into it, and the category page shows how many are enrolled;
• carries point caps (candidate max and team max), so toppers can be ranked fairly as a percentage of achievable points. Seniors who may enter five items and Juniors who may enter ten are compared fairly.

A candidate can belong to more than one category, for example THANIYA and KULLIYYA.

3. Sections, collections and skills

Page	What it groups
Sections	Divisions that candidates are assigned to within the sub-fest
Collections	Groups of programmes (Stage, Off-stage, Language…) that rules and reports refer to. Standard collections are seeded
Skills	Skills a programme exercises, for reporting

4. Candidates

Participants → Candidates. Add candidates from the real student roster, which is searchable across every participating institution on a cross-institution fest, or as guests who aren't students. Assign team, category and chest number in bulk.

Chest numbers

The chest number is the key used everywhere downstream: registrations, judgement sheets, results, reports, ID cards and the public "my result" lookup. Settle the chest-number rule (prefix and format) before importing candidates. Numbers are generated by rule, or entered by hand.

The candidate inspector

Opening a candidate shows their whole fest in one place: every item they're entered in, when and where it runs, attendance, scores, and their rank within the team and within their category. It's scoped to the selected sub-fest.