Ranji Trophy: Delhi Take First-Innings Lead Against Services as Doseja's 78 Anchors Hosts

The first reply in my Hyderabad WhatsApp group when I posted the Delhi-Services score was telling: 'Bro, is this 299/6 at stumps or what?' I liked the question. Anyone who reads a scorecard knows that 299/6 is not just about six wickets falling—it means a team has already taken the first-innings lead, and the match has moved into the 'how do we win from here' category. Services had made 266 in their first innings. Delhi's 299/6 at stumps means the hosts sit on a 33-run lead at the end of Day 2, and under the rules they have already banked the three points for the first-innings lead. But what that sentence hides is that Delhi still have four wickets in hand, and the question is how long they will bat.

I have been noting over the last few seasons the Ranji Trophy innings where teams reach around 300 in the first innings but do not declare, and the match drifts toward a draw. Delhi's score falls into that category. If Mayank Mathur fails to build on his 80* tomorrow morning and Delhi are bowled out around 340, Services will not have enough time to make 300-plus in their second innings. On the other hand, if Delhi go to 380-400 and Services are set a target of 310 in 60 overs, the game opens up. That is where the real skill of Ranji Trophy lies—the timing of the declaration.

But the centre of this story is Ayush Doseja. The 26-year-old played an innings of 78, the number that refreshed memories of last season's 949 runs. I have notes from some of Doseja's matches last season—innings where he would get out for 30-40 and commentators would say 'shots look good, just needs to make a big score.' The start of this season followed the same pattern. He made 45 in the first innings against Bengal, where the opposition attack included Mohammed Shami, Mukesh Kumar and Akash Deep. Four innings passed without a half-century, but Doseja himself says he was 'batting well and getting unlucky dismissals.' That is where I think we need to look beyond the scorecard.

There is another aspect to this Doseja innings that does not make it into any match report—the NCA in Bengaluru, now called the Centre of Excellence. He underwent three months of red-ball training there under the watch of coaches like Wasim Jaffer and Hrishikesh Kanitkar. This is the place where the foundation for long Ranji innings is laid. A coach friend who has worked at the academy tells me the biggest emphasis there is on 'converting a start into a big score.' Doseja's 78 is a product of that training—it is not some magical 'return to form,' but an innings where he played his shots the same way but did not get out this time.

Now comes the part that got the least space in this match report—the Services bowling. Arjun Sharma took 2 for 48, decent figures for a left-arm spinner, but in Ranji Trophy, two wickets for 48 means he bowled a lot of overs and Delhi's batsmen learned to play him. Jayant Goyat took 2 for 51, which would have been important as early breakthroughs. But the biggest moment was Pulkit Narang dropping Doseja on 52. Had that catch been taken, Delhi would have gone from 135/5 to 135/6 and the entire first-innings lead arithmetic would have changed. This is the moment Services' coach will replay all night.

Let me be clear about one thing here. This whole report revolves around a player who made 78, but there is another name on the scorecard—Mayank Mathur, unbeaten on 80*. It is Mathur's innings that, along with Doseja, added 144 runs for the sixth wicket. If Doseja was out for 78 and the team was 279/6, then Mathur and the seventh-wicket batsman must have added 20 more runs. But the name of that seventh-wicket batsman is nowhere. This is an old problem with Ranji Trophy coverage—we write the star's story and forget the partner who helped him stay in.

There was an interesting debate on this match in my Hyderabad fan desk. Someone wrote in the group—'Delhi should declare tomorrow, otherwise the draw probability increases.' Another countered—'But Services made 266, they could make 400 in the second innings.' Both arguments had logic, but neither was talking about how the pitch is behaving. That is the peculiarity of Ranji Trophy—we debate numbers, but the pitch's story often goes untold. Delhi reaching 299/6 has at least proved that the pitch is still fine for batting. But Services' spinners' figures suggest the ball is turning—Arjun Sharma's 48 runs would include several overs where batsmen had to struggle.

The biggest tactical question of this match is—when will Delhi declare? If Mathur adds another 20-25 runs tomorrow morning and Delhi reach 340-350, they will have 80-90 overs to bowl Services out. But if they go past 400, that time shrinks to 60 overs and Services will have every chance to fight for a draw. In Ranji Trophy, this is the moment when a captain has to show faith in his bowling. Delhi have all-rounders like Badoni, but is their bowling enough to bowl Services out twice? This question was not asked anywhere in this match report.

One more thing that bothered me—Doseja is 26. That number means nothing on its own, but when you put it alongside the Indian cricket selection calendar, it becomes important. Scoring 949 runs in Ranji Trophy at 26 and now, after a slow start to this season, playing an innings of 78—this is the time when selectors keep an eye on young players. If Doseja scores 800-900 runs this season, he will be considered ready for the next step beyond domestic cricket. But for that, he needs to convert this 78 into bigger scores—that work remains.

I am also a little uncomfortable with the opening line of this match report. 'Doseja regains touch'—that headline is itself a claim. But look at his last four innings and he was getting out for 20-30, and he himself says 'he was batting well, just unlucky.' In that case, both 'losing touch' and 'regaining touch' are the wrong words. The right word is 'conversion.' He was playing the shots but not converting them into big innings. Judging a player's form on the basis of four innings is statistically wrong—that is noise, not signal. The real signal will come when he scores 70+ in three or four consecutive matches. One innings of 78 is a step in that direction, but it is not enough to announce a 'comeback.'

As for Services, they need a clear plan tomorrow morning. If they restrict Delhi to under 350, they will have 60-70 overs left in the second innings and can save the match. Arjun Sharma and Jayant Goyat will need early success with the new ball. Mathur is unbeaten on 80* and his wicket is the most important. If Services can get him out in the first hour of the morning, Delhi's entire innings could collapse around 320. This is the moment when Services' coach will hug the fielder who dropped the catch and say—'Come on, there is still a chance.'

The biggest lesson from this match is that no score is safe in Ranji Trophy. 299/6 looks good, but if Delhi are bowled out for 350 tomorrow morning and Services make 300 in their second innings, Delhi will face a target of 250 and the game will change completely. That is the beauty of domestic cricket—no team is weak on paper here.

The debate is still going on in my Hyderabad fan desk WhatsApp group. Someone has written—'Doseja should get a chance in Team India.' I replied—'Let him score 800 runs this season first.' That is my habit—I do not trust the numbers behind the scorecard until they form a pattern. 78 is a good innings, even a great one, but it does not decide the direction of a player's career. What decides the direction is the next morning—when Mathur extends his innings, Services attack with the new ball, and Delhi's captain makes the declaration call. The future of the entire match is hidden in that one decision.