A college hackathon is a weekend with a deadline, a room, and a set of teams who need to know how they will be judged before they write a line of code. The ones that feel chaotic usually skipped the boring list: power, mentors, a locked problem statement, and a rubric the judges have actually read.
This is that list. It fits a society hackathon or a track inside a larger fest. The fest around it is the college fest playbook.
Eight weeks is a workable runway
- Week 8: dates that are not inside exams. One faculty advisor who will reply. A room you can have overnight if you are running overnight — confirm security and access, do not assume it.
- Week 6: problem statements drafted. Judges asked. Sponsors only if you need them for prizes or food; the ask is in how to get sponsors.
- Week 4: registration open. Team size, eligibility and the rubric are on the page.
- Week 2: mentors confirmed, GitHub or submission link tested, food order placed.
- Week 0: check-in, kickoff, a mid-point check, submissions frozen, demos, results the same day.
A hackathon announced on Thursday for Saturday is a coding contest with snacks. Call it that, or give it the weeks.
Checklist before you open registration
- Theme or tracks (one to three, not eight).
- Team size: minimum and maximum. A captain who registers everyone.
- Who may enter: your college, or others. ID at the door.
- What they may use: any tools, or a restricted stack. Say it now.
- Submission: a repo link plus a two-minute demo. A slide deck alone is not a build.
- Hardware: desks, power boards, Wi-Fi that you have tested with a room full of laptops. The classroom network is the usual failure.
- Overnight plan: if people stay, who is responsible, and what the college allowed in writing.
- Food and water on a schedule. Hungry teams do not demo well.
- A code of conduct in one short paragraph, and one person who enforces it.
Registration
Take teams, not a pile of solo sign-ups you will merge at the door.
- Captain name, phone, email.
- Teammate names.
- College and year, as custom questions.
- Track they are entering, if you have more than one.
If there is a fee, collect it at registration. The same pattern as an esports roster is in how to host a BGMI or Valorant tournament. Check the captain in with a QR ticket so you know who is actually in the room: check-in guide.
Judging rubric
Give this to judges and publish it for teams. Score each line from 1 to 5. Do not add a line you cannot see in a three-minute demo.
- Problem. Is it specific, and did they talk to a real user or just invent one?
- Build. Does something run, on a laptop, in the demo? Slides of a future app score low.
- Use. Can someone who is not on the team tell what to do next?
- Scope. Did they finish a thin slice, or start five features?
- Questions. Can they explain a choice they made, including what they cut?
Add the scores. Highest total wins. Break a tie by the Build line, not by which team the faculty knows. One judge should not also be a mentor of a team in the same track.
Tell teams the rubric at kickoff. Judging people against a secret list is how the results get disputed in the corridor.
Demo day
- Freeze submissions at a clock time. Late repos do not get a special case announced in the group.
- Three minutes to show, two minutes of questions. A volunteer holds the timer in public.
- Order posted in the morning. Teams who are not in the room when called move to the end once, then they are skipped.
- Results the same day, with the winning team named and the prize handed over as you promised.
After
Send judges a thank-you. Send sponsors the number of teams that checked in and a photo of the winning demo, not a montage with no count. Keep the rubric. Next year’s team will try to rewrite it from memory and make it worse.
Ready to open teams?
Create the hackathon, collect rosters, and check captains in before kickoff.