Blog

Hackathon checklist for students: what to do before, during and after

· buildtolaunch

This checklist is for students who have signed up for a hackathon and want to know what to do before, during and after. Copy it into your team chat and tick items off. It is the practical companion to our Vietnamese guide to hackathons for students.

Short answer

A hackathon checklist has five parts: read the rules and confirm your team (2 weeks out), set up tools and accounts (1 week out), pack and sleep (the day before), freeze scope and test the demo (the last 3 hours), and submit early with the link, video and slides ready. Most teams lose points on submission mistakes, not on ideas.

2 weeks before: rules and team

  • Read the full rules. Note the deadline, time zone, team size limit, and what must be submitted.
  • Check whether AI tools and vibe coding are allowed, and what you must disclose. If it is unclear, ask the organiser in writing. See can you use AI and vibe coding at a hackathon.
  • Check the judging criteria and write them at the top of your team notes. Every decision later should point back to them.
  • Confirm eligibility: student status, year, university, age, nationality, and whether mixed-university teams are allowed.
  • Register every team member and keep confirmation emails or screenshots.
  • Confirm whether it is in person, online or hybrid, and how you check in.
  • Set up the team chat (Zalo, Messenger or Discord) with all members and one backup contact.
  • Agree on roles. Our guide to team roles in a hackathon (in Vietnamese) shows a 15-minute way to do it.

1 week before: tools and practice

  • Pick your stack now. If you will use a vibe-coding tool, build one tiny app end to end this week so the first login and deploy do not happen at 2 am.
  • Create all accounts and check free-plan limits, because a hosting or AI quota that runs out mid-event can end your demo.
  • Create a shared folder for assets, a shared document for notes, and one code or project workspace everyone can open.
  • Prepare a starter template: a blank project, a colour palette, a logo placeholder and a slide template.
  • Do a 30-minute dry run: pick a random problem, build the smallest version, record a one-minute demo.
  • Read the pitch format. Practise a 3-minute talk with a timer. Our 3-minute pitch script template (in Vietnamese) can help.
  • If the problem statement is released early, talk to 3 to 5 real users of that problem.
  • Share any dietary needs, accessibility needs or travel constraints with the organiser.

The day before: logistics

  • Charge laptops, phones and power banks. Pack chargers, a power strip and a mouse.
  • Pack student ID, ID card or passport as required, and the confirmation of your registration.
  • Bring a water bottle, snacks, a light jacket and earphones.
  • Download offline copies of key documents, docs and slides, in case the venue wifi is poor.
  • Share your venue address, route and arrival time with the team.
  • Sleep. A tired team makes bad scope decisions.

First hour: lock the problem

  • Write the problem in one sentence: who has it and why it matters.
  • List 3 must-have features and 3 nice-to-have ones. Build only the must-haves first.
  • Decide who is responsible for the demo, the slides, the submission and the final test.
  • Set 2 checkpoints, for example at the halfway mark and 3 hours before the deadline.
  • Note where mentors are and when they are available. Ask early, not at the end.

During the build

  • Keep one working version at all times. Save a stable copy before adding any new feature.
  • Demo-first: build the path a judge will see before anything else.
  • Use realistic sample data, not "test test".
  • Take screenshots and screen recordings as you go. You will need them for the submission.
  • Eat, drink water and rest in turns. Do not let the whole team go without sleep at the same time.
  • Write down the sources for every number or claim you will mention in the pitch.
  • Keep a short log of what AI tools you used, if disclosure is required.

The last 3 hours: freeze

  • Freeze features. Only fix bugs from now on.
  • Test the demo on a second device and a different network.
  • Remove broken buttons, empty pages and placeholder text.
  • Record a backup demo video in case the live demo fails.
  • Finish the slides: problem, user, demo, why it matters, team and next step.
  • Rehearse the pitch at least twice with a timer.
  • Prepare 5 likely questions and who answers each one.

Submission checklist

Many hackathons ask for some or all of these. Check your event's rules for the exact list.

  • Project title and a one-sentence description.
  • A working link (and a login for judges if needed) or a repository link, with public access.
  • A demo video within the time limit, uploaded or linked where the rules say.
  • Slides or a one-page summary.
  • Names of every team member and their roles.
  • Tools, APIs and datasets used, with licences where relevant.
  • Anything else the organiser lists.
  • Submit at least 1 hour before the deadline. Then open the submission as a stranger would and check every link.

More on this in how to write a hackathon submission.

Right after the event

  • Thank your teammates and mentors.
  • Save the demo, video, slides and code in one place.
  • Write down what you learned and what you would do differently.
  • Ask judges or mentors for feedback.
  • Decide in 48 hours whether you will keep building. See after a hackathon: turning a contest project into a real product (in Vietnamese).

One example: details released on the day

Some events keep the problem secret until the start. RMIT Hackathon 2026, held on 22 and 23 October, released challenge details only on the day, used teams of four, and scored entries through a mix of automated grading and an expert panel. In an event like this, your preparation is about tools, roles and a fast workflow, not about a fixed idea.

Use buildtolaunch to prepare

buildtolaunch is a free community for university students in Vietnam and Southeast Asia, with no paid tier and no coding needed to start. You can take 70+ free courses, practise skills with the AI tutor in Practice, build a small project in a Space with an AI teammate, and post it to the Launch League to rehearse showing your work. Browse hackathons and competitions open to students on Opportunities and check each listing's last-checked date.

FAQ

What should I bring to a hackathon?

Bring your laptop and charger, a power strip, a phone and power bank, your student ID and registration confirmation, a water bottle and snacks. Pack earphones and a light jacket because venues can be cold. Check the organiser's email for anything specific.

How early should I start preparing?

Two weeks is comfortable: rules and team first, then tools and a practice build in the final week. If you have only a few days, prioritise reading the rules, choosing roles and doing one dry-run build with your chosen tool.

What do I do if my team has no coder?

You can still compete if the rules allow AI and vibe-coding tools. One teammate builds with a tool such as Lovable, while others handle research, design and the pitch. Test the full build once before the event, and read the rules on AI use.

When should I stop adding features?

Freeze features about 3 hours before the deadline. Use the remaining time to fix bugs, test on a second device, record a backup video and rehearse the pitch. Teams that keep adding features at the end often submit something that breaks.

What do judges care about most?

It depends on the event, so read the criteria. Common themes are a working demo, a real problem, impact or feasibility, and a clear pitch. Write the official criteria at the top of your notes and check each decision against them.

What should I do the day after?

Save your files, thank your team, collect feedback and decide whether to keep building. If you do, share the project somewhere public and ask five real users to try it.

Read the full Vietnamese guide to hackathons for students for how to find events, form a team, pitch and follow up.