Seven Wickets for 22 Runs in the Irani Cup: J&K's Collapse and India's Invisible Red-Ball Pipeline

The scoreboard read 89/3. In Test-format cricket that is not a number of danger: three wickets down, but a settled pair at the crease, runs coming at a steady pace, the innings moving along. Then it happened — the collapse. The last seven wickets fell for just 22 runs. Jammu & Kashmir's innings ended at 111. Two names are stitched into this Irani Cup result: Mukesh Kumar and Akash Deep, both pace bowlers, both familiar faces in the structure of India's red-ball setup. Rest of India won the match, but beneath the scoreline lies a story that is not merely about a defeat.

I keep a field notebook for the moments the scoreboard forgets. In that notebook the pages on collapses are many. The pattern is almost always the same: one wicket falls, the next arrives within two overs, the third follows immediately after. Seven wickets for 22 runs is not just a number — it is a description of a broken rhythm. And who breaks a rhythm? A new-ball pacer, or a seamer getting new-ball behaviour from an older ball. Both named men here are pace bowlers — that in itself is a signal.

To understand what the Irani Cup really means, you must first understand its structure. This is no franchise tournament, no arena of profit and loss. It is an annual Indian domestic first-class fixture in which the Ranji Trophy champion faces a composite representative side — Rest of India. The name itself tells you: this is not one state's team but a selected XI drawn from across the country. The Irani Cup is, in effect, a clash between two different tiers. On one side a Ranji-winning side; on the other, a near national-standard attack.

For Jammu & Kashmir, simply reaching this stage is a statement. To play the Irani Cup you must have won the Ranji Trophy the previous season — meaning J&K have come through a memorable red-ball campaign. So the seven-for-22 collapse sits somewhat against their season's narrative. It is a bad session, perhaps a single bad session — but when one session turns a match, it becomes a question in itself.

In this piece I look at three layers. First, the anatomy of the collapse — how seven wickets for 22 runs becomes possible, and why it is almost always a pace-driven cluster. Second, the pipeline question — when international-standard seamers like Mukesh Kumar and Akash Deep stand before domestic batting, how fair is that gap, and what does it signal in a match like the Irani Cup. Third, and most importantly, where the real risk of such a performance lies: not in the glory, but in the overs piling onto fast bowlers' shoulders.

The anatomy of the collapse

Let me break the number down. 89/3 to 111 all out. Meaning the last seven wickets fell for 22 runs. In first-class cricket this is unusual, though not unprecedented. It carries a clear signature — a sequential failure of middle and lower order, where a new batsman never gets time to settle. In red-ball cricket that settling time is the most precious commodity. When a new batsman arrives, the pacer can bowl a targeted spell at him — either a direct examination on a good length, or a trap by changing trajectory and moving off the line. In the middle of a collapse the batsman cannot handle both pressures at once, and that is exactly where one wicket brings two.

I have written in my field notebook: when seven wickets fall for 22 runs, roughly 80 percent of the time the damage comes from two ends. One end sustains the attack, while the other lays a trap with bounce, yorker or seam movement. Mukesh Kumar and Akash Deep are both known for seam movement and stump-to-stump consistency. So their joint naming as the 'trigger' of the collapse is no coincidence. It is two faces of a single pace spell.

But a caution is essential here, and I state it plainly. The individual bowling figures — who took how many, what the economy was, how long the spell lasted — are not in my hands. All that is known is that these two pacers caused the collapse. So in the bowling analysis I am as limited as I am number-driven. Filling in what is not known with imagination is not my practice.

The gap the Irani Cup does not hide

Here lies the structural truth of the Irani Cup. Rest of India means a patched-together XI of the country's best. Jammu & Kashmir means one state's finest batting line-up. This was never a contest of equals — it is a selected attack against a season-winning side. So when an international-standard seamer gets the new ball against domestic batsmen, the gap that opens is not merely J&K's weakness; it is the expected result of the structure itself.

I have watched this pipeline for a long time. A pattern recurs in domestic red-ball cricket: the side that gets an international-standard new-ball pair takes control of the match in the very first session. The side that does not, produces innings exactly like this — calm up to a point, then suddenly broken. 89/3 to 111 — I have seen this archetype many times.

Watching this pattern from Dhaka, one thing must be kept in mind. In South Asian domestic cricket the gap between batting and bowling standards often comes from off-field causes — training facilities, fitness support, the absence of pace-bowling coaches, and the lack of dedicated preparation time for the red ball. However hard a state side works all season, an invisible ceiling stands before it when it faces a selected national-standard pace attack. J&K could not break it in this match, but that does not diminish their season.

Mukesh and Akash: an incomplete picture beside the glory

Two pacers named together means two possibilities. Either they shared a new-ball spell, or they held the pressure one after another through the middle overs. Either way, being jointly called the 'trigger' means they built a rhythm together — a rhythm that, once set, is nearly impossible for batting to break.

