Free template
Hackathon judging criteria
Five weighted criteria, each with what a 1 and a 5 mean. Print the page as a score sheet, or start a free Innovote event with the same rubric.
The rubric
Judge: ______________________ Team: ______________________
| Criterion | Weight | 1 means | 5 means | Score (1 to 5) |
|---|---|---|---|---|
| Impact | 25% | Solves no clear problem, or one that nobody has. | Solves a real problem for a group the team can name, and it would matter to them. | |
| Technical execution | 25% | Mostly slides or mockups; little of it runs. | Works end to end in the live demo, and the hard part is built, not faked. | |
| Creativity | 20% | A copy of something that already exists. | A fresh idea, or an unexpected use of a technology or a data set. | |
| Design and usability | 15% | Hard to follow, even when the team explains it. | A first-time user could use it without help. | |
| Presentation | 15% | The judges could not tell what was built or why. | A clear story and a live demo within the time, and good answers to questions. |
Total: ________ Comment: ____________________________________________
Print this page for a paper score sheet: the menus and buttons drop away and a score column appears, one sheet per team.
Why these criteria
A hackathon project is judged on what the team built in a weekend, so the rubric rewards a real problem and working software first, and polish second. Impact and technical execution carry half of the total between them; creativity, design and the presentation share the rest.
Keep it at four to six criteria. Judges score many teams in a short time, and every extra criterion is one more number they have to tell apart at the end of a long day.
Change it to fit your event: a sponsor track can swap Creativity for “Use of the sponsor’s API”, and a social impact hackathon can give Impact more weight. Keep every criterion on the same scale, and tell the teams the criteria before they start building.
How the total is calculated
Each team’s score on a criterion is the average of all judges who scored it. The total multiplies each criterion’s average by its weight and divides by the sum of the weights (100), so it stays on the same 1 to 5 scale as the criteria.
Example: a team scored 4, 3, 5, 4, 2 gets (4 × 25 + 3 × 25 + 5 × 20 + 4 × 15 + 2 × 15) / 100 = 3.65.
This is how Innovote ranks a weighted scorecard. Judges see the weight next to each criterion, for example “Impact (25%)”. Teams with the same total, to two decimals, share a place.
Running the judging
- Publish the criteria and the weights when the hacking starts, so teams know what the judges look for.
- Brief the judges with the “1 means” and “5 means” columns. In Innovote the same two sentences show under each criterion on the judge’s phone.
- Run every prize with its own judges as its own event in Innovote: the main prize, each sponsor prize and the hackers’ choice. Each one has its own link and its own results.
- Decide before the event how a tie is broken, for example by the Impact score. Two teams with the same total share the place.
Entering it in Innovote
With one click: Start an event with this template. You name the event, and it starts with these 5 criteria, their weights and their descriptions, a scale from 1 to 5 without a 0, and judges who sign in with a username and PIN. Without an account you sign up first (free), and the template comes along.
By hand, in an existing event:
- In the event settings, under Sign-in, choose Username and PIN. Your screens then call the people who vote judges.
- Under Voting and rubric, choose Detailed scorecard and set the number of criteria to 5.
- For each criterion enter the title, 5 as Max points, the weight, and the “1 means” and “5 means” sentences as the description.
- Under Judge options, switch on Disable the “0” vote option, so the scale starts at 1.
Then add the teams (or switch on the application form under Entry fields and let them apply through its link), add the judges with their PINs or import them from a spreadsheet, print one card per judge, and put the voting link or its QR code on the screen.
What the rubric does not do
Innovote does not normalize strict and lenient judges: a judge who never gives more than a 3 pulls every team they score down by the same amount, so let every judge score every team when you can. It also does not assign judges to tables, and it does not blend a jury score with an audience vote.