For judges

An organizer sends you an invitation link. Open it, sign in or create an account, and accept. Your reviews then lists the projects assigned to you, and how long the rest will take at about ten minutes each.

Scoring

Each project has a scoresheet: the project’s description and links, then one row of bubbles per criterion. Pick a number in each row. The weight of each criterion is shown next to its name.

• Save draft keeps your scores without submitting them.
• Submit review records them. After that the sheet offers only Resubmit review: you can change your scores and resubmit until judging closes or the results are published, but a submitted review never goes back to being a draft.
• The comment goes to the organizers. Other judges never see it.

What you can and can’t see

You see your own assignments and your own scores, nothing else. Another judge’s review isn’t hidden on a page: it’s not reachable at all. The server answers “not found” for it, whatever URL you type or tool you use.

Conflicts

If you know the team, or have any other reason you shouldn’t judge a project, open it before you submit a review and choose I have a conflict, giving the reason. You’re taken off it, the organizers see it needs another judge, and it’s recorded in the audit log with your reason. You can’t be assigned a project from a team you’re on in the first place.

How your scores are used

Everyone reads a rubric a little differently: some judges are generous, some harsh, some use the whole scale and some stay near the middle. The calibration learns your habits from the projects you share with other judges and takes them out, so it doesn’t matter whether your 4 is someone else’s 3. If you give every project the same score, your scores carry no weight: they say nothing about which project is better. The method explains it all.