The Report Came Back Empty, the Injuries Did Not: Kabaddi's Data That Never Gets Filed

Twelve pages. Nine sections. And in every single field, the same line — "N/A — insufficient information". No raider's name. No date. Not one number. This document had been prepared to comment on a report in which a player's ankle, a corner defender's ankle hold and a franchise's lone physio were supposed to sit in one causal chain. It came back blank.

This was not new to me. On the evening of the 2026 Asian Games semi-final in Jakarta, I watched India's defender Sandeep Narwal standing on the mat with a strapped shoulder. Iran's raiders kept coming at that side, and every angle of the fall ended on the same shoulder. India lost 18-27, and with that defeat the men's kabaddi gold streak at the Asian Games stopped. What the team physio gave me that night was the width of a tape job and the density of a match calendar. Neither was written down anywhere.

Back then I thought the information gap was temporary. It now looks structural.

Kabaddi's public world looks saturated with data, but it keeps no ledger for the body. After 2026, the Pro Kabaddi League converted every raid, every tackle, every do-or-die attempt and every auction price into a searchable record. Raid success rate, tackle success rate, super raids, super tackles, bonus-line touches — all of it is there, all of it tidy. And the same player's body? Nowhere. Which month the injury happened, how long rehab ran, when medical clearance was issued, how many raids it took before that knee spoke again — none of it exists in the public domain.

I arrived at this gap through my own route. In 2026, covering the inter-university tournament in Chennai for campus radio, I watched SRM University's raider Vikram (No. 7) go down during a do-or-die raid after attempting a dubki. His knee twisted on landing and he left the mat. I obtained the video, broke the landing down frame by frame, and wrote 1,500 words for the university magazine, blaming landing technique and an inadequate warm-up. Reading that sentence back today, it is the weakest line I have written — I had diagnosed from a replay, which is the single largest failure mode of my own method. But the same day built a habit: collect the injury footage, and then ask what made that injury possible.

After Jakarta in 2026, I spoke to the team physio and wrote that India's rushed return to play and incomplete protective strapping played a direct role in the semi-final defeat. National outlets picked it up. In 2026, when the world had stopped, I opened the case of former Jaipur Pink Panthers raider Rajesh Narwal, who retired in 2026 with an untreated ankle injury. Medical records, testimony from three former team-mates, and one number — at the time, only 12 per cent of PKL players had any form of injury insurance. The piece started a policy conversation inside the AKFI. That is where I learned the craft rule I now follow: testimony is only as strong as the document behind it, and in kabaddi the document is the rarest object in the room.

So when the twelve-page file came back empty, I did not file it as a technical glitch. I read it as evidence.

Any injury analysis needs three things — a name, a date and a number. Kabaddi's public record fails on all three, consistently. The name is usually withheld because it is tied to an auction valuation. The date has to be reverse-engineered from a fixture list because no official injury list exists. And how many raids passed before the body gave up — that number is recorded nowhere, because the desk that counts raids was built for scoring, not for workload monitoring.

I started with the injury and ended with the system that allowed it. That is the actual subject. And in this case the system spat the answer out on paper.

Two pipelines: the injury chain and the recording chain

The moment a raider's ankle is caught in an ankle hold, one chain begins: the keeper's tackle, rotational load on a planted foot, the raider losing balance, the fall onto the mat. This chain is almost always visible, because the broadcast takes it from twelve angles. From that same instant, a second chain should begin: medical assessment, injury classification, rehab timeline, return-to-play clearance. In most cases that second chain never starts. Where it does, it stays inside the club's walls.

The consequence is direct. The mechanism was visible; the mismanagement was hidden in plain sight — in the width of the strapping, in the face of the man sitting on the bench, in the word "fit" issued before the next night's match.

I reconstructed the collision frame by frame, then asked who looked away. The answer is rarely one person. It is a system in which a franchise carries one physio, a league calendar collides with national camps, and a player has no standing to say he is not playing tonight.

