How to Configure GPS Trackers for Ultras

2 days ago

6 min read

A tracker that reports perfectly for the first six hours but goes silent before an overnight ridge section is not a safety tool. To configure GPS trackers for ultras, race directors need to start with the event plan: course exposure, athlete spread, cellular coverage, aid-station workflow, finish-line timing, and the decisions staff must make from live location data.

An ultra is not simply a longer race. The field separates quickly, weather can change the route conditions, support crews may be moving between distant access points, and the final finisher can be on course long after the winner arrives. GPS tracking must be configured around those realities, not around a default device profile.

Start with the operational question

Before assigning a tracker, define why each participant or asset needs to be visible. A 50K with dense aid stations may use tracking primarily for spectator updates and lead-pack monitoring. A 100-mile mountain race may need location intelligence for overdue runners, evacuation coordination, cutoffs, and crew communication. A stage race may require a different setup each day, with fresh start times and separate course files.

This decision affects everything that follows: which participants carry devices, the reporting interval, the alert rules, the dashboard views, and the staffing plan. Tracking every entrant is valuable for some events, but it is not automatically the right answer. For a large race on a well-supported course, tracking leaders, medically relevant athletes, sweep personnel, and remote-course vehicles may deliver the operational visibility you need at a more manageable budget. For a highly remote ultra, full-field tracking may be appropriate.

The key is to avoid treating live dots on a map as the objective. The objective is faster, more confident decisions when conditions change.

Match the device profile to the course duration

Battery planning begins with the actual time-on-course, not the advertised race distance. Build the estimate from the final cutoff, then add a practical reserve for delayed starts, device activation before the race, cold conditions, elevation-related signal searches, and post-finish collection. A device rated for a certain number of hours under ideal reporting conditions may perform differently during a cold, wet overnight section with intermittent cellular service.

Reporting frequency creates the main trade-off. More frequent location updates make the public map feel more immediate and give staff a clearer view of moving athletes. They also consume more battery and can increase data traffic. For a fast, compact race, a short interval may be useful. For a 24- to 36-hour ultra, a longer standard interval with exception-based alerts often produces a better operational result.

Consider using different profiles for different roles. Lead runners and bike marshals may warrant tighter reporting intervals. Back-of-pack runners may need battery preservation and reliable SOS capability more than frequent public-map updates. Sweep teams, course vehicles, and medical staff can be configured to support the command view without being displayed in the same way as competitors.

Plan for coverage gaps rather than wishing them away

No configuration can create cellular service where there is none. On a remote course, identify the expected coverage gaps before race day and decide what the map should show during those periods. Depending on the device and network setup, a tracker may store points and transmit them when it reconnects, or it may use another communications method. Staff should understand the difference between a stationary participant, a delayed transmission, and a device that has stopped reporting.

Map notes and internal operating procedures matter here. If a known 12-mile canyon section has no service, volunteers and dispatch staff should not escalate every missing update as an emergency. Conversely, an absence of updates outside a known blackout area should have a clear response path.

Build the course and checkpoints into the tracking platform

A useful tracking map gives context to every location point. Load the verified course route, major alternates where applicable, aid stations, cutoffs, crew-access locations, medical extraction points, and finish areas. Name these locations in language your operations team actually uses. “AS4 - Pine Creek” is more actionable on a busy radio channel than a generic waypoint number.

Geofences can add value at major checkpoints, particularly when they support race control rather than create unnecessary notifications. A participant entering an aid-station zone can confirm expected movement. A participant leaving the course corridor may trigger a review. The configuration should account for GPS accuracy, terrain, and the physical size of the checkpoint. A geofence that is too tight can create false alerts; one that is too broad can obscure meaningful information.

For ultras with multiple route options, temporary reroutes, or out-and-back segments, test the map logic carefully. A live dot close to the route is not always evidence that an athlete is on the correct portion of the course. Your staff needs a display that makes direction of travel, recent movement, and checkpoint passage easy to interpret.

