The Fourteen Pages Nobody Read: In Kabaddi, the Spreadsheet Knew Before the Court Did

August 2026, an indoor hall in Jakarta. The second half of a semifinal, and the Indian raider had less than thirty seconds. Iran's defence had been shutting the right channel since the twelfth minute of that match. The raider chose that channel anyway. The Iranian corner did not dive — he waited, took the ankle, and the cover closed the chain. Raid over. The scoreboard read 18-27.

In the mixed zone that night, a twenty-one-year-old left corner was being blamed online. I rewrote my match report around the chain-tackle structure and kept his name out of it.

On my laptop at the time was a fourteen-page file, filed before the tournament began. Page nine had the diagram of Iran's wrestling-derived ankle holds. Page eleven had South Korea's dash angles. I wrote fourteen pages. Nobody read them. The data still held.

This piece is not a lament about that defeat. It is about the audit that kabaddi should run every cycle and postpones every cycle — and about the three places where the sport's money, its selection and its audience all repeat the same mistake.

Context: the sport you can actually count

Kabaddi gets watched with feeling, not with an audit. That is unfair to a sport that is, technically, India's most measurable team contact game. In football you count passes completed. In kabaddi you can count the price of a point, because the rules themselves convert every decision into a number.

The thirty-second raid limit creates quantified time pressure, which means decision speed is measurable. The bonus line pays one point only when the defence has six or more players on the mat, which means the size of the defence changes the price of the raid. Do-or-die arrives after two empty raids and dismisses the raider if he fails, which hands you a clean measure of risk. A super tackle pays two points when the defence is down to three or fewer, doubling the stake on a defender's gamble. An all out pays two points and revives an entire side, which means one raid can rewrite the arithmetic of a match.

Those five rules together mean kabaddi throws up a countable decision roughly every twenty seconds — and that is precisely why the sport has very little room for excuses.

The problem is that this measurement exists in one place only: the Pro Kabaddi League. Launched in 2026, the league produced raid-by-raid, match-by-match data. Outside the league — on the mud courts, in state teams, in junior championships — almost nothing is coded. So we have excellent data for an auction and almost none for a selection meeting.

The second thing any analysis should state first: kabaddi has two codes, and they breathe differently. Circle style is played on the mud of Punjab's festival circuit, where grip and the fall come before speed. Standard style is played on the mat — the PKL and Asian Games code — where angles, distances and switches matter. Calling either of them the "real" one is the biggest available error. What differs is not technique but the reward structure: mud rewards the defender who can bring a raider down; the mat rewards the defender who can shift space from left to right.

And the third principle behind everything I write: in kabaddi, the cause of a defeat is never a player. It is the selection calendar, the retention rule, the coaching pipeline. Blaming a left corner overnight is easy only because he has no publicity budget.

Core: three audits, and a bill for each

Audit one — where the raid came from is not the same as what the raid looked like

February 2026, an auction room in Mumbai. A statistics degree, a laptop and a freelance rate nobody respected. A senior print reporter's first question was whose numbers I was there to run. I coded all twelve squads against a raid-zone model built from Season 4 footage.

By July my weekly raid maps showed that Pardeep Narwal's 369 raid points for Patna Pirates were coming overwhelmingly from the right-corner channel — not from the celebrated dubki whose clip ran every week. By August, two digital desks had syndicated those maps.

I have to state my limits here, because a rate without a limit is decoration. My large database covers 1,842 raids across nine seasons, 2026 to 2026, coded in 2026 — the year the stadiums were empty and only video was left. Coding 1,842 raids taught me more than any full stadium ever did. But that coding cannot see what matters: a raider's fatigue, a defender's starting position, a coach's instruction, or whether the raider chose that channel or was pushed into it. What I can see is the touch point and the channel. What I cannot see is the reason.

So I stopped writing "he was unstoppable" and started writing "he was unstoppable from there." In kabaddi, "from where" almost always says more than "how many."

The same test applies to every raid: every raid is a small argument about how the game should be played. The raider who attacks the bonus line is arguing that a point is available against six defenders. The raider who takes the right channel is arguing that his body can hold that angle. Neither argument is wrong in principle; the result shows up in the total.

The real cost of this audit did not arrive in rupees but in bylines. I coded for four months and did not ask for a byline, believing the work would speak. The work did speak — my maps spoke instead of me. I have never fully lost that habit, and it is the most expensive one I own.

Audit two — the auction is a forecasting problem, not a television event

Every auction season, the press asks who was bought and for how much. The better question is why the market's consensus lags the data by exactly one season.

My method is unglamorous: publish a projected price board days before the gavel, then grade yourself against the result. I did this ahead of the Pro Kabaddi Season 5 auction. The spreadsheet knew the auction before the room did — and that is evidence of nothing except a process that can be repeated.

