A hackathon starts with strangers and a deadline. If you know their skills before the doors open, you can form balanced teams on day one, not by guesswork. I would collect that in one link, along with food needs and the rules.
Who it is for
Organisers of student hackathons, company build weekends and community game jams who want to know who is coming and what they can do.
What each question is for
- Contact and profile link: a way to reach people and a quick look at their work.
- Team status and team name: whether someone has a team, wants one or comes alone.
- Skills and experience: so teams are balanced and first timers get support.
- Idea notes: what people want to build, which helps you pick mentors.
- Food needs and t-shirt size: for the catering and swag orders.
- Code of conduct: a required tick before submitting.
What a participant's AI would ask
"Do you already have a team?" Then "Which skills do you bring?" Then "Is this your first hackathon?" The AI shows every answer and sends them only after a yes. Learn about agent-fillable forms.
Before you use it
Set max_responses to your venue capacity and close sign ups a few days early, so you have time to form teams. For an online kickoff, a webinar registration form works well. A pre-event skills session suits a workshop registration form. See forms for events and forms for SaaS and startups.
Questions
How do I match people who need a team?
Filter the CSV on team_status for people who want to join a team, then group them by the skills column. Each new team then gets a mix, such as backend, frontend and design.
Can I make the code of conduct compulsory?
Yes. The code of conduct question is a required tick box, so nobody can submit without agreeing. Paste a link to your own rules into the form description.
Does it show who actually turns up?
No. It records sign ups only. On the day, run an attendance or sign in form and compare the two CSV files to see who came.