From an Empty Data Cell to Kolkata: Where the 41-Field Accounting Breaks in Indian Women's Cricket Reporting

Last week I reopened an old spreadsheet on my Kolkata desk. The file name was from July 2026, the Derby semifinal — Harmanpreet Kaur's 171 not out off 115 balls, India 281 for 4, Australia beaten by 36 runs. I had coded every delivery of that match into my 41-field schema, after a credentialing officer told me women's matches didn't need a stats desk. Nine years later, the first thing that stung when I opened that file was not the score. It was an empty cell — the attendance column, which I had left blank because no official source carried the number. In the past month, in Kolkata, across newspaper reports, websites, board press releases and transfer-market chatter on Indian women's cricket, the rows that stayed most consistently unfilled were the ones that tell the story beyond the boundary. This is the audit report of that.

Let me define the method first, because without definitions every cricket argument stays half-finished. My 41-field schema is no magic model. It is a public instrument: 41 columns, each with a written definition, each with a specified source and an owner. I have run it on men's internationals since the 2026 Eden Gardens final, and in 2026 I applied it to women's matches on the same terms. Its one principle: a standard is a column you must fill, not a slogan. If a column exists and is empty, that is not a technical glitch — it is an editorial decision. And editorial decisions can be held to account.

The biggest lesson of this audit came in 2026, when the outlet handed me the Russia World Cup xG and PPDA desk because the 41-field schema had travelled to football. Across 64 matches I rebuilt the model from raw event feeds; three providers disagreed on what counted as a big chance, so I wrote one definition and applied it 1,580 times. My model gave Croatia a 4% chance of reaching the final. They reached it. I did not discard the model — I added columns for rest days, extra time and travel, and published the errata myself. Data does not lie — my schema can. The same principle applies to women's cricket reporting. The problem is not that the data is wrong. The problem is that many columns are simply never filled, and the ones that are filled have no written definition.

Here is a necessary disclosure. In 2026, when the registry went dark and the board called me back because an auditable ledger had suddenly become the only thing anyone trusted, I rebuilt the IPL player-movement desk remotely from Kolkata in 14 days: 8 franchises, 200 registered players, NOC scans, quarantine windows, a 48-hour clearance checklist for the UAE shift. While the league played to empty stands, I logged 512 closed-door matches across football and cricket. Home win rate fell from 44.8% to 40.2%; in the 2026 IPL, the toss winner took 61% of matches. The crowd was a variable. But in women's cricket, that variable still does not get recorded in any spreadsheet. The crowd is visible; the column is not filled.

Now to the actual count. Three things I counted on separate days in the past month, each pointing the same way.

First: broadcast minutes versus reporting minutes. The Women's Premier League launched in 2026, and after the 2026 home World Cup win the domestic media was full of "new era" language. But when I compared the average word count of women's match reports at some major outlets against their men's Ranji reports, the ratio was the same old ratio. Scores and results appeared; the lines on which bowler built pressure in which over, which fielder dropped a catch, which captain changed which field, were consistently missing from the women's games. A new tournament brings headlines, not depth of reporting. Depth comes from filling columns, not from celebration.

Second: scorecard depth. I placed side by side, from the same day, a men's Vijay Hazare card and a women's senior one-day card. The men's card carried economy, maidens, wides, no-balls, plus a separate fielding and catch-stumping breakdown. The women's card carried the same detail half-finished, sometimes wholly blank. This was not one outlet's negligence; the pattern repeated. When the fielding column stays empty, the story stays empty — and the player who saved a match with her runs saved is remembered next time without the numbers.

Third: regional-language broadcast. Bengali, Tamil, Marathi and Telugu commentary feeds today still cover matches where the English feed does not go. Women's domestic games fall in this category. But when I found that no standard transcript or data record of these feeds is archived anywhere, it became clear that coverage that never reaches the English desk never enters history. This is not a reporting gap; it is a record gap. And a record gap costs not just numbers but careers.

This is where I must stay away from my oldest danger. Spreadsheets tempt me. Fill all 41 columns, reach 100% completeness, and it feels like the job is done. It is not. The schema must also state what it cannot see. My schema does not record a bowler's sore shoulder. It does not record a rain-soaked outfield. It does not count the mother in the stands with her child, whose presence no column carries. In cricket's language — fielding, weather, crowd, body pain: these four are my data's blind corners, and I should write them as findings, not as excuses.

Here the audit turns into argument. The three counts above are correlations, not causes. It is easy to assume everything improved after the WPL — a new tournament, sponsors, television, therefore reporting. But between correlation and cause stands the column that is filled by editorial people, not by production. A TV camera at the ground and a permanent women's cricket reporter on the desk are two different things. Broadcast rose after 2026, but how much did permanent bylines rise? In my count, bylines lagged well behind broadcast. That does not mean the WPL gave nothing; it means a tournament does not bring coverage by itself, someone has to open a column and fill it.

The second counter-intuitive point is that the home World Cup win proved to be an injection, not a drip. In the week of the win, headlines ran several times the annual average, and then the old count returned. This is not an India-specific thing; it is the economics of the tournament cycle. So the next question is not "are we covering women's cricket?" It is: "does our scorecard carry the columns that stay filled after the win?"

I should also state clearly that this essay is not a verdict on Indian cricket culture. I have been in Kolkata for years, but I cannot explain its desk-reporting tradition from the outside; Indian data journalists and desk reporters did this work before my columns existed, and the credit is theirs. My scope is only the dataset I can reopen. That dataset says this much, and no more.

Which is why one outside analogue is needed, and only one. In 2026, Croatia's 4% taught me that a model can be wrong even with every column filled — because it cannot see what is not in its definition. The same happens with women's cricket reporting: the columns look filled, but the most important thing — who played, who watched, who wrote, and who kept it in history — never enters any column. The Croatia problem began where the broadcast data ended. Our women's cricket reporting problem also begins where the ground broadcast ends and the desk's accounting should have begun — and that accounting has not begun.

So next time you read a women's match report, don't look at the score. Look at which columns are empty. Is fielding mentioned? Is the byline a permanent reporter or a bureau snippet? Is attendance written down, or is that cell left blank the way I left it in the 2026 Derby semifinal? The day we start filling those empty cells, reporting will not change — the count of reporting will change. And only when the count changes does a player's career become complete.