An Empty Report Is Not a Clean Bill of Health: The Data-Void Trap in Cricket Injury Surveillance

The scan did not explain the pain.

The MRI showed a clean grade-2 tear of the right hamstring, 2.1 centimetres. But the pain behaviour of that 24-year-old winger, his isometric strength scores, and the angular behaviour of the hamstring at sub-maximal sprint speed told a different story, one the report had no field for. That evening in 2026, in the medical room after a 2-1 win over Melbourne Victory in Sydney, I understood for the first time that imaging is never the whole patient. It is one chapter — and usually the least informative one. (— Root: 2026 A-League Hamstring Protocol)

Last month a file of the opposite kind landed on my desk. Fourteen pages of return-to-play documentation, structurally flawless, every table in the right place — and every risk cell reading "N/A", every evidence point blank, with a green tick on the final page declaring: "No significant concerns."

These two incidents are symptoms of the same disease. The first had data but not the data that mattered. The second had a conclusion with no data behind it at all. And this is where cricket's injury management fails most often: it reads an absence of information as an absence of risk.

Engineering has a plain name for this. When the sensor lead falls off, the monitor reads zero — and a zero-reading monitor can easily be mistaken for a healthy patient. In cricket's injury surveillance, the fallen-sensor event happens quietly, routinely, and almost never gets caught.

Across 32 years of watching this game, I can say one thing without hedging: no league can yet answer accurately whether cricket injuries are rising or falling, because the format being played is not the first thing anyone writes down.

A Test bowler delivers 15 to 20 overs a day, four or five spells across five days, 40 to 50 minutes between bursts. A T20 bowler's entire workload is four overs — but those four overs may arrive across three different cities in five days, past three flights, two hotels and a sleep deficit. These two loads cannot be measured in the same unit, yet franchise workload dashboards have done exactly that for years. This is not a measurement error; it is a unit-conflation error, the equivalent of averaging pounds and kilograms in one column.

While working remotely from Sydney for an Australian broadcaster during the 2026 World Cup, I logged every soft-tissue injury across 64 matches. Teams with three-day turnarounds suffered 27 per cent more hamstring injuries than teams with four days or more. I published "The 72-Hour Problem" before the final; two Premier League medical staff later cited it in internal notes. A veteran broadcaster told me women do not understand tactics. I answered with a 12-page data appendix. (— Root: 2026 World Cup Hamstring Data)

The most useful lesson from that study was methodological, not statistical. I began forcing every injury entry to carry format, fixture density and travel distance alongside the diagnosis. I no longer write injury news without fixture-density data.

Cricket has not made that mandatory. Our surveillance counts overs, runs, strike rates and economy rates — but never the one field that matters most: what we did not manage to collect.

That leads to the second failure: benchmark error. A 150 strike rate is below par for a T20 finisher; a 50 strike rate is entirely acceptable for a Test opener. Injury data carries the identical trap. Forty overs in a week for a 24-year-old quick and forty overs for a 34-year-old quick are the same number and a completely different risk. Without age, action, injury history and heat acclimatisation, that number means nothing.

In 2026, during Liam O'Connell's grade-2 right hamstring tear, I formalised this. I reviewed 42 A-League hamstring cases from 2026 to 2026, recording grade, MRI lesion size, match minute at injury, and actual return time. On that basis I published a 1,200-word return-to-play explainer on the club's new digital platform, predicting six weeks. O'Connell returned in five. The piece drew 250,000 reads. In a press box of 40 men, I was the only woman. I had been slow to trust new media; the data changed my mind.

Since then I use a fixed template: grade, MRI size, precedent cases, expected return range. I never guess timelines again. (— Root: ISTJ method plus protocol work)

The third failure is the most dangerous because it is invisible: the silent false negative. An empty risk screen gets passed downstream as "no concerns found", when the correct sentence is "no screen was performed." The distance between those two sentences is, quite literally, the patient.

When the A-League suspended in March 2026, I was team doctor liaison at Western Sydney Wanderers and helped draft a 14-page return-to-play protocol with five substitutes and a three-week pre-season. After the restart, five ACL ruptures occurred in ten matches. I reviewed each case methodically: compressed schedules, empty stadiums, insufficient preparation windows. I wrote a 2,000-word warning for The Sydney Morning Herald; the league added five substitutes for 2026-21. I then built a personal ACL database of 120 cases and adopted a precedent-first rule — every new injury is compared against historical clusters before anything else. (— Root: 2026 Empty Stadiums ACL Cluster)

The precedent method has transferred to cricket only partially. Football's hamstring protocol — the Nordic curl block, the eccentric loading steps, the six-week ladder — arrived in cricket as a near-literal translation, without adjustment for bowling load, subcontinental heat or travel fatigue. What the 2026 A-League protocol gave cricket was process; what it did not give was the connection between that process and the sport's own mechanics. (— Root: Team Doctor Liaison | Scenario: discussing return-to-play decisions)

Let me be explicit about confidence levels. On the format-conflation risk I am highly confident, because it is arithmetically demonstrable. On any individual player's fragility I am at zero confidence, because the file contains no format, no age, no spell count, no travel schedule. Treating those two registers as one voice is the oldest sin in injury journalism.

Invert the question and an uncomfortable truth appears: the player we label injury-prone usually has an empty file. The label is not a diagnosis; it is a trace of our own collection failure. We can count the overs of a fast bowler who has broken down three seasons running, but we cannot see his sleep debt, his flight count, a change in his action, or whether his contract is expiring. We call the athlete fragile while our surveillance was blind.

More data is not the answer either. Cricket now has GPS vests, ball-tracking, sleep logs and heart-rate monitoring. All of these systems share the same structural weakness: they keep no column for what they fail to record. In a spreadsheet, a missing cell and a zero look identical. The analyst reads an empty cell as zero risk, and the decision goes the wrong way. The failure is not technological; it is a design failure.

One more thing transferred badly from football: the transfer-medical template. In Europe, buying a player triggers broad screening in which imaging, functional testing and load history are read together. In a cricket auction, that process compresses into a few hours and one scan. Judging a novel from one chapter is still judging a novel from one chapter. (— Root: Team Doctor Liaison plus transfer market)

So what should change next season? My proposal is ruthlessly simple. The first field of every injury report is format: Test, ODI, T20I, The Hundred, or franchise league. The second is the assessment date, because 30-day-old information cannot underwrite today's decision. The third is an explicit declaration — screened, or not screened.

In a regular season those three fields do the most work, because the real story of a regular season is never in the table. It sits in fixture density, in travel, and in the small signals that appear in data long before they become headlines. In my experience, teams that discover an injury crisis mid-season usually knew about it earlier. They simply had not written it down.

Which brings me back to that fourteen-page file with every cell blank and a green tick on the last page. The question is plain and deeply uncomfortable: when the file was empty, who ticked the box — and whose name goes on the report when the next injury arrives?