Nine Columns, Zero Numbers: The Real Scorecard of Kabaddi Coverage

1:40 a.m., Bangalore. A document lay open on the laptop — nine sections, a table inside every section, and the same answer beside every table. Rules analysis: insufficient information. Player and team tactics: insufficient information. Competitive landscape, regional and cultural context, business model, governance, risk matrix, public narrative, industry transmission — nine out of nine, blank. Across the top sat a line no reporter had written, a system had: template complete, facts empty.

I scrolled it twice. Then a third time, the way you hunt for a scorecard that got trimmed off the page in printing. It wasn't there. And in that moment something landed that twelve years of writing on kabaddi had never shown me this cleanly — the biggest problem in this sport isn't a raider, it's our template. An empty document with nine handsome headings reads exactly like a full analysis. That is the basic grammar of our journalism.

We don't print insufficient information in kabaddi. We cover it in words: "this young raider has something", "the defence has found its rhythm", "this team looks different under pressure". Those sentences aren't wrong. They're useless, because anyone can write them and nobody can disprove them. An empty template and a filled preview do the same job — they let the reader believe something was said.

The July 2026 story keeps circling back at me, so I'll repeat it without the victory drums. Railway clerks and police constables turned into crore-rupee auction lots within weeks — the best economics story in Indian sport. One column of that story is still unwritten: no women's franchise league, thin coverage outside the Haryana–Punjab–western UP belt, and an unsettled federation turf war between circle style and standard style. Filling that column needs numbers, and numbers need a second layer that says which question each number answers.

The numbers themselves are not scarce. Raid points, tackle points, super raids, super tackles, do-or-die conversion, auction price — all of it gets published, all of it instantly. What's scarce is the slower layer. That layer requires somebody to pause the tape and sit with it.

I still have a logsheet out of the 2026 lockdown tape room: 214 matches across Seasons 1 to 7, every dubki attempt by raider and outcome. My first serious piece came out of that sheet. And at the August 2026 auction in Mumbai, back from a friend's wedding, I filed a value table forty minutes before deadline and two base prices went out wrong. A copy editor caught them. Since that day I have a rule: no deadline filing within twelve hours of a night out, and a second reader on every number. The rule exists because the template is fast and the fact is slow.

That empty document had nine dimensions and exactly one factual sentence in it: the input is empty. That is the template-completeness illusion. A report that arrives with nine tables and not a single figure is the analytical cousin of a preview saying "India's raiders are in form". The only difference is that nobody challenges a preview, while the system was challenging its own document.

Then there's terminology. Raider, attacker, assaulter — same man, three reports, three sets of implications. Translate do-or-die raid into "crucial raid" and the rule vanishes: the third raid after two consecutive empty ones is forced, not chosen. A dubki on a Punjab mud court and a dubki on a PKL mat are two different animals; the sentence has to name the code. If a parser choked on Devanagari, that is the same failure as a translated report turning do-or-die into "crucial".

The costliest problem is volume versus efficiency. In 2026, Patna Pirates beat Gujarat Fortunegiants 55-38 in the Season 5 final, and the whole campus was talking about Pardeep Narwal's record 369 raid points. I opened the match sheets and argued that the three-peat ran on a cheap, disciplined corner pairing and do-or-die conversion, not star power. That thread made me a columnist. Three-peat is a word fans invented to avoid saying that a corner pair won three finals. Raid points tell you how long a raider stayed on the mat; successful raid percentage tells you what he did with the time. The first number sells at auction. The second one wins.

Which brings back Jakarta, always with a date stamp attached. In 2026 India lost 23-24 to South Korea in the group and 18-27 to Iran in the semifinal — bronze, the first gold missed since 2026. I rewatched that semifinal at 2 a.m. and found a different sport: India raiding on reputation, Iran stacking zone-wise tackle points inside a wrestling-based defence built around Fazel Atrachali. In Jakarta the gold was guaranteed right up until the guaranteed part died. Before that we used to call India "unbeatable" at the Asian Games; since then every preview names Iran as co-favourite, never as spoiler. That shift came from tape, not template.

Underneath all of it sit the structural gaps the blank document exposed simply by being blank. No women's league is the largest long-term talent-pipeline risk in the sport, and every season we pay it tribute in one feature and move on. Broadcaster concentration is the league's biggest commercial vulnerability, and not one value table gets published on it. And in fixtures against Iran or Pakistan, nationalist framing is the default setting — when the scoresheet says it's just another match.

Now the part where I try to prove myself wrong, because I argue loudest about the things I could be wrong about. First possibility: this is plumbing, not journalism. A paywall, a JavaScript-rendered page, a parser that broke on Devanagari script. If so, this column is a genre error — me delivering a lecture on journalism at a server. Second possibility: the sample size is one. The dubki obituary stood on 214 matches; this piece stands on a single document. Declaring an entire ecosystem diseased from one empty file is exactly the single-tape overfitting I warn others about.

The third possibility is the uncomfortable one: maybe insufficient information was the honest finding. A district-level women's final with no scorekeeper sitting courtside — writing N/A there isn't failure, it's reporting. In that case I shouldn't be complaining; I should be writing that no verified record of this match exists. Which is the story.

So my next test is clean and it completes inside the next auction window. Within 48 hours of the hammer, count every "value" piece published: how many carry something like raid-points-per-crore, and how many carry only the price? My estimate is fewer than one in five. Second estimate: the season's first big emerging-raider profile will quote raw raid points and skip successful raid percentage. Both can be proven false — and if they are, I'll be the first man to print my own error with a timestamp. The question is simpler: next time the data doesn't arrive, do we print N/A, or fill in another template?