AIML@TU
Hurricane Hackathon
AIML @ The University of Tulsa
Print-friendly PDF for the judging panel — one page per project.
Download PDF
Judging Rubric

Hurricane Hackathon Judging Rubric

Team Name:
Project:
Judge Name:
Date:

This Year's Prompt: 2030 and Beyond

What challenges, technologies, trends, opportunities do you imagine for the year 2030? How will the world be different? What are you excited about? What are you worried about?

Spend the next 24 hours diving deep into what you can't stop thinking about, but haven't given yourself permission to spend enough time on.

Build something that expresses your vision of the future — and show the rest of us why it matters.

Gate Check: Follows the Prompt

Did the team address the hackathon prompt?

☐ Yes — proceed with scoring
☐ No — flag for panel before scoring
Notes:

Scored Categories

Score each category 1–5. Multiply by the weight to get the weighted score.

1. Compelling (Weight: ×4)

How creative, original, and engaging is the idea?

ScoreDescription
1Generic, derivative, or hard to care about
2Familiar idea, modest twist
3Solid concept with some original elements
4Genuinely fresh angle, makes you lean in
5Surprising, memorable, "I've never seen that before"
Score: × 4 =

2. Impact (Weight: ×6)

Magnitude of the problem solved and value created. Consider who benefits and how meaningfully — depth of value counts as much as breadth of audience.

ScoreDescription
1Niche curiosity, unclear who needs this
2Solves a small problem for a small group
3Useful for a clearly defined audience
4Significant value — either broad real-world demand, or deep value to a clearly underserved group
5Could meaningfully change how an industry, community, or process works — or be transformative for its users
Score: × 6 =

3. Technical Rigor & Quality (Weight: ×5)

Engineering thoughtfulness, working implementation, and technical difficulty. Includes feasibility — is this actually buildable and does it work?

ScoreDescription
1Doesn't work, or trivial implementation
2Partially working; obvious shortcuts
3Works as demoed; reasonable engineering choices
4Solid, well-built; tackled real technical challenges
5Impressive technical execution; novel or non-obvious solutions
Score: × 5 =

4. Execution & Communication (Weight: ×3)

Quality of the presentation, documentation, visible process, and team coordination.

ScoreDescription
1Disorganized; hard to follow; no documentation
2Basic demo; minimal documentation
3Clear presentation; adequate README and process notes
4Polished demo; good documentation; process is visible
5Excellent storytelling; thorough docs; team contribution is evident
Score: × 3 =

Total

CategoryScoreWeightWeighted
Compelling×4
Impact×6
Technical Rigor & Quality×5
Execution & Communication×3
TOTAL / 90
Tiebreaker: highest Compelling score wins. If still tied, panel discusses.

Judge's Comments

Strongest aspect:
Biggest opportunity for improvement:
How AI was used (briefly — tools, role in the work, anything notable):
Other notes: