How to build a hackathon registration form (questions and template)

Muhammad Khawaja
Muhammad Khawaja
Updated

A good hackathon registration form collects contact details, skills and experience, team status, track or challenge interest, in-person or remote participation, T-shirt size, dietary and access needs, and agreement to the code of conduct, in about 15 questions. Use logic so solo hackers and teams see different follow-ups, and close registration automatically when you hit capacity or the deadline.

Below is the full question list, how to set up the logic, and what to do with the data once people register. You can start from the hackathon registration form template, which includes all of these except the portfolio link (add a website question if you want it).

Hackathon registration form questions

Section Question Question type
About you Full name Short text
Email for event updates Email
Which best describes you? (student, professional, first-time hacker...) Dropdown
Where do you study or work? Short text
Skills Which skills do you bring? (frontend, backend, design, data, product...) Multiple choice, multiple selection
GitHub, LinkedIn or portfolio link Website
Teams Are you joining with a team? Multiple choice
Who is on your team? (if yes) Long text
Would you like us to match you with a team? (if no) Yes/no
Event Which track interests you most? Multiple choice
How will you take part? (in person, remote) Multiple choice
Logistics T-shirt size Dropdown
Any dietary requirements? Multiple choice with "Other"
Anything we should know about access or support on the day? Long text
Agreement Do you agree to follow the event code of conduct? Yes/no (required)

Keep it to what you'll actually use. Every extra question is one more reason to stop halfway, and most people register from a phone.

Set up logic for teams and solo hackers

Team formation causes the most back-and-forth for organizers, so let the form sort it out:

  • "Are you joining with a team?" If yes, go to "Who is on your team?" and ask for team members' names and emails. If no, skip to "Would you like us to match you with a team?".
  • Matching list. Everyone who answers yes to matching goes on a list you can use for a team-forming session at the start of the event. Filter the response table or your Google Sheet by that answer.
  • Remote participants. If someone picks "Remote", skip the T-shirt and dietary questions (or ask for a shipping address instead if you post swag).

Logic in FlowyForm is set per question: "if answer is ... go to question X", with all-or-any conditions. See the best conditional form builders for more patterns.

Code of conduct and waivers

Link to your code of conduct in the question text and make the yes/no question required. If your venue needs a signed liability waiver, add a signature question after the waiver text, or send a separate liability waiver form to confirmed participants.

Capacity, deadlines and tracking sources

  • Close the form automatically at a date and time or after a set number of completed registrations, so you don't oversubscribe the venue.
  • Track where sign-ups come from with hidden fields. Add ?source=discord or ?source=university to the link you share in each channel and the value is stored with each registration.
  • Personalize the ending with answer recall ("You're registered, Sam") and tell people what happens next: when you'll confirm places and where to join the community chat.

What to do after someone registers

  1. Get the data to your team. Connect Google Sheets so each registration becomes a row for logistics, or post each one to a Slack channel for organizers.
  2. Send a confirmation. You get an email notification for each response on any plan. On Premium you can also send registrants a confirmation email with the schedule and community link, or redirect them to your event page when they finish.
  3. Plan catering and swag from real numbers. Export to CSV and count T-shirt sizes and dietary needs instead of guessing.
  4. Shape the program. If most registrants pick one track or skill, adjust workshops, mentors and prizes to match.
  5. Check in on the day. Print a QR code that links to a short check-in form, or work from the registration sheet.

FlowyForm doesn't sell tickets or take payments. For a paid hackathon, send people to your ticket or payment page with an ending redirect after they register, or read our guide to automating event registration and ticket sales.

After the hackathon

Collect feedback while it's fresh. Ask about the venue, mentors, tracks and judging, and whether people would come back. Our post-event survey questions cover what to ask.

FAQ

What should a hackathon registration form include?

Name, email, role or experience level, skills, portfolio links, team status, preferred track, in-person or remote, T-shirt size, dietary and access needs, and agreement to the code of conduct.

How do I handle team registrations?

Ask whether the person is joining with a team. If yes, collect team members' names; if no, ask whether they want to be matched, then use those answers to run a team-forming session.

How do I limit the number of hackathon registrations?

Set the form to close after a number of completed responses, or at a date and time.