Geco capabilities allows one to perform different styles of organisations, from lightweight training up to formalized events of medium size. This page presents those styles and options through a few models, providing links to detailed subsections.
For a training, you usually don’t have any pre-registration since runners come and go. They can run multiple exercises with different courses. Then Geco works best as a self service station where each participant reads his ecard after his run.
Geco configuration for a training is minimal: just create (or import) courses, optionally set up an archive to get enriched data.
The training page details the features of this mode as well as the capability to import the log from a reading station.
For a small race, some people will choose to pre-register before the day, but a lot of runners can also just show up on the day of the race.
You can use the different capabilities of Geco for registration.
It is advised to set up Geco to use the archive in auto mode. This model allows one to minimise work beforehand as well as error risks, since all the information is computed with the ecard, from the course to the archive data (name, category, club).
Of course, you should supply results regularly, but don’t forget to deal with the end of stage, DNS and still running competitors.
When it comes to a medium-size event, most competitors would pre-register to ease the logistics. This can imply a greater control of runner registration, including the allocation of start times.
Even if Geco can handle pre-registered start times, it does not provide any function to automatically allocate times. This should be made with another software beforehand. Consequently, it is recommended to perform registration with an OE CSV file. Other methods are still available, in particular for onsite registration.
On the day of the race, you can choose between the manual process and the auto process to resolve problems: it’s mainly a matter of taste. The former opens the merge wizard, while the latter first create entries before giving you control. However, it can be advised to turn off archive lookup for the auto handler: this provides a greater control of unexpected entries.
The end of stage is also important here. Learn how to manage DNS and running competitors efficiently by using the backup memory from stations.