Event template
The event rules: age categories, race types and models (how the heats are formed), officiating codes, point tables, formulas and performance sources, start colors. Usually they come from the federation and you do not touch them; when you need to, this is the place.
You open it with the banner's Template… button or with , directly: no password is asked. The editor is the same as the one for shared templates, prepared once for the whole federation; it shows only what the event's mode uses. A template that came from the federation keeps the “modified locally” mention and can be compared with the shared template at any time, with a way back (see Differences from the shared template).
- The tabs (those of the mode: here Time, with Formulas, Performance and Conversions; in Position: Rounds and total).
- The selected tab; at the top, where the template comes from and its mode, fixed.
- The template's problems.
- The commands: files, library, example; check, save, close.
The commands
Check
Where: Template, bottom right
Lists all the template's problems (tab by tab), above the buttons: “The template is valid.” or “2 problem(s) in the template.”. With problems, saving asks for confirmation.
Save
Where: Template, bottom right
Writes the template (and the start colors) into the event, with a log line; the workspace tabs reload. The event's age reference date follows the template. An unreadable entry or an unreadable JSON prevents saving (“The template cannot be saved: …”).
Keep in my templates also puts this template in the computer's local library, offered when creating the next events (for a shared template: a “… (modified locally)” copy).
Import…
Where: Template, bottom left
Replaces the template with a template read from a JSON file, of the same mode (a template of the other mode is refused). Nothing is written before “Save”.
Export…
Where: Template, bottom left
Writes the template to a JSON file (for another computer, another event, or to send it to the federation). The event's start colors do not go with it.
Start again from the example
Where: Template, bottom left
The list offers the example templates bundled with EVENT for this mode, under a name that gives the discipline and the level (“Example — long track, cup”, “Example — short track, elite”…); the button replaces the whole template with the selected one (after confirmation if there are unsaved changes).
The tabs
General
Where: Template, first tab
At the top, where the template comes from (“Shared template “…” (version 3), received from the national federation.”, “… modified locally for this event”, “Local template”) and the event type: “Event type: Time (fixed)”. A template of the other type is refused on import (“This template is of type Position; the event is of type Time. The type of an event does not change.”).
Differences from the shared template
Where: Template › General, at the top (template that came from the federation)
The event's template is compared with the shared template it came from, in the latest version received with the shared data: “Identical to the federation's shared template.” or “3 part(s) differ from the federation's shared template.”, then each part that differs (Season, Point tables, Event types, Race models, Decimals, Formation options shown…). The ↺ button of a part brings that part alone back to the shared template's value; Compare compares again. Nothing is written before Save. The frame is not shown for a local template, a bundled example or a shared template the computer does not have.
Restore the shared template
Where: Template › General, differences frame
The whole event template takes back the federation's shared template, in its latest version received, after confirmation. Once saved, it is no longer “modified locally”. The event's start colors do not change.
Name
Where: Template › General
The template's name, shown in the record of a new event.
Description
Where: Template › General
A free text, shown under the list of templates when creating an event.
Discipline
Where: Template › General
The intended discipline (“Long track”, “Short track”).
Track length (m)
Where: Template › General
The races' track when the context (the event's discipline) does not give it: 400 in long track, 111.12 in short track. Empty: unknown. See a race's track.
Season
Where: Template › General
The season the template is made for (“2026-2027”).
Categories
Where: Template, tab
How the entries' age category is calculated.
Age reference day (MM-DD)
Where: Template › Categories
The day on which age is counted, each season: “07-01” for July 1. Or a fixed date. The resulting date for the event is shown (“Age on 2026-07-01”). An athlete born on that day already has their new age.
Genders
Where: Template › Categories
The event's genders: code and label (“F” Femmes, “H” Hommes…). Race types and groups refer to them by their code.
Age groups
Where: Template › Categories
Code, label, min. age, max. age: “U13” 0–12, “U15” 13–14, “U17” 15–16, “U19” 17–18, “Senior” 19–34, “Master 35”… Compute categories (Entries tab) keeps the categories of the discipline's common data, but with the limits of the age band with the same name (name or short name of the category); an age band without a category of that name is reported, and nobody is placed in it. Without age bands: the limits of the common data.
Race types
Where: Template, tab
The races created with each event (then adjustable). On the left, the list (Add, duplicate, move up, move down, Delete); on the right, the record: Code (“500”, “1500-groupe”: the performance sources of another race refer to it), Label, Distance (m), Finish line (m after the track zero) (56 in long track, 0 for the 1000 m and pursuits), Approximate race time (m:ss) (the schedule uses it for the duration of each heat; empty: from the distance), Formula variable (“t500”), Genders allowed (“F, H”; empty: all; one race per gender is created), Race model, Heat names, Point table and Time its own Performance (otherwise the template's).
Race models
Where: Template, tab
Time A model says how a race's heats are formed: the groups (formation, size, number, minimum of the last, separated by gender), then the heats (formation, athletes per heat, draw within the group, fill pairs, quartets, unique start position, inside lane, heat order and threshold, incomplete heat, rebalance; mass start and pursuit), and the model's own performance; time decimals. These are the starting values of the heat formation settings of the Line-up module.
Position A model says how the rounds follow one another: heat sizes (qualification, eighth-final, quarterfinal, semifinal, final), X + Y criteria and reductions, semis and quarters allowed, direct final, everyone in the semis, finals for everyone, safety semi, advanced athletes, distribution (“Linear (A B C A B C)”, “Serpentine (A B C C B A)”), order of entries and qualifiers, start positions, codes in the final standings, and the progression table: one row per range of entries (“17 to 24 entries: qualification 4 × 2+2, semis 2 × 2+1”).
Formation options shown in EVENT Time
Where: Template › Race models, above the list
Not every formation option is useful to every discipline. Untick “All (no indication)”, then tick the options that the heat formation settings bar of the Line-up module shows (Heat size, Quartets…); the others remain available there through Show all options. With no indication, or no option ticked, all are shown. Usually the federation sets this in the shared template.
Plan preview Position
Where: Template › Race models, on the right
Type a number of Entries: the plan the selected model would give is shown (rounds, stages, number of heats, criteria), with its problems. To check a progression table without creating an event.
Officiating codes
Where: Template, tab
The table of codes (DNF, DNS, DQ, NT…) and their effect. Columns: Sort rank, Code, Label, Effect (Keeps their rank; Last of the heat: placed after the ranked athletes, at their sort rank; Excluded: removed from the standings), Position Qualifies (position), Qualifies (time), Advances (A, B: the final an advanced athlete moves up to), Scope (The race; All rounds of the event: yellow card; Whole event: red card), Reason required, No points, Time valid. The labels of the default table (“Did not start”…) are shown in the language of the interface.
The order of unranked athletes is set with the arrows, “Tied with the previous one”, or by typing the sort rank then Re-sort; it is summed up on one line (“Order of the unranked after the ranked: NFIN, NDEP / DRC…”).
Reasons (referee comments)
Where: Template › Officiating codes, at the bottom
The penalty reasons: code (“P-CHARGE”), label, and the code applied (DQ). Typing a reason as a code, in the results, gives this code; a code that requires a reason refuses a row without one.
Point tables
Where: Template, tab
The points tables: name, Points from 1st rank to last, separated by spaces (“10 8 6 5 4 3 2 1”), Floor (the points for the following ranks; empty: those of the last rank listed), Ties (Same points: the points of their shared rank; Average: the average of the ranks they occupy). In Time mode, a race takes the point table chosen in its own form (Races tab), “(none)” included; it comes from the race type when the race is created.
Formulas Time
Where: Template, tab
Named formulas (name, description), reused by seeding and by the combined standings: “combine” = t500 + t1000/2… Add, delete.
Expression of the selected formula Time
Where: Template › Formulas
An editor that colors variables, functions, numbers and times, shows the error live and its position (a click takes the cursor there), accepts only the variables of the race types and conversions, and calculates a preview on sample values (“t500 = 40.12; t1500 = 2:05.30”). Functions: meilleur, somme, moyenne, min, max (best, sum, average, min, max).
Performance Time
Where: Template, tab
The default sources of the seeding time, in order: the first one that gives a time wins. A race type can have its own. For each source: Type (Performances: the athlete's over a distance; Formula; Race: the result of another race of the event; Entry: the time given on entry), label, distance (variable), race, N best, Calculation (the best or the average of the N), factor (1.5 for a time taken over another distance). “Other settings of the selected source”: date window or number of seasons, venues and tracks allowed or excluded, ratified times only, require N performances, conversions applied.
Example: 1. Performances t1500 (best of the last 2 seasons); 2. Race “1000” × 1.5; 3. Entry.
Without time: Time
Where: Template › Performance
Where athletes go when no source gives them a time: after the slowest (default), ahead of the fastest, or in a group of their own.
Formula of the selected source Time
Where: Template › Performance
For a source of the Formula type: an expression, or the name of a formula from the Formulas tab (same editor, same preview).
Groups
Where: Template, tab
Time The default groups, before the heats (a race model can have its own): formation (by size, by number of groups, a single group), size, number, minimum of the last group, separated by gender, gender order. Position How level groups are formed: target group size, minimum of the last, groups of equal size, special cases depending on the number of athletes, maximum number of imposed priorities (sub-tab Groups and entry).
Conversions Time
Where: Template, tab
The coefficients applied to performances that meet their conditions (a distance, a track, a venue): converted time = time × factor + addition (s). To compare a time set on a shorter track or at altitude.
Rounds and total Position
Where: Template, tab
What the officiating codes do from one round to the next (destination in the next round, races the next round, points in the final), the event's overall total of points (rule, N best races, keep the total after a yellow card), the order of rounds in a program block, the decimals.
Standings
Where: Template, tab
How the event standings combine the races (formula, points or converted times), races counted, variables, separate standings, order of unranked athletes, decimals. Without its own settings: those of the mode. This is what Save settings in the Standings tab keeps.
Start colours
Where: Template, tab
The color of the cap or armband for each start position of the event (lanes in Time mode, start positions in Position mode): one row per position, background and text in #RRGGBB (empty text: black or white depending on the background), preview, one-click palette (“Background of the selected position:” white, red, yellow, blue, green, orange, purple, pink, gray, black). Add a position, Delete. With no rows: white, red, yellow, blue. An unreadable color or a duplicate position blocks saving (“Problem” column).
These colors are those of the cards in the Line-up module, and go to FINISH and TABLEAU. They belong to the event: exporting the template does not take them along.
| Position | Background | Text | Preview | Problem |
|---|---|---|---|---|
| 1 | #FFFFFF | 1 | ||
| 2 | #DC143C | 2 | ||
| 3 | #FFD700 | 3 | ||
| 4 | #1E5AC8 | #FFFFFF | 4 |
Default colours
Where: Template › Start colours
Sets back the four default colors: white, red, yellow, blue.
Export the colours to FINISH
Where: Template › Start colours
When ticked, the colors go with the heats to FINISH (.cfevent file and shared database), which shows them and passes them on to the scoreboards.
Advanced (JSON)
Where: Template, last tab
The whole template as JSON, as it is published: for a setting the forms do not show, or to copy a piece from one template to another.
The whole template as JSON
Where: Template › Advanced (JSON)
The text is rebuilt when the tab opens; what is changed in it is checked with each keystroke (the error gives the line and column; a template of the other mode is refused) and goes back into the other tabs when you leave this one, or through Apply to the form. An unreadable JSON is not applied and blocks saving.