A QR Code race does not begin when the first athlete starts. The decisive work happens earlier: define the discipline, organize Control Points, review sequences, test scans, and prepare the crew for areas without a connection. Split combines checkpoint logging, participant status, and online standings, but reliable results still depend on consistent configuration.

This guide presents a complete workflow for orienteering, adventure racing, Rogaine, and rural-course organizers. It reflects current Split capabilities such as the Organizer profile, course testing, duplicate-checkpoint validation, cached data, invalid-scan feedback, and result recalculation.

1. Turn the regulations into clear parameters

Before registering any checkpoint, write down the rules the system must represent. For every category, answer:

• must checkpoints be visited in a fixed sequence?
• does each Control Point have its own score?
• is there a maximum time or overtime rule?
• does a missing checkpoint disqualify, reduce points, or only mark an incomplete course?
• are starts and finishes individual, team-based, or within a common window?
• which categories share the same course?

These answers distinguish events that may look similar on a map but produce different standings. In a sequential course, checkpoint order is part of the result. In a point-based event, athletes may be allowed to choose different strategies. Rogaine scoring and time limits must be established before the first test.

Maintain a separate control table containing category, course identifier, checkpoint list, scores, and maximum time. It becomes an independent reference during validation.

2. Plan Control Points without ambiguity

Every checkpoint needs a unique, readable identifier. Avoid visually similar combinations, duplicate codes, and accidental repetitions in the sequence. Current Split versions prevent duplicate Control Points in Orienteering or Rogaine courses and block the same checkpoint twice in sequence, but planning still requires review.

For each point, record:

The QR Code installed in the field must match the registered identifier exactly. Protect printed codes from rain, mud, and abrasion, and keep replacements for critical locations.

3. Separate crew responsibilities

Decide who uses the Organizer profile and which actions each person performs. A small event may combine tasks; a larger one benefits from clear ownership:

• coordination: validates rules, categories, and closing;
• setup: installs and confirms checkpoints;
• start/finish: controls participant milestones;
• course support: receives field incidents;
• results: monitors standings, inconsistencies, and recalculations.

Share a correction procedure. Changing a course during the event without recording the decision can make final standings difficult to audit.

4. Complete a full participant test

An Organizer can register to test a course and participate in an event. Use that capability to reproduce the real experience instead of simply opening every screen.

The rehearsal should include:

1. registration in the correct category;
2. course start;
3. scanning every checkpoint in the expected order;
4. a controlled attempt to scan an invalid point;
5. a period with limited connectivity when that reflects the venue;
6. finish and result publication;
7. verification of score, time, and final status.

Split uses distinct audio feedback for an invalid checkpoint. The crew should recognize that response before the event and know that an alerted scan is not a confirmed passage.

After an athlete starts, current versions prevent the phone screen from automatically turning off. Still verify battery, brightness, rain protection, and how the device will be carried.

5. Validate every QR Code in the field

A desk test does not replace verification after setup. Visit each point with the same device type used during the race and test:

• direct sunlight and shadow;
• scanning distance and angle;
• partially wet or dirty codes;
• reflections from plastic covers;
• correspondence between location, code, and registration;
• network coverage along important sections.

Replace a code that requires several attempts under normal conditions. Seconds lost to a poor scan can affect the participant experience and create disputes.

6. Prepare for limited connectivity

Split includes fixes that allow system data to remain listed from cache without a connection. This helps in remote areas, but it does not remove the need for preparation.

Before leaving coverage:

• open the application and refresh event data;
• confirm that the event and course appear on the device;
• keep the session authenticated;
• avoid clearing data or reinstalling the application;
• identify where synchronization can resume;
• define how the crew records an incident if a device fails.

When connectivity returns, wait for updates and verify that passages appear before closing the event or declaring results final.

7. Monitor statuses and standings

Split uses colors to distinguish classified, disqualified, on-course, and not-yet-started participants. Treat these statuses as an operational dashboard:

• not-yet-started athletes may indicate a delay or absence;
• unusually long on-course times may require contact with support;
• disqualifications need a verifiable reason;
• classified athletes should have consistent course, time, and score data.

Online standings help organizers, athletes, and spectators, but provisional results remain subject to incident review and pending synchronization.

8. Correct data with traceability

Recent versions improved result management and allow standings to be recalculated. Recalculate when a correction to a passage, score, or course actually changes the outcome.

Before recalculating:

1. record which data was wrong;
2. confirm evidence with the responsible crew;
3. make the authorized correction;
4. run the recalculation;
5. compare the previous and new result;
6. communicate changes that affect positions.

Avoid several undocumented corrections at once. If a dispute occurs later, the reason behind a decision matters as much as the final value.

Pre-start checklist

• discipline and classification rules confirmed;
• categories and courses reviewed;
• unique checkpoints in the correct order;
• scores and overtime checked;
• QR Codes tested after setup;
• Organizer registered and course simulated;
• invalid-scan feedback recognized by the crew;
• devices charged and data refreshed for cached use;
• correction and recalculation procedure defined;
• start, course, finish, and result owners identified.

Split reduces manual work and speeds up standings, but it cannot replace a clearly defined course and a rehearsed operation. When rules, checkpoints, and responsibilities are clear, QR Codes become part of a verifiable process from start to final result.