Documentation

Meet

A Meet is the top-level container for everything — participants, events, results, connectors, and configuration. It maps to a single race day or competition: a 5K road race, a cross country invitational, a regatta, etc.

Meet data lives in the browser's IndexedDB. You can have multiple meets on the same device, each completely independent. Meets can be imported and exported to a .2t file for backup, restore, or sharing.

Genre

Genre is the sub-type of a running meet. Options include Road, Cross Country, Trail, OCR (obstacle course racing), and Other. Genre affects which features are available — for example, cross country enables team scoring.

Event

An Event is a single race within a meet — for example, "Open 5K" or "Varsity Boys 5K." A meet can have multiple events, and each participant is entered into one or more events.

Each event has a distance, a scheduled start time, an event number, and its own set of results.

Division

A Division is a named group of events within a meet. Use divisions to organize race programs such as "Morning Events," "Championship Races," or "Youth Series" without changing the event data itself.

Divisions help structure navigation, setup, and reporting by letting you work with a subset of events as one logical unit.

Participant

A Participant is a person registered in the meet. They have a bib number, name, age, gender, and optional team affiliation. Participants can be imported from CSV, HY-TEK, RunSignUp, or entered manually.

A participant's record contains their personal and demographic information. Their actual race result is tracked separately as an Entry.

Entry

An Entry links a Participant to a specific Event. It holds the timing data: gun time, chip time, finish time, place (overall, gender, and group), and status code.

Places are calculated automatically when timing data is processed. Each entry has one status that controls whether it is eligible for placing.

Group

A Group is an award category within an event. 2Timer supports two kinds of groups:

• Age Group — a range of ages (e.g., 40–49) within a gender. Any finisher whose age falls in the range competes for awards in that group.
• Band — a top-N bracket (e.g., top 3 Open finishers in each gender). Used for overall open awards and similar prize structures.

Every group has a gender, an award count (number of places that receive an award), and belongs to a specific event.

Wave

A Wave is a sub-group start within an event. Waves let you split large fields into separate start groups with different start times. Each wave has a time offset from the event's gun start. Gun times for participants in each wave are adjusted accordingly.

Team

A Team is an organization — a school, club, or running group — identified by a short code (e.g., WHS for West High School). Teams are used primarily for cross country scoring, where the top finishers from each team accumulate points.

Each participant can be assigned a team code, and the Teams section of the app shows current standings and scoring breakdowns.

League

A League (coming soon) is a group of teams. It will make it easier to organize multi-team competitions and apply shared league-level logic across meets.

Think of a league as a reusable container above teams, similar to how a division groups events.

Chip

A Chip is a timing chip that has been assigned to a specific bib number. The chip-to-bib mapping tells 2Timer which participant a timing detection belongs to.

Chips can be assigned manually or imported. 2Timer maintains a full audit trail of chip assignments.

Read

A Read is a single raw detection from a timing chip reader — one antenna picking up one chip at one moment. Every read has a chip ID, a bib number (resolved via the chip mapping), a timestamp, a reader/antenna ID, and a marker.

You can view all raw reads in the Reads section of the app, which is useful for troubleshooting missed or duplicate detections.

Marker

A Marker is a timing point on the course. The three marker types are:

• Start — the starting line
• Finish — the finish line
• Split — an intermediate timing point (e.g., 1-mile mark)

Each marker is linked to an event and defines a time window for valid reads — for example, a finish marker might accept reads between 10 minutes and 6 hours after the gun. Reads outside the window are flagged.

Connector

A Connector is a meet-level connection that defines how that specific meet exchanges data with hardware, files, and external services.

Connectors can be inbound (bringing data into 2Timer), outbound (publishing data out), or bidirectional. A connector can reference an Integration for persistent credentials and endpoint settings.

Integration

An Integration is configured outside any individual meet. It stores persistent connection details such as server addresses, API authentication, and publishing credentials.

Examples include FTP/SFTP server credentials, S3 configuration, or authentication to services like RunSignUp. Meets then leverage these saved integrations in their connectors.

CSV Import Wizard

2Timer's CSV import is designed to be flexible rather than tied to one rigid file layout. It can pull in participants, teams, events, entries, and result fields from a single delimited file.

• Flexible header mapping — recognizes a broad set of column aliases and lets you review or adjust the mapping before import
• Delimiter support — works with comma-, tab-, and semicolon-delimited files
• Derived fields — can split full names, normalize gender and dates, derive team codes from team names, and build preview columns before you commit the import
• Smart matching and dedupe — can match existing participants by bib, registration ID, name plus team, name plus date of birth, name plus age, or name plus city
• Event-aware import — can resolve events by number or name, and create missing events when needed
• Reusable templates — save column mappings and reuse them on future files with similar layouts

Other Import Paths

Beyond CSV, 2Timer can also bring in meet and timing data from several more specific workflows.

• .2t meet files — import a full 2Timer meet for restore, transfer, or backup recovery
• HY-TEK import — bring in participants, teams, events, and entries from HY-TEK semicolon-delimited files
• RunSignUp sync — pull registration data through a connected integration
• Timing inputs — ingest reads or timing files from supported systems such as FinishLynx, IPICO, and generic RFID readers

Export Capabilities

2Timer can export both full meet data and outward-facing files for other meet management and results workflows.

• .2t meet files — export an entire meet as a portable backup or handoff file
• HY-TEK results export — download HY-TEK semicolon-delimited results files for road racing and cross country workflows
• Report formats — generate result outputs as CSV, JSON, HTML, XML, or TXT
• FinishLynx outbound files — export PPL, SCH, EVT, and AFL files for Lynx/RaceTab-style workflows
• Current publishing target — publish generated report files to the local filesystem from within a meet

What’s Next

Import and export support is expanding. More source formats, registration systems, timing platforms, and publishing targets will be added over time.

The goal is to let 2Timer sit comfortably in the middle of a real timing workflow, whether data is arriving from registration platforms, meet files, CSVs, timing systems, or downstream export formats.