Swimming league appendix | URX

The Competitive Rulebook is shared across URX leagues. Pages written in discipline-neutral language apply to every competitive event unless they explicitly point here.

This appendix holds Swimming league specifics: min/100 m pace, distance in metres or kilometres, pool lap counting vs open-water splits, and integrity expectations that differ from Running. For min/km, outdoor GPS routes, and running pace floors, read the Running league appendix.

Units and display

Metric	Swimming league standard
Pace	min/100 m (minutes per 100 metres) for pool and most published swim formats. Open-water events may state an alternate display in the race brief—follow the brief.
Distance	m or km, as published (for example 400 m, 1 km, 1.9 km).
Pool segments	Laps (or lengths—match your tracker’s definition and the race brief).
Open-water segments	Splits at published checkpoints or per tracker partials, depending on format.

When a shared Rulebook page gives a numeric example without naming a league, check this table—or the Running appendix—before comparing your effort to a threshold.

When shared pages defer here

Shared articles describe activities, publication, verification, and mechanics for all leagues. Consult this appendix when you need:

Pace in min/100 m or swim distance in m / km
Pool vs open-water evidence and lap/split semantics
Swim mechanic bands (pace corridors, distance locks, ladder steps) as published for Swimming races
Accuracy and progression signals that read swim pace stability rather than outdoor GPS routes

Core policy remains in Submission requirements, Accepted evidence, and Race mechanics (mechanic types are shared; numeric thresholds are league-scoped in each brief).

Pool vs open water

Pool sessions

Pool activities are recorded in a lane environment with repeatable lap (or length) counts. Evidence should show:

Total distance and time
Average pace in min/100 m when the tracker provides it
Lap or length count consistent with pool size (25 m / 50 m / other—as your app and the race brief assume)
A visible session date within the three-calendar-day freshness rule

If the screenshot omits pool length or lap semantics, add a tracker link during publication so reviewers can reconcile distance without guessing.

Open-water sessions

Open-water activities may use GPS track, buoy segments, or hybrid tracker views. A strong capture shows total distance, time, pace (as published), and route or segment context when available. The same integrity standards apply as for any verified effort: fabricated routes, impossible lap maths, or mislabelled pool sessions as open water are Rule violations, not simple publication blocks.

Swimming mechanics

Mechanic types (Classic, Open, Pace Lock, Multirun, …) are shared product names. Swimming races apply league-specific pace and distance bands in the race brief—always in min/100 m and swim distance units unless the brief states otherwise.

If an activity does not fit the race mechanic, publication to that event is blocked at publish time; that is not Disqualification (DQ) unless integrity abuse is involved. See Race mechanics for the shared model.

Integrity notes (swimming)

One activity, one publication — the same swim session must not be bound to multiple race publications.
Fresh activity — session date must fall inside the three-calendar-day window ending on the publication day.
Lap and distance honesty — edited lap totals, wrong pool length, or duplicated screenshots across entries are treated under Abuse & manipulation policy.
Accuracy — Accuracy metric evaluates pace stability on verified swim sessions over a rolling window; inconsistent reporting can increase review scrutiny.

When you are near the top of a leaderboard, include a tracker link whenever the publication form offers it—see Provisional leader.

Running league appendix

Running-specific units, outdoor GPS expectations, pace floors, and integrity notes for the URX Running league—when shared Rulebook pages defer here.

System Model

One-page map of activity through verification, race states, progression, and ranking—aligned with Structural states and Appendix A.