Skip to content
ChronoFEED EVENT Help

Entries

Who races, and what. One row per entry, one box per race: here you import the list, confirm who is present, compute the categories, assign groups and bibs. Everything you change here is saved immediately.

Search (name, club, bib…)2 Athletes… Import… Export… 1 All categoriesAll gendersActive (without withdrawn) Age on 2026-07-01
Selection (otherwise the displayed list): ConfirmEnteredAbsentRemove Compute categoriesSeniorSet category GroupSet group Category racesBibs… Delete 3
Races in bulk:2 selected entry(ies) 500 m Femmes1500 m Femmes500 m Hommes1500 m Hommes Apply to racesCancel 4
500 m Femmes: 181500 m Femmes: 16 500 m Hommes: 201500 m Hommes: 17 5
BibNameFirst nameGBirthAgeClubCategoryGroupStatusJokerGuestRaces500 m Femmes1500 m Femmes
101DuquerroyRosalieF2003-04-2523PRJSeniorAConfirmed2
102LebrasseurOcéaneF1996-09-2329SLBSeniorAConfirmed2
103DvořákováMilenaF2006-04-1620SGSSeniorAEntered1
104EllingsenNoraF2007-11-0918SLBU19BEntered2
104VerhaegenLotteF2001-12-1224SLBSeniorAAbsent1
6
Lebrasseur, Océane
500 m Femmes 42.780 42.780 — entry time   1500 m Femmes 2:18.550 2:18.550 — entry time
NotesArrive samedi midi
7
5 shown of 38 entries; 36 active, 21 confirmed. 1 duplicate bibs.
The Entries tab of the Coupe Hollywood longue piste, filtered on a few women (example data).
  1. Just to the right of the search: the athlete database, importing and exporting the list, refreshing.
  2. Search, then the filters (category, gender, status) and the date on which ages are calculated.
  3. Batch actions, on the selected rows (otherwise on the whole list shown).
  4. Races in bulk: one box per race for the selected rows (indeterminate if only some are in it).
  5. The number of entries in each race (without withdrawn athletes).
  6. The grid of entries; bib 104 is a duplicate (in red).
  7. The details of the selected entry: entry time per race and notes.

The top bar

Athletes…

Where: Entries, top bar, just to the right of the search

The athlete database window (all competitions): search, create, edit a record, its affiliations, statuses and performances, find and merge duplicates, exchange records between databases, and enter the checked athletes in the event. See Athletes and import.

Import…

Where: Entries, top bar, just to the right of the search (also File menu)

Imports a CSV, Excel (.xlsx) or JSON list: each column is mapped to a field, each row is matched against the athlete database, then the athletes are created or completed and entered in the races (one “Inscrit 500 m Femmes” or “Temps d'inscription 500 m Femmes” column per race). A file's format is remembered for the next one. See importing entries.

Races written as a list (“500m, 1500m, Poursuites”), not always in the same column: check the import window's Extract the entered races option. See extracting the entered races and the scenario Importing entries whose races are in any order.

Export…

Where: Entries, top bar, just to the right of the search (also File menu)

Writes the list shown (search and filters included) as CSV, readable by Excel: bib, name, first name, gender, date of birth, club, reference, category, group, status, joker, guest, then one column per race (the entry time, or “x” without a time). The message gives the file written.

Search (name, club, bib…)

Where: Entries, top bar

Filters the grid as you type: each word typed must be found in the name, first name, club, bib, reference, category, group or member number. Accents and capitals do not matter (“lebras slb” finds Océane Lebrasseur).

Just to the right of the search: Athletes…, Import…, Export… and the button that reads the list again; the filters come next.

After these buttons, three lists: category (all, “No category”, or one category), gender (all, one gender, “(unknown)”) and status (all, “Active (without withdrawn)”, or one status). Then the date for ages: “Age on 2026-07-01”.

Clear search and filters

Where: Entries, button to the right of the filters

Empties the search and sets the three filters back to “All”: the grid shows all entries again.

Batch actions

“Selection (otherwise the displayed list):”: each button acts on the rows selected in the grid (click, Shift+click, Ctrl+click); if there are none, on all the rows shown. A confirmation says how many entries are affected, and each batch is written to the event log. Ctrl+A selects the whole grid.

Confirm

Where: Entries, batch actions

Sets the entries to the Confirmed status: the athlete has shown up (at the race office, at bib pick-up…). “Set 12 entry(ies) to status “Confirmed”?”.

Entered

Where: Entries, batch actions

Sets the status back to Entered (the starting status: entered, not yet confirmed).

Absent

Where: Entries, batch actions

Absent status: the athlete did not come. An absent athlete does not go into heats generated afterwards (neither withdrawn nor absent: only those are formed) and does not appear in the athletes column of the Line-up module.

Remove

Where: Entries, batch actions

Withdrawn status (scratched). The athlete stays in the heats already formed, but goes into no new one; they are no longer counted in the races' badges. It is also what to do when deletion is refused because the athlete is already in a heat.

Compute categories

Where: Entries, batch actions

Gives each entry the category for its age, from the date of birth, on the event's reference date (the template's: July 1 by default; an athlete born on that day already has their new age). The candidate categories are those of the event's discipline (common data), of the athlete's gender or mixed; if there are several, the one with the highest minimum age, and the one for their gender before the mixed one.

