Navisport Documentation

The scenario

You're running a relay event with 4 legs and 20 teams. You want live split times at an intermediate control so the announcer can report gaps between teams as the race unfolds. You'll need phones at the checkpoint, start, and finish — plus the desktop client for live monitoring.

Before the event (Desktop)

Step 1. Create the relay event

Create a new event and select "relay" as the race type. Set the number of legs to 4 and assign a course to each leg.

Set the class default start time to the moment when all first-leg runners begin — this is the mass start time for the relay.

Step 2. Set up teams and registrations

Import or manually enter the 20 teams. Each team needs runners assigned to each leg. Verify that every runner has a valid chip number — missing chips at a checkpoint will show as "unknown" in the monitor.

Step 3. Configure checkpoints

Go to the Checkpoints page and add an intermediate checkpoint. Give it a name (e.g. "Radio control – Hill top") and assign it a control code matching the physical control in the forest. This tells Navisport which punch to watch for when phones report reads from that location.

You can add multiple checkpoints if you want splits at several points on the course. Each checkpoint needs its own phone in the forest, so plan according to how many devices and volunteers you have available.

Step 4. Assign devices to roles

Plan which phone goes where: one at the start (Automaton mode for mass start), one at the intermediate control (Online Control mode), and one at the finish (Reader mode). Note down which device handles which role — this helps troubleshooting if something goes wrong during the race.

Event day — Checkpoint setup (Mobile)

Step 5. Place the phone at the intermediate control

Arrive at the checkpoint location early. Mount the phone in a waterproof case near the control flag, positioned so runners can easily read their chip. Connect the USB reader and verify the green indicator in the footer bar.

Step 6. Enter Online Control mode

Open the app, select your event, and choose Online Control mode. Select the checkpoint you configured in Step 3. The phone is now listening for chip reads and will transmit each one to the cloud as it happens.

Step 7. Verify connectivity

Do a test read with your own chip. Check that the read appears in the Event Monitor on desktop within a few seconds. If connectivity is weak, the app queues reads locally and sends them when signal returns — but for live announcer use, you want real-time transmission.

If the signal is too weak for reliable real-time data, the checkpoint still works — splits will arrive in bulk once the phone gets signal again. You just won't have live commentary for that control.

Event day — Start and Finish (Mobile)

Step 8. Set up the start with Automaton

At the start line, open the app and enter Automaton mode configured for starts. For a relay mass start, all teams start together — as each runner reads their chip before the start, the Automaton registers them as "Competing." The actual start time comes from the event's configured mass start time. This confirms which runners were present and ready to race.

Step 9. Set up the finish with Reader

At the finish line, open Reader mode on the finish phone. Switch to the Finish tab. As each leg's runners come in, you'll record their finish, which also triggers the next leg's start time for that team.

Step 10. Record leg changes

When a runner finishes a leg, their teammate starts the next leg. Reader mode shows the team name and which leg just finished, so you can confirm the handover is correct. The next runner's start time is recorded automatically based on the previous runner's finish.

During the race (Desktop)

Step 11. Monitor splits in Event Monitor

Open the Event Monitor on the desktop. As runners pass the intermediate control, their split times appear in real time. You can see which teams are leading at the checkpoint and how big the gaps are.

The monitor updates automatically — no need to refresh. Keep it visible on a second screen if possible, so you can work on other tasks while watching the race unfold.

Step 12. Handle DSQ proposals and missing punches in real time

When a runner's chip data shows a mispunch or missing control, the Event Monitor flags it immediately. Handle these issues as they come in — the runner is likely still at the finish area or nearby, so you can check their chip data and resolve the problem on the spot.

The same applies to checkpoint data: if a runner's punch at the intermediate control doesn't match expectations, you see it in the monitor right away. This real-time visibility means problems are dealt with during the race, not discovered afterwards.

Step 13. Use the Announcer's Window

Open the Announcer's Window for a simplified view designed for commentary. It shows incoming splits and finishes in a large, readable format. The announcer can see "Team A passed the radio control 45 seconds ahead of Team B" and relay that to spectators.

Step 14. Track team progress

The Event Monitor shows each team's progress across all legs. You can see which teams have runners still in the forest, which have completed leg changes, and which are approaching the finish.

After the event

Step 15. Collect devices and confirm sync

Retrieve the phone from the intermediate control. Check that all reads were transmitted — the app shows a sync status indicating how many reads are pending upload. If any are still queued, keep the phone connected until sync completes.

Do the same for the start and finish phones. Once all devices show zero pending uploads, your data is complete.

Step 16. Take a backup and export results

Results have been live on the public results page throughout the event — spectators and teams have been following standings in real time. Now that the race is over, take a backup of the event data and export results in the format your federation requires (e.g. IOF XML for upload to Eventor or IRMA).

Tips

Charge all phones to 100% before the event. Online Control mode with constant data transmission drains battery faster than normal timing.
If the checkpoint location has poor mobile signal, consider a portable WiFi hotspot. Even a weak 3G connection is enough for transmitting punch data.
Test the full chain before the race: read a chip at the checkpoint phone, verify it appears in Event Monitor, and confirm the Announcer's Window updates.
For longer relays, you can set up multiple intermediate controls — each one needs its own phone in Online Control mode with a unique checkpoint assignment.
Label your phones physically (tape with "START", "FINISH", "CHECKPOINT") so volunteers know which device does what.
Brief the person at the finish on how relay leg changes work. They need to understand that saving a finish also starts the next leg's clock for that team.
Have a volunteer at the checkpoint to watch the phone and handle any issues (reader disconnection, phone overheating in sun). The phone works unattended, but someone nearby provides peace of mind.

Relay with Intermediate Timing