80% of hackathon success is preparation. Teams that show up with a plan, pre-configured tools, and clear roles outperform teams that figure things out on day 1. Use this checklist.
1 Week Before
- [ ] Team formed and roles assigned
- [ ] Problem statements/tracks reviewed (if available)
- [ ] Tech stack decided (what framework, what database)
- [ ] Starter kit/boilerplate ready (auth, DB, deployment pre-configured)
- [ ] AI tools installed: Cursor, Claude, Copilot
- [ ] Deployment pipeline working (push to GitHub = live on Vercel/Railway)
- [ ] API keys obtained: AI APIs, maps, any external services
- [ ] Design system picked (shadcn/ui, Tailwind components)
- [ ] Laptop fully charged, charger packed, extension cord ready
- [ ] Snacks, water bottle, comfortable clothes prepared
Day Before
- [ ] Final team sync: who builds what, hour-by-hour plan
- [ ] Git repo created, all members have access
- [ ] Test deployment works (deploy empty project, verify URL)
- [ ] Backup plan: what if primary idea doesn’t work?
- [ ] Read the rules: submission format, judging criteria, deadlines
- [ ] Sleep well (seriously – tired teams make terrible decisions)
During the Hackathon
First 2 Hours (Plan)
- [ ] Understand the problem statement completely
- [ ] Sketch the user flow (5 screens max, paper is fine)
- [ ] Define MVP: what’s the ONE thing the demo must show?
- [ ] Split tasks among team members
- [ ] DO NOT start coding until plan is clear
Hours 2-20 (Build)
- [ ] Frontend and backend work in parallel
- [ ] Deploy by hour 6 (even if half-broken)
- [ ] Use AI for ALL boilerplate – don’t hand-write CRUD
- [ ] Check in every 4 hours: “Can we demo right now?”
- [ ] If stuck for 30 min, ask mentors (that’s what they’re there for)
Hours 20-30 (Polish)
- [ ] STOP adding features – polish what exists
- [ ] Add loading states, error messages, empty states
- [ ] Fill with realistic data (Indian names, real-looking content)
- [ ] Test on mobile (judges often check on their phones)
- [ ] Fix the top 3 bugs only (don’t chase all of them)
Last 6 Hours (Present)
- [ ] Write pitch script (3 minutes max)
- [ ] Assign who presents, who demos, who answers questions
- [ ] Practice 3 times – time it each time
- [ ] Record backup demo video (in case live demo crashes)
- [ ] Prepare for 3 most likely judge questions
After the Hackathon
- [ ] Polish project for 1 week – fix bugs, write README, add screenshots
- [ ] Deploy to custom domain if possible
- [ ] Pin on GitHub profile
- [ ] Post on LinkedIn with demo video
- [ ] Write a blog post about what you built
- [ ] Connect with teammates, mentors, judges on LinkedIn
- [ ] Register for next hackathon (momentum matters)