Entries & seeding

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

Entries

Entries come in from the same exchange files as rosters (SD3/CL2), or are added by hand on the meet setup. Dual-meet entry files also carry relay lineups, which are imported as relay legs.

Per OMPA rules, swimmers have a max events cap (e.g. 3 individual + 2 relay for 7–18). Exceeding it removes that swimmer’s times — the app surfaces this.

Seeding

Run Seed from the meet. 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 — broken alphabetically (last name, first name) by default.

How the meet type changes seeding

• Dual / tri — lanes split by team (home even, visitor odd; tri-meet uses 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.

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.

Validate first

Run Validate before printing to catch lone-swimmer heats and relay consolidation opportunities.