Skip to main content
DeltaHacks uses a table-based judging system where projects are evaluated by judges using a standardized rubric.

​
How Judging Works

​
Project Tracks

Projects are organized into different tracks (categories) such as:
  • General track (default)
  • Specialized tracks (e.g., Health, Education, Sustainability)
Each track has its own judging table and may have track-specific rubric questions in addition to general questions.

​
Judging Tables

Judges are assigned to specific tables that correspond to a track:
  • Each table has a table number and track assignment
  • Projects in that track present at the assigned table
  • Judges evaluate all projects at their table

​
Project Submission

When submitting your project, you’ll provide:
  • Project Name - The name of your project
  • Project Description - What your project does
  • Project Link - Link to your demo, GitHub repo, or live site
  • Track Selection - Which track(s) your project falls under
Project submission details are managed through the judging system interface. Make sure to submit your project information before judging begins.

​
Presentation Timeslots

Projects are scheduled into specific presentation timeslots:
  • Each timeslot has a start and end time
  • Projects are assigned to a table and timeslot
  • Multiple projects present at the same table throughout the day
  • You cannot have two projects in the same timeslot at the same table
Make sure to arrive at your assigned table before your timeslot begins. Late arrivals may miss their judging opportunity.

​
Judging Rubric

Judges evaluate projects using a rubric with multiple questions. Each question:

​
Question Structure

  • Title - Short question identifier
  • Question Text - Full question with evaluation criteria (supports Markdown)
  • Point Value - Maximum points for this question
  • Score Range - 0-3 scale

​
Scoring System

Each rubric question is scored on a 4-point scale:
The project does not meet the criteria or shows major deficiencies.

​
Question Types

Track-Specific Questions:
  • Asked only for projects in specialized tracks
  • Evaluate criteria specific to that track’s focus
General Questions:
  • Asked for all projects
  • Evaluate fundamental aspects like:
    • Technical implementation
    • Innovation and creativity
    • User experience
    • Presentation and pitch
    • Completeness
General track projects only answer general questions. Other tracks answer both their track-specific questions AND general questions.

​
During Judging

​
For Hackers

  1. Prepare your demo - Have your project ready to present
  2. Arrive early - Get to your table before your timeslot
  3. Present your project - Explain what you built and why
  4. Answer questions - Judges may ask about your implementation
  5. Show the demo - Demonstrate your project’s functionality

​
For Judges

Judges see a judging interface where they:
  1. Select their table from a dropdown
  2. View project queue - See all projects assigned to their table with timeslots
  3. Load project details - Click a project to view:
    • Project name, link, and description
    • Judging rubric questions
  4. Score the project - Rate each rubric question (0-3)
  5. Submit judgment - Save scores for the project
  6. Update if needed - Can revise scores for already-judged projects
Judged projects are marked with a “Judged” badge in the project list. Judges can click them again to update scores if needed.

​
Scoring and Results

​
How Scores are Calculated

Each judge’s response is stored as:
  • Question ID
  • Score (0-3)
  • Associated with the specific judge, project, and table
Final scores are calculated by:
  1. Multiplying each question’s score by its point value
  2. Summing across all questions
  3. Aggregating across multiple judges

​
Leaderboard

After judging concludes:
  • Projects are ranked by total score
  • Top projects in each track are recognized
  • Overall winners are announced
  • Results are typically shared at the closing ceremony
Scores and rankings are not visible to hackers during judging. Focus on giving your best presentation rather than comparing scores.

​
Tips for Success

  • Practice your pitch - You usually have limited time to present
  • Focus on the problem - Explain what problem you’re solving
  • Demonstrate value - Show why your solution matters
  • Be ready for questions - Judges may ask technical questions
  • Show enthusiasm - Your passion for the project makes a difference
  • Have a backup - Prepare for demos that might not work (screenshots, video)

​
After Judging

Once all judging is complete:
  • Continue working on your project if time remains
  • Attend closing ceremonies for winner announcements
  • Network with other hackers and sponsors
  • Share your project on social media with #DeltaHacks

Build docs developers (and LLMs) love

Get started for freeTalk to us