Jaiswal's Gloves: What the Training Ground Says Three Days Before the Wankhede Opener, and What the Match Report Never Will

On the practice nets beside the Wankhede Stadium, as the evening light slants low, two sounds carry furthest: the flat crack of ball on willow, and the muffled thud of a ball sinking into keeping gloves. On Tuesday evening the second sound was louder than the first. Three days before Mumbai's Ranji Trophy opener, on Mumbai's own ground, India's Test opener Yashasvi Jaiswal stood in one corner of the nets keeping to the spinners. Nobody forced him. Nobody announced it on a microphone. Just an ordinary practice session in which a batter spent an extra half hour with gloves on.

I learned the tempo before I learned the tactics. And tempo tells you which session is natural and which is manufactured. That half hour inside the nets was not natural. Because in that session Jaiswal never once returned to his batting stance — he only crouched low, spread his fingers, and kept glancing at the little finger of his left hand. The part of the body that is almost invisible to an opener was, that evening, the centre of his attention.

The training ground is a lie detector. Who is lying about being fit, who is quietly hiding an injury, who is genuinely ready for a match — the pace of the nets, the time spent putting on gloves, the posture at the boundary rope, all of it builds an accounting that lives in a reporter's notebook, not on the scoreboard. That quiet half hour on Tuesday was a signal to me. The signal is not that Jaiswal wants to be a keeper. The signal is that he is doing sums about his own future — and the sums are not about batting.

The outside story reads differently. A news report claims a Mumbai legend warned Jaiswal to stop sweating over wicket-keeping and focus on batting. The report does not name that legend. His remark was compressed into a single word in the headline — “It's a joke.” The same report carries a confession from Mumbai captain Siddhesh Lad that almost nobody read: “That is what I feel, but I haven't got any clarity on that.”

The headline is loud; the source is quiet. Cricket journalism swings between the two. So my job here is to reduce it to one simple question — three days before a Ranji opener, what do we actually know, and what do we not.

Mumbai begin this season at home, at the Wankhede. The Ranji Trophy is India's premier domestic first-class competition, and it is the pathway to the Test team. Three days before a match, a squad is not in match condition — it is in preparation condition. And every decision in a preparation phase is half-finished, half-experimental. Jaiswal's keeping belongs to that preparation, not to a match result.

This is where the layering of formats matters, because that is where the real analysis hides. The value of wicket-keeping is not the same in every format — in Tests and ODIs it is a scarce, hard-to-replace skill; in T20 it is far more fungible. For a player established in the Test top order, keeping sometimes means “an extra skill” and sometimes means “a second identity.” Two different meanings, and journalism routinely conflates them.

That Jaiswal is an established Test opener is not speculation. On his Test debut in Dominica in July 2026 against West Indies he scored 171 — among the highest scores by an Indian batter on debut. Then, in the home series against England, he made 209 in Visakhapatnam and an unbeaten 214 in Rajkot, finishing with 712 runs and the Player of the Series award. These are public facts, and they are exactly what puts the report's key sentence under pressure: that he “has yet to seal his spot across formats.”

Two different things are being merged here. One is a batting decline; the other is selection uncertainty. The report is talking about the second, but its headline is sounding the first. Jaiswal's problem is not runs; nobody is questioning the runs. The problem is selection continuity across formats. Fail to grasp that distinction and the whole story runs in the wrong direction.

In football I have watched this error repeat. Possession percentage is the most deceptive statistic in football — plenty of teams hold sixty per cent of the ball, passing sideways, and create almost nothing. Cricket has the same trap. If someone counts the number of keeping sessions or the minutes with gloves on and concludes that a batter is “losing focus,” he has not measured the batter's real work. He has only grabbed a visible number.

In 2026, at the Delhi Dynamos training ground, I was the only woman in the press area. After a 2-2 draw with Mumbai City, I dug out the fact that midfielder Marcos Tébar had completed 87 of 94 passes — but the piece was not about numbers; it was about how his tempo protected Delhi's young backline. Since then I have kept a “service log”: who is doing work for the team that the scoreboard never shows. Jaiswal's gloves are exactly that kind of entry.

The question now is why an opener is keeping in Mumbai's preparation phase. The report offers no clear answer. So the hypotheses need to be separated, and each one tagged with its weakness.

First hypothesis: this is a hedge against selection risk. Keeper-batter slots in the Indian team are always scarce, and a batter who adds a scarce skill raises his squad value. Jaiswal putting on the gloves is therefore not a signal that he is abandoning batting, but a kind of insurance — two doors into the team instead of one. Medium confidence, because not a single word from Jaiswal himself is quoted.

