Teams and Leagues

Purpose

Set up school, club, and conference structure so rosters, reports, relays, scoring, and team-lane seeding stay consistent.

Prerequisites

• A meet already created.
• Athletes imported or ready to import.
• For scored meets, a consistent team-code convention decided before race day.

Teams

Open Teams to manage the master list of schools or clubs used by athletes and relays.

Each team has:

• Code — the stable short identifier used by athletes, relays, imports, and scoring.
• Name — the full display name shown in reports and results.
• Unattached — whether the team is excluded from team scoring.
• Lane Slot — an optional meet-wide slot used by team-lane seeding.

Unattached and non-scoring teams

If a team should appear in the meet but not count toward team scoring, mark it as Unattached on the Teams page or in the individual team editor.

In the current UI:

• the teams list shows an Unattached column
• the team editor includes a scoring toggle for the team

When a team is marked unattached, it is treated as excluded from team scoring. This is the main workflow to use when a school, club, or composite team should remain in results but not score as a team.

Team Lane Slots

Track meets can assign each team a Lane Slot.

This is used by the team-lane seeding workflow:

• 0 means unassigned
• positive values map the team into a team-lane template slot
• the slot applies meet-wide, not just to one event

Use lane slots when duals, tri-meets, quads, or similar formats need reserved lane blocks by team.

See Team-Lane Seeding for the round-level setup that uses those slots.

When to Create Teams First

Create teams before importing athletes when:

• you want consistent team-name display immediately
• you expect scholastic or XC team scoring
• you will import relay entries that rely on team codes

If athletes are already imported with team codes, you can still create missing teams later and map those codes to display names.

Team-Code Guidelines

• Pick one code per school or club and use it everywhere.
• Keep the code short and stable.
• Do not create separate codes for cosmetic spelling differences.
• For relays, use the team code for the school and the relay letter for the squad, not a brand-new team code per squad.

Examples:

• LETO with relay letters A, B
• BOLLES with relay letters A, B, C

Editing Team Assignments

You can assign a team code from multiple places:

• Athletes page for athlete roster records
• Athlete editor for detailed profile changes
• Relay entry editor for relay team code

Keep athlete team codes and relay team codes aligned when the same school appears in both individual and relay results.

Leagues

Open Leagues to group teams into conference or league buckets for reports.

Leagues are useful when:

• one meet includes teams from multiple conferences
• you want league-specific splits or reporting
• you need conference results alongside overall results

Leagues do not replace teams. They are a second layer of grouping built on top of team codes.

Double-dual scoring via leagues

If you are running a double dual or another small head-to-head scored format, 2Timer can generate the pairwise league groupings for you.

When the Leagues page is empty and the meet has 2 to 6 scoring teams, the empty state shows a Generate Double Duals Leagues button so you can start from there immediately.

You can also use the page macro:

• Macros
• Generate Double-Dual Leagues

Both entry points run the same macro. It creates league definitions for each scoring-team matchup so reports can split or score by those head-to-head league groupings instead of requiring you to build every pairing manually.

Important details:

• the macro uses scoring teams only
• unattached teams are ignored
• it requires at least 2 scoring teams
• it currently supports up to 6 scoring teams in the meet

This is one of the more distinct league workflows in 2Timer and is especially useful for dual, tri, and quad style T&F scoring setups.

Typical Scholastic Setup

1. Create or import teams.
2. Confirm each athlete has the correct team code.
3. Create leagues if your meet spans more than one conference.
4. Add the right team codes to each league.
5. Use reports that split or filter by team or league.

Import Paths

Teams can be created or enriched from:

• athlete imports that include team codes
• HY-TEK team data
• Lynx PPL or AFL files
• CSV team imports

If an import provides team codes without team names, create or update the teams list afterward so reports show readable names.

Team Scoring Notes

Cross Country

XC scoring depends on athletes having the correct team assignment. Missing or inconsistent team codes are one of the most common reasons team scores look wrong.

If a team should not score, mark it Unattached so it stays visible in results but is excluded from team scoring.

Track and Field

T&F team scoring uses athlete team codes for individual events and relay team codes for relay events. Keep both aligned to the same school code if they should contribute to one team total.

If a team should appear in the meet but not score, mark it Unattached on the team record. If you need head-to-head double-dual style groupings, use leagues and the Generate Double-Dual Leagues macro.

Team-Lane Seeding

If your meet uses team-lane seeding, verify the teams list before race day. A missing or wrong lane slot can change lane ownership and heat layout in the seeding workspace.

Common Problems

Verification Checklist

• Every scored school or club has one stable code.
• Team names are filled in for operator-friendly reports.
• Athletes on the same team share the same code.
• Relay entries use the intended school code plus squad letter.
• Team lane slots are assigned correctly if team-lane seeding will be used.
• League definitions include all expected team codes.

Related Pages

• Meet Setup
• Importing Data
• Athletes and Entries
• Results and Reports
• Track and Field
• Team-Lane Seeding
• Track and Field Team Scoring

Metadata

• Last Updated: 2026-04-18
• Version: 0.2
• Status: Active