Concepts and Workflow Reference

Purpose

One consolidated reference for 2Timer terminology, data model, connectors, and end-to-end workflow patterns.

Prerequisites

• Basic familiarity with chip timing or meet management operations.
• Access to 2Timer Manager at manager.2timer.app.

Platform Overview

2Timer is a browser-based meet management and timing application.

• All meet data is stored locally in your browser — no server is required during timing operations.
• Most core meet workflows continue offline after the app has loaded, but internet-based features still need a connection. See Offline Access and PWA.
• Meets are backed up and transferred as .2t archive files — a single portable file that restores everything.
• The public site lives at 2timer.app; the meet manager app lives at manager.2timer.app.
• Version 1 provides the stable core for road racing, cross country, and track & field. Optional Hub settings and connected services remain separate from local meet operation.

Core Concepts

Meet

Top-level container for everything: events, athletes, results, connectors, and configuration.

Sport controls the time mode and available features:

Genre refines display defaults (which columns are shown — team, age, city, grade) within a sport.

Event

One scheduled contest within a meet. Every event has an event number that must match your timing system’s configuration exactly. For T&F, events also have a discipline — Dash/Run, Hurdles, Steeplechase, Race Walk, Relay, Horizontal Jump, Vertical Jump, Throw, or Multi-Event — that controls how results are recorded and displayed. Multi-round events (prelims → finals) have each round configured separately.

Super-Event

A super-event is a container for one physical race or contest that feeds results into two or more separate sub-events. Operators typically time or import the combined race once, then let 2Timer route results back to the correct sub-event for separate placements and scoring. Entries remain on the sub-events, not on the super-event container.

Athlete

A participant profile: name, bib number, gender, age, date of birth, city, state, and team.

Entry

Links one athlete to one event and one round. Holds the result: gun time, chip time, final place (both overall and within the heat for T&F), heat and lane assignments, seed, and outcome status.

Chip

A chip assignment maps a timing chip’s unique ID (as reported by the reader) to a bib number. Required for chip-timed events unless the timing system provides the bib number directly (as FinishLynx does).

Marker

A timing point on the course: Start, Finish, or Split. Assigned to one event. Has a read window that defines the earliest and latest valid time relative to the gun. Reads outside the window are flagged but preserved for manual review.

Read

One raw detection from a timing device. Each read is processed against active markers to determine whether it can be applied to an entry. See the Markers and Reads page for read status explanations.

Wave

A corral or sub-group start with a time offset from the gun. Athletes in a wave have their gun time adjusted by the wave delay for fair placing across all corrals.

Group

An award category (age group, overall open, masters band, etc.). Athletes are auto-assigned to groups based on age or grade. Each group has a configurable number of award places.

Division

An organizational grouping of events (e.g., Varsity Girls, Junior Men, Open Women). Does not affect timing — used for report structure and seeding organization.

Team

An organization code used in cross country and T&F team scoring. Athletes’ team affiliations are matched to team records to compute team totals. In T&F, teams can also carry a meet-wide lane slot for team-lane seeding. Teams marked Unattached remain in the meet but are excluded from team scoring.

League

An optional grouping of team codes used for conference-style splits, league views, and head-to-head reporting. A team can belong to zero or more leagues.

For small scored meets, the Leagues page also includes a Generate Double-Dual Leagues tool that creates pairwise league groupings from the meet’s scoring teams.

Seeding Profile

A reusable T&F default ruleset that supplies discipline-group seeding behavior for new meets and round workspaces.

Session

A scheduled time block within a meet (e.g., “Morning Field Events”, “Afternoon Finals”). Used to organize large T&F meets across parallel venues.

Stopwatch

The built-in hand-timing watch, and a meet destination in its own right. At a hand-timed meet the watch is the timing system. See Hand Timing with the Stopwatch.

Display board

A physical scoreboard or video board fed by a display connector. What each board shows is driven from the meet’s Scoreboard page. See Scoreboard.

Connector

A meet-level integration for inbound data (timing hardware reads) or outbound data (publishing results). See Connectors.

Integration

Reusable account credentials configured in Settings → Integrations. Connectors reference integrations for RunSignUp, RaceRoster, ONETIME, Total Active Sports, FTP, and S3 / R2 connections.

Import and Export Summary

Import Sources

Every file-based source lives behind one Import… door on the meet dashboard, grouped by the job it does. Connectors are separate: they carry live or repeating data.

Live and repeating inbound data comes from connectors instead:

Export and Publishing

Typical Workflow

1. Create meet — Click a sport card on the home screen for a blank meet, or From .2T File / Import HyTek File when your starting point is an existing file.
2. Add events — Assign event numbers consistent with your timing system. Set discipline for T&F events.
3. Configure divisions, groups, teams, and leagues — Divisions for structure; groups for awards; teams and leagues for scoring and reporting.
4. Import athletes and entries — Spreadsheet, Hy-Tek meet file, Athletic.net, RaceTab, or a RunSignUp / RaceRoster connector.
5. Review team setup — Mark non-scoring teams Unattached, assign Lane Slot values for team-lane meets, and generate double-dual leagues when needed.
6. Assign chips — Map chip IDs to bib numbers if your system requires it.
7. Create markers — Start and finish (and splits if needed) with correct read windows.
8. Configure connectors — Link timing hardware for inbound reads; set outbound publishing targets.
9. Pre-race test — Verify test reads land as Used.
10. Seed T&F rounds — Use the seeding queue, workspace, bulk seeding, and advancement tools as needed.
11. Run the meet — Monitor reads, drive display boards from Scoreboard, resolve exceptions in real time.
12. Post-race — Finalize athlete statuses, generate reports, archive the meet.

Related Pages

• Getting Started
• Starting a Meet
• Importing Data
• Connectors
• Markers and Reads
• Timing Workflow
• Results and Reports
• Teams and Leagues
• Super-Events
• Seeding and Advancement
• Seeding Profiles and Defaults

Metadata

• Last Updated: 2026-09-09
• Document Version: 0.7
• Status: Active