| Workflow | Steps through the stages of preparing and running an event Entry, Registration, Seeding, Merging, Race order, Drawing, Scoring, Ranking | |
| Workflow gates | Physical gates between all steps in the workflow, event cannot be run until all gates have been manually checked | Progression through the gates has been designed to be deliberate and to force the user to think about each step |
| Import rider entries from online entry systems | Australia OSM, Moto-sheets | |
| Imported entries - Entry only or Entry and Registration | Imported riders can be entered in an event for confirmation via the registration process or can be entered and registered in an event | |
| Manual entry | Entries can be made manually | |
| Barcode scanning | Barcode scanners can be used for entry and registration of riders by reading barcode on licence | National rider database information is required |
| Late entries | Late entry or entries on the day can be managed from the registration screen Automatic Entry system for entry and registration of late entries | Late entries can be made even after the first moto has been run Late entries after the first moto has been run will incur a DNS score for the first moto, the assumption is that the gate is full to the late rider will receive 10 points (8 + 2) |
| Apply any rulebook to an event | Rulebooks can be customised and applied to any event | Future roadmap includes linking different rulebooks to different classes in an event |
| Edit rider details | Rider details can be edited | |
General
Content
Integrations