DNF is not failure — it's data
Runners DNF for many legitimate reasons: injury, medical intervention, cutoff time, withdrawal at their own decision. Your DNF handling protocol defines how your event treats people at their most vulnerable moment. Get it right and you keep their trust; get it wrong and they never come back.
Categories of DNF
DNF is an umbrella. Sub-classify for proper handling:
Medical DNF — runner pulled by medical team or walked off injured
Cutoff DNF — runner didn't make the required time at a checkpoint and was stopped
Voluntary DNF — runner chose to stop (conditions, feeling, schedule)
Disqualification (DQ) — different from DNF; cheating, cutting course, etc.
Did Not Start (DNS) — registered but never started
Results display
Best practice for publishing results:
- Official final rankings include only finishers
- DNF/DQ/DNS listed separately (clearly labeled)
- DNF participants keep their registration record but don't have a finish time
- No rank assigned to DNF
Do NOT include DNFs in sorted ranking lists — it's misleading and looks unprofessional.
Who decides DNF status?
The decision chain:
- Race director or medical lead on course marks the call
- Race director reviews and finalises in results system
- Published result reflects the call
Avoid ambiguity — the runner should know at the moment of pulling out whether they're DNF-M (medical), DNF-C (cutoff), or DNF-V (voluntary).
DNF communication protocol
When a runner DNFs, within 48 hours:
- Personalised email from race director
- Acknowledge they attempted
- If medical: offer contact info for follow-up
- If cutoff: explain the cutoff rationale briefly
- Invite them to next year's event
This email turns a negative experience into a relationship moment.
Refund policy for DNFs
Standard approach: no refund for DNF. Reasons:
- Your costs (T-shirt, medal, per-participant fees) are already spent
- The runner took a start slot that could have gone to someone else
- Refunds create admin burden
Some races offer partial goodwill:
- 50% credit toward next year's registration
- Free comeback entry next year for medical DNFs
- Transfer of their registration to a friend post-race (informal — your T-shirt/medal went to them)
Decide policy in advance. Publish it. Don't negotiate on a case-by-case basis (you'll create inequity).
DNS (Did Not Start) specifics
Different from DNF. DNS is the 5-10% of registered participants who never appeared. Typical causes:
- Last-minute injury / illness
- Life event (work emergency, family)
- Weather concerns
- Registered impulsively, lost interest
DNS default policy: no refund, no transfer. State clearly on registration page.
Some races allow DNS registration to become a next-year credit (40-50% off next year), which reduces refund pressure and builds loyalty.
Marking DNF in Time-Monkey
During or after the race, race director can:
- Open Participants list
- Find runner by BIB or name
- Mark status: Finished / DNF / DQ / DNS
- For DNF: select reason (Medical / Cutoff / Voluntary)
- Optional: add notes (visible only to admin)
The results page filters and displays appropriately.
What DNFs tell you about your race
Track DNF rates by distance:
- 5K: 1-2% typical
- 10K: 2-4%
- Half-marathon: 3-5%
- Marathon: 8-15%
- Ultra: 25-50%
If your DNF rate is significantly higher than typical:
- Too aggressive cutoffs
- Course issues (bad signage, dangerous sections)
- Weather extremes
- Participant mismatch (entry-level runners signing up for advanced distance)
Use DNF data to tune future events.
Participant-side UX
When a runner with a DNF views their Time-Monkey profile:
- Race listed with "DNF" label (not hidden)
- Attempt recognised
- Option to add personal note / reason (private)
Hiding DNFs as if they didn't happen feels dishonest and doesn't serve the runner.