The Empty Swimming File: When Data Stays Silent, Don't Let Belief Speak

In June 2026, at a pool in Hai Phong, I opened the monitoring file of a sixteen-year-old breaststroke swimmer and saw an empty column. That column records weekly training volume, the one thing anyone working in sports medicine must have before saying anything at all about injury. Without it, the rest of the file is just paper. She had just missed two weeks with knee pain, and her coach wanted a single answer: could she accelerate back to full speed right now? It took me forty minutes to say what I had to say, and my answer was neither yes nor no. It was: “I don't yet have enough data to conclude.”

That moment has repeated many times in nearly twenty years of work. It taught me something the swimming injury-analysis world in Vietnam rarely says outright: a data gap is more dangerous than a bad result, because a bad result tells you what to fix, while a gap invites you to fill it with something that merely sounds plausible.

At Lach Tray, I learned to read injury from the very first numbers. In 2026, working as an injury-analysis assistant for a football club in Hai Phong, I built my own training-load monitoring system and logged 127 injuries across 43 players in a single season. The coaching staff at the time called my approach “too defensive.” Four months later, eight high-risk players were detected before they developed serious problems, and the team cut injury days lost by 23% compared with the first half of the season. The lesson was not the number 127. It was this: if I leave the first cell blank, the whole spreadsheet collapses.

Today I work mainly in swimming, and this sport poses a far harder problem than football. A footballer runs on grass, and you can measure distance, sprint count, heart rate. A swimmer moves through water, where drag, stroke rate, distance per stroke and breathing rhythm merge into a mass the eye struggles to separate. Without a standard measurement system, all you have left is feel. And feel, in sports medicine, is a poor adviser.

Vietnamese swimming has a paradox: results on the regional stage exist, but standardised injury records barely do. In many provinces, the monitoring data of a young athlete is scattered across a coach's notebook, group chats, and parents' memories. When a swimmer has shoulder pain, people ask when it started, and the answer is usually about a few weeks ago. A time marker of “about” is not data; it is a guess wearing make-up.

In esports, a small patch can reverse the entire power order of teams, and people call that meta adaptation. In swimming, the role of the patch is played by input data. Without it, every conclusion rests on a version of the athlete that does not exist.

I once received a deep professional analysis running dozens of pages about a swimming article. Opening it, every data field read “insufficient information, cannot assess.” No athlete name, no lane data, no times, no dates. What stood out was that the author fabricated no conclusion at all. They stated plainly that the input data was empty, that any expert judgement would be a product of imagination, and that the correct action was to stop, re-run the extraction step, and not fill the gap with hypothesis. In an industry where many believe there must always be something to say, the courage to stay silent is a professional act. I read that document as a mirror held up to myself and to everyone working in swimming injury science in Vietnam.

Take the breaststroker's knee. The breaststroke kick forces the knee to flex and rotate outward continuously against water resistance, the densest mechanical load zone of any stroke. The risk of patellofemoral pain, tendinitis, or meniscal damage here does not appear in a day. It accumulates by number of sessions, by kicks per session, by volume and intensity. If the file only says “knee pain,” we do not know whether it is cumulative overload or an acute injury. Those two need completely different handling. One reduces load then builds back gradually; the other stops entirely. A wrong conclusion here doesn't just cost the swimmer a few extra weeks; it can push a sixteen-year-old knee into a spiral of chronic damage.

Then the shoulder. Shoulder pain is the signature injury of swimming, so much so that it has its own name: swimmer's shoulder. Its problem is that shoulder pain may originate in the tendon, the muscle, the joint capsule, or an imbalance between the pulling and pushing muscle groups. To separate those possibilities, you need data on range of motion, on muscle-group ratios, on long-term training logs. Without those three data sets, a diagnosis is merely an educated guess.

And the case I fear most: the adolescent swimmer. This is the phase when swimming prodigies get hyped in regional press, and also the phase when the body changes so fast that six-month-old figures become meaningless. For female swimmers, changes in height, body composition and relative strength can turn an age-group champion into a mid-table finisher within a single season. If the file does not record the onset of puberty, quarterly height, and the corresponding training cycle, we cannot tell whether we are looking at a temporary regression or a permanent ceiling. And when they don't know, people usually choose the worst option: increase training load to push the athlete through — precisely the method that generates injury waves.

Covid once showed me the same thing at scale. In 2026, when Vietnamese football returned after a five-month suspension, I recorded a 40% rise in hamstring injuries compared with the same period a year earlier. I proposed that one club adopt a ten-day progressive loading protocol for substitutes; the coach refused because he wanted to win the opening match immediately. By round five, that same team had lost 15% of its squad to injury. An empty stadium, a golden rule bent out of shape, and a body paying the price. Had there been a complete load file then, the debate would no longer have been about opinion, but about numbers.

The 2026 World Cup in Qatar reinforced that belief. I cross-checked 48 group-stage matches and recorded 31 muscle injuries, while the 2026 World Cup had only 19. Many rushed to conclude the cause was the pitch or the weather. But when I classified each case by match temperature, rest interval between matches, and pressing volume, a different picture emerged: injury here is a sequenced overload problem, not a curse, and that sequence only becomes visible when you take the trouble to classify data instead of lumping everything into a single number. Back in 2026, I had warned about Harry Kane's decline based on 412 minutes in which his sprint intensity fell 12% below his Tottenham season average. He faded from the knockout rounds. That was no miracle, and no misfortune. It was a simple subtraction.

What I want to say to those working in Vietnamese swimming, including the young coaches themselves, is this: you are sitting on an unmined data deposit. Every training session is a data row. Every shoulder pain is a signal. Every coaching change, programme change, pool change is a variable. The task is not to buy expensive equipment, but to record consistently and long enough. A notebook kept correctly is worth more than software kept wrong. The crowd always wants a story: a prodigy, a curse, an innate talent. And I, after all these years, only trust what can be written down again.

Numbers stay silent, but their sequence always knows how to tell a story. Every fall has a graph, and every graph has a break point. And the break point, in most cases, is not where a swimmer botches a movement. It is where someone left a data cell empty long before the body spoke up. Hai Phong, Moscow and Covid taught me that injuries never repeat themselves, but the way we record them can. The next task is boring: a shared spreadsheet, a recording standard, and a person patient enough not to fill the blank with a guess. If Vietnamese swimming does that boring thing over the next three years, I believe we will have a generation of athletes spared injuries that never needed to happen.