Delhi's Ranji Ledger Stays Blank: Dahiya's Diagnosis Is Accountability, Not Skill

For five weeks now my notebook has carried a column for Group C, and the number written beside Delhi has not moved once. Seven. In the three rows above it: Maharashtra on nineteen, Bengal on eighteen, Gujarat on sixteen. After every round I open the scorecard, update the table, and the Delhi line sits there unchanged. A draw against Services, three points from the first-innings lead, seven in total, fifth place. Not a single win this season.

The points table does not lie. It does not explain either. So when I read head coach Vijay Dahiya's assessment, it felt as if the real scorecard was filed somewhere else — in the two catches dropped at Kalyani, in the Gujarat match that slipped out of the hand, and in the answers owed by men who have been in the Delhi set-up for years.

At Kalyani, Delhi put down two catches. Both times the beneficiary was the same batsman who went on to score a century. Catches appeal to me because they are the most honest metric in the game — there is no room for talent in them, only the timing of hand and foot. A single match can lie; a season rarely does.

I watch Ranji from Bangalore, which puts me in an awkward position. The city I am typing this in treats its Ranji side with a seriousness that borders on pilgrimage, and the city I am writing about is one whose ground I have never seen up close. Everything below should be read with that guilt attached: I can see the numbers, but I cannot see the evening when twenty overs pass without a wicket.

Dahiya's complaint has three layers, and each can be measured differently.

The first layer is technical — control of sessions. The real currency of multi-day cricket is not points but the session. A day has three; a team wins by claiming three of four across a match. Dahiya says Delhi are not dictating sessions. My notebook has no column for that, because session-level data in Indian domestic cricket is not publicly available. This is where the coach's experience runs ahead of the data, and here I have to trust him — while conceding the claim cannot be audited.

The second layer is execution, and that is fully measurable. Against Gujarat, Delhi were in a commanding position and failed to close it out. Catches went down. In Dahiya's language these are the small windows that decide multi-day matches. His case is strongest here, because a dropped catch is a currency that cannot be rewritten. Once it is down, it is down.

The third layer is cultural, and this is where the argument begins. Dahiya says players who have been in the Delhi set-up for years are not taking accountability. Blaming pre-season shortcomings on others is not acceptable to him. His logic is simple — the system extended faith and resources; what has been returned in exchange? That is not a technical complaint. It is a complaint about professional ethics.

And then comes the Ayush Badoni case, which turns the whole story personal.

Badoni's numbers are clean: 559 runs, second-highest scorer in the competition, double centuries against Gujarat and Jharkhand. That is the single largest batting positive in the team's season. And about this exact player the coach says publicly that he is selling himself cheaply, that he must spend more time at the crease, that he must respect bowlers who string together maiden overs, that his ego is standing in his way.

Read that as a contradiction and you are filing run volume and conversion in the same ledger. I have looked at the shape of Badoni's season in my notebook — 559 runs do not arrive in even instalments. If two double hundreds dominate the bulk of the season, there is a gap in the rest that the coach is calling selling himself cheaply. In the language of data, call it variance. In the coach's language, call it temperament. They are two names for the same ailment.

A public statement about the captain is a management gamble — and one that is played very rarely in Indian domestic cricket. Dahiya has offered Ayush a challenge rather than a compliment. But the challenge carries a price. Naming a captain's ego in front of the media is something only a coach who believes the relationship can survive it would do. It is easy to feel that Badoni should absorb this deeply; it is equally easy to feel that it is an enormous weight on his shoulders. The way he has carried the side for a year and a half will be put on trial once more.

In eleven years of this work I have seen one pattern repeat: when a captain is performing and is still publicly criticised, the numbers of his next three innings tell you whether the criticism landed on the bat or on the head. There is no fixed test, but the track record has taught me that the first response in such situations is usually haste — and haste is exactly what the coach was afraid of.

This is where I begin to doubt my own story.

Dahiya's diagnosis is clean, and clean diagnoses are always attractive. The media likes what I like — one cause, one character, one quote. But a twelve-point gap (nineteen against seven) does not begin with ego. That gap is built from three things: how often Delhi's bowling attack broke an opposition innings this season, the injury list that no institution publishes, and the availability of senior players. A team discloses injury or unavailability only when the disclosure serves its image; otherwise it is a file that never reaches the outdoor press conference.

And a larger point. Accountability is being spoken about by the coach — not by the selection committee, not by the association. When a team sits on seven points, the questions should travel past the captain's ego and stop at team selection, support staff and pre-season planning. The same old error is being made here that every report makes — putting a character in the dock instead of a process. One player's temperament does not lose a season; teams do.

I would still not dismiss Dahiya's core point, because there is something in it that never shows up in data: professional accountability. Ranji teams routinely draw matches they should win, and the most solid reason is that nobody took on the job of batting out thirty overs with the eighth or ninth wicket. Responsibility of that kind is not summoned; it is habituated, and habit forms only in a set-up where somebody asks. Dahiya is becoming the one who asks. Language is his biggest weapon in that job, and also his biggest risk.

Before the transfer fee there is a spreadsheet nobody wants to read. In Ranji, that spreadsheet is the points table, and Delhi's row is currently the least-read row in it.

For the next round I will add three columns to my notebook. One: Badoni's average balls faced per innings, not runs — because the coach's entire argument rests there. Two: the score at the third session of the match — whether Delhi are still protecting wickets at the end. Three: whether the senior batsmen can bat five hours in the first innings of a domestic game. If all three improve and the points still do not, the problem will not be Ayush Badoni's ego. And if they do not improve, Dahiya will have one line left to say — I told you so.

The truth is that my notebook cannot answer how much trust remains inside a dressing room. That is not a number; it is only a question. And only Delhi's next session will answer it.