Coach's Log / 6:15 AM

The pool is alive. Eight lanes of swimmers, three training groups. Some are mid-season, some returning from injury, some peaking for conference. You stand at lane four with a stopwatch. The first 50 comes through: 27.4. Good pace. But something looks off on the third length. Tempo seems slower. Is it fatigue, or just visual noise?

The athlete touches. You log the time. 56.1. Solid. But the most important part of the length never reached the surface.

From the Pool Deck to Real-Time Truth

The Gap

What Coaches See vs. What They Miss

Above Water / Visible

  • Split Times Measurable
  • Stroke Count Manual Tally
  • Tempo By Feel
  • Surface Technique Visual

Below Water / Hidden

  • Velocity Stability Invisible
  • Body Angle Drift Invisible
  • Depth Consistency Invisible
  • Turn Efficiency Invisible
  • Fatigue Markers Invisible

Under the Surface

The Truth the Stopwatch Cannot Tell

Two swimmers touch the wall with the same split. One held 1.48 m/s for the entire length. The other started at 1.55 and decayed to 1.38 by the flags. Same time. Completely different effort profiles.

Underwater, variables compound. Body angle shifts by two degrees. Depth drops from 0.7m to 0.5m. Stroke rate climbs while distance per stroke shrinks. The stopwatch sees none of it. But the next repeat will show the cost.

Lane 4 Live Live
Velocity
1.42 m/s
Effort
76%
Body Angle -3.1°
Depth 0.68 m
Stroke Rate 1.30 Hz
SWOLF 39

Example live readout

Book a Demo

Founder Perspective

Built From the Pool Deck

I coach the University of South Florida Swim Club. I have spent more than a decade in this sport, first in the water, now on deck with a stopwatch. I train and compete in triathlon, which forces an honest understanding of fatigue, pacing, and what breaks first when effort is sustained. I study mechanical engineering at USF. That background dictates how I think about systems: tolerances matter, reliability matters, and anything that cannot survive real conditions is irrelevant.

The stopwatch tells you when the wall was touched. It does not tell you why the second 50 unraveled. It does not show body angle drifting before it becomes visible, stroke rate climbing as distance per stroke quietly shrinks, or depth collapsing long before the flags. Coaches feel these things, but feeling is not the same as knowing. I kept seeing patterns I could not verify in time to act on them.

I built HydroVision because coaching decisions happen during practice, not after it. If fatigue can be detected earlier, it should be. If technique is degrading before the split changes, it should be visible. If data cannot be understood in seconds on a wet pool deck, it is not useful. This system exists to give coaches clarity where guesswork used to live.

Design Doctrine

  • If it cannot survive daily life on a wet pool deck, it does not ship.
  • If a coach cannot understand it in under ten seconds, it is redesigned.
  • If accuracy is compromised, the feature is removed.
  • No metric ships without validation against video and manual timing.

This system is being built alongside real teams, in real practice, with real constraints.

Roadmap

What's Next

HydroVision is entering a closed beta for the 2026 season. We are working with pilot programs to validate hardware, refine the dashboard, and stress-test the system across training environments.

The roadmap includes richer dashboards, individualized fatigue alerts, longitudinal tracking, and integrations with existing team management platforms.

For partnerships: contact@hydrovision.io

Planned Metrics Roadmap
Pace Stability Score 94
Fatigue Risk Medium
Turn Consistency ±0.08s
Breakout Quality A

Planned for 2026 release