Royal Challengers Bengaluru finally brought cheer to their fans at the Chinnaswamy, notching up a much-needed win against Rajasthan Royals. While several factors aligned for RCB on the night, one subtle but crucial influence has gone slightly under the radar — the Decision Review System (DRS). And standing tall behind those sharp, successful reviews has been wicketkeeper Jitesh Sharma.
Jitesh has shown remarkable clarity and conviction, often urging captain Rajat Patidar to take reviews — ones that have turned the tide in RCB’s favour. In fact, he’s done it more than once, and his accuracy has become a vital asset to the team.
Take the match at the Wankhede against Mumbai Indians. Josh Hazlewood bowled a classic in-between length delivery to Ryan Rickelton. It wasn’t too full, nor too short, and just tailed away a fraction after pitching on leg stump. Rickelton, looking for a swipe across the line, misjudged the length and was struck around the knee roll. Rajat Patidar hesitated, unsure whether to challenge the umpire’s not-out decision. It was Jitesh who stepped in, backing the review despite Hazlewood himself being unsure if it had pitched outside leg. Jitesh was right. The ball had indeed pitched on leg, nipping away just enough to hit the stumps — a match-shaping moment.
In the Rajasthan Royals clash, the stakes were even higher. RR needed 18 off 12 balls. Dhruv Jurel, on 47 off 32, was in ominous touch. Hazlewood came on for the 19th and delivered a wide yorker in the third ball. Jurel missed the attempted squeeze and the ball snuck under the bat. Jitesh appealed instantly, but Hazlewood didn’t seem convinced. Once again, it was Jitesh who insisted on the review. UltraEdge confirmed a faint bottom edge as Jurel backed away and tried to open the off-side. The spike on UltraEdge brought the big breakthrough and arguably, the moment that swung the match RCB’s way.
To understand the dynamics of DRS within a team, I reached out to former India wicketkeeper Deep Dasgupta.
“There are three important people when it comes to LBWs,” Deep explained. “The bowler is critical because he judges the point of impact. The keeper is often blinded in that situation. Then comes the point or square leg fielder, who’s key to assessing the height. But for caught-behind decisions, the ‘keeper is almost always the best judge.”
But what makes some keepers excel in this area while others struggle?
“Some just have a better judgement of where the ball’s going,” Deep said. “Then there’s confidence — it’s a big call after all. A lot depends on how forthcoming the keeper is, his relationship with the captain, and even his place in the team. If the keeper sees himself as an integral part of the team, he’ll back himself to speak up.”
Commenting on the Jurel dismissal, Deep broke it down into three layers: “There’s the technical bit — who judges what; the non-technical — which includes the keeper’s positioning and confidence; and the tactical. The Jurel review was a brilliant example of all three coming together. Tactically, RCB had two reviews left and 9 balls to go in the innings. Jurel was looking dangerous and could’ve taken RR across the line. So, they took a calculated chance — a smart, easier choice given the context.”
Then what fuels Jitesh’s unwavering confidence and why Rajat, a relatively new captain, trusts him so implicitly?
“Jitesh and Rajat go way back,” he revealed. “Same coach, same batch. They’ve grown up together. They also spend a lot of time together off the field, so there’s a deep sense of trust. That’s why you see Jitesh being vocal and Rajat backing him without hesitation.”
“For captains who field in the deep, like Rajat does, it’s critical to have a wicketkeeper they can rely on for those tight calls. And Jitesh has been playing that role to perfection,” Deep signed off.
Jitesh Sharma might not grab the headlines, but in a tournament often defined by fine margins, his sharp judgement and confident calls have made all the difference for RCB — proving once again that the keeper’s role extends far beyond gloves and catches.