hackathon-submission-checklistlisted

## The Submission Advantage Your submission is the artifact that outlives your pitch. Judges deliberate without you, so your Devpost, README, and demo video speak on your behalf. TL;DR Judges deliberate without you, so your Devpost, README, and demo video are what win the room. Treat the submission as a first-class deliverable, not a last-30-minutes rush. Your Devpost README, GitHub repo, and demo video are what judges reference during deliberation. When they can't remember your project, the submission is the tiebreaker. #### Devpost README Most judges read this during deliberation. It frames your project for everyone, including those who never saw your live demo. Tell the full story: problem, solution, tech, and vision. Most hackathon winners allocate 1-2 hours specifically for writing this. It's not an afterthought. #### GitHub README Technical judges will click your repo link. Clean code, clear structure, and a README with architecture diagrams separate serious teams from weekend projects. The GitHub README is for developers. The Devpost is for everyone. Write both. #### Demo Video Visual proof that persists into deliberation. When judges forget your project (it happens often), the demo video is the reminder. Nothing beats seeing it actually work. Devpost calls the demo video [one of the most important elements](https://help.devpost.com/article/84-video-making-best-practices) of your submission. [Tom Preston-Werner](https://tom.preston-werner.com/2010/08/23/re