Configure alerts for action, not noise

Alerts should lead to a defined action. If race control receives dozens of routine notifications per hour, the meaningful ones will be missed. Start by identifying the conditions that genuinely require attention: an SOS activation, prolonged lack of movement outside an aid station, an unexpected departure from the course, a low battery threshold, or failure to report in an area with expected coverage.

Set ownership for each alert type before the event. An SOS may go directly to the medical lead and incident commander. A low-battery alert may go to tracking operations, who can contact the runner at the next aid station. A course-deviation alert may require a quick map review before anyone reaches out, especially in narrow switchbacks or dense tree cover.

Use escalation windows rather than reacting to every imperfect point. For example, a runner near a course boundary may remain within a review status until several consecutive updates indicate continued movement away from the route. The right threshold depends on the terrain, device accuracy, and consequences of a wrong turn.

Connect live tracking to timing and field operations

GPS and timing solve different problems. Timing produces the official record at start, checkpoints, and finish. Tracking provides situational awareness between those locations. When both systems are planned together, race staff can compare a missing checkpoint read with last-known location, pace trend, and the status of nearby support resources.

This is particularly helpful late in an ultra, when athletes can slow significantly and the field becomes widely distributed. A timing gap alone might look concerning. A tracker showing steady progress toward the next aid station may show that the runner is moving safely, just slowly. The reverse is also true: an athlete who checked in hours ago but has since stopped in an exposed area deserves a closer look.

Enabled Tracking can be configured alongside timing and event operations so organizers are not forced to reconcile disconnected views during a busy race. The best setup is the one that gives the right people a shared picture without requiring them to manage multiple tools under pressure.

Test the complete race-day workflow

Device testing is more than confirming that a dot appears on a screen. Conduct a practical test using the selected reporting profile, the real event map, and the staff dashboard. Move devices through a start sequence, a checkpoint, a known coverage gap if possible, an alert condition, and a finish or return process. Verify that the public view shows only what spectators need and that internal users can see the operational detail required for response.

A strong pre-race test should confirm five areas:

Device activation, assignment, labeling, and battery status

Map accuracy, course overlays, checkpoints, and geofence behavior

Alert delivery, acknowledgment, escalation, and staff ownership

Public-facing tracking permissions and participant privacy settings

Finish-line collection, device reconciliation, charging, and return logistics

Also test the human handoffs. Who distributes devices? How is each unit tied to a bib number? What happens when an athlete withdraws at an aid station? Who marks a tracker as recovered? These details prevent inaccurate public maps and misplaced equipment after a long event.

Brief athletes, crews, and staff clearly

Participants should receive a short, direct explanation of what the tracker does, how to wear or carry it, when to charge it if charging is permitted, and what to do if it is damaged or lost. Do not imply that the device replaces normal race safety requirements. Athletes still need to follow course markings, carry required gear, check in at aid stations, and report emergencies through the event's established procedures.

Crew members and spectators benefit from clear expectations as well. Live tracking is useful, but it is not a promise of second-by-second precision. Tell them that terrain, network coverage, and device settings can affect update timing. This reduces unnecessary calls to race staff when an athlete enters a known communication gap.

For the operations team, make the briefing scenario-based. Walk through a stopped tracker, an SOS, a missed timing point, a low battery, and a runner who is off course. Staff should know not only where to look, but who has authority to act.

Treat post-race review as part of configuration

After the finish, review the tracking record with your operations leads. Which alerts were useful? Which ones produced noise? Did battery reserves match the real-world course duration? Were aid-station geofences accurate? Did staff have enough context to distinguish a normal delay from a possible incident?

Those answers should shape the next configuration, especially for annual events with the same course. A well-run tracking operation becomes more precise over time because the settings reflect actual athlete movement, actual coverage limitations, and the way your team works on the ground.

The right tracker configuration gives race control a calmer, clearer view when the course is at its most complicated. Build it around the decisions your team must make, test it before the start line, and let the technology support the people responsible for bringing every participant home.