Raid count is not proof of risk — it is an estimate of risk, and we have been presenting it as proof. This is where kabaddi coverage deceives itself. We say a raider attempted 214 raids across a season and his ankle went. The inference writes itself: the load did the damage. But what is the sample? How many players in that same season attempted as many raids and survived? What was their floor time? What was their previous rehab history? That dataset does not exist. The day I tried to draw a straight arrow between load and injury, I had to admit the causal step was inference — and an evidence chain with an invisible link is not a chain.

So I now write three things alongside every number: what the sample was, which dataset is missing, and where the inference begins. Before the transfer fee, read the medical file — a fine slogan, except in kabaddi the file was never created. A player is valued at crores in an auction and not one public line exists about the state of his ankle.

Iran's wrestling-derived defensive school rewrote the risk map

After 2026, the physical grammar of India-Iran fixtures changed. Iranian defenders come out of a wrestling tradition in which taking a body off balance is technique, not merely obstruction. That meant ankle holds and thigh holds stopped arriving as separate events and started arriving as two phases of the same raid — pin first, rotate second. The raider's body is pulled in two directions, and for a player whose ankle was already loose, that double load is where careers end.

This is the same tactical shift that broke a gold streak and simultaneously redrew where Indian bodies would break. I was sitting in Jakarta watching it happen. What I could not show was how many Indian raiders that season faced a rising share of low tackles, because tackle-direction data is public and injury data is not. Without both halves, the map stays incomplete.

Crore-rupee market, zero registries

Auction prices climb. Broadcast rights climb. On-screen graphics glow with every player's success rate. Underneath all of it: no central injury registry, no standard for workload monitoring, no public return-to-play protocol. The sport adopted a professional market without adopting professional medical governance.

Women's kabaddi is the fastest illustration. India's women won Asian Games gold repeatedly, and they have no franchise league and no medical structure — not even the incomplete one the men receive. No league means no auction, no auction means no contract, no contract means nobody to claim against after an injury. Four gold medals decorate a table; the Asian Games medical room told a story the medal table could not.

The men's layer is not different, only longer in history. Before 2026, an elite kabaddi player was a railway clerk or a police constable with no rehab infrastructure behind him at all. That inheritance still operates. Job security pushed players to play through pain, and the habit survived the arrival of league money. When a 32-year-old retired raider tells you he played three years in pain, that is not a hero story. It is a report on a contract system in which the price of speaking was too high.

The empty document carries its own risk

The most dangerous thing about that twelve-page file was not its blankness. It was that its skeleton was complete — nine sections, nine headings, formal language throughout. A reader in a hurry could mistake it for analysis. It was a record of failure. This is the everyday accident of kabaddi coverage: structure present, substance absent, one confident sentence holding the middle together.

I do not separate this from injury management. A culture that sends a player onto the mat before he is fully fit is the same culture that lets an analyst publish a conclusion before the data has arrived. Both come from the same impatience. Injury is a language; most clubs only hear the noise. An empty dataset is also a language, and most desks fill it in rather than read it.

The popular assumption is that federations and franchises hide information. True, and half-true, which is the most misleading kind. The deeper problem is that kabaddi's public record was never built to hold injury at all. It was built to count raids and tackles, not to measure wear on a body. In a sport where everything is visible live, almost nothing gets filed — that is the blind spot on its bright surface.

One more thing belongs here, because my own method has been caught by it. When we make injury a pure output of the system, the athlete becomes a passive object. He is not. He chooses — to absorb pain, to play taped, to skip the last fortnight of rehab. But those choices happen inside constraints, and showing the constraints is the journalism; sorting players into brave or foolish is not. That is why I interview retired players by name, with dates, and ask for documents. Anonymous off-the-record quotes protect nobody and occasionally bury somebody.

Next season, when a raider goes down on the mat, the video will be watched by thousands within four hours, and his medical record will be found by no one. The replay will show us the angle of the ankle. It will not show how many nights he had already spent in pain, which raid he needed, or who told him the tape would be enough. Kabaddi's largest injury stories will stay invisible, because we never built them a file. Watch what the camera records. Then ask what was entered in the file — the answer will be empty almost every time.