The art of declaration is a risky business in a Test match. It requires a blend of ballsy audacity and sharp timing and calculation. It seems very simple during the game, but it comes with its challenges. If the toss goes in the right direction and one makes a big total on the board, it becomes even more difficult to make that statement.
In Test cricket, declaring early or late carries its own risks, and there have been plenty of times when the Indian team management has played it safe and paid a heavy price. And it seems like we are going to witness it again now, with the young captain Shubman Gill being in a dilemma at Galle after his team managed to score 460-9 for 116 overs on Day 2. Whether they win or not in Sri Lanka remains to be seen as the same mistakes of the past haunt Team India again and again.
Here are three prominent instances where caution overrode killer instinct, and late declarations backfired on Team India
1. The Kanpur Stalemate: India vs New Zealand (1st Test, 2021)
In Rahul Dravid's first Test as India's head coach, there was never any chance that the home team would have batted second. Fresh from Shreyas Iyer's debut century, the hosts scored a healthy 345 in the first innings, securing a 49-run advantage over the Blackcaps.
With overcast skies and the pitch condition deteriorating by the day, the sensible decision for India was to make a strong declaration on the fourth day. However, they made the baffling decision to prolong the second innings. A torturous 67-run stand between Wriddhiman Saha and Axar Patel consumed more than 20 overs, and the declaration was made late in the day. India gave New Zealand a target of 284 to chase in 90 overs.
As expected, the time wasted by the home team came right back to haunt them. On the fifth and final day, New Zealand's Rachin Ravindra and Ajaz Patel batted through the evening, taking advantage of the worsening light. As the sky turned dark and the shadows grew longer, the Kiwis made a stand of 165 for the ninth wicket, salvaging a draw.
2. The Milestone Trap: India vs England (2nd Test, 2008)
Fresh from a thrilling run chase in Chennai, India arrived in Mohali for the second Test with a 1-0 series lead and the opportunity to complete a clean sweep. With a commanding first innings lead of 151 points, they were well poised to set England a daunting target and allow their bowlers to run riot.
What happened on day five was unbelievable. Having already clinched the match with a lead of nearly 300, India continued to bat through the afternoon session and evening, just to add on to the lead and make it more than 400.
MS Dhoni was quick to point out that they held back the declaration to let opener Gambhir (97) and his partner Yuvraj Singh (86) reach their respective centuries.
Little did he know, even as the two batters were nearing their tons, they would eventually fall short of the milestone. Thus, when England was set a target of 403, no time remained for either to make any meaningful attempt at victory. A match that was poised to end in emphatic wins for either team, with India batting first and having such a commanding lead, degenerated into a lowly draw.
Also read: WCL 2026: AB de Villiers, Yuvraj Singh, Warner and Bravo Set to Return in Star-Studded Season
3. Running out of Daylight: India vs Pakistan (3rd Test, 2007)
Having taken a 1-0 lead in the third Test series between India and Pakistan at Bengaluru, India set a massive target for Pakistan, scoring 626 and posting a lead of 89 by day four, which they increased to 240 eventually.
Instead of accelerating as they began day five, India played cautious shots, allowing over 30 overs to be batted on the last day. As a result, the target was pushed to 375, well beyond the reach of Pakistan.
When India opened up later, there was sufficient left in the pitch for Kumble to grab a five-wicket haul as Pakistan was all out seven down in only 36 overs. However, India turned out to be three wickets short of victory as bad light cut the game short with Pakistan at 212-7.