SOS position and emergency procedure for rally raids

The SOS button on a GPS beacon sends a position in a few seconds. What happens next, who picks it up, who decides, who goes out on the ground, should owe nothing to improvisation: it is a written procedure, known to the whole race control team before the first start. Here is how to build a rally raid’s emergency procedure, from the SOS signal to the all-clear, and where safety is actually won or lost.

The SOS button triggers an alert, not an intervention

On the beacon, pressing SOS does one thing: it sends the crew’s exact position to the tracking platform, ahead of every other event. That already matters, but it is only the first link. The beacon does not know whether the crew is injured, stuck in the sand, or dealing with an accidental press. It does not call a doctor and it does not send anyone to the scene.

It is the organizer’s emergency procedure that turns that signal into a response: who sees the alert, who decides, which team goes out, how following crews are warned, and what gets logged for after the race. Without a written procedure, even the best SOS button on the market protects nobody.

Writing the procedure, from signal to all-clear

A rally raid emergency procedure fits on one page when it is built well. It answers seven questions, in the order they actually come up during a stage:

Who sees the alert first. A single station, watched continuously through the whole stage: race control. Broadcasting the SOS to several screens with no designated owner dilutes the response exactly when every minute counts.
Who attempts contact. Direct call to the crew, then a backup channel (radio, messaging) if the call fails. Contact does not delay sending a team out; it adjusts what gets sent.
Who assesses severity. Based on the position, the context (a known crash, a technical sector, weather) and any contact made, a designated person decides the level of response: mechanical assistance, sweep vehicle, or a medical team.
Which team goes, and from where. The procedure lists the teams available per sector, their starting position, and their estimated time to reach each part of the route.
Who secures the area. Stage marshals are alerted to slow or stop following crews if the incident sits on the racing line.
Who escalates to outside emergency services. The threshold for calling in fire brigade, ambulance services or a helicopter is set in advance with the event doctor, not improvised under pressure on the day.
Who logs everything. Time triggered, time contacted, time the team departed, time it reached the scene, time closed. This log feeds the debrief and, in the event of a dispute, serves as a record of what actually happened.

Every line on this list needs a name attached to it, not a vague role. On race day, nobody should have to wonder who makes the call.

Sizing the medical response with the right people

GPS tracking locates and alerts: it never replaces the event’s medical setup. The number of doctors, ambulances and aid stations, their position on the route, and the thresholds for escalating to public emergency services are defined with the event doctor and, depending on the format and country, with the sporting authority and local emergency services. This sizing work is specific to each event (number of crews, how remote the terrain is, stage length) and no generic article can reduce it to one universal figure: rely on your event doctor and your federation for the requirements that apply to your race.

What the organizer can control directly is making sure the alert reaches the right place without delay, with an exact position, so that medical setup departs at the right time instead of departing late or blind.

The tracking platform’s role in the SOS chain

Between the beacon and the decision, the tracking platform is the link that saves the most time: it shows the SOS position on race control’s map without delay, keeps the crew’s track history to understand the context (speed before the stop, last valid point), and lets you contact the crew without switching screens. That is the difference between an alert handled in a few seconds and one spotted five minutes later in the middle of a stream of other information.

RaidLine surfaces SOS alerts as top priority on race control’s map, with a direct call and messaging one tap away, without leaving the crew’s position. For the full build-out of an alert setup (SOS, speeding, low battery, immobilization), read our article on the GPS beacon and the core of a safety setup; for organizing the command post itself, see our guide to race control for rally raids.

One SOS alert, one position, one tap

RaidLine surfaces SOS alerts as top priority on race control’s iPad, with the exact position, track history and a direct call to the crew without switching screens. Compatible with Neyos beacons, with custom connectors for other providers. Demo available on request.

Request a demo

Dead zones: planning the procedure for when the SOS does not go through

On sectors with no mobile coverage, a GSM-only beacon transmits nothing in real time: only a satellite or hybrid beacon guarantees an SOS gets through immediately, wherever the crew is. If your route crosses dead zones and your whole fleet is not satellite-equipped, the procedure needs a safety net: vehicles passing through the sector regularly, closely spaced checkpoints, and an alert delay agreed in advance (past which a crew missing at a checkpoint triggers a search, even with no SOS received).

Channel redundancy matters for race control too: if race control’s network goes down, a backup radio or satellite channel must keep alerts flowing without interruption.

The crew brief and rehearsing the procedure

The pre-start brief. Ten minutes cover the essentials: when to press SOS (injury, immediate danger), when not to (a flat tire, a simple sand stuck), and what happens next for a crew that is waiting.
The full-scale test. Simulating an SOS during scrutineering or a recce exposes the procedure’s gaps (nobody reachable, a team unavailable, a poorly covered zone) while there is still time to fix them.
A procedure that is displayed, not just written. Race control needs the sheet in front of them, not filed away and consulted after the fact. A simple table, with the day’s names and numbers current, beats a theoretical document.
A debrief after every trigger. Every SOS, real or false, deserves a quick review: what worked, what took too long, what to adjust for the next stage.

Mistakes that cost time on the day it matters

A procedure that only exists in the organizer’s head. If one person alone knows the sequence and they are unavailable at the critical moment, the chain stops. The procedure must be written down and known to the whole race control team.
No clear threshold for medical escalation. Deciding under pressure whether to call public emergency services wastes precious minutes. The threshold is set calmly, with the event doctor, before the start.
A single communication channel. If race control’s mobile network fails at the same time as the race’s, nobody receives anything. Plan an independent backup channel.
No crew brief. Competitors who do not know when to press SOS generate false alerts that wear down race control’s vigilance, until the day a real alert gets handled a beat too late.
Zero rehearsal before the race. A procedure never tested reveals its flaws under real conditions, at the worst possible moment.

Frequently asked questions

Who should receive the SOS alert first?

Race control, on a single station watched continuously during the stage. Routing the SOS to several people with no designated owner dilutes the response; one person must be responsible for triggering the procedure.

Should an intervention team always be sent after an SOS?

Yes, assuming severity until the crew confirms otherwise. Radio or phone contact that reassures lets you adjust which team you send, not skip sending one.

What if the SOS is sent from a dead zone?

A satellite or hybrid beacon keeps transmitting where GSM disappears, which should drive the hardware choice on remote sectors. Otherwise, the procedure relies on following vehicles, checkpoints, and an alert delay agreed with crews before the start.

How do you test an emergency procedure before the race?

By simulating an SOS during scrutineering or a recce: trigger, reception at race control, decision, team departure. This drill exposes gaps (nobody assigned, a team unavailable, a poorly covered zone) while there is still time to fix them.