Relays

Purpose

Explain how relay events are represented in 2Timer and what operators should verify for relay entries, team letters, and imports.

Prerequisites

Meet created as track and field.
Relay event created with discipline set to Relay.
Teams configured or team codes imported.

Relay Entries

Relay entries are team entries rather than standard individual event entries.

Each relay entry typically includes:

school or club code
relay team letter such as A, B, or C
optional relay-leg data for display or export workflows

The team code identifies the school or club. The team letter distinguishes multiple squads from the same school.

Team Codes and Team Letters

Use the school code for the organization itself.

Do not create separate team codes for each relay squad if they are still from the same school. Instead:

LETO = school code
A / B / C = relay squad letters

This keeps scoring and reporting consistent.

Relay Legs

Relay legs may be tracked separately for display and roster clarity, but the standard timing result is still attached to the relay team entry as a whole.

That means:

the scored result belongs to the relay team entry
the legs support identification and display
the standard workflow does not treat each leg as an independent chip-timed finish

Import Behavior

HY-TEK import can bring in relay entries and leg information when the source file provides them.

Before race day, verify:

team codes map cleanly to your teams table
relay letters are correct
duplicate squad naming has not turned into duplicate school codes

Race-Day Check

Before seeding or exporting to FinishLynx:

confirm each relay event is marked as a relay
confirm each relay entry has the correct school code
confirm squad letters are present where a school has more than one relay
confirm relay legs are populated when your workflow depends on them

2Timer Help