The Empty Report at the Pool: Why Swimming Injury Data Always Arrives Late

In August 2026, I received an injury summary from a swimming training centre in northern Vietnam. The report had every column: athlete name, event, weekly training volume, rest days. The injury section was blank. Six weeks in a row, not a single case was marked. The person in charge signed it, sent it off, and added one short line: "Squad healthy, no issues." In nineteen years on the job, I have learned one thing: an empty table is never good news. It is only a question that has not been answered. At Lach Tray, I learned to read injuries from the first numbers — and the first number here is zero. Swimming has a lower injury rate than football, but lower does not mean none. Long-term studies of national teams show that the shoulder — specifically swimmer's shoulder, damage to the rotator-cuff tendons — accounts for roughly half of all injuries among freestyle and butterfly swimmers. Breaststroker's knee is the second cluster. Yet at most centres in Vietnam, this data does not exist in any traceable form. The reason is not expertise. It is record-keeping habit. Football has a dedicated medical department, load-monitoring software, and mandatory reports every matchday. Swimming relies largely on the coach's memory and a few lines in a notebook. When a swimmer's shoulder hurts, he usually does not report it, because reporting means his volume gets cut — and volume is everything in this sport. One rest session can cost a competition slot. I saw this during the COVID-19 period. In 2026, when pools reopened after months of closure, I recorded a sharp spike in shoulder injuries among athletes who returned to training too fast. The mechanism was clear: load rose before soft tissue could adapt. Hai Phong, Moscow and COVID — three milestones taught me that injuries never repeat, but the way they appear always does. The empty report is evidence of a record-keeping system left blank, not of a healthy squad. Those two things are completely different. When I cross-checked, I started from what could be measured rather than what was told. The average weekly training volume of a competitive swimmer ranges from 40 to 70 km at peak. The shoulder performs thousands of rotation cycles per session. Biomechanically, this is an accumulation problem: every time the arm leaves the water, the rotator tendons take a small tensile load, and the sum of thousands of small loads is the injury. No single moment is big enough to be called an accident. Only accumulation. I took the report's six weeks, matched them to the volume log, and found a familiar pattern. The first three weeks, volume rose steadily. In week four, there was a dry-land session with a pulling weight — an exercise I have seen appear right when the body had not recovered. In weeks five and six, two butterfly swimmers cut volume abruptly, with no reason written in the log. One freestyle swimmer changed training content midway. No one wrote the word "injury". But the sequence told the whole story. Every fall has a graph, and every graph has a breaking point. Here, the breaking point was week four. To test it, I built a two-column comparison table: the left column held what the report said — six weeks, no injuries. The right column held what the volume log said — one heavy session at the wrong time, two unexplained taper cuts, one content change. The two columns did not match. When two independent data sources disagree, I do not pick a side. I go looking for a third source: the competition calendar. And there I found a mandatory fitness test falling exactly in week five. The first reaction most people have when they see an empty table is to fill it in. They speculate: the squad must be healthy, the coach must be managing well. I understand that impulse, because an empty table makes an analyst look useless. No one pays someone who only says there is nothing to say. But filling gaps with guesswork is the most serious mistake in this profession. A conclusion drawn from missing data is still a conclusion, and it will feed into someone's decision — whether to let him compete, whether to raise the volume, whether to renew the contract. The body is a closed system, but data is the key that opens it. If the key is misplaced, the only correct move is to say I do not yet have enough information to conclude. This is where I differ from most of sports media. Media needs a story, and an empty story does not sell. I need a fact, and a missing fact is still more useful than a full story. The discipline of saying "not enough data" is far harder than guessing, but it is the line between analysis and fabrication. There is a second, subtler temptation. Once a hypothesis exists — say, shoulder injury from volume — the analyst tends to view all data through that lens and turn it into evidence. I nearly made this mistake myself. The defence is to force myself to find an opposing hypothesis: if the squad really were healthy, what would the data look like? The answer is that the volume log would be flat, with no unusual heavy sessions. The log was not flat. The opposing hypothesis was eliminated. Only then did I allow myself to take the next step. That empty report is still on my desk. I did not fill it with inference. I sent back a list of what needs to be measured before the next season begins: weekly volume, the number of dry-land sessions, and one simple column recording any pain lasting longer than two sessions. If I had to choose between a table full of wrong numbers and an honest empty one, I would still choose the second. But I will not leave it empty for long. Next season, I want an answer to one question: were the three swimmers who cut volume in week five truly healthy, or had no one simply asked them hard enough?