Describe your race, trail run, or club event. Get a focused form covering route difficulty, markings, aid stations, safety, and overall experience.
Send runner feedback to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your event, or send it to the builder. The structure shown is an example.
Audience
5K, 10K, and half-marathon finishers
Format
Mobile-friendly post-race survey
Prompt size
287 chars
Example form structure
Mobile-friendly post-race survey
Which distance did you complete?
Rate the route and course markings
Rate aid stations and traffic control
Where did you notice an issue?
What should we keep or improve?
Suggested routing tags
Course issue
Aid station
Positive feedback
Ask runners to identify the course section before describing a problem; a location turns vague feedback into an actionable course note.
Step 1
Finish
share the form while the course is fresh
Step 2
Rate
score route, markings, aid, and safety
Step 3
Locate
tie issues to a mile, turn, or checkpoint
Step 4
Improve
group themes for the next course plan
Feedback organizers can use
A satisfaction score cannot identify an unclear turn. Structure responses around each runner's path.
Use matching scales for route design, markings, aid stations, safety, and enjoyment across distances and waves.
Request a mile marker, intersection, segment, or checkpoint after reports of confusion, congestion, or hazards.
Tag comments by course, aid, volunteers, or logistics for the relevant event lead.
Made for different running events
Choose an event format, then edit ratings and follow-up questions.
Compare distances and start waves while gathering precise notes on turns, closures, congestion, and water stops.
Match feedback to trail segments and checkpoints, with follow-ups for marking visibility, terrain, and conditions.
Reuse a compact form after each group run to assess route clarity, pace suitability, and regroup points.
Separate early and late course experience and identify issues that emerge after repeated loops or after dark.
Build the survey
Provide event details, then edit the form around decisions your race team can make.
Include distances, surfaces, intersections, checkpoints, aid stations, and groups to compare.
Keep scales consistent. Reveal detail fields after low ratings so other runners finish quickly.
Use the finish email, results page, club message, or QR sign while locations remain memorable.
Filter by course, wave, segment, or station before assigning changes to event leads.
Focused vs generic feedback
Keep the survey short unless a rating reveals something the team should investigate.
Field guide
Connect each response to the runner's course without making everyone complete a long report.
Response context
Ask for distance, wave, or route before ratings. Conditions and congestion vary, so context prevents misleading averages.
Course experience
Separate enjoyment from difficulty. A demanding course can be well designed, while an easy route may have bottlenecks.
Navigation
Ask about signs, marshals, cones, and splits. Reveal location and detail fields only when a runner reports confusion.
Aid stations
Rate placement and supplies separately to distinguish a station-plan issue from a temporary shortage.
Safety and access
Let participants report traffic, surfaces, crowding, lighting, or access concerns with a time and place.
Open feedback
Focused prompts beat a generic box. Ask what should remain and which single change deserves attention.
Related tools
Pair course feedback with registration, volunteer coordination, and broader event surveys.
Gather feedback about the full event, including check-in, atmosphere, scheduling, and organization.
Open toolCreate a broader follow-up survey for participants, spectators, sponsors, or partners.
Open toolCollect participant details, distance choices, and registration information before race day.
Open toolRecruit course marshals, aid-station crews, setup teams, and finish-area volunteers.
Open toolAdapt an evaluation structure when your running club also delivers a coached course or program.
Open toolManage signups for club training sessions, coached workouts, and related fitness activities.
Open toolFAQ
Practical answers for race directors and running clubs planning a focused participant survey.
It is a post-run survey about route design, difficulty, markings, aid stations, traffic control, safety, scenery, and enjoyment, with follow-ups that locate problems.
Ask for distance, then rate layout, wayfinding, aid stations, safety, and overall experience. Request an issue location, favorite feature, and priority change.
Keep the core path to a few minutes. Reveal location, timing, description, and photo fields only after a low rating or reported issue.
Anonymous responses can encourage candid comments. Make contact details optional unless you need follow-up, and explain why they are requested.
Yes. Use distance, route, or wave as a required structured field to separate different terrain, congestion, and aid conditions.
Ask about crossings, traffic, surfaces, lighting, bottlenecks, and marshals. For a concern, request the nearest marker or landmark and approximate time.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge.
Share it soon after the run. Add the link to the results email or event page, or display a finish-area QR code.
Make every mile easier to improve.
