Skip to main content
Hackathon Planning

Hackathon Judging Criteria & Printable Scoring Rubric

A 100-point hackathon rubric and expo tally, score bands, judging rounds, demo and submission rules, tie-breaks and how to lay out team tables at a tech conference.

How Hackathon Judging Works

A hackathon ends with dozens of tired teams and a few hours to pick winners. Without set criteria, judges reward the slickest slide deck or the project closest to their own work. A published rubric tells teams what to build toward and gives judges a common scale.

Most hackathons judge in stages:

  • Submission: teams submit a project page, a repository link and a short video or description by a hard deadline
  • Eligibility check: organizers confirm the work was built during the event and the team followed the rules
  • Expo round: judge pairs visit numbered team tables, science fair style, and score short live demos
  • Finals: the top teams demo on stage to a finals panel, often in front of the whole event
  • Sponsor prizes: sponsors judge their own challenges, such as best use of their API, separately from the main prizes

Hackathon Judging Criteria and Weights

Six criteria cover what judges can see in a short demo. The weights below make a 100-point rubric for a general hackathon; publish them at kickoff.

Hackathon judging criteria on a 100-point rubric
CriterionWhat judges look forPoints
Technical complexityHard problems solved, sound engineering, and how much of it actually works in the demo25
ImpactA real problem for real users, and how much the project would help them20
CreativityAn original idea or a fresh use of a familiar tool15
Design and UXA product someone could pick up and use; clear flow and interface15
PresentationA clear demo in the time allowed, and direct answers to questions15
Theme fitAnswers the hackathon theme or the chosen challenge track10
TotalAll criteria100
Hackathon judging criteria on a 100-point rubric
Score bands for the 25-point technical complexity criterion
BandPointsWhat it means
Mockup1 to 8Slides or screens with little or no working code
Partial9 to 15The core works with hard-coded steps or a narrow happy path
Working16 to 21A working build of the main feature, with real data or integrations
Impressive22 to 25Difficult work done well in the time, and stable in a live demo
Score bands for the 25-point technical complexity criterion

Printable Hackathon Scoring Sheet

Judges fill in one sheet per team during or right after the demo. Use the tally sheet to combine each pair's scores before finals.

Judging Rounds: Expo Tables, Then Finals

The expo round works like a science fair: teams stay at their tables, judges move. It lets you see every team in an hour or two instead of a full afternoon of stage demos.

  1. 1

    Calibrate Judges

    Brief judges together before demos start. Walk through the rubric and bands, and score one sample project as a group so everyone agrees what a middle score looks like.

  2. 2

    Assign Tables

    Split judges into pairs and give each pair a run of table numbers in walking order. Make sure every team is seen by at least two judges, and avoid sending a judge to a team they know.

  3. 3

    Run the Expo Round

    Each team gets the same time, often three to five minutes including questions. A volunteer with a timer moves judges on.

  4. 4

    Tally and Pick Finalists

    Average each team's scores. If one judge pair scored much higher or lower than the rest, compare their ranks rather than raw totals, or have a floating judge re-score borderline teams.

  5. 5

    Run the Finals

    The top five to ten teams demo on stage to a finals panel of three to five judges, with a few minutes of questions each. The panel deliberates while a sponsor talk or the audience vote fills the break.

For pitch-heavy events where teams also present a business case, the pitch competition judging criteria add market, traction and the ask to the rubric.

Demo Rules, Submissions and Tie-Breaks

Write the rules at kickoff and pin them where teams work. These are the ones judges most often have to rule on:

  • Team size, often two to five people, and whether solo entries are allowed
  • Fresh code: projects start at kickoff; open-source libraries, APIs and templates are allowed when the team names them
  • AI tools: whether AI coding assistants are allowed and whether teams must say how they used them
  • Submission: a repository link, a short description and a demo video, by a hard deadline, with no commits counted after it
  • Demo: a live demo is preferred; a recorded video counts only if the live demo fails, and judges note which they saw
  • Ownership: who owns the code, especially at a corporate hackathon; have the wording reviewed, since it is a legal question
  • Conduct: a code of conduct and a named contact for reporting problems

Running a Hackathon at a Tech Conference

Many hackathons run inside a tech conference or a developer event, which gives teams an audience, mentors and sponsors already on site. The room needs more planning than most breakout spaces.

  • Number team tables in walking order and print the same number on the table tent, the rubric and the tally sheet
  • Plan power for every seat, plus spares; the event power calculator helps size it
  • Plan Wi-Fi for every laptop and phone at once, with a wired fallback for demos; see event Wi-Fi planning
  • Mark a mentor desk, sponsor tables, food, a quiet room and the demo stage
  • Put kickoff, workshops, the submission deadline, demos and awards on the run of show template
  • For the wider event, the technology conference software page covers the schedule, app and sponsor booths
How Map D Helps

Run the Hackathon Floor and Demos in Map D

Map D doesn't take project submissions or score teams. It fits when the hackathon runs inside a tech conference or developer event: draw the hacking room in the floor plan editor with numbered team tables, mark the mentor desk, food and quiet room, put the kickoff, demos and awards on the schedule, and run a People's Choice vote among finalists in the app. The editor is free for one event; publishing, the app and booth sales need a paid plan.

  • Rows of team tables placed with the booth layout generator at real width and depth in feet, numbered with a prefix such as T-101
  • Named areas for the mentor desk, sponsor tables, food and the demo stage, searchable in Find a place on the published map
  • Kickoff, workshops, the submission deadline, demos and awards as sessions on your schedule, on your Homebase and in the app
  • Live app polls of 2 to 10 choices on the finals session, for a People's Choice vote among finalists, one vote per signed-in attendee
  • App notifications for the submission deadline, the expo round and the winners, sent now or scheduled
  • Sponsor and exhibitor booths numbered and sold from the same floor plan as the rest of the conference
See it on your own floor plan

Stop reading about it. Build one.

Upload the floor plan you already have and place your booths on it yourself, in Map D’s editor. Free to build, no contract, and nothing to install.

900+
Organizers who have run shows on Map D
9,000+
Events powered since 2011
1.8M+
Booths drawn to date

“I am really excited about this. The staff met with me this morning and we all LOVE the platform. People are already filling out their booths.”

· Director, International Trade and Development @ Maine Insurance Agents Association
FAQ

Questions Organizers Ask

What do hackathon judges look for?

Judges look for a working demo that solves a real problem, technical work that is hard or well executed, an original idea, a product someone could use, a clear presentation, and a fit with the theme or sponsor challenge. A smaller project that works usually beats an ambitious one that doesn't.

How are hackathons judged?

Teams submit their project, usually with a code repository link and a short description, by a deadline. Judges then score each team on the same criteria, often in an expo round where judges visit team tables, followed by stage demos for the top teams and a deliberation to pick winners.

How long is a hackathon demo?

Two to five minutes per team is common in the expo round, including questions. Finalists often get three to five minutes on stage plus a couple of minutes of judge questions. Keep times the same for every team and enforce them.

How do you break a tie at a hackathon?

Use a fixed tie-breaker set in the rules, such as the higher technical complexity score, then the higher impact score, then a panel vote. Publish it before the event so no team feels the result was decided after the fact.

How many judges does a hackathon need?

Five to ten judges is common for a hackathon of several dozen teams, split into pairs for the expo round so every team is seen by at least two judges. Three to five judges usually make up the finals panel. Mix engineers, designers, product people and sponsor representatives.