The one-season lag has three concrete causes. First, scouts watch highlights, and highlights show the dubki, not the channel. Second, retention rules shrink the supply of proven raiders, so the price is set by scarcity rather than by capability. Third, bonus-line points count the same on the scoreboard as the third point of a super raid but are priced differently by the market, because a bonus-line point arrives against six defenders — cheap to produce, therefore read as cheap.

Add up the bill: a franchise paying a premium for volume is also paying for points that were available more cheaply. A large raid-points total never reveals how many of those points could have come from an option the squad already had. That is the most expensive mistake in an auction, and it is repeated every season.

Audit three — Jakarta's answer was in the selection calendar, not on the mat

Back to those fourteen pages. Page nine was on Iran's ankle holds. Iran's defence comes out of wrestling, and a defender raised in wrestling does not dive — he works the grip and the ankle, stopping the raider rather than bringing him down. Indian raiders were trained for the dive and the touch, not for changing body angle against an ankle hold. Page eleven was on South Korea's dash angles: Korea was converting its defence from a straight line into angles, and our scouting was reading them off old footage.

The result is in the file: a 23-24 group defeat to South Korea, then an 18-27 semifinal defeat to Iran. India's first men's Asian Games gold went with it. The same evening, Iran beat India 27-24 in the women's final.

This was not a collapse of nerve. It was the predictable output of selecting on reputation rather than on technique, and it was forecastable in advance. The specialist who could have simulated an Iranian grip was at home; the player picked on reputation was standing at an angle he had never rehearsed.

The easiest and most wrong route is to blame Fazel Atrachali. He had already been rewriting tackle-point records in the PKL before Jakarta. He was in the data — in any scouting department's data, in any video analyst's data. What was missing was not evidence; it was the vote that evidence gets in a selection meeting.

The bill is clean: one gold, and the selection slots given to reputation instead of to a technical requirement. That is why I now publish before the tournament, not after. An analysis written after the result is a claim; an analysis written before it can be checked.

Audit four — four golds and not one auction

India's women have won Asian Games gold in 2026, 2026, 2026 and 2026. Four golds. And the women's game still has no franchise league; the PKL remains men-only.

Calling this a talent failure is the most comfortable and the most false sentence available. A sport with four Asian Games golds and not a single auction does not have a talent problem; it has a pricing problem. Where there is no auction there is no price discovery; where there is no price discovery there is no salary floor; where there is no salary floor, a daughter's career becomes, for her parents, a risk rather than a plan.

The bill is denominated in broadcast hours. Not one women's match has been sold in prime time the way the men's matches were, so the audience base on which advertising rates are set never formed. This is an attention-economy failure, and the evidence is on the mat: at the 2026 Asian Games the final was pulled to the last moments, decided by a single point against Chinese Taipei. The contest has arrived; the camera has not. Anyone who files women's kabaddi under "developing" should also write down that Chinese Taipei and South Korea are no longer objects of sympathy but genuine contenders.

Contrarian: the problem is not a shortage of data, it is that data has no price

This is where I am most often misread.

Kabaddi does not lack data. The PKL generates a denser per-match record than any non-cricket league in India. The real blind spot sits elsewhere: ninety per cent of analysis is about the moment that is on tape, and zero per cent is about the moment in the lungs at the sixtieth minute. A do-or-die raid at the sixtieth minute is not a data problem; it is a conditioning and rotation problem. And the rotation decision comes from the bench, not from a spreadsheet.

The second, more uncomfortable truth: the analysis exists, it simply is not priced. Those fourteen pages were free, so they went unread. What carries no invoice carries no weight, and in a selection meeting weight is everything. I have no trouble conceding that my own coding is incomplete: 1,842 raids can tell me where a raider went, not what a coach said. An analyst who does not print his limits is hiding them inside the result.

The third trap is language. Since 2026 every Indian preview has called Iran a spoiler. It flatters the home audience and it is factually lazy — in the men's game Iran is a co-favourite, not a spoiler. Calling your opponent a spoiler converts your defeat into an accident, and accidents require no learning.

Takeaway: count three things next match, argue about the rest later

My method is to publish the claim first and check it later. In the next match, count three things.

First, the raid channel — what share of a team's points came from the right corner, and what share from the bonus line. Second, how often a team attacked the bonus line against six or more defenders, and how often that produced the cheap point. Third, after a super tackle, how many seconds it took before the next raid was stopped — because those seconds reveal whether a team is playing from data or from habit.

And the next time a twenty-one-year-old left corner is blamed overnight, ask one question: who had read the fourteen pages first?