Outdoor sports safety: is your plan really in place on race day?

It's 11:20 a.m. A runner is reported in trouble somewhere between kilometer 46 and kilometer 52, on a stretch that's hard to reach. At race HQ, the question isn't "Do we have medical cover?" That was settled three months ago, in the safety plan. The question right now is much simpler, and much harder: who is closest, where exactly are they, and how long will it take them to get there?

In many organizations, the honest answer is: we don't know right away.

A duty of care, not a guarantee

No organizer is expected to guarantee that nothing will go wrong. Nobody can promise that, and the law doesn't ask for it. What you are expected to do is put reasonable measures in place to prevent the risks of your event and respond to them. In French law, this is known as an obligation of means: you are judged on the effort, not the outcome.

The safety guidance sheets circulated within the French Athletics Federation (FFA) put it bluntly: event organizers carry a general duty of safety. That duty is one of means: the organizer must do everything possible to limit risk, and can be held liable if the setup falls short.

For events in natural settings — running, Nordic walking, trail — the same document sets a far more concrete benchmark, and it's the one to keep in mind: the medical setup must be able to reach and treat a casualty at any point on the course within 30 minutes.

Thirty minutes, anywhere on the course

Read that again with your own course map in front of you.

"Anywhere" doesn't mean race HQ or the main aid station. It means kilometer 48, up on the ridge, where the access track ends two kilometers further down. And the 30 minutes don't start when you understand what's happening. They start when the participant gets into trouble.

Meeting that window takes three things, in this order: knowing there's a problem, knowing where, and knowing who to send. The first two depend largely on how well your course is covered. The third depends entirely on you, and it's almost always the one that eats up the most time.

Because response time isn't a property of your plan on paper. It's a property of where your resources actually are when the alert comes in.

What counts as "reasonable" keeps moving

The 30-minute benchmark doesn't change. What changes is what's expected of you to meet it.

The level of resources expected of an organizer is measured against what's available and what others are doing. Ten years ago, not knowing in real time where your team members were across 80 kilometers of course was a technical limitation nobody questioned. Today, most of your team members carry a device in their pocket that can pinpoint their position within a few meters, and tools exist to turn that into something race HQ can actually use.

In other words, the standard is shifting not because the rules have changed, but because the available means have. And the more common a tool becomes among organizers like you, the more its absence needs a reason: a deliberate choice, not an oversight.

Safety is a chain, not a setup

At an outdoor event, safety plays out in six stages, and each one depends on the others:

Prevention — risk assessment, the course, sensitive spots, the expected weather.
Information — what participants know, and what your teams know.
Presence — posts actually staffed, on time.
Location — knowing where your resources are at any given moment.
Communication — reaching the right person, fast.
Response — the actual time between the alert and help arriving on scene.

A chain is only as strong as its weakest link. And the weakest link is almost never the one you worry about. It isn't a lack of first-aiders or a missing emergency plan. It's the gap, on race day, between the setup as planned and the setup as it actually exists at 11:20 a.m.

An approved schedule tells you who should be there. It doesn't tell you who is.

Three questions that reveal the gap

Ask your team before your next edition. If all three answers come without hesitation, your setup is solid.

1. Right now, do you know which posts are staffed and which are empty?

It's the simplest question and the most uncomfortable one. With a hundred posts spread along a course, information usually comes back by radio, by phone, or through a zone lead doing the rounds. So it's patchy, delayed, and it ties someone up. A course marshal who didn't show up at 7:30 a.m. may not be noticed until 9:00, when the first runner reaches the junction.

2. When an incident is reported, how long does it take you to identify the closest person and reach them?

You have a doctor, first-aiders, sweepers, and mobile team members. On paper, they cover the course. But when the alert comes in, knowing which one is six minutes away and which one is forty often comes down to memory and guesswork. Those are the minutes where the 30-minute window is won or lost.

3. After the event, what's left of the setup you put in place?

If a question comes up six months later, what can you show? Many organizers discover at that point that their setup only ever lived in a spreadsheet, a few WhatsApp threads, and the heads of three people. Documenting your safety decisions — the ones you made and the ones you ruled out, with your reasons — won't prevent an accident. But it's the difference between an organization that can demonstrate its diligence and one that has to piece it together after the fact.

Dead zones. You know them for participants. Have you mapped them for your team members, and planned what happens when a post there can't be reached?
Handovers. The moment one team leaves its post before the next one arrives is the most common gap, and the hardest to see.
Abandoned posts. A team member who didn't turn up, or who leaves early for personal reasons, rarely tells race HQ. Sometimes they tell the person at the next post.
The end of the event. How do you make sure nobody — participant or team member — is still out on the course?

What changes when your setup becomes visible

No tool guarantees an accident-free event, and you should be wary of anyone who claims otherwise. But making your setup visible in real time changes three things.

From a planned schedule to the actual situation: staffed and empty posts are visible at a glance, with no one sent out to check.
From guesswork to informed decisions: when an alert comes in, you send the person who is genuinely closest.
From reconstruction to a record: what was planned, assigned, and staffed stays on file.

That's exactly what we built with Qoezion, our volunteer and team management platform: recruitment, scheduling, attendance tracking, and team communication in one place, from one edition to the next. Across all recruitment run through Qoezion, the no-show rate stands at 6%, against a national average of 15 to 20% — that's posts that stay filled on race day.

It's also why we launched Qoezion Spot, our field team tracking app, included in the Qoezion subscription. It turns each team member's phone into a location beacon for the duration of their shift: on a map, race HQ sees staffed and empty posts in real time and can locate the first-aider or doctor closest to an incident.

Privacy is built into the app, and that matters when you're working with volunteers: consent is requested for every session, location is shared only during the shift, only GPS position and battery level are sent, and location data is automatically deleted after 30 days.

The bottom line

Technology doesn't eliminate risk. It raises the bar for what you can reasonably put in place — and when it comes to participant safety, that bar won't come back down.

So the question to ask before your next edition isn't "Are we compliant?" It's this: if an incident happens tomorrow at the most remote point on my course, will I know within a minute who to send and where they are?

Thirty minutes goes fast. The first ten shouldn't be spent searching.

Want to talk it through? Twenty minutes with one of our project managers is enough to review your setup and see what can be supported by the right tools: book a call. Or create your event on Qoezion and try it for free.

This article offers operational guidance and does not constitute legal advice. For the obligations that apply to your event, refer to your federation's technical rules and, where appropriate, your legal advisor.