Why rotations

A large hackathon organiser guide, listed below, recommends science fair style judging: teams present at their tables as judges arrive, every project is seen by at least three different judges, and projects are staggered across judges rather than clustered. Its planning figure is about four minutes per judge visit, with the demo, questions, scoring and the walk to the next table inside that time.

The slot arithmetic

With 18 teams and 3 visits each, the rotation holds 54 visits. Spread over 6 judges that is 9 visits each, so the rotation needs at least 9 slots. At 4 minutes a slot that is 36 minutes of judging; the example adds 3 spare slots so there is room to move a visit when a demo overruns.

Worked example: 18 teams, 6 judges, 4 minute slots

An invented hackathon with 18 teams at tables A1 to A9 in the hall and B1 to B9 in the lab, and 6 judges with no categories, was given 12 slots of 4 minutes from 13:00 to 13:48, one judge at a table at a time, and 3 judges per team. The judge assigner filled 54 of 54 visits, gave every judge 9 teams, and broke 0 rules. Judge A's rotation:

Example rotation for Judge A
TimeTableRoomTeam
13:00 to 13:04A2HallTeam 2
13:04 to 13:08A1HallTeam 1
13:20 to 13:24A9HallTeam 9
13:24 to 13:28A8HallTeam 8
13:28 to 13:32A7HallTeam 7
13:32 to 13:36A6HallTeam 6
13:36 to 13:40A3HallTeam 3
13:40 to 13:44A4HallTeam 4
13:44 to 13:48A5HallTeam 5

Setting it up

Paste the teams as projects, with the table and room of each; the category column can hold the prize track. Paste the judges with the hours they are there. On the Rules tab, set the judges per project, switch on time slots, add a run of slots and set one judge at a table at a time. Assign, check the grid, lock anything a sponsor has asked for, and print the route sheets.

Common mistakes

The same method runs a science fair with timed interviews; see judge route sheets and schedules.

Sources

Frequently asked questions

How long should hackathon judging take?

Work it out from the visits: teams times judges per team, divided by the number of judges, gives the visits each judge makes. Multiply by the minutes per visit and add a few spare slots. The example on this page needs about three quarters of an hour.

Should judges visit teams or teams present to judges?

Expo style, where teams stay at their tables and judges rotate, is fairer than judging rooms, because every team is compared across several judges rather than against the few projects that happened to share a room.

What about sponsor prize judges?

Add them as judges with the prize track as their only category and a small maximum, and give the track's teams that category. With category matching preferred, the assigner sends them to that track's teams first. Or keep them out of the rotation and give them the project list.

Can a judge's teams be kept in one area?

Yes. The assigner prices walking between tables and rooms, so each judge's rotation tends to stay in one room and move along a row.

More guides

Last reviewed 27 September 2026. Judgegrid is not affiliated with any science fair, science fair organisation, competition, hackathon, school, school district or judging software company.