Royal Challengers Bengaluru (RCB) realised early on Tuesday that this wasn’t going to be a contest they could treat like a standard T20 chase-or-attack script. With the usual pre-match talk about sticking to “our strengths” and ignoring the opponent, RCB instead opted for a plan aimed at disrupting Gujarat Titans (GT) in Qualifier 1 of IPL 2026.
Quick facts
- RCB approached Qualifier 1 with an aggressive, opposition-aware game plan to unsettle GT.
- Shubman Gill and B Sai Sudharsan had formed an opening partnership that topped 700+ runs this season.
- GT had been highly effective in the powerplay across the competition, but RCB challenged that pattern early.
- RCB brought Jason Holder into play by the fifth over after Gill had shifted to plan B.
- RCB’s impact-player approach and selection were described as conditions-based by Mo Bobat.
- RCB had previously lost momentum after a fast start in Ahmedabad, but this time Patidar’s acceleration changed the tempo.
To beat a side that has repeatedly hunted down totals with ease, RCB needed to take more chances than they would normally in a knockout situation. Gill showed the kind of calm that comes with experience, while Sudharsan batted with the assurance of a player who looks comfortable across formats, turning chases into something almost routine.
That’s why the stakes felt clear even before the ball was swung properly: Gill and Sudharsan had already piled up more than 700 runs as an opening duo this season, the most by any pair. RCB knew they couldn’t simply “compete”—they had to force the match to move into unfamiliar territory for GT.
Mo Bobat, RCB’s director of cricket, explained that the mindset was to generate pressure rather than merely absorb it. “We put ourselves under some healthy pressure and said, ‘Let’s see if we can take the game beyond them,’” Bobat said. He added that the aggression from the first delivery was rooted in respect for GT, especially the calibre of their top order, with RCB trying to push the tempo and direction of the match out of GT’s comfort zone.
Powerplay pressure and early disruption
The first real signal that RCB’s plan was working came as early as the fifth over. Gill had already moved towards plan B, and the bowling rhythm reflected how much RCB wanted to test GT’s early phase. Kagiso Rabada and Mohammed Siraj had been dominant through the powerplay in match after match, and GT had the best economy and the most wickets in that phase in the competition.
Even so, by four overs in, RCB had brought on Jason Holder. The move wasn’t just about personnel—it was about making GT adjust. RCB’s powerplay challenge asked GT to deviate from what they typically script for themselves when the innings begins.
There was also context from the venue. The previous two IPL 2026 matches in Dharamsala had ended comfortably in favour of the chasing team. GT, playing their first-ever game here, were hoping the pattern would continue. Bobat later noted that RCB would have chosen to field first had they won the toss, and the twist of losing it may have actually helped unlock the strategy they had shaped.
That decision pushed RCB into committing fully to the only route they believed could work—dragging GT away from their planned execution. Their team selection mirrored that idea. Instead of packing the XI to the point of flexibility until No. 8, RCB effectively travelled with one batter fewer, leaving room for the impact-player manoeuvre.
Romario Shepherd was eventually called in, but only after GT had already stumbled early by losing five wickets in the powerplay—the first time that kind of collapse had happened to them. RCB could have gone for another seamer, or even Suyash Sharma, if they wanted extra bowling cover, but the initial choice aligned with what they expected the wicket and match situation to demand.
Bobat described the approach as strongly tied to conditions. He said RCB had the advantage of having played at the venue previously, giving them a sense of what the pitch might do. He also acknowledged the difference in timing—this was an evening game, after a day match experience—before adding that they used the impact player differently from earlier fixtures. “It ended up being a decent luxury,” Bobat said, “because we didn’t use all our batters and could think more specifically about what we needed in the second innings.”
In other words, it wasn’t just a case of backing strengths. RCB had designed selection, match tempo, and bowling-batting intent with GT and the surface in mind, tailoring the contest rather than copying a generic template.
A blueprint from Eden Gardens
Recently, KKR had shown the rest of the competition a possible way to attack GT at Eden Gardens. Before that, most teams had treated GT cautiously—trying to survive Rabada and Siraj first, then hitting back later. KKR changed the pattern immediately: Finn Allen attacked the new ball, disrupted lengths before GT’s quicks could settle, and most importantly carried the pressure all the way to a century.
That century powered KKR to a formidable total of 247, taking the game beyond GT’s reach. In many ways, the defeat that followed—and now this one—highlighted the boundaries GT can hit when opponents refuse to play their early phase on GT’s terms.
RCB’s method found parallels in how GT’s batting was challenged. Virat Kohli, Venkatesh Iyer and Devdutt Padikkal attacked the lengths right away, similar to what Allen had done earlier in Kolkata. Rajat Patidar then completed the picture with a knock that shifted the match decisively.
RCB had already previewed parts of this approach when they met earlier in Ahmedabad. Kohli went after Rabada and struck five boundaries off him. Still, Tuesday’s execution felt even bolder. Rabada’s first three deliveries to Kohli in the second over beat him completely—there was movement, bounce and pace off the deck, and the early signs looked ominous.
Yet Kohli responded quickly, getting into rhythm within minutes. The same Rabada who had been suffocating batters in the powerplay for much of the season ended up conceding 39 in his first three overs. That was the most expensive he had been this season in the opening six overs. RCB’s powerplay impact stood out not only for the aggression, but for how they maintained tempo—many boundaries came from balls that weren’t necessarily bad deliveries.
There was also a clear learning curve from the Ahmedabad meeting. After a fast start there, RCB lost their way. This time, they had their captain to thank for a sharper recovery when the innings threatened to unravel after Holder dismissed Kohli and Padikkal in the same over. The early stage wasn’t smooth at all: at one point Patidar was 16 off 11 and he was dropped on 20.
But the shift after that was ferocious without looking like Patidar was swinging in anger. GT were left stunned. Then RCB accelerated hard, smashing 114 runs in the final six overs on the back of Patidar’s assault—he made 71 from his last 19 balls. Once that burst arrived, the flow of the match changed completely.
GT had never chased anything close to this in the past. They hadn’t scored more than 233 in a chase, and suddenly the target wasn’t one their top order could simply glide through with clinical execution.
Early wickets and a clear message
RCB understood early wickets would be decisive, and they acted accordingly. They took two early strikes: Sai Sudharsan was dismissed hit wicket, while Gill fell to Bhuvneshwar Kumar in a way that echoed Gill’s earlier dismissal against Trent Boult in Qualifier 2 last season. The pattern was familiar—Gill was looking to whip one across the line against the angle coming in—until the ball didn’t cooperate, and this time it ended with a bowled dismissal.
Gill’s long walk back and the frustrated tap on his helmet before he sat down summed up the night’s story. GT had been outsmarted and outplayed—RCB’s plan had not just put them under pressure, it had forced GT to react to a match that refused to follow their script.
