Entries & seeding

Entries are which swimmers swim which events. Seeding turns those entries into a heat-and-lane assignment.

Entries

Entries get into a meet three ways:

• SD3 entry file — the hub’s Details → Import entries section. Dual-meet entry files also carry relay lineups, which are imported as relay legs. A file containing several teams’ entries requires explicit multi-team confirmation and per-team permission.
• By hand — the Enter a swimmer panel on the hub’s Details tab: pick a swimmer from a participating team’s bound roster and the event. (Teams and rosters must be in place first — see Rosters & participants.)
• On deck — late/deck entries are added from the run screen during the meet (see Handling changes on deck).

A CL2 file is not an entries source — the CL2 import mirrors Meet Manager’s heat/lane assignments onto entries that are already imported, for meets seeded elsewhere.

Building relay lineups

The relay workspace at /meets/<id>/relays?team=<team> (open it by URL — it has no nav link yet) builds a team’s lineups from scratch, one card per relay event: a ranked candidate pool per stroke, drag-and-drop or click-to-place legs, an Optimize button that picks the fastest legal assignment, a projected time next to what the squad was entered at, and badges for finals conflicts (a swimmer already racing an individual final that day) and lead-off record chances. Free-relay leg order defaults to the team’s usual order learned from the season, switchable to 2-3-4-1 and friends. Lineups auto-save as drafts; the legs of a live, seeded relay entry are still edited on the run screen.

Max events

League rules cap how many events a swimmer may enter (e.g. 3 individual + 2 relay for 7–18). Validate and Seed both report violations; seeding refuses to run while a swimmer is over the cap, unless you explicitly choose Seed anyway to acknowledge the violations (e.g. an exhibition arrangement the referee has approved).

Seeding

Run Seed from the meet’s Seed tab. Seeding is a deterministic function of the entries, their seed times, and the resolved configuration: the same inputs always produce the same heats and lanes, so re-importing data never reshuffles a meet.

Key behaviors:

• Heat order — slowest heat first, fastest last.
• Lanes — center-out within a heat (fastest swimmers toward the middle).
• No-time (NT) swimmers seed last.
• Ties — for OMPA-style leagues, equal seed times (and the NT block) break by birthdate — oldest first, then name — mirroring Meet Manager, so older swimmers in an age group seed toward the faster heats. Leagues can configure plain alphabetical (last name, first name) instead.
• Lone-swimmer heats are consolidated automatically into an adjacent heat as part of seeding.

How the seeding mode changes things

The behavior is driven by the meet’s resolved seeding mode (from the meet → template → league cascade — see Create a meet):

• Team lanes (dual/tri) — lanes split by team (home even, visitor odd; tri-meets use a three-way split). Girls + Boys relays consolidate into one centered heat when the combined count fits the pool.
• Championship — the sprint strokes (<100 Free/Breast/Back/Fly) run prelims and circle-seed the fastest three heats; IM, the 100s, and all relays are timed finals.
• Strict by time — straight seeding, no team split.

Re-seeding

Seeding again after edits shows an override confirmation. Once results have been entered, re-seeding is deliberately harder: it discards the recorded results for re-seeded events, and the app makes you confirm that. Prefer the per-entry tools below (or deck moves) once the meet is under way.

Validate

Run Validate before seeding or printing. It reports:

• Max-events violations (blocking).
• Relay composition warnings — e.g. a 6&U mixed relay without the required 2-boys-2-girls balance.
• Seed-time course conversions — a summary of which seed times were converted between courses and how.

Editing after seeding

On the schedule you can move or swap a swimmer between lanes, add or remove explicit (empty) trailing heats, and unseed or remove an entry. Edits use optimistic locking — if someone else changed the same heat, you’ll be asked to refresh.