Describe your race, distances, entry fees, shirt options, and participant requirements. Makeform turns the brief into an editable race registration form that keeps runner details, selections, waiver acknowledgment, and payment information in one organized submission.
Route registrations to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a complete starting prompt, tailor it to your event, or send it to the Makeform builder. The structure shown is an example for planning your form.
Audience
Runners and walkers joining a local road race
Format
Single-distance entry with shirt and waiver
Prompt size
229 chars
Example form structure
Single-distance entry with shirt and waiver
Runner and contact details
Running or walking?
Shirt size
Emergency contact
Waiver acknowledgment
Suggested routing tags
5K runners
10K runners
Payment follow-up
Ask for shirt size only when a runner orders a shirt, and show the correct fee after the runner selects a distance.
Step 1
Choose
distance, wave, shirt, and extras
Step 2
Identify
runner and emergency-contact details
Step 3
Acknowledge
event information and waiver text
Step 4
Confirm
fee, payment status, and race instructions
Built for race day
Structured entries support bib planning, shirt counts, runner communication, and fee follow-up.
Show price, start time, pace, or gear questions for the selected distance.
Keep names, age groups, emergency contacts, clubs, and waves in consistent fields.
Review the race, merchandise, fee, waiver, and acknowledgment before submission.
Flexible race formats
Branch one form around courses, waves, prices, merchandise, and participant types.
Combine runner details, shirt, waiver, fee, and confirmation.
Branch fees and questions by course or relay leg.
Add experience, wave, aid-station, and gear questions.
Group households, shirts, fundraising, donations, and adult acknowledgment.
Registration workflow
Refine generated fields, publish, and route registrations to the race-day team.
List distances, prices, shirts, waiver text, deadlines, and confirmation details.
Require runner data, connect course fees, and reveal applicable questions.
Route entries and tag distance, wave, merchandise, or payment follow-up.
Share the form and give runners confirmation and race-day instructions.
Form vs basic signup
Give packet pickup, merchandise, timing, and finance teams structured details.
Field guide
Structure decisions that affect course operations, inventory, communication, and reconciliation.
Runner profile
Collect preferred name, contact, birth date or age group, and optional club. Separate a household's adult contact from each participant.
Race selection
Use fixed choices for distance, category, wave, and pace. Reveal course-specific information, relay details, or equipment conditionally.
Shirts & extras
Show cut, size, and quantity only when a runner wants a shirt. Match real inventory and separate other add-ons.
Acknowledgment
Display organizer-provided waiver text and notices before acknowledgment. Add guardian fields when applicable and follow your normal review process.
Payment record
Show the total for distance and extras. Record route, reference, and status, using a configured payment workflow instead of card-detail text fields.
Safety & follow-up
Request an emergency contact and relevant notes. Confirm the course, packet pickup, arrival time, change process, and organizer contact.
Related tools
Coordinate general event registration, shirts, athletic acknowledgment, payments, volunteers, and post-race feedback with related Makeform tools.
Create a broader attendee form for expos, pasta dinners, briefings, and other race-weekend sessions.
Open toolCollect standalone merchandise orders when shirts are sold beyond participant registration.
Open toolStructure organizer-supplied acknowledgment questions for amateur athletic participation.
Open toolSet up a focused payment workflow for fees and extras that require separate reconciliation.
Open toolRecruit and assign volunteers for packet pickup, course support, aid stations, and finish-line roles.
Open toolAsk runners about registration, course support, merchandise, and race-day experience after the finish.
Open toolFAQ
Practical answers for race directors organizing participant information before entries close.
Start with runner name, contact information, birth date or age group, emergency contact, and selected distance. Add start wave or pace, shirt choices, extras, entry fee, payment status, and the organizer's waiver acknowledgment. Finish with a clear confirmation and race-day instructions.
Yes. Offer the distances as fixed choices and use conditional logic to show the matching price, start time, pace question, gear information, or relay fields. This keeps one registration link while giving each runner a relevant path.
First ask whether the participant wants a shirt. If yes, show the available cut, size, and quantity choices. Use the exact inventory labels your merchandise team tracks and include the order deadline or note that late selections may differ.
Yes. Place your organizer-provided waiver and event notices before a required acknowledgment checkbox and signature field. Makeform structures the collection step; your organization remains responsible for the wording and any review appropriate to the event.
Show the price connected to the selected distance and extras, then use your configured payment workflow. Store the amount, route, reference, and status staff need for reconciliation. Do not ask runners to type full card details into ordinary text fields.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. A paid tier is available only to remove the Makeform badge; it does not gate the core registration workflow.
Yes. Collect one primary contact, then repeat participant details for each runner or ask for a team roster in a structured section. Keep each person's distance, age group, shirt, and acknowledgment requirements distinct so the operational lists remain usable.
Confirm the participant name, selected distance, merchandise choices, amount or payment status, and registration reference. Then provide packet-pickup details, arrival guidance, change instructions, organizer contact information, and when the runner should expect further updates.
Open registration with a cleaner runner list.
