Navisport Documentation

The scenario

You're organizing a local orienteering race with 80 participants, individual start times, one start place, and one finish line. You'll use the desktop client to set up the event beforehand, then two phones on event day — one at the start running Start Clock mode, and one at the finish running Reader mode. The Event Monitor on desktop gives you a live view of the race as it unfolds.

Before the event (Desktop)

Step 1. Create the event

Open the desktop client and create a new single-stage event. Give it a name, set the event date, and choose the correct timezone. Set the race type to Individual — this tells Navisport that each participant has their own assigned start time.

Step 2. Set up classes and courses

Add the classes you need (e.g. H21, D21, H16). For each class, assign a course with the correct length and climb. If you have course data from OCAD or Condes, import it directly — otherwise enter the details manually.

Double-check that each class has the right course assigned. A common mistake is accidentally giving two classes the same course or leaving a class without a course entirely.

Step 3. Import registrations

Go to the Registrations page and import your entry list. You can drag a CSV file onto the page or use the Import participants button. If your federation uses IRMA, you can import directly from there. After import, verify the participant count matches what you expect. Check that each participant is assigned to the correct class and has a valid chip number.

If some participants registered without a chip number, contact them before race day. Missing chip numbers mean you'll have to handle them manually at the finish — possible, but slower.

Step 4. Assign start times

Open Edit start times / numbers from the registrations toolbar and generate start times. Set your first start time, the interval between starts (typically 2–3 minutes), and any class separation rules. Review the generated list — you can drag participants to swap slots if needed. Once you're happy, save the start list.

Export a printed start list for the start official as backup. You can also export a list sorted by start time for posting at the start area so participants can check their slot.

Event day — Start area (Mobile)

Step 5. Open Start Clock mode

On the phone at the start place, open the Navisport app and select your event. Choose Start Clock mode. The screen shows a large clock synchronized to accurate time, with participant names displayed below based on the prestart offset.

Make sure the phone's volume is turned up — the countdown beeps are the primary signal for participants. In noisy environments, connect a Bluetooth speaker for louder audio. Set the prestart time in Settings to match your start procedure (e.g. 4 minutes if you want participants called to prestart 4 minutes before their actual start).

Step 6. Call participants to prestart

The Start Clock announces participant names at each minute mark based on the prestart offset. When you hear a name, that participant should be arriving at the prestart area. If a USB reader is connected, they can optionally read their chip for verification — the app confirms their registration is correct and their start time matches.

At the same moment, the start beep fires as the GO signal for participants whose actual start time is now — they're already at the start line, ready to go.

Step 7. Handle no-shows and late arrivals

If a participant doesn't show up for their start time, the clock simply continues — it doesn't require any action from you. You can mark no-shows as DNS directly from Start List mode on a second phone, or from the desktop client's participant information view after the event.

If someone arrives late, they can still start — but their result time will be calculated from their originally assigned start time, not from when they actually left. If you need to correct this, update their start time on the desktop after the event.

Event day — Finish line (Mobile)

Step 8. Open Reader mode

On the phone at the finish line, open the app and select the same event. Choose Reader mode and switch to the Finish tab. The phone is now waiting for chip reads.

Step 9. Record finish times

As each runner crosses the finish line and reads their chip, the app shows their name, class, and elapsed time. The system automatically calculates the result status (OK if all controls are punched, DSQ proposal if controls are missing). Tap the status button (usually OK) twice to confirm and save the result. The result syncs to the cloud immediately, so anyone watching the live results sees it within seconds.

The reader locks after each chip read until you confirm or clear — so process each runner before the next one reads their chip. The finish time is calculated from the chip's internal data, not from when you confirm, so there's no rush to tap quickly.

If a chip read shows "Unknown chip," the participant may not be registered or may be using a different chip than expected. You can search for them manually by name or bib number. If someone finishes but their chip doesn't read properly, use the manual time entry to record their finish.

During the race (Desktop)

Step 10. Monitor the race with Event Monitor

Keep the Event Monitor open on the desktop throughout the race. As each runner finishes and their result syncs, you see it appear in real time. The monitor shows you who has finished, who is still in the forest, and — critically — any problems that need your attention right now.

Step 11. Handle disqualification proposals as they come in

When a runner's chip data shows a missing or incorrect punch, a DSQ proposal appears immediately in the Event Monitor. Handle it right then — while the runner is likely still at the finish area and can show you their chip or explain what happened.

Review the punch data and decide: set the status to OK if the result is valid, or confirm the disqualification. Common issues include missing punches, punching in wrong order, or punching a wrong control. If a participant disputes a disqualification, you can view their full punch sequence with timestamps to investigate.

Dealing with mispunches in real time means you can talk to the runner, check their chip again, and resolve the issue on the spot — rather than trying to track them down hours later.

Step 12. Track who's still out

Use the Event Monitor to check if anyone is still marked as "in forest." This helps you know when the last runner is in and whether anyone might need help on the course. Runners who retire mid-course (DNF) won't have a finish read — you can mark them from the desktop when they report back.

After the event (Desktop)

Step 13. Take a backup and export results

Results have been live on the public results page throughout the race — participants and spectators have been following in real time. Once all runners are accounted for, take a backup of the event data. Then export results as IOF XML for upload to Eventor or other result services if needed.

Share the results link with participants — many will want to check their time and compare with others as soon as the event is over.

Tips

Test both phones before the event starts — verify the USB reader connection shows green in the footer bar and that a test chip read works.
Keep a backup phone charged in case one device has issues during the race.
If you lose mobile connectivity during the event, don't worry — results are cached locally and sync automatically when the connection returns.
Print a paper start list as backup. Technology is reliable, but paper doesn't run out of battery.
Assign one person per timing station. Trying to handle both start and finish on one phone works for small events but gets stressful above 40 participants.
Brief your timing volunteers before the event. Show them how to handle DNS, unknown chips, and manual time entry — five minutes of preparation prevents confusion during the race.
Set up the finish phone 30 minutes before the first expected finisher. This gives you time to troubleshoot any connection issues without pressure.
Keep the Event Monitor open on a laptop at the event center so you can watch results come in and handle DSQ proposals immediately as each runner finishes.

Running a Standard Race