In 2025, Jasprit Bumrah found himself at the center of a debate about workload management. Former Indian pacer Balwinder Sandhu dismissed concerns about “overworking” as “bull,” arguing that Bumrah’s bowling load was spread across matches instead of coming from one long, taxing stint.
This conversation ramped up because the statistics being referenced told different stories. Sandhu’s claim of “150-something” overs across five matches or nine innings conflicted with a report from Hindustan Times, which showed Bumrah leading in Test pace workloads for 2024. Here’s the thing: focusing solely on overs misses the real picture—how the workload is distributed, handled, and understood.

The before: the “overworking” narrative that took hold
Before this debate, many in Indian cricket viewed a heavy workload for a frontline pacer as a significant concern.
This mindset gained traction with Bumrah, given that his role involves high-intensity bowling—short bursts or spells that require immense skill and physical effort. Yet, Sandhu’s main argument was straightforward: the “overworking” label doesn’t accurately reflect how Bumrah’s overs were distributed.
Sandhu illustrated his point by stating that Bumrah bowled “150-something” overs across five matches or nine innings, roughly translating to 16 overs per innings or 30 overs per match.
This suggests that the risk profile changes when overs are spread out, compared to being crammed into one long spell. If you keep claiming “more overs = more damage” without context, the myth sticks around because it seems logical.
The catalyst: workload numbers collide—Sandhu vs Hindustan Times
The turning point came when Sandhu’s argument about overs distribution clashed with the more traditional “total workload” perspective presented in a Hindustan Times report.
That report highlighted Bumrah bowling 410.4 overs in Test cricket in 2024, the highest for any pacer, along with 78 wickets—a combo that understandably raises workload concerns. During the same timeframe, Mitchell Starc was noted as a close pace peer with 362.3 overs, according to the same report.
The discussion wasn’t just about numbers. Sunil Gavaskar rejected claims that India mishandled Bumrah’s workload, insisting the team and Bumrah were making the best decisions for the side, and blaming management wasn’t warranted.
Meanwhile, Gautam Gambhir reportedly confirmed before India’s trip to England that Bumrah would skip two of the five Tests due to workload concerns, indicating that even the “system” recognized the need for workload management. So, which narrative holds: is it the myth of overwork, or the truth of monitored usage?
The after: what Bumrah and India’s voices actually said
Once the debate hit mainstream discussions, Bumrah provided a candid take on workload inquiries. He stated, “these questions are not my questions,” emphasizing that he strives to perform his best in every format while also being mindful of his body. This perspective shifts the focus from public blame to athlete-driven responsibility—acknowledging that workload is still a factor.
Additionally, Ryan ten Doeschate remarked that workload decisions were based on long-term fitness and well-being, not just personal preference, in a report by India Today. This aligns with how professional fast-bowling is managed: it’s more than just “rest vs play”; it’s about deciding when and how to push a pacer to peak performance while ensuring their body is safeguarded for future challenges.
Side-by-side: the two ways people measure “overwork”
| Measure | Source / voice | What it suggests |
|---|---|---|
| “150-something” overs across five matches / nine innings | Balwinder Sandhu | Distribution reduces concentration risk |
| 410.4 Test overs in 2024 + 78 wickets | Hindustan Times | Total workload was extremely high |
| Missing 2 of 5 Tests due to workload | Gautam Gambhir (reported confirmation) | Management actively shaped availability |
| “These questions are not my questions” | Jasprit Bumrah | He frames it as body-care plus performance |
You need both perspectives. Total overs show exposure, while distribution reveals strain patterns. Relying on just one creates shortcuts to myth. For more details, check out BBC Sport.
What’s next: how India’s pacer usage should be judged
Looking ahead, the smart move is to assess pacers using a combination of workload exposure and transparent decision-making—not just one headline figure.
India’s public voices, like Gavaskar’s defense, and the reported squad availability choices, such as Gambhir’s note on missing two Tests, indicate that management acknowledges workload realities. They’re actively addressing them. Bumrah’s response also suggests he prioritizes performance and body care over the ongoing workload discussions.
So, if you keep hearing “Bumrah is overworked, that’s it,” be mindful of how you interpret the data: if you focus only on overs, you’ll only worry; if you consider distribution and availability decisions, you’ll grasp why the system makes certain trade-offs.
Related Articles
FAQs
Jasprit Bumrah Myth: Is he “overworked” by design?
The “overworked” label faced a direct challenge from Balwinder Sandhu, who claimed Bumrah’s overs were evenly spread across five matches or nine innings instead of being clustered. At the same time, Hindustan Times pointed out 410.4 overs in Test cricket in 2024, indicating the workload was undeniably significant.
Evaluating Jasprit DRS: What’s the better way to judge workload?
Rather than viewing any large number as evidence of overwork, this debate highlights two approaches: distribution (Sandhu’s innings/match framing) and total exposure (Hindustan Times’ overs total). And when squad decisions come into play—like the reported missed two Tests—it shows management is actively responding to workload.
Jasprit Bumrah: Five quotes/anchors that define the debate
Key lines from the discussion include: Sandhu calling the concept “bull,” Hindustan Times’ workload snapshot of