One thing must be remembered here, and it is what makes a match like the Irani Cup significant. This match is effectively a selection stage. In the fight for a place in India's red-ball pyramid, domestic performance knocks directly on the door. A good spell in the Irani Cup means a line in the selectors' notebook. So the value of this performance is not confined to winning this match — it gestures toward the doors of the season ahead.

But here is my professional caution. From the two facts of a single-innings collapse and two pacers having a good day, reaching a conclusion is dangerous. As the only woman in the press box, I learned to dig quietly, not loudly. That is, to look not at what is seen but at what is not. Here what is not seen: the bowling figures, the nature of the pitch, the full state of the match. So the two pacers' performance cannot be marked as 'proof of excellence'. What can be said is that they got an opportunity and used it.

The real risk: overs piling on the shoulder

When writing about fast bowlers' performances, almost everyone forgets one dimension. Fast bowlers never just take wickets — they simultaneously spend their body's future. Every long spell means growing debt in shoulder, back and ankle. In Indian pace-bowling management discussions these two names recur — and there is a reason. Both are workload-sensitive quicks whose spells the board watches with particular care.

Here a match like the Irani Cup takes on a dual role. On one hand it is a selection opportunity; on the other, a workload burden. If the two had to bowl long spells to force this collapse, those overs add to an already packed calendar. Domestic red ball, then national duty, then franchise cricket again — in this cycle the fast bowler's shoulder bears the heaviest load.

In my notebook there is a separate page for fast bowlers, where each match I record not only wickets but the number of spells. Because a match result is fleeting, but a spell's effect shows up six months later as a hamstring or calf injury. The return timeline that is often announced — 'week to week' — frequently means the injury is far from healed. So in matches like this I keep the workload calculation beside the bowler's glory.

The counter-intuitive angle: a collapse is not weakness

Now to the place where the conventional reading is questioned. Seeing a seven-for-22 collapse, the natural reaction is — 'weak batting line-up'. But I am not ready to reach that conclusion. Because a single innings can never testify to a whole team's batting standard.

First, the collapse is the event of one session or one spell. Second, the opponent was a selected attack whose standard is far above the domestic average. Third, in a Test-format innings, seven wickets for 22 runs is a mixture of two things — batsmen's errors on one side, and the bowlers' precise planning on the other. Blaming only the first means doing injustice to the second.

The reverse is equally true. Two pacers' good spell does not mean they are established at international level. There is a big gap between success in domestic conditions for a selected side and success under national-team pressure. Crossing that gap requires consistency, the ability to handle varied conditions, and the durability of fitness. One match does not close that gap.

My biggest fear here is analytical. After a big performance in domestic cricket, a wave of excitement often follows — 'this boy is ready'. My notebook's rule does not accept that. I wait. One collapse, one spell, one innings — these cannot write anyone's future.

What lies beyond the domestic structure

The Irani Cup is an event outside the commercial franchise world. There is no auction here, no team sale, no big broadcast market. Its evaluation is therefore cricketing, not economic. Its entire importance hides in the talent pipeline — the place where domestic performance slowly becomes national selection news.

In this pipeline a good match by two pacers is a small but real signal. India's red-ball future is built in exactly this kind of match — where a seamer with the new ball proves he can trigger a collapse under pressure. Selectors read this signal, not the fantasy world.

But a question remains. The domestic red-ball window shrinks every season — the IPL and the busy white-ball calendar leave little time for first-class cricket. If this compression continues, the real cause behind the collapse will no longer be only batsmen's errors — it will be a lack of adequate preparation.

What I will keep watching

My field notebook always holds some 'tracking signals' I watch in the following matches. Here too. First, the detailed figures of these two pacers' spells. If either has four or more wickets, the weight of the performance grows. Second, J&K's subsequent red-ball innings — if they keep getting bowled out below 150, it points to a structural problem. Third, whether this performance affects the next national red-ball squad announcement. Fourth, the pacers' workload reports — because the most real risk in this story is not in the wickets column but in the physio's column.

One thing must be remembered here. The longer I watch this game, the more I learn — a collapse never comes alone. Behind it lie a plan, a condition, a structural gap. And a win is never the fruit of a single heroism — behind it lies a whole system built over a season's labour.

Final word

89/3 to 111 — the scoreboard will forever remember this change, but the scoreboard does not give its explanation. The explanation comes from the ground, the air, the seam of the new ball, and the doubt that gathers in a batsman's eye mid-collapse. For Jammu & Kashmir this match is a lesson; for Rest of India a routine task. But for us — those who dig into domestic cricket — it is a question. The question: in India's red-ball pipeline, what are we actually building? A selected side of national-standard pacers who will demolish state teams every time — or a system where those state batsmen also get the preparation to handle an international-standard new ball? The answer will come in the next few seasons, not in the scoreboard's column, but inside the pipeline.