University tournament software for inter-faculty, without losing the semester.

University sport has a constraint that club sport does not: your players have timetables, and those timetables are not yours to move. Inter-faculty competitions therefore run in one of two shapes: a league spread over a semester in evening slots, or a single weekend where everything happens at once. The format that works for one is wrong for the other.

For eight faculties, a league round robin is 28 matches across 7 rounds. Spread over seven weeks that is four matches a week, which fits comfortably into two evening slots and gives every faculty a home-and-away feel without a double round robin’s 56 matches. Compress the same eight faculties into one weekend and groups into semi-finals is the better shape: 16 matches total, done in a day and a half.

Whichever you choose, publish the whole fixture list at the start. Faculty reps plan around it, and half your committee’s inbox disappears. The tournament schedule maker shows the shape of the output before you commit to a format.

The thing that breaks university sport is not the schedule. It is March, when the committee that learned how everything works graduates, and next year’s committee inherits a Google Drive folder with four files named “final”. The system resets to zero every twelve months, and the new secretary rebuilds the same spreadsheet from scratch.

Tournamyx keeps events under an organization rather than a person. Roles are assigned per tournament, so a scorer can enter results for their sport without being able to edit the draw, and last year’s competition stays readable as a record instead of a dead file. Handing over becomes adding the new committee to the organization, not exporting and re-explaining.

It also solves the smaller version of the same problem during the event: you can hand scoring for the badminton hall to whoever is standing in it, without giving them the keys to the entire competition.

Inter-faculty sport is followed far more closely than the entry numbers suggest, because the audience is not the players. It is every faculty group chat arguing about the standings. If the table lives in a spreadsheet only the committee can edit, you become the bottleneck for a question hundreds of people are asking simultaneously.

A public link takes you out of the middle. Results entered courtside appear on the table immediately, and the argument moves from “what is the score” to the score itself, which is where it belongs. Tournamyx was built to this standard at the 406-team IIUM Robotic Competition, where 755 matches were scored live on a single public link.