How to write a hackathon submission
· buildtolaunch
This guide is for students submitting to an online or hybrid hackathon on Devpost, Devfolio or a similar platform, including students who did not write the code themselves. You will get a clear structure for the write-up, a template to copy, a plan for the demo video and a last-hour checklist. For the whole journey from finding an event to what comes after, see the Vietnamese-language hackathon guide for students.
Short answer
A good hackathon submission lets a tired judge understand your project in under a minute. Open with one sentence on who it is for and what it does. Then explain the problem, show a short demo video, say honestly what you built and what is still a prototype, and make sure every required link works. Submit before the deadline, not at it.
What a submission is made of
Fields differ by platform, but most ask for the same items. Devfolio's project submission guide lists a project name, a tagline (a one-line pitch), the problem it solves, challenges you ran into, technologies used, links, a video demo and screenshots (the first image becomes the cover). A Devpost guide published by a hackathon team lists a title, short description, public repository link, public demo video link, images and team members.
Read your event's rules first. Required items change from event to event, and a missing one can make a project ineligible.
Write for a judge with five minutes
Judges often see many projects. Jacklyn Biggin, writing on DEV Community, says judges may have about five minutes per project, so the most important information should come first. She also advises keeping the template's headings, because deleting them makes it easy to skip key details, and tailoring the write-up to the event's published judging criteria.
A judge who wrote up what separated teams in a year of judging, in another DEV Community post, found that teams that opened with context instead of a plain statement of the product lost about a third of their slot. The lesson for writing is the same: first sentence, what it is.
A template you can copy
Replace the brackets. Keep each part short.
Tagline (one sentence): For [who], [project name] helps [do what] by [how], so they can [result].
The problem (2 to 3 sentences): [Who] struggles with [specific problem]. Today they [what they do now], which [why it fails]. [One fact, number or short quote from someone you asked.]
What it does (3 to 5 bullets):
- [Main feature, described as what the user can now do]
- [Second feature]
- [Third feature]
How we built it (3 to 4 sentences): We used [tools and AI services]. During the event we built [parts]. We used existing [libraries, templates or data] for [parts].
What works and what does not (2 to 3 sentences): Working today: [list]. Prototype or mocked: [list]. Not built yet: [list].
Challenges (2 sentences): [One real obstacle and how you handled it.]
What is next (1 to 2 sentences): [Next step, and who you would test it with.]
Links: Demo video: [link]. Live app or prototype: [link]. Repository or project files: [link].
Here is a filled-in example for a made-up project. Tagline: "For first-year students who never learned to budget, SplitMate helps a dorm room track shared costs by turning a photo of a receipt into a split, so nobody has to chase anyone for money." That one sentence already says who, what and why.
RevenueCat's guide to pitching a Shipaton app suggests a similar order for the written description: a one-sentence logline, a paragraph on the problem and why existing options fall short, a paragraph on how the app works, and a closing paragraph with evidence such as test results or early user feedback.
Plan the demo video
Check the event's limit before you record. Examples from public guides: MLH recommends a 2-minute demo video in its judging guidance for organizers, which should show the hack working rather than present it; the Shipaton guide above sets a three-minute maximum. Whatever the limit, put the proof early.
A simple structure:
- Seconds 0 to 15: who it is for and the problem, in one or two plain sentences.
- Next 60 to 90 seconds: one full flow, working, with narration about what the user achieves.
- Last 15 seconds: what is next and where to find the project.
Practical tips:
- Record the screen first and add voice after, so mistakes are easy to redo.
- Make the video public and test the link while logged out.
- Avoid music or logos you do not have rights to, as the Shipaton guide warns.
- Split the work: one person writes the script, one records, one narrates. Biggin makes the same point.
Check links and required items
Judges cannot score what they cannot open. Use this list in the last hour:
- Open every link in a private browser window. The NASA Space Apps Challenge's submission guide says to set files to public and test the links that way; if judges cannot access your project, it cannot be judged.
- Repository public if the event requires one. The HackHCC guide above warns that private repositories risk disqualification.
- Video uploaded to a public platform such as YouTube or Vimeo, not only on your laptop.
- Team members all added. On Devfolio, for online events, only the team admin can submit for the team, so add everyone first.
- Sponsor prizes named. Devfolio's guide advises naming sponsor tools under technologies used so judges can find them.
- Press submit, not save. On Devfolio, a project stays "In Draft" until you click "Publish Project".
Start the submission early. Biggin recommends beginning it no later than Saturday evening for a weekend event so that Sunday is free for updates and screenshots.
If you used AI or vibe coding
Be plain about it. Say which tools generated which parts, what you directed and what you checked. Some events require this: the NASA Space Apps guide above has a field where you state whether and how you used AI tools. Honesty also protects you from judges' questions about what you built during the event. See Can you use AI and vibe coding at a hackathon? for how to read an event's AI rules.
Practice with buildtolaunch
buildtolaunch is a free community for students of any major, with 70+ free courses in one library at /courses and no coding needed to start. A good way to practise your write-up is to post a project on the Launch League, a public board that resets every Monday, and see whether strangers understand it from your first sentence. You can build projects in Spaces with an AI teammate, and find hackathons for students on the Opportunities page. For how judges score what you submit, read Giám khảo chấm hackathon dựa trên tiêu chí gì? (in Vietnamese).
FAQ
How long should a hackathon submission be?
Short enough to read in a couple of minutes. A tagline, a few sentences on the problem, a few bullets on what it does, a short note on what works and what does not, and your links is usually plenty. Follow any word or character limit in the event's rules.
What should I put first in my project description?
One sentence that says who the project is for and what it does. Judges may have only about five minutes per project, so context and backstory should come after that sentence, not before.
How long should my demo video be?
Use the event's limit. Public guidance varies: MLH recommends 2 minutes for a hack demo video, and the Shipaton guide sets 3 minutes as a maximum. Show the working product early and keep the narration about what the user can do.
Do I need a GitHub repository to submit?
It depends on the event. Some require a public repository and warn that a private one can lead to disqualification; others only ask for links to a demo or project files. Check the rules, and if you did not write code, ask the organizer what they accept.
Can I edit my submission after I submit?
Often yes, until the deadline, but platforms differ. One Devpost guide says submissions can be edited and resubmitted until the final deadline. Another platform's guide is unclear on editing after publishing, so confirm on your event page and avoid relying on a last-minute fix.
What if my project is not finished?
Submit anyway and say clearly what works, what is mocked and what is not built. MLH advises first-timers to demo their hack even if it is incomplete, and a JetBrains piece written from the judging table says judges notice when teams talk around missing features, while being upfront reads as more confident.
Read the full guide (in Vietnamese): Hackathon cho sinh viên, from finding an event to what comes after.