# Retirements, breakdowns and recovery: managing assistance in a rally raid

Published October 1, 2026 · Race control · The RaidLine team

> Spotting a stopped crew on the live map, calling the retirement, organizing recovery: how to manage assistance in a rally raid from race control.

- Article (HTML): https://raidline.net/en/blog/rally-raid-retirements-recovery
- French version: https://raidline.net/blog/gestion-abandons-assistance-rallye-raid
- Publisher: RaidLine, white-label mobile app for live GPS tracking, navigation and route management for rally raids: https://raidline.net/ (contact@raidline.net)

On a rally raid, not every vehicle makes it back to the bivouac under its own power. Mechanical failure, a hopeless bogging, broken parts, an exhausted crew: assistance in a rally raid is part of the race, just like timing, and a retirement is something you manage, not something that happens to you. Here is how to spot a stopped crew on the live map, run the decision chain from race control, organize the recovery and keep the people watching from home informed.

## Spotting the stop: the live map before the phone

Most retirements do not start with a radio call: they start with a dot that stops moving. With [live GPS tracking](https://raidline.net/en/blog/rally-raid-live-tracking), race control sees the stop before anyone reports it, and that is the whole difference between an organized recovery and an improvised one.

You still have to read that stop correctly. A stationary dot can be a photo break, a puncture fixed in twenty minutes or a dead gearbox. Three pieces of information settle it:

- **The beacon’s status buttons.** A crew that sends “all good” or “mechanical assistance requested” answers the question before it is asked. It is the first reflex to teach at the briefing.

- **How long the stop lasts.** Set a threshold before the race (say fifteen or twenty minutes stationary with no status) beyond which race control contacts the crew. A written threshold avoids debates mid-stage.

- **Where it happens on the route.** A stop at a passage control or a refuelling zone does not mean the same thing as a stop in the middle of a difficult sector, far from any access track.

One case ends all analysis: the SOS signal. It no longer belongs to assistance but to emergency response, with its own alert chain, described in our article on [the SOS procedure for rally raids](https://raidline.net/en/blog/rally-raid-sos-procedure). Everything that follows concerns the crew that is safe and sound while its race is in danger.

## The decision chain at race control

Once the stop is identified, the decision always follows the same thread: contact, diagnose, decide, log.

**Contact.** From the crew’s card on the tracking screen, the call or message goes out in seconds, without digging through a binder for a number. If the crew does not answer and has sent no status, you escalate: the next crew on the route, the nearest organization vehicle, then dedicated means.

**Diagnose.** The question is not “what is broken?” but “can the vehicle restart, how soon, and with what help?”. Three possible answers: the crew repairs alone and carries on; one-off assistance is enough (a short tow, a part, a hand); the vehicle will not restart today.

**Decide.** As long as there is no safety issue and no missed deadline, the retirement belongs to the crew. Race control decides in two cases: the sector’s closing time has passed, or leaving the vehicle out would create a risk (nightfall, isolated area, weather). The most useful criterion is time: a recovery decided at 3 pm is a logistics operation, the same one decided at 7 pm becomes a night search.

**Log.** Every contact, every decision, with the time, in the race control log. That document is what counts in a dispute, and it is what lets the night shift pick up an open case. We detailed this organization in our article on [race control in a rally raid](https://raidline.net/en/blog/rally-raid-race-control-gps).

## Organizing assistance and recovery

Recovery is planned before the start, not at the moment of the breakdown. The classic setup rests on two complementary resources:

- **The sweep vehicle** runs the route behind the last competitor. It guarantees nobody is left out on the course, but it moves at the race’s pace: a crew stopped early in the sector can wait for it for hours.

- **A fast intervention vehicle**, able to cut to a point on the route via access tracks: it handles the urgent or isolated cases without waiting for the sweep.

For every retirement, race control has four things to bring home, and it pays to treat them as four separate lines in the log: the vehicle (to the evening bivouac or an agreed pick-up point), the crew (in which vehicle, with how many free seats), their belongings, and the GPS beacon. The beacon stays powered on the vehicle to the end: it lets you follow the tow on the same map as the race, and proves where the vehicle was left if the recovery stretches over two days.

Sizing is calculated on the most isolated stage, not the average one: how many vehicles can drop out on the same day, how many free seats remain in the organization’s vehicles, and who closes the course if the fast vehicle is already engaged? RaidLine’s race-control tools (live map, prolonged-stop alerts, crew cards with direct contact, detailed on our [features page](https://raidline.net/en/features)) do not replace that setup: they feed it the right information at the right time.

## The retirement in the results and on the public map

A retirement is also an administrative act. As soon as the decision is made, the results must reflect it: the crew moves to retired in the stage results, and the overall standings published in the app update for everyone at once. A paper board corrected in the evening at the bivouac, while the app still shows the crew racing, manufactures protests.

On the public map, resist the temptation to make the dot disappear. A crew that vanishes from the map without explanation triggers exactly the worried calls you wanted to avoid. A clear status (retired, crew taken care of) says the essential: their race is over, their safety is not in question. The track history, on the other hand, is kept: it documents the day and backs you up if the discussion resumes after the race.

## Closing the loop with family and sponsors

While race control organizes the recovery, families and partners are watching the same race on the public map. For them, a dot that has not moved for two hours in the middle of a desert is a source of anguish, not a data point. That is the second half of managing a retirement: informing the people following from afar.

Two habits are enough. First, update the crew’s public status as soon as the situation is understood, as covered above. Second, ask the crew, as soon as they are safe and reachable, to message their family themselves: nothing reassures better. The organizer does not have to run each crew’s private communication, but must make sure the public map does not tell a more worrying story than reality. On what family members actually see, read our article on [sharing the race live with family and sponsors](https://raidline.net/en/blog/share-rally-live-family-sponsors).

## Common mistakes

- **Improvising the doctrine during the race.** The stop threshold that triggers a contact, who calls a retirement, the cut-off time for a daylight recovery: all of it is written before the start and presented at the briefing.

- **Deciding too late.** Waiting “one more hour” to see whether the crew can repair turns a daylight recovery into a night operation. Set the cut-off time and hold it.

- **Recovering the vehicle and forgetting the rest.** The crew with no seat, the belongings left in the vehicle, the beacon never returned: four lines in the log, four boxes to tick.

- **Leaving the public map unexplained.** A dot that sits still or disappears with no status generates calls to race control at the worst moment. The public status is part of the procedure, not of marketing.

- **Sizing the sweep on the easy day.** A single sweep vehicle for the whole field holds up as long as there is one breakdown. It is the day with three simultaneous retirements that dictates the setup.

> **See the stops before the calls**

> RaidLine equips rally raids with a white-label platform: live map for race control and the public, status buttons and alerts, crew cards with direct contact, standings updated in real time. Demo available on request.

> [Request a demo](https://raidline.net/en/demo)

## Frequently asked questions

### How do you know whether a stopped crew is in trouble?

Cross-check three things: how long the dot has been stationary on the live map, the status sent from the beacon (all good, assistance requested, SOS) and direct contact with the crew. A stop with no status that passes the threshold set by race control triggers a call; no answer, and you escalate.

### Who decides that a crew retires?

The crew decides for itself as long as there is no medical emergency and no safety issue. Race control decides when the sector’s closing time has passed or when the state of the crew or the vehicle demands it. Either way, the decision is formalized at race control, with the time, in the log.

### What happens to the GPS beacon after a retirement?

It stays powered on the vehicle until recovery is complete: it lets race control follow the recovery the same way it followed the race. It is only handed back once the vehicle has reached the bivouac or the agreed pick-up point, and its return is ticked off in the inventory.

### Should a retired crew be removed from the public map?

Better to switch it to a retired status than to make it vanish. A dot that disappears without explanation worries the family members following the race; a clear status says the crew is being taken care of and the race goes on for everyone else.

## Also worth reading

- [Rally raid live tracking: give your spectators the race in real time](https://raidline.net/en/blog/rally-raid-live-tracking)

- [Race control: running a rally raid on live GPS tracking](https://raidline.net/en/blog/rally-raid-race-control-gps)

- [SOS button and emergency procedure for rally raids](https://raidline.net/en/blog/rally-raid-sos-procedure)