The flag dropped on July 21: after ten days of racing, Blue Rally Europe 2026 wrapped up with 50 teams and a dozen people on the organizing side. It was a first for us too: RaidLine’s first real-world event, with every module in production from start to finish. Here is how it went, and what we take away from it.
A first under real conditions
We built RaidLine for rally raids, but software proves nothing until it has run during a race. From July 12 to 21, the app, in the event’s colors, served 50 teams in the field and the organizing crew every day. Live tracking, navigation, announcements, leaderboard, race control: nothing stayed on the shelf, everything was used, every day.
Navigation, judged by the people driving
The teams’ feedback converged on two points. First, ease of use: the app was called intuitive and usable without training, which matters when you onboard 50 crews with very different backgrounds. Second, navigation: several teams told us the app genuinely helped them follow the official route, stage after stage, with pre-downloaded offline maps and the day’s track always at hand.
That is the feedback we care most about: navigation is the module crews use the longest each day, in the worst conditions (sun on the screen, rough tracks, no-coverage areas). For how it works in detail, see our article on offline GPS navigation for rally raids.
A leaderboard plugged into the organizer’s Google Sheet
The organizers kept their results in a Google Sheet. Rather than force double data entry, we connected the RaidLine leaderboard to that sheet, used as the master data source: the race team kept working in its own tool, and the standings published in the app updated for teams and the public.
That is a lesson we are keeping: the master data can stay with the organizer. The platform’s job is not to replace tools that already work, but to extend them out to participants and spectators.
Announcements and race control: the daily rhythm
Announcements set the pace of the event: race information, schedules and instructions, broadcast globally or to specific groups, delivered as native push notifications even with phones locked. On the race-direction side, race control followed the event continuously on the live map, with search and per-crew filtering to answer questions from the field quickly. We had described that setup in our article on running race control on GPS tracking; seeing it hold for ten days under real conditions was the point of this first.
On the organizing side: the software, and the people behind it
The organizing team’s feedback was less about a feature than about the accompaniment: continuous monitoring of the systems throughout the event, and our team’s availability to help with the software as the race days went by. This event reinforced a conviction of ours: on a raid, software is not delivered, it is accompanied. A question at 6 am at the stage start deserves an answer at 6 am, not a ticket.
What we take away
- Every module validated in production: ten days of racing, 50 teams, tracking, navigation, announcements, leaderboard and race control in continuous use.
- The master data can stay with the organizer. The leaderboard plugged into a Google Sheet showed we can integrate with existing tools instead of replacing them.
- Ease of use outweighs the feature list. An app that crews understand without training is an app they actually use.
- Support is part of the product. Monitoring the systems and being present during the event count as much as the code.
Next stop: Blue Rally Bardenas, October 24 to 30, 2026.
What about your next event?
RaidLine equips rally raids with a white-label app: live tracking, offline navigation, announcements, real-time leaderboard and race-control tools, with our team on call during the event. Demo available on request.
Request a demo