short answer
Most hackathons score a working project on a short list of criteria. Devpost's list is technological implementation, ease of use, the demo, potential impact, quality of the idea and design; many events rename these or add relevance to a track. Before any scoring, judges check the requirements: eligibility, required tools, working links and the demo-video limit. In expo-style judging a judge spends about four minutes per project, so the proof has to be visible fast.
beginner hackathonson this page
Requirements come before scoring
Devpost's guide to judging criteria tells participants to read the rules before building and confirm five things: who is eligible, which technologies are required, which APIs or libraries must be used, whether the submission needs project or demo links judges can open, and whether the demo video has a length limit or must be public.
Judges treat those as a gate. Karen Bajza-Terlouw of Databricks told Devpost that the first thing she does is go over the requirements the hackathon asked for. Warren Marusiak of Atlassian said a project that does not nail the prompt is hard to give full points. A private repo, a dead demo link or the wrong required tool can sink a strong idea before anyone scores it.
The criteria most rubrics use
Devpost names six criteria that submissions are most often scored against: technological implementation, ease of use, demonstration (usually the video), potential impact, quality of the idea, and design. Events rename and reweight them, but the judge keeps asking the same thing: does it work, does it matter, and can I tell in a few minutes.
Here is how one real event wrote them down. HackAI 2025, a 24-hour in-person hackathon on Devpost, rated each of six categories from 1 to 5:
| Criterion | What judges were asked |
|---|---|
| Technical implementation | How technically impressive is the project? |
| Innovation and creativity | How unique is the idea? |
| Usefulness and impact | Would it help solve a real problem? |
| Execution | Does the project feel complete? |
| Clarity of explanation | Was the idea explained and the project demoed well? |
| Relevance to track | Does it fit the track it was submitted to? |
Richard Moot of Square told Devpost that strong submissions clearly try to balance across all the judging criteria. One brilliant bucket rarely carries a project that is weak everywhere else.
The judging format changes your strategy
MLH's organizer guide strongly recommends science-fair judging: teams stay at a table and judges walk between them. It aims for each project to be seen at least 3 times and plans about 4 minutes per project, covering the demo, questions, scoring and walking to the next table. Its suggested ranking method has each judge name a top three, worth 3, 2 and 1 points.
That format rewards a short explanation you can repeat word for word to every judge, a demo path that works every time, and a project page that still makes sense after the judge walks away. Build the pitch and the demo for four minutes, not for a stage slot you may never get.
Weighted rubric or top picks
Some events score every project on a rubric. HackHQ's planning guide shows a sample on a 1 to 10 scale: innovation and creativity 30 percent, technical implementation 25 percent, business value and impact 25 percent, presentation and communication 20 percent. It calls those percentages starting points, so expect your event to change them.
Other events skip the rubric. HackHQ's rubric scoring page suggests rubric scoring when there are fewer than 50 submissions and quick top-pick voting when there are 50 or more and speed matters. In a top-pick room nobody adds up your weak buckets, but nobody remembers a project they could not explain to the next judge either. Read the rules for which one your event uses.
A scoring sheet to use while you build
When the event publishes weights, use those. When it does not, HackHQ's sample weights are a reasonable stand-in. Score each criterion out of 10, multiply by its weight, and add up. The scores below are an example, not a real project:
| Criterion | Weight | Example score | Weighted |
|---|---|---|---|
| Innovation and creativity | 30% | 8 | 2.40 |
| Technical implementation | 25% | 6 | 1.50 |
| Business value and impact | 25% | 7 | 1.75 |
| Presentation and communication | 20% | 9 | 1.80 |
| Total | 100% | 7.45 out of 10 |
Before the sheet, run the pass or fail gate: eligibility, required tools and APIs, working project links, demo-video length and visibility, a public repo if code is required, AI-tool credits if the rules ask for them, and the sponsor requirement for any sponsor track you enter.
Then use the sheet to cut scope. If a feature cannot raise a weighted bucket or clear the gate, it is stealing demo time. In the example above, the cheapest gain is usually technical implementation: make the hard part visible in the demo instead of adding a fifth screen.
Use judge math to choose scope
MLH says its 2026 season (August 2025 to March 2026) averaged 1 submitted project per 4 checked-in hackers. Its worked example: 175 projects, each seen 3 times, at 4 minutes a visit, inside 2 hours of judging, needs 18 judges.
That math is why subtle features disappear. A judge gets minutes, not an afternoon with your repo. Put the winning evidence where it will be seen: the first 30 seconds of the demo, the first lines of the project description, the screenshots, and the top of the README. Sponsor prizes work the same way: if a track requires an API or a platform, show it in the main demo path, not in a footnote.
FAQ
What are the most common hackathon judging criteria?
Devpost lists technological implementation, ease of use, demonstration, potential impact, quality of the idea and design as the criteria submissions are most often scored against. Many events add execution or completeness, clarity of the pitch, and relevance to the track.
Do requirements matter before scoring starts?
Yes. A Databricks judge told Devpost the first thing she does is go over the hackathon's requirements, so missing links, the wrong required tool or a video over the limit can hurt a strong idea before any criterion is scored.
How is a hackathon scored?
Either on a rubric, where judges rate each criterion on a scale such as 1 to 5 or 1 to 10 and the weighted scores are added, or by top picks, where each judge names favourites. MLH's suggested method has each judge rank a top three worth 3, 2 and 1 points.
How long do judges spend on each project?
Often only a few minutes. MLH's organizer guide plans about 4 minutes per project per judging visit in science-fair judging, with each project seen at least 3 times.
sources
- Devpost: understanding submission and judging criteria info.devpost.com
- Devpost: tips from hackathon judges info.devpost.com
- HackAI 2025 rules and judging criteria (Devpost) hackai-2025.devpost.com
- MLH Hackathon Organizer Guide: judging plan guide.mlh.com
- HackHQ planning guide: judging hackhq.io
- HackHQ: rubric scoring hackhq.io
Checked against these pages when published. Rules and dates change, and the organizer's own page is the authority. Spotted an error? Send a correction.