Define Event
What is Event
Event is the central operational object in the platform. All competition-related configuration and operations are linked to a specific Event context.
One Event can contain multiple Races (for example: marathon, half-marathon, and 10K), with each Race having its own categories, and result interpretation.
Minimum setup steps
- Creeate Event;
- Create Races;
- Create Category sets (if multiple);
- Create Categories
If you use multi-event registration, this minimum must exist for each Event included in the registration flow.
Define Event
Fill in the Event creation form with the core metadata:
- Event name;
- optional Event image (displayed in the public view);
- discipline mapping (used by public-side discovery/search);
- start date and (if different) end date;
-
event location (at minimum, country).
-
Assign an Organization to the Event.
The assigned Organization is responsible for event organization and can represent either a legal entity or a private individual. If the Organization does not exist yet, create it first. This also enables grouping events by Organization in the public portal.
-
Set Event visibility for the public portal:
- Public: visible to all users;
- Organization members / Event creator: visible only to those users when logged in.
-
Participant limit sets how many participants can register for the whole Event. Manual import can still add participants above this limit.
After the Event is created, it is recommended to upload regulations and other informational materials in the Event documents list.
Define Races
Fill in the Race creation form with the core metadata:
- Race name;
- optional Race partners logos (displayed in the public results view);
For registration minimum setup, this is sufficient. The remaining Race/Run(s) configuration can be completed later (see Configure Run sections).
- Participant limit sets how many participants can register for that specific Race. Manual import can still add participants above this limit.
After creating Races, you can reorder them. The same Race order is used across other areas (for example, results, filters, and selection lists).
Define Category sets
If your Event has only one standings context (ieskaite), no additional action is needed. One default category set is already created.
Create additional category sets only when the same Event contains multiple parallel standings, and each standings context needs its own categories.
Example:
- main competition standings with one set of categories;
- national championship standings with a different set of categories.
In such cases, define separate category sets so that each standings context uses its own categories.
Category sets can be managed in the Categories section under the More icon.
Define Categories
Fill in the Category form in this order:
- Name (required).
The following fields control participant eligibility for registration in this Category (beta):
- Gender: Any / Male / Female;
- Age limit:
- Type: Birth year / Age at event start date / Age at Jan 1 / Age at custom date;
- From (birth year or age, inclusive);
- To (birth year or age, inclusive);
- Age comparison date (used only with Age at custom date).
If From is empty, the lower bound is not applied. If To is empty, the upper bound is not applied. If both From and To are empty, no age restriction is applied regardless of Type.
Example:
- if Type is
Age at event start date, From is19, and To is21, the system calculates participant age from date of birth using Jan 1 of the event year (year taken from the Event start date) and allows registration only for participants aged 19 to 21, inclusive (including both 19- and 21-year-old participants).
Gender and Age limits are optional. If configured, they help narrow the Race and Category lists in the registration form after the participant enters date of birth or birth year, making selection easier. These limits apply only to the registration form. When adding, editing, or importing participants in Event, organizers can still assign any Category manually.
Important: if at least one Category in any Category set uses an age-based limit (not birth year), the registration form must use a Date of birth input field, not Birth year. Otherwise, Race and Category filtering will not work.
- Participant limit sets how many participants can register for that specific Category. Manual import can still add participants above this limit.
After creating Categories, you can reorder them. The same Category order is used across other areas (for example, results, filters, and selection lists).
Operational shortcut
In some cases, you can skip manual Race and Category setup during participant import by enabling Auto create non-existing races and categories. Any missing Races and Categories will then be created automatically during the import process.
This option is primarily intended for situations where registration setup is not required (for example, when importing participants from an external registration system), but it can also be used when registration is enabled.
Note: When Races and Categories are created via the import process, only the category names will be created. Gender and age restrictions will not be set automatically.