Incident tracking
Every race incident logged, until it is resolved.
An injured runner, missing course markings, an aid station running out of water: Zenko keeps incidents in one shared log, with priority, location and status.
- Injured runner, ankleCheckpoint 3 · Col de la Croix
- Course markings missingNorth descent · km 22
- Running out of waterAid station km 12
- Volunteer running lateAid station km 18
A digital event log for the command post
Four priority levels
Low, medium, high, critical: urgent incidents rise to the top and stand out.
Linked to the right checkpoint
Attach the incident to a checkpoint and a race to know instantly where to send help.
Status tracked as a team
Open, in progress, resolved, closed: the whole team knows what is handled and what is still waiting.
Full history
After the race, review the timeline of every incident for your debrief and next year’s edition.
Fewer lost messages, a calmer command post
On race day, information comes from everywhere: radios, text messages, calls, runners passing through aid stations. Without a tool, an incident reported at 9 a.m. can be forgotten by 10.
With Zenko, every incident becomes a record visible to the whole organizing team. The command post sees open incidents in real time, next to checkpoint coverage.
FAQ
Frequently asked questions
Does Zenko replace the medical response plan?
No. Zenko is an operations tool that helps log and coordinate. It does not replace medical teams, emergency procedures or official emergency numbers.
Who can report an incident?
Organizers as well as volunteers registered for the event, from the command post or their phone. The incident is immediately visible to the rest of the team.
Can I review incidents after the race?
Incidents remain available after the race, newest first, to prepare your race debrief.
Your next race deserves a calm command post.
Create your event in two minutes. Free for the whole beta, no credit card.