Running a Standard Race

See also: Creating Events, Classes, Courses, and Maps, Registrations, Reader, Start Clock, Event Monitor, Results

Before the Event (Desktop)

Step 1. Create the event

Create a new single-stage event in the desktop application. Enter the name, date, time zone, and select Individual as the competition format.

Step 2. Define classes and courses

Add classes (e.g., M21, W21, M16) and assign each one a course with distances and climb. Course data can be imported from OCAD or Condes. Verify that each class has the correct course — a common mistake is leaving a class without a course or accidentally assigning two classes the same course.

Step 3. Import registrations

Import the participant list on the Registrations page (CSV, drag and drop, or IRMA import). Check participant count, classes, and chip numbers. Missing chip numbers mean manual handling at the finish.

Step 4. Set start times

Open Edit start times / bib numbers from the toolbar. Set the first start time, start interval, and class separation rules. Review the list and save. Export a printed start list as backup and for posting at the start area.

Race Day — Start Area (Mobile)

Step 5. Open Start Clock mode

Select the event and switch to Start Clock mode. The display shows the clock synchronized to accurate time and participant names based on the pre-start time.

Make sure the volume is up — the countdown beeps are the primary signal. Set the pre-start time in Settings to match your start procedure.

Step 6. Call participants to pre-start

The Start Clock announces names at each minute mark based on the pre-start time. If a USB reader is connected, the participant can read their chip for confirmation — the app verifies the registration and start time.

At the same moment, the start beep sounds as the start signal for participants whose actual start time is right now.

Step 7. Handle missing and late starters

Missing participants require no action — mark them Did Not Start from the Start List mode or from the desktop afterwards. Late starters can start, but the result time is calculated from the original start time. Correct from the desktop if needed.

Race Day — Finish (Mobile)

Step 8. Open Reader

Select the same event and switch to Reader → Finish tab.

Step 9. Record finish times

After a chip read, the app shows the name, class, and running time. Result status is calculated automatically (OK or DSQ proposal based on missing punches). Tap the status button twice to confirm. The result syncs to the cloud immediately.

The reader locks after each read — process each runner before the next one. The finish time is calculated from the chip's internal data, not from the confirmation moment.

For an "unknown chip" situation, search for the participant by name or bib number. For a malfunctioning chip, use manual time entry.

During the Race (Desktop)

Step 10. Monitor in Event Monitor

Keep the Event Monitor open. Results appear in real time as they sync. The monitor shows finishers, runners on course, and problems.

Step 11. Handle DSQ proposals

A missing or incorrect punch appears as a DSQ proposal in the Event Monitor immediately. Handle it right away — the runner is likely still in the finish area. Check the punch data and decide: OK or confirmed disqualification. The full punch sequence with timestamps is available for review.

Step 12. Track runners on course

The Event Monitor shows who is still on course. This helps you know when the last runner has come in. Did Not Finish (DNF) runners are marked from the desktop when they report back.

After the Event (Desktop)

Step 13. Back up and export results

Results have been on the public results page throughout the race. Once all runners are accounted for, take a backup and export results in IOF XML format for Eventor or other systems as needed.

Tips

  • Test both phones before the event — USB reader connection green in the bottom bar and a test chip read works.
  • Keep a backup phone charged.
  • If connectivity drops, results are stored locally and sync automatically when the connection returns.
  • Print a paper start list as backup.
  • For larger races, Automaton on a tablet is the most convenient finish solution — no continuous manual confirmation required.
  • Brief the timing staff: DNS, unknown chip, and manual time entry.
  • Test the finish phone before the first expected finisher — test chip read and sync to Event Monitor.
  • Keep the Event Monitor open at the event center for immediate DSQ proposal handling.