The Dharamsala Squad Sheet, an Incomplete 'Grade', and Mumbai's Invisible Ledger

Last evening, beside a rain-streaked London window, I was reading the squad sheet. Two names out, two names in. It is such an ordinary event in cricket news that the eye skips over it. I stopped—because a squad sheet is not a list of names to me, it is a ledger. Who is in, who is out, why they are out: those three questions together give a full report on a team's internal condition. Ayush Mhatre is out. Yashasvi Jaiswal is out. In come Suryansh Shedge and Angkrish Raghuvanshi. Mumbai's Ranji Trophy match against Himachal Pradesh at the HPCA Stadium in Dharamsala begins on October 18, 2026. Before a ball is bowled, Mumbai has lost two first-choice top-order batters—one to injury, one to national duty. The training ground told me the truth three days before the transfer market did. That habit is the single greatest asset of my working life. But today's event is different. There is no auction here, no transfer, no hot take. There is only a team, a pitch, and one question: will Mumbai still be strong after losing two batters? The Ranji Trophy is India's premier domestic competition. A four-day red-ball format, session-based tactics, the new-ball attack, declarations, the follow-on—all of it operates on a different ledger from T20 or ODI cricket. In this format patience is a weapon, and one way to break patience is to lose wickets in the morning session. Mumbai is the most successful side in the history of this competition, and a large part of that success is its pipeline. Based on my years of watching matches, I have noticed one thing repeatedly: Mumbai's strength is never confined to the first eleven; its strength sits in the hands of the ninth, tenth and eleventh batters. This match is no exception. The special feature of the Mumbai system is a constant circulation between India A, Ranji and the IPL that no other domestic side can match. But this time there is a geographical shift I am not willing to treat lightly. Dharamsala. Roughly 1,300 metres above sea level, cold air, and a rain risk in early October. Very few Indian domestic grounds let seam bowling matter more than spin—Dharamsala is one of them. The new ball swings here, the wind changes its path, and the morning session often decides the course of the match. That is precisely why Mumbai's squad sheet becomes more important. Not by looking at names, but by looking at structure. The squad contains Siddhesh Lad (captain), Sarfaraz Khan, Raghuvanshi, Shedge, Mushir Khan and Parkar. Two wicket-keepers—Akash Anand and Hardik Tamore. A crowd of spin all-rounders—Mulani, Kotian, Ankolekar. In the seam attack, Tushar Deshpande, Mohit Awasthi, Sylvester Dsouza and Omkar Tarmale. Now look at the inconsistency. A side is travelling to a seam-friendly ground with three spin all-rounders in its middle. That raises a question by itself—will Mumbai read the pitch and pick a seam-heavy eleven, or lean toward its own habit? I have written it in my notebook: decisions of this kind reveal a team's internal thinking before the match does. If the seamers are given more minutes, it means the team management respects the Dharamsala pitch. If the spinners bowl more, it means they trust their own strength more. Either way a story will form—only the result will differ. A small but significant question is the presence of two wicket-keepers. Akash Anand and Hardik Tamore—both have been kept. This is either rotation or an uncertainty over the first choice. The wicket-keeper's call is never small, because in red-ball cricket the number of catches and the speed of the stumping can change the course of a match. Now to the real data—Ayush Mhatre's injury. A Grade 4 tear in the right hamstring, four to six weeks out. The injury occurred while playing against Chandigarh. There are two separate layers here, and I want to see them separately. The first layer is organisational. Mhatre is not merely a top-order batter; he was named vice-captain before the season. That is, he was part of the leadership core. Losing a vice-captain to injury means multiple vacancies—a batting slot, and a voice of reassurance in the dressing room. The squad sheet does not mention that second vacancy, but the dressing room knows it. I always speak to the steward first, then to the striker. Because the steward knows who walks onto the ground and when, who laughs, who stays silent. In the same way, the absence of a vice-captain shows up not only on the scorecard—it shows up in small moments, such as who plans the next session at the drinks break. The second layer is medical, and this is where my deepest doubt lies. 'Grade 4'. I have tracked injury news for many years. The standard grading of a hamstring strain runs in three steps—Grade 1 (mild), Grade 2 (partial), Grade 3 (complete rupture). A category called 'Grade 4' is not recognised in the medical literature. I wrote it in the third notebook—the one where I keep what I cannot yet prove. This does not mean the injury is mild. Quite the opposite. A four-to-six-week layoff means it is unquestionably serious—probably close to Grade 3. But my job as a journalist is not only to report a number, but also to test its reliability. If 'Grade 4' is a misclassification, then anyone who cites this information in future will spread a falsehood. I learned that lesson while working at a London sports desk. January 2026, 3:40 p.m. The phone would not stop, and neither would my hands. I had the news of Christian Eriksen's medical in hand, but I held it for six hours—to verify it with two independent sources and to let the player's family be told. That lesson applies here too. Before writing 'Grade 4', one should at least ask the question—did the club or board's medical department actually use this word, or did it change on a journalist's pen? Now to the second absent player—Yashasvi Jaiswal. His absence is not due to injury, but to India A's tour of New Zealand. This is a different kind of event, and analytically its significance is greater. Jaiswal is an established opener in India's Test side. There are usually a few reasons why an established Test opener goes on a red-ball India A tour: red-ball rhythm management, preparation for an upcoming Test series, or a phase of rebuilding form. The article gave only the fact of the tour, not the reason. I want to be careful here. Because guessing is easy, proving is hard. In my third notebook I wrote: 'Jaiswal's India A tour—a directional signal, not a final decision.' But one thing is clear. This event shows a clear priority chain in Indian cricket: national duty first, then the A team, then the domestic side. In Jaiswal's case the Ranji side will wait, because something bigger waits above. This chain is not about one player; it is evidence of the vertical integration of the entire Indian cricket system. Now to the two replacements—Shedge and Raghuvanshi. There is a subtle asymmetry here that the eye does not easily catch. Suryansh Shedge arrives having played red-ball matches for India A against Australia A. That is, he is match-fit, in red-ball rhythm. Raghuvanshi's readiness, by contrast, is not stated in the article. It is a small difference, but in the first session of the match its impact can be large. A batter who has recently played red-ball cricket returns to rhythm quickly, especially in conditions as demanding as Dharamsala. That is why I am keeping a closer watch on Shedge. Now I come to the place where I disagree with the conventional reading. Most analyses will see this event as proof of 'Mumbai's depth'. Two first-choice batters out, yet the side is strong—that is their story. From the outside it looks reasonable. But I think the real story lies elsewhere. The real story is workload and injury management. Notice—three different signals have arrived together in this one squad sheet. A young player (Mhatre) is out with a high-grade hamstring injury, whose recurrence risk is documented as high. An established Test opener (Jaiswal) is carrying a workload in two places, national and A-team. And of the two replacements, one is coming off back-to-back red-ball matches, meaning he too has a rest calculation. Read together, these three signals create a larger picture: in modern Indian cricket the greatest challenge is no longer finding talent—it is managing the workload of that talent. Based on my years of watching matches, one pattern returns again and again. Young players play every format, every team, every time—because everyone wants them. But there is only one body. At Mhatre's age a high-grade hamstring injury is not just the news of one match; it is a long-term signal. The recurrence rate of hamstring injuries is significantly higher in young players, and each recurrence takes longer than the last. The second disagreement is about structure. Those who know Dharamsala's seam-friendly character will assume Mumbai picks a seam-heavy eleven. But the squad holds three spin all-rounders. So the selectors may have favoured their own habit over the pitch. That is not a blunder, it is a conscious risk—and the result of that risk will be clear in the first innings. The third disagreement is with journalism itself. The way 'Grade 4' is spreading, no one is asking whether this classification is actually correct. In my third notebook this remains the biggest question. When an unproven number spreads like truth, correcting it later becomes difficult. There is also a commercial layer we often skip. The Ranji Trophy is not a franchise league; there is no auction here, no vast broadcast-rights accounting. But this match is indirectly a scouting bulletin. Shedge, Raghuvanshi, Mushir Khan, Parkar—these young players are writing their names into the IPL auction reckoning with every red-ball innings. In Dharamsala's difficult conditions, a good innings carries more weight than in easy conditions. So what should we watch from here? First, Mhatre's rehabilitation timeline. If he fails to return after six weeks, or if there is a recurrence, that is a red signal not only for him but for Mumbai's whole season plan. Second, Jaiswal's path. The result of the India A tour and the selection for the next senior series will tell us whether this tour was rhythm management or the start of a new chapter. Third, the first session in Dharamsala. If Mumbai's seamers take quick wickets there, the selection was right. If not, the spin-heavy structure will come under question. Fourth, which of the two wicket-keepers holds the first-choice spot—a small but lasting signal. A squad sheet is not dead paper. It is a living ledger, in which a team writes down its fears, its plans and its limits at once. I only need to know how to read it. And the true extent of Mhatre's injury—that still waits in my third notebook. Because what is unproven cannot be written as truth. Not at my desk, at least.