Hackathon Judging Rubric Builder
Build your hackathon judging rubric
Choose your judging criteria and their weights, and watch the points add up on a sample entry. Then send your judges a brief and a score sheet.
Why a sample idea: you cannot see what a set of weights rewards until it scores something. We wrote eight typical corporate hackathon entries and scored each on every criterion, from 0 to 10. On the day, your judges score your teams.
How important is the problem being solved?
A named problem with a visible cost: who has it, when it bites, and what it costs in time, money or risk. The pitch should make the judges feel the problem before they see the product.
How aligned is the problem with the strategy?
The theme and the problem statements in the brief are the yardstick. On-theme work that advances a named portfolio bet scores high, however unglamorous; off-theme work, however impressive, goes to the chair rather than being quietly rewarded.
How well does the idea address the problem?
The mechanism, traced from problem to outcome. “AI will optimise it” is not a mechanism: the demo should show the problem dying, not features existing.
How novel is the idea?
Novelty that was checked: what exists, what was tried internally, and where this genuinely differs. A team that found three competitors and still differs beats a team that found none.
How feasible is it, technically and economically?
Buildable with means the team can name: technology that exists, data that is accessible, costs that make sense. Honesty about what is mocked counts in favour, not against.
How quickly could a production version exist?
The distance from demo to production: integration, data plumbing, edge cases and the parts that were mocked. A credible 90-day pilot path is the benchmark.
How easily would it run in production?
Someone must own this on a Tuesday in February: support load, running cost, data governance and compliance. Teams that thought about the unglamorous parts are rewarded.
What is the potential business impact?
The value, quantified honestly and bottom-up: users × frequency × value per use. Estimates are marked as estimates, and judges punish confident fictions, not small numbers.
How certain is sufficient demand?
Evidence of pull: user quotes gathered at the event, sign-ups, a measurement, a stakeholder asking to pilot it. Push (“everyone will want this”) is not demand.
Does AI do real work that could not be done without it?
A step that would be impossible or uneconomic without AI, shown working on real inputs. AI added for the demo, or a chat window over an ordinary form, scores low.
How much better is it for the people who use it?
The difference for the people who use it, shown rather than claimed: fewer steps, less waiting, fewer errors, ideally measured on a real task with a real user.
How well does it handle data, privacy and regulation?
Data the team is allowed to use, privacy handled by design, and the regulations that apply named. A credible plan for review counts in favour; ignoring the question does not.
What is its environmental or social effect?
A measurable environmental or social effect, such as emissions, waste, access or inclusion, estimated honestly and bottom-up, with the assumptions shown.
How convincing is the working demo?
We leave it out of our nine. With AI tools any team can produce a convincing prototype in hours, so polish no longer separates strong entries from weak ones; evidence does. Add it only if the demo itself is the point of your event.
Your rubric, ready for your judges
Name it and tell your judges why it is weighted this way. The rubric card updates as you go; it is what your judges receive.
The name and the note open the judges’ brief, the slides and the link. The brief is a two-page PDF: the criteria, the weights and the instructions for judges, then a score sheet. The briefing slides are three 16:9 PowerPoint slides. Both are made in your browser and carry our logo and a QR code back to this tool; nothing is stored.
- Problem importance15%
- Problem alignment10%
- Idea effectiveness15%
- Idea feasibility10%
- Ease of development5%
- Ease of operations5%
- Impact15%
- Novelty10%
- Demand15%
How it works
How the hackathon rubric builder works
Choose the criteria
Start from our nine hackathon judging criteria, switch off what does not fit your event and add what does. Open any criterion to read what it asks.
Weigh them and test them
Set each weight as a share of 100 and watch a sample entry, scored by us, earn its points. Flip the switch to compare with all criteria equal.
Brief your judges
Download a judges’ brief with a score sheet, or briefing slides, and send your judges the link. Every judge scores the same questions the same way.
The theory, briefly
How to score a hackathon: criteria, weights and a scorecard
A hackathon judging rubric is the list of criteria every judge scores, each with a weight published before the event. Judges score each project from 0 to 10 on every criterion, alone and before any discussion, and the weights turn those scores into a total out of 100: the project’s line on the scorecard.
The weights are a choice about what the event rewards: insight over polish, readiness over ambition, or the reverse. Publish them with the brief, so teams build to them, and settle ties by rules written in advance. That is what lets organisers defend the winner to the sponsor and to the teams that did not win.
The anchors for every criterion, the scoring workbook and the judge pack come with the Hackathon Masterclass. To run the judging with us, with a calibration session for your panel and an independent chair, see Corporate Hackathon Programmes.