Second hypothesis: a keeper shortage in the Mumbai squad. In domestic cricket, looking for keeping cover is routine, especially early in a season. Siddhesh Lad's comment points this way — he said Jaiswal could keep for Mumbai or for India. But in the very next breath he added that he had no clarity on it. When a captain is unsure about a player's role in his own team, that is not the player's decision — that is a gap in the reporting.

Third hypothesis, which nobody is writing: it may simply be a practice experiment. In a preparation phase many players do things that never resurface in a match. Writing a career-pivot story off half an hour of practice is risky. And here my second professional memory helps — in 2026 I spent 78 days with Kerala Blasters in the ISL bio-bubble in Goa. In empty stadiums every sound echoed, and every small training decision looked enormous. In a bio-bubble I learned that the clock is the only defender you cannot beat. When the preparation window closes, many experiments simply dissolve on their own.

Now we reach the point where analysis stops and caution begins.

The conventional view says Jaiswal is walking the wrong path. As a Test opener his job is to score runs, and keeping will split that focus. The argument is pleasant to hear, but its foundation is weak. Because the man making the criticism is unnamed. And the man who spoke about Jaiswal's motive admitted he had no clarity.

Start by stating the mainstream position plainly: the popular view is that keeping will damage Jaiswal's batting. That claim is neither likely to be false nor likely to be true — because there is no performance evidence on either side of it. It is a guess, and once a guess is placed in a headline it is no longer a guess; it becomes an assertion.

There is one real risk the critics missed. Keeping is a repetitive, physically heavy skill — it loads the fingers, the wrist, the back, and the balance of a session. A top-order batter's core assets are his hands and his rhythm. Loading that asset further is not a joke; it is a working decision. But how big that risk is requires injury or form data, which the report does not have. So I keep it as a direction, not a verdict.

The second risk nobody is counting is journalistic. One unnamed “legend,” one punchy headline, and one captain's own uncertainty combine to build an uneven game around a young national player. That imbalance is the real subject of the story. The bigger risk here is not physical but narrative — turning a small preparation experiment into a large controversy.

In Indian cricket, ex-players carry an informal power of opinion. They hold no office, yet a single sentence from them can swing selection discourse. When that power is used without a name, it is protected from scrutiny and accountable to nobody. That is where the question lands on journalistic values. In the 2026 bio-bubble, a 21-year-old reserve player tested positive for COVID-19. I knew his name from a source and did not print it, losing a scoop. That experience taught me that protecting a player's boundaries is not laziness; it is a long-term investment in trust.

In 2026 I got the chance to cover the World Cup from Kazan. In that 4-3 France-Argentina match everyone wrote about Kylian Mbappé's two goals. I wrote about Olivier Giroud's zero shots on target, seven defensive clearances and four fouls won — how his sacrifice freed Mbappé. That piece was picked up by a national outlet. Kazan taught me that a host city has a heartbeat, too. Mumbai is the same — this city loves turning cricket into story, and that love sometimes crosses a line.

Mumbai's media expression is larger than any other Indian city's. That is why a domestic team's preparation decision becomes a national selection debate. The shift happens silently, and the reader never notices he is no longer reading domestic cricket but a national-team narrative.

The question now is whether Jaiswal's keeping will last if it is real. Tempo helps again. My years of watching matches tell me the true test of a role change comes in the first match, in the first pressure over, the first time a keeper has to dive to the leg side. Until that is seen, this story is incomplete.

Three signals matter most to me. First, Mumbai's Ranji team sheet for the opener — whether Jaiswal is listed as keeper or batter. Second, Jaiswal's own statement — whether he says anything directly. Third, the rhythm of his batting in the matches after keeping — his leave outside off, the pace of his footwork, his patience in seeking boundaries. If any one of these becomes clear, the debate settles itself.

Until then, one simple rule for the reader. Cricket has two kinds of numbers — those that explain the game, and those that are merely visible. Just as xG is abused in football, cricket abuses keeping minutes or glove-days to explain career decisions. The real question is never “how many minutes did he keep”; the real question is whether his rhythm is changing, and whose benefit that serves.

Leaving the Wankhede nets, Jaiswal took the gloves off. He picked the bat up again. Tomorrow morning he will practise opening again, and that much I can say with certainty — because in a preparation phase, rhythm has the final word. Who kept, who called it “a joke” — that chatter may be gone in three days. But one question will remain: when a player learns a new skill for his own security, is stopping him in the team's interest, or in the interest of the conversation around him?

Time will answer. Three days from now, at the Wankhede, the first ball will be bowled. Then we will know where the gloves were kept.