Without a date of birth or a possible category, the category does not change and the summary names the athletes concerned.

Set category

Where: Entries, batch actions

Gives the category chosen in the list just to the left (or “(none)”) to all the targeted entries, whatever their age: to move a group up, or when dates of birth are missing. The category of a single row can also be changed in its cell.

Set group

Where: Entries, batch actions

Puts the targeted entries in the group typed in the “Group” field (free text: “A”, “Elite”, “3”…); an empty field removes the group. The group is used for the combined standings “by group”, for the event overall total in Position mode and, depending on the template, for forming the heats.

Category races

Where: Entries, batch actions

Enters each targeted athlete in all the races of their category whose gender allows them (a Senior woman: “500 m Femmes” and “1500 m Femmes” if those races are for Seniors). Nothing is removed. Athletes without a category receive no race; the summary counts them.

Refused if no race of the event has a category (“No race of the event has a category (Races tab).”).

Races in bulk

Where: Entries, bar below the batch actions

Enters or withdraws several athletes at once in one or more races. Select the rows in the grid (Ctrl+click, Shift+click, Ctrl+A); with no selection, the displayed rows are used. The text next to it says how many entries are targeted (“12 selected entry(ies)”). Each race has a box:

Checked
All targeted entries are in the race.
Empty
None is.
Indeterminate
Only some are (mixed selection).

Check a box to enter the whole selection in the race, uncheck it to withdraw them; a box left (or set back to) indeterminate changes nothing. Changed boxes turn bold. Cancel resets them to the state of the selection.

Apply to races

Where: Entries, races in bulk bar

Writes the changes of the races in bulk, after a confirmation that sums them up (“Apply to the 12 targeted entry(ies): enter in: 1000 m Femmes; withdraw from: Mass start Femmes; 15 change(s).”). What is already done is not rewritten. The summary says so, and the batch is written to the event log.

Bibs…

Where: Entries, batch actions

The “Automatic bibs” window numbers the targeted entries:

One number sequence
“A single sequence”, “By gender”, “By category” or “By gender and category”. The table shows each group with its entries, its first number (101, 201… offered, can be changed), its step (usually 1) and the numbers it will receive.
Order within the group
“Name”, “Club, then name”, “Age” or “Entry order”.
Keep bibs already assigned (only empty ones are numbered)
To complete after late entries.

Assign writes the numbers. A number already worn by another entry is skipped (and named in the report); the remaining duplicates (numbers kept or entered by hand) are reported, never silently corrected.

Delete

Where: Entries, batch actions

Deletes the targeted entries, after confirmation; the athletes stay in the database. Refused for an athlete already placed in a heat: give them the Withdrawn status instead.

The grid

Entry grid

Where: Entries, in the middle

One row per entry. Editable cells are saved as soon as you leave them:

Bib
In red if it is worn by another entry (tooltip “Duplicate bib”); the bottom of the tab counts the duplicates.
Name, First name, G, Birth, Age, Club
Come from the athlete's record (read-only here: you change them in Athletes…). The age is the one on the reference date.
Category, Group
Editable row by row (or in batch).
Status
Entered, Confirmed, Absent, Withdrawn.
Joker
Placed among the fastest in seeding by default (a top-level athlete with no recent time). The joker applies to all the athlete's races.
Guest
Ranked, but keeps guest status (may be unofficial depending on the template).
Races
The number of races they are entered in.
One column per race
Ticking enters them in the race; unticking removes them (refused if they are already in a heat of that race). The header gives the number of entries. For several rows at once: races in bulk. Clicking the column header sorts the list: entrants in the race first, then, on the next click, non-entrants first (the previous order is kept within each block). You can see at once who is entered in a race.

The bottom of the tab sums up: “5 shown of 38 entries; 36 active, 21 confirmed.”.

The details of the selected row (under the grid): for each ticked race, the entry time (“1:23.45”, “43.21”; an unreadable time is refused with an example), then:

  • Time the seeding time selected by the calculation in the Performances module and its source (read-only);
  • Position the Pre-qualified box: the athlete goes straight into the second round of the plan.

Cells in yellow. A conflict kept at import (“Show this conflict” box) highlights in yellow the cell it concerns, with its explanation in the tooltip; the yellow goes away when the conflict is resolved, or with right-click › Conflict resolved (remove the yellow highlight). The Import conflicts only filter box shows only these entries. See Entry import conflicts.

Notes

Where: Entries, details of the selected entry

A free note on the entry (“arriving Saturday noon”, “borrowed skates”), specific to this event.