> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/use-wiclax/entering-importing-results.md).
# Entering, importing results
There are 3 main ways of entering results into Wiclax: \
\- via [electronic acquisitions](/en/use-wiclax/acquisition-of-timing-data.md) \
\- via file import \
\- via insertion from the entry form
## The Results Grid
The main results grid enables several actions and serves as the primary tool for race monitoring.
For instance, split times for the finish line or intermediate checkpoints can be edited directly within the grid cells.
## The Entry Form
The results entry form opens by double-clicking on the results grid or via the F3 keyboard shortcut.
The **Bib Number** field is the first item to complete, unless it is already pre-filled during a context-specific form opening. The form displays the following data and actions:
1. A summary of the key data identifying the competitor: first and last name, race; their current rank in the standings if a result already exists; their individual start time and race start time.
2. Their finish line split time, which calculates their race time (referred to here as Net Time). This split time can be replaced by a non-finisher status, such as "Did Not Finish" (DNF) or "Withdrawn."
3. Action buttons to:
a. validate the most recent entries.
b. Delete the current competitor's result.
c. Modify their ranking in the standings (e.g., in cases of ties).
4. Their split times at intermediate checkpoints. Similarly to the finish time, the corresponding net race times are displayed to the right of the split time.
5. Additional action buttons to:
a. Navigate to the competitor's data in the grid or in the registration form.
b. Display the history of recorded splits for the competitor, whether currently integrated or not.
{% hint style="info" %}
Certain form functionalities are particularly useful for manual timing and are described here.
{% endhint %}
{% hint style="info" %}
It is possible to enter Net Race Times directly, which will automatically calculate the corresponding split times.
{% endhint %}
{% hint style="success" %}
Remember the useful shortcuts: Tab to move between fields, Enter to validate the form, and P to recall the previously entered finish time.
{% endhint %}
## Deleting Results
The (complete) deletion of a result corresponds to removing a row from the results grid. This includes the finish time and any intermediate checkpoint split times, if applicable. For lap-based events, this action removes all recorded split times for the competitor.
{% hint style="info" %}
Deleting a result does not affect the recording of individual start times, as these are preserved as registration data.
{% endhint %}
Results can be deleted:
* Individually, via the Delete button in the entry form.
* Individually or in batches, by selecting rows in the results grid and using the Del key on the keyboard or the Context Menu > Delete option.
## Modifying Rank
Accessible from the entry form or the results grid context menu, the Modify Rank function (i.e., standings position) allows you to reorder competitors classified within the same group.
This feature also handles specific scenarios, such as a fall in the final kilometers of a cycling race.
Reordering a group can also be performed directly from the grid using the Ctrl + Up/Down Arrow keyboard shortcuts to swap a competitor's position with the preceding or following competitor.
## Importing Results
The basic principles for importing results mirror those for importing entrant lists, covering file types, delimiters, column mapping, and more.
The source for importing split times can be a local file or web-accessible content. Processing is automatic if you simply enter the data access URL—for example: `https://mon-site.com/passing-data/pointage_2.txt`.
{% hint style="info" %}
Do not overlook copy-paste operations: pressing Ctrl+V while the results grid is active opens the import wizard in the same way, eliminating the need to handle files manually.
{% endhint %}
In this context, the import wizard focuses on the following data:
* Bib Number or Chip ID (transponder)
* Split Time
* Split Source (optional)
### Passing destination
The first step of the wizard, in addition to requesting the location of the data to import, allows you to specify the destination for the passings.
The logic for these destinations is identical to that used for passing acquisitions.
### Time Formats
Passing dates and times can be provided as two separate data fields or combined into a single column. If the column contains both date and time, map it to the Time field.
In all cases, you must provide the appropriate import masks. You can verify their correct interpretation in the data preview by hovering your mouse over a value.
## **Participant Statuses**
The main statuses that can be assigned to a competitor are listed below, along with their standard English abbreviations, in order of ranking value:
* Laps behind (x Laps)
* Overtime (OTL)
* Did Not Finish (DNF)
* Disqualified (DSQ)
* Did Not Start (DNS)
With the exception of Did Not Start (DNS), all other statuses are considered official rankings and will generate a line in the results grid.
A competitor not assigned any of these statuses will be considered a Finisher if an arrival time has been recorded, or In Progress otherwise.
{% hint style="info" %}
Competitor rows in the grids display distinctive colors or icons based on their status.\
\
{% endhint %}
### Assigning Statuses
Statuses can be assigned either via the results entry form or directly from the main grids using the context menu (note: for Did Not Start (DNS), this is only available in the participants grid).
In the entry form, use the dropdown menu located to the right of the arrival time field to select a status. Then, confirm the entry by clicking the Validate/Modify button.
To revert a competitor to In Progress or Finisher status, simply reselect the Time... option from the same dropdown list.
The grid context menu offers several options. It allows you to work on a selection of rows or to enter a list of bib numbers for which a status change is requested:
### **Outside time limit Competitors**
The **Outside time limit (OTL)** status is generally applied to competitors who have crossed the finish line.
Consequently, their race time is preserved, but the OTL status marks them as unranked. In the final standings, they appear before those who abandoned the race (DNF).
The Outside time limit tool is particularly useful when race regulations require eliminating competitors based on a percentage of the winner's time.
Participant Summary
Very often, if you are looking specifically for information regarding a competitor's status or results, remember that their Summary is both faster to access and more comprehensive than the results entry form.
* Ctrl+R Opens the summary if the competitor is selected in the grid.
* Ctrl+F Searches for a competitor by name or bib number.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.wiclax.com/en/use-wiclax/entering-importing-results.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.