RUBRIC

Each category is worth 20 points. Total score out of 100, with an optional +5 bonus. Design with care, not speed.

17–20Exceptional
13–16Proficient
7–12Developing
1–6Beginning
01

RELEVANCE TO STUDENT BARRIERS

/20

Clear connection to real community college challenges

Exceptional17–20

Barrier is clearly defined with specific, empathetic detail. The team demonstrates deep understanding of how this barrier affects real students' daily lives and connects it directly to the chosen track.

Proficient13–16

Barrier is well-identified and explained. The team shows solid understanding with some supporting context and a clear link to community college students.

Developing7–12

Barrier is stated but explanation is surface-level. Limited evidence of research or empathy for the student experience.

Beginning1–6

Barrier is vague, generic, or not clearly connected to the track. Little evidence of understanding the student perspective.

02

AI USE (PLAYLAB & ANYTHING OR V0)

/20

Intentional, appropriate, and well-explained

Exceptional17–20

AI tools are used intentionally and creatively. Playlab and the prototype platform work together seamlessly. The team clearly explains how and why each tool was chosen.

Proficient13–16

AI tools are used appropriately with a logical connection between Playlab and the prototype. Explanation of tool choices is solid.

Developing7–12

AI tools are present but their use feels surface-level or disconnected. The connection between tools is unclear or underdeveloped.

Beginning1–6

AI tools are barely used or misused. No clear explanation of why the tools were chosen or how they serve the student.

03

PROTOTYPE & USER EXPERIENCE

/20

Clear flow and purpose using vibe coding

Exceptional17–20

Prototype is functional and clearly demonstrates the core idea. The user experience is intuitive, student-centered, and shows thoughtful design decisions via vibe coding.

Proficient13–16

Prototype shows the key concept effectively with a clear user flow. Some rough edges but the idea and purpose come through.

Developing7–12

Prototype is partially built or only shows one tool. The user experience is confusing or the purpose is unclear.

Beginning1–6

No prototype shown, or the demo does not meaningfully represent the proposed solution. No clear user flow.

04

EQUITY, ETHICS & REALISM

/20

Considers inclusion, boundaries, and feasibility

Exceptional17–20

Thoughtful, nuanced equity analysis. The team clearly articulates who benefits, what the tool cannot replace (e.g., counselors, advisors), and identifies meaningful risks, limitations, and feasibility constraints.

Proficient13–16

Solid equity and ethics reflection. Considers inclusion, identifies boundaries of the tool, and acknowledges at least one realistic limitation.

Developing7–12

Some ethical awareness shown but responses are generic. May miss key considerations around inclusion, boundaries, or feasibility.

Beginning1–6

Little to no consideration of equity, ethics, or realism. Limitations and risks are not addressed.

05

COMMUNICATION & PITCH

/20

Clear, engaging, and accessible

Exceptional17–20

Pitch is compelling, well-structured, and delivered with clarity. The team communicates the problem and solution in a way anyone could understand. Human, authentic, and jargon-free.

Proficient13–16

Pitch is clear and covers all key points. Delivery is confident, engaging, and mostly jargon-free.

Developing7–12

Pitch covers the basics but may be disorganized, overly technical, or exceed time. Key points are present but delivery needs polish.

Beginning1–6

Pitch is unclear, missing key elements, or heavily reliant on jargon. Difficult to follow.

RELEVANCE TO/20
AI USE/20
PROTOTYPE &/20
EQUITY, ETHICS/20
COMMUNICATION &/20
Total Score/100
Optional+5

BONUS

Strong student voice
Pilot-ready idea
Especially inclusive or trauma-aware design

REMEMBER

Empathy for real student lives

Responsible, realistic AI use

Clear thinking over fancy tech

This hackathon is about designing with care, not coding the fastest.

Hackathon Helper