Ranji Trophy: Inside Rajasthan's 'back-to-back draws' — two matches, four facts and one empty spreadsheet

In 2026, from the scorer's assistant chair at Feroz Shah Kotla, I logged 1,412 legal deliveries across four days — line, length, release point, every ball that reached slip. That notebook ran on one rule: if an event cannot be reconstructed, it is not a number.

A report on Rajasthan's Ranji campaign surfaced this week. I opened the notebook before I opened the spreadsheet. Four lines were there. Rajasthan have drawn their last two meetings with Uttarakhand. Rajasthan want to break away from that run. Rajasthan and Uttarakhand are the two sides in the fixture. And Rajasthan's selection calls are under scrutiny.

No score. No venue. No date. Not one named player.

That absence is the biggest fact in the story, and it is the one fact no headline has room for.

Context: the word 'draw' already tells you the format

T20 and ODI cricket does not produce draws. It produces ties and no-results. A draw is a multi-day outcome, which makes this near-certainly a first-class fixture, and in India that means the Ranji Trophy. Of the four facts available, that single word is the only format marker — everything else is inference, and I will label it as such.

Uttarakhand were granted first-class status from the 2026-17 season, which gives them under ten seasons of Ranji history. Rajasthan hold the 2026-11 and 2026-12 titles, so on paper they arrive as the senior side. The head-to-head sample between the two is small enough that calling it a 'record' would be generous.

There is a trap here. In a Ranji group stage, two sides normally meet once per season. The likeliest reading of 'back-to-back draws' is therefore two fixtures in two different seasons — two seasons, two pitches, two captains, two squads. To call those two results a 'sequence', you first have to erase everything that separates them.

Core: in Ranji, a draw is a design feature, not just an outcome

I followed the decimal point until it became a story, in the way I usually do. This report has no decimal point to follow. So the question has to change: why do Ranji matches actually end in draws?

Three mechanisms, and all three are about structure rather than cricket.

First, the points system. Ranji awards points for a first-innings lead, and the exact value has to be checked against the playing conditions of that particular season, but the principle is plain. When a side is 300 for 5 and a first-innings lead is worth points, the return on aggressive cricket falls. That is not a captain's cowardice. A Ranji draw is often the rules working as designed, not a team failing.

Second, weather. Rain, bad light and moisture are the most under-reported causes of draws in Indian domestic cricket. Writing 'selection under scrutiny' in a headline is easy. Writing 'rain took 40 overs out of day one' is equally true and considerably duller. Dull truths rarely travel.

Third, bowling penetration. Can this attack take 20 wickets? That is the real cricketing question, and the supplied information contains not a single bowling figure to test it with.

The fourth cause — the one that became the headline

Selection. Notice that this is the only one of the four that requires no data at all. It is also the author's opinion, not a press conference. No statement from the state selection panel or the BCCI appears anywhere in the report. Based on my years of watching and scoring domestic cricket, the phrase 'calls under scrutiny' is almost always one journalist's angle rather than the output of a formal review.

There is a second trap that every Ranji report should defuse. Rajasthan, the state team, and Rajasthan Royals, the IPL franchise, are separate legal entities. There is no auction in the Ranji Trophy, no RTM card, no trade window. A reader who imports auction logic into this fixture is playing chess on the wrong board. No franchise, broadcast-rights or capital-flow element exists in this story at all — it is entirely a competition-structure story.

Contrarian: maybe the scrutiny is fair, and I am the one who is wrong

Now the strongest case against my own argument. Suppose the question is legitimate. If Rajasthan took first-innings leads in consecutive matches and still could not find 20 wickets, that is precisely a selection question — does the pace attack have the edge to work on a fifth-day surface, can a spinner hold up for 35 overs, and is a draw against a young side like Uttarakhand anything to be satisfied with?

At Kotla in 2026 I watched Mayank Agarwal make 176. The scorecard records a commanding innings. My notebook records Delhi's seamers beating his outside edge 19 times. The card said one thing; the ball-by-ball log said another. The word 'draw' is the card. The story is the log, and the log is missing from this report.

Here is the other side of it. First-innings lead points can win qualification in a tight group. A side that banked points from a draw may have been strategically correct rather than inadequate. Reporting two draws as a 'sequence' then becomes the reporter's problem, not the team's.

Takeaway: the next XI, the next toss

I pre-register what I am watching, so I cannot build the explanation after the result. The team announcement is the first hard fact — the only event that converts 'scrutiny' into 'decision'. Second, the toss and the first hour of pitch behaviour. Third, that season's points regulations. I trust the heatmap after I have walked the touchline, and here there was no touchline to walk.

If a third draw arrives with the same attack on a similarly flat surface, the selection question is fair and provable. If rain intervenes, the entire debate goes in the bin. Both remain open, and I would rather leave them open.

Sixty-four matches fit in one spreadsheet, but the dressing room does not. Right now we do not even have the spreadsheet — only four lines. The question is whether the next report brings a fifth line, or reprints the same four in a different order.