Swimming Laps Monitor
Track pool sessions by laps completed, stroke type, and total distance. Includes a field for pace per 100m so swimmers training for time can see real progress, not just volume.
Swimming is unusual among cardio activities in how easy it is to misjudge effort. The water's support means a hard session can feel deceptively manageable in the moment, only for fatigue to show up afterward in a way that running or cycling rarely does so subtly. A laps log helps correct for this by tracking concrete numbers — laps, strokes, pace — rather than relying on how a session felt while it was happening.
Why pace per 100m matters more than total distance alone
Total distance swum is the easiest number to log but tells an incomplete story on its own. Pace per 100 meters reveals whether a 2,000m session was swum at a genuinely challenging pace or comfortably cruised through, two very different training stimuli that can produce an identical distance entry in a log that only tracks total laps.
Stroke type changes what a session actually trains
Logging stroke type alongside distance matters because freestyle, breaststroke, backstroke, and butterfly place meaningfully different demands on the body. A week that looks balanced by total distance might be almost entirely freestyle, missing the more varied muscular demand that mixing strokes provides, which only becomes visible once stroke type is part of the regular log entry rather than an afterthought.
The plateau that shows up in lap counts before it shows up in feel
Swimmers who log consistently for a few months often notice their lap count per session plateauing well before they consciously feel like progress has stalled. The log tends to catch this stall earlier than perceived effort does, since the water's support can mask early fatigue and a swimmer can keep completing the same number of laps for weeks while genuinely tiring faster within each one — a distinction invisible without pace data logged alongside the lap count.
A practical tip: log the first and last 200m pace separately
For longer sessions, logging your pace for the first 200m and the last 200m separately reveals pacing strategy in a way a single average pace can't. A big gap between the two usually means starting too fast and fading, which is worth knowing and adjusting for, rather than assuming an even, well-paced effort throughout simply because the average looked reasonable.
Frequently asked questions
Do I need a smartwatch to track swimming, or can I count laps manually?
Manual counting works fine, especially in a pool with consistent lap lengths. Many swim watches automate this and add stroke detection, but they aren't required to get useful data into a log.
What's more important to track: total distance or pace?
Both matter, but pace per 100m gives a clearer picture of actual effort and progress than total distance alone, since the same distance can be swum at very different intensities.
Should I log every stroke type I swim in a session, or just the main one?
Logging the breakdown, even roughly (for example, 70% freestyle, 30% backstroke), gives a more complete training picture than lumping everything under one stroke label.
Why would my lap count stay the same for weeks even though I feel like I'm working harder?
This is a common pattern and usually means fatigue within each lap is increasing even though total volume hasn't changed yet. Logging pace alongside laps tends to catch this shift before it's consciously obvious.
Is it useful to track rest time between sets too?
Yes, especially for structured interval sessions, since shortening rest intervals over time is itself a meaningful form of progress that a laps-only log would miss entirely.
How often should I log my swimming sessions to see a real trend?
Most swimmers find a clear trend over 4-6 weeks of consistent logging, since pace and endurance changes in swimming tend to be gradual rather than sudden.