Collecting extra information and waivers from athletes

What can I ask beyond the core fields?

Anything you need, as a participant question. Five answer types are available:

• Text, for free-form answers like a club name.
• Select, a fixed list of options such as shirt size. A select needs at least one option.
• Number, for things like an estimated finish time in minutes.
• Date, for a qualifying-race date.
• Yes or no, for a simple confirmation.

Mark a question required and an athlete cannot complete registration without answering it. Ask for as little as you can: every required question is a place an entry can stall.

Can a question depend on another answer?

Yes. A conditional question appears only when a previous answer matches a value you choose. The usual shape is a yes/no question followed by its detail:

• "Are you running for a charity?" then, only if yes, "Which charity?"

That keeps the form short for everyone it does not apply to.

Why can I not edit some fields?

Name, date of birth, gender, email, and emergency contact are core fields. They are seeded on every event and reserved, so you cannot rename or remove them. Results, age-group scoring, and race-day safety all read them, and an event that let them vary would break those.

How do I add my waiver?

Add your waiver text as an addendum on the registration setup. It is presented during registration and accepted before payment, and the acceptance is recorded against that entry.

The addendum is your race's own terms. It sits alongside the platform terms rather than replacing them, so write it as your rules for your event.

Can I show what the entry includes?

Yes. Add included items and they render as a list on the registration page: shirt, medal, finisher photo, post-race meal. Up to 40 items. This is the cheapest conversion win on the page, because it answers "what do I get" without the athlete emailing you.