How to set up live tracking for a race or ride

To set up live tracking, decide who will carry what, test the course for signal, brief participants, publish one link for viewers, and plan for gaps. Do the testing early. Almost every tracking problem on the day was visible a week before.

Step 1: what do you want tracking to do?

Name the purpose before the tools. It changes every later choice.

• Event with many participants: you want the whole field on one map, with each person easy to find.
• A small group or club ride: you want members to see each other and friends to follow.
• One athlete on a long effort: you want family and supporters to follow a single dot, possibly in remote places.

Write down who will watch, on what devices, and what they need to know: position, trail, expected arrival, or all three.

Step 2: which devices will participants carry?

The choice is between phones, dedicated trackers and sports devices that report to a service. Phones are convenient and need coverage. Trackers cost more to supply and manage but work where coverage doesn't. Phones or dedicated trackers for live race tracking sets out the trade-offs.

For an organiser, the question is also logistical. If you hand out trackers, who collects them, charges them, assigns them to people and gets them back? If participants use their own phones, how will you help those who don't have the app working?

Step 3: how good is the signal on your course?

Walk, ride or drive the course with the exact setup you plan to use and note where positions stop updating. Check the start, the finish and the places spectators will gather, since those are where demand peaks.

Then decide what to do about gaps:

1. Accept them, and tell viewers they are normal.
2. Add satellite trackers for the weakest sections or for lead and sweep riders.
3. Choose a device that stores positions and fills in the trail when it reconnects.

Step 4: how will participants join?

Every extra step loses people. Keep the path short:

• Tell participants what to install or carry, and when.
• Give a clear way to match each person to a dot on the map, such as a name or bib number.
• Ask them to test before race day, not at the start line.
• Tell them to start tracking before they start moving, and to keep the device charged.

Decide what participants control. Some will not want to be followed, or not for the whole course. Offer a clear choice about who sees them and when, and respect it.

Step 5: what will viewers see and how do they follow?

Viewers should be able to open a single link and see the map, with nothing to install and no account to create. Put that link wherever your event is announced: the event page, emails, social posts and any printed programme.

Check what the page shows:

• each participant's current position, easy to find by name or number;
• a trail showing where they have been;
• when the position was last updated, so a stalled dot is understood;
• a view that works on a phone, since most spectators will be on one.

What spectators need from live race tracking lists what viewers look for.

Step 6: what can go wrong, and what is your plan?

Prepare for the usual failures.

• A device dies. Remind participants to charge before the start and to carry a power bank on long events.
• A participant's dot disappears. Decide who checks, how, and how fast. For safety, tracking should supplement your safety plan, never replace it.
• Too many viewers at once. Check that your service copes with a crowd at the finish.
• Wrong or missing names. Review the participant list before the start.
• Confusion about what is live. Say clearly when tracking starts and ends.

Run a rehearsal with a small group, using the real course and the real link, and fix what it shows.

Who owns the data afterwards?

Think about this before the event, not after. Positions and trails are personal information. Decide how long the tracking page stays up, whether the trails remain visible after the finish, and whether participants can ask for theirs to be removed. Say so in your briefing. Clear answers build trust, and trust is what gets people to carry the device in the first place.

Should you tell supporters what to expect?

Yes. A short note before the event helps: how to open the link, how often positions update, and that gaps can occur. People who are told a gap is likely stay calm. People who are not, worry.

How do you tell people about it?

Mention tracking everywhere you publish the event, because it is a reason to come and a reason to share. A single link is easy to forward. If you want to see how an AI assistant describes your event page or service today, the Citewake checker can show what it says. Your own tracking page is also something assistants may read, so keep its title and description clear.

What to remember

Tracking is a promise to viewers that the dot on the map is where the person is. Keep that promise by testing early, keeping steps few and showing honestly when a position is old. What is live race tracking? covers the basics if you are new to the field.