WhatsApp was never built for sharing training sessions. The result: PDFs buried under memes, swimmers who can't find last Monday's set, coaches resending the same file every week. There is a better way.
WhatsApp has become the unofficial tool of every swimming coach. It was never designed for this. Open any group conversation and the evidence is immediate: the PDF from Monday is buried under birthday messages and memes, a swimmer asks "can you resend the session?" for the third time this week, and you're copy-pasting the same training block into a new message because nobody can scroll back far enough.
The tool works for messaging. It doesn't work for training documentation. The difference matters more than it first appears.
WhatsApp became the default because it was already there. Every swimmer already had it. The friction of adopting something new felt higher than the friction of using an imperfect tool. That's a reasonable calculation in the short term.
Over a season, the cost compounds:
The group management problem is less obvious than lost files, but just as real. When a swimmer leaves your group, you cannot remove them from a WhatsApp conversation without creating a new group. Over a season, groups accumulate former swimmers, parents who should no longer have access, and contacts from previous years. Every session you share reaches all of them.
There is also a personal boundary issue that most coaches notice only after it has already eroded. Your coaching conversations live in the same app as your family messages and private conversations. That separation disappears gradually. Swimmers message you at 11 p.m. because the app is the same one you check for personal messages.
Version control is the third layer. When you update a session at 7 p.m. and some swimmers already saved the 4 p.m. version, you have no way of knowing who has which version. In a race or a competition context, that matters.
The core idea is simple: a direct link, not a file. A link stays live. A swimmer bookmarks it and finds the session in thirty seconds, six weeks later. If you update the session, the link reflects the update without you resending anything.
From the swimmer's side, the experience is: click a link, see the session in the browser, no installation required, no account needed. That's it.
From your side, you have one place where all your sessions exist, organized by date and group, and searchable. When a swimmer asks what you did three weeks ago on Thursday, you find it in ten seconds. That history is yours, structured, and not buried in a chat thread.
Access control becomes straightforward. You share the link with the people who should have it. You stop sharing it with those who shouldn't. No group management, no migration, no orphaned contacts.
The transition is simpler than it sounds. You don't need to announce a system change or explain anything to your swimmers. The next time you would have sent a WhatsApp message with a PDF attached, send a link instead. That is the entire transition.
Your swimmers click the link, see the session, and most of them won't register that anything changed. For swimmers who ask where the file is, the answer is: there's no file, just click the link.
WhatsApp remains useful for what it does well: last-minute announcements, quick questions, logistics. What you're replacing is specifically the document-sharing use case, the one that creates the most friction and the most confusion over time.
When you stop resending files and start sending links, the "can you resend the session?" message stops appearing. Because the session was never lost in the first place.
320+ active coaches · 7,500+ sessions · Since 2017
Send a link, not a file. On Padlie, every session has a shareable link that stays live, updates automatically, and needs no installation on your swimmers' side. Free plan, no commitment.
Try for free →