Form · Event registration
Hackathon registration form template
Covers what organisers actually need before the weekend: skills, experience, which track people want and whether they already have a team. Anyone looking for teammates says what they can bring and what they need, so matching is quick, and everyone agrees to the code of conduct before they finish.
Try it live
Try it as a respondent
Every question, and where it leads
The conversation
What a respondent is asked, in order.
Ready to build something? Let's get you registered for the hackathon.
Who's hacking?
Which best describes you right now?
Which school, college or university do you attend?
Link to your GitHub, portfolio or a project you've built
How many hackathons have you taken part in?
What can you bring to a team?
Which track are you most interested in?
Do you have a team?
Who's on your team? Name and email for each person.
What kind of teammates would suit you?
Got an idea already? Tell us in a sentence or two.
T-shirt size?
Any dietary requirements?
Any allergies, access needs or anything else we should plan for?
Please agree to the code of conduct
Ends with
You're in 🚀
The flow
Where each answer leads. Every route here is editable once the form is yours.
Contact info
Single select
Short text
Website
Single select
Multi select
Single select
Single select
Long text
Long text
Long text
Dropdown
Multi select
Long text
Consent
What this template uses
- Contact info
- Single select
- Short text
- Website
- Multi select
- Long text
- Dropdown
- Consent
- 7 branches
Questions to consider
- What are your real tracks or challenge themes? Replace the track options with them.
- What's your maximum team size, and should the teammates question say so?
- Is the event open to everyone, or only students? If only students, remove the other status options.
- Will you provide food and T-shirts? Delete those questions if not.
- Does your code of conduct need to match an existing policy from your school or sponsor?
How to use the responses
Start with team matching: filter for people who asked to be matched, then group them so each team has a mix of the skills they listed and an interest in the same track. Check that everyone named as a teammate has registered too. Count the tracks to plan mentors and judges, and send the T-shirt and dietary totals to suppliers from a CSV export. First-timers are worth a welcome message or a beginner session.
How to customize and share it
- 1Replace the track options with your themes and edit the greeting with your dates and venue.
- 2Swap in your own code of conduct wording, keeping it short enough that people actually read it.
- 3Share the link on your event page and with student groups, or embed it on the hackathon website.
Frequently asked questions
What should a hackathon registration form ask?
Contact details, background, skills and experience, team status, track interest, and practical details like dietary needs and T-shirt size. Agreement to a code of conduct is standard too.
How do you form hackathon teams from registrations?
Ask who needs a team and what they can bring, then group people so each team has a mix of skills, such as a developer, a designer and someone to pitch.
Should a hackathon have a code of conduct?
Yes. It sets expectations for behaviour and gives organisers a clear basis to act if someone causes harm. Asking people to agree during registration means nobody can say they didn't see it.
Can beginners register for a hackathon?
Usually, yes, and many events welcome them. This form asks how many hackathons someone has done, so you can offer first-timers extra help.