Rohan Khan's Dressing-Room Ledger: Ranji Round 4, Day 4, Where the Scorecard Is Quietly Lying

In the press box of a Mumbai club ground, on the morning of Day 4, I opened my bound ledger and the first number I wrote was not a score — it was 311. Mumbai's overall lead against Railways. The newspaper will call it a "strong position," the live blog will call it "control," and both will be right — but in my copy, beneath that 311, there is a blank space where I write the same question every time: how much time remains, what is the state of Railways' second innings, and how many times has this pitch flipped on the fifth day this season. Until those three questions are answered, 311 is a lead, not a win. The gap looks small, but over twenty years I have seen more incomplete victories printed in Ranji's May newspapers than I can count, and they all came from exactly this gap. And this is the day — Day 4 of Round 4 — when across eight or ten grounds in the country, something is turning. I follow the same method all day: three columns for every fixture — target, runs remaining, wickets remaining. Everything else comes later. Because the truth of Day 4 in Ranji is that the scorecard often does not show you the state of the match; it shows you the fatigue of the match. And fatigue, in my experience, is the most honest indicator — of the batter, of the bowler, and of that empty stand which sits with its own shadow on a fourth-day afternoon. Saurashtra are 134/8, chasing 342, 208 runs still needed with two wickets in hand. In that one line is a three-day story. I have tracked Tripura's fielding set-ups over recent seasons — they traditionally play home matches on spin-friendly wickets, and on a fourth-day morning, when their spinner chooses between reverse swing and seam movement, the scorer does not see his intent first. 208 runs and two wickets — that is the cruellest arithmetic in cricket, because in it your number seven batter plays on nerve more than ability, and the number eight walks out knowing a single mistake will change the balance of the entire innings. I have watched Saurashtra's batters practice sweep shots for hours in the Chepauk nets — this is the same team that has weaponised technique in domestic cricket over recent years. But when climbing a 208-run mountain, it is not technique that moves, it is rhythm. And rhythm is weakest on a fourth-day morning. On the same day, Himachal Pradesh are 83/4, chasing 447, 364 runs still needed. When you chase 400-plus, the arithmetic in the dressing room changes — nobody talks about "winning," everybody says "tough," and the coach's speech gets shorter. I have seen in such situations that the number five or six in the batting order does not play his own game; he buys time for the team. Himachal's 83/4 does not mean the match is over — it means every over is now a ledger entry, and every entry records the question of how much the batter read the pitch, not how much the bowler extracted from it. As for Mumbai, Tanush Kotian's seven wickets — that is the number everyone will pick up, but in my ledger it carries a parenthesis: how many overs, on which day, and in which innings. A seven-wicket haul in Ranji can mean three different things — a spinner's patience in the first innings, a tail-ender's surrender in the second, or a fourth-day morning of reverse swing. For Mumbai this matters because their domestic season is usually spin-based, and Kotian's performance fits the structure the team management has been building over recent years — at least on paper. But a structure built on paper and a structure built on the field are two different things, and I have watched both fall. Now the part that often gets left behind in reports: Tamil Nadu closing in on a bonus-point win against Chhattisgarh. The bonus point is the most misunderstood rule in domestic cricket — many readers treat it as an "extra point" and move on, but in reality it forces teams to gamble with their schedule and their weather. When a team chases a bonus point, its bowling attack takes risks, the fielding set-up changes, and sometimes, in the race to win in three days, it shakes the foundation of its own batting. I am not saying the bonus point is wrong — I am saying it is a decision that should be measured not by a single day's score but by the arithmetic of the whole season. Tamil Nadu have the depth to absorb that risk, but not every team does. And Uttarakhand's ten-wicket win — that is a complete result, not a snapshot, and so in my copy it is written in different ink. That win over Haryana does not lift Uttarakhand up any ranking — remember, I am a sample-size skeptic — but it is a historical fact that must be recorded. Such wins in domestic cricket are often the story of a team's confidence, one that nobody is watching. For Uttarakhand, this win is most valuable precisely because it had no TV camera. Raj Biswa's duck in Meghalaya's chase of 295 — I will not write a single word on it unless I have three innings of data. A duck is one day's account, not a career's. In my ledger, next to Biswa's name there is only this: "that day the ball did it, not the batter." In Ranji, every batter has a day when he is out to a good ball and scores a century off a bad one the next. Those who draw a career map from a single duck commit cricket's oldest mistake — they chase the scorecard, not the game. Now the part I linger on most, and which never makes the headlines of any live blog: the gap between Mumbai and Railways on a fourth-day morning, after the first hour has passed and the second is beginning. This is the time when everyone on the ground knows that nothing is going to happen — or everything is. I have called this hour the "empty hour" in my ledger. During it, the sounds that come through the stump mic are not for any TV broadcast. A bowler says "this wicket is dying," another laughs, a fielder changes his position at slip, and the wicketkeeper says "change the stumps." Over recent years I have kept a count of these sounds, and on a fourth-day morning they tell the most truth. This season I have seen one more thing, which is a new entry in my ledger: the gap between the pitch report and the batting order. Several teams have changed their batting orders in Round 4, and the reason is usually given as "form," when in reality it is "pitch." I cannot verify this without data from three matches, so I am recording it only as an observation. The biggest thing missing from the reports of this fourth day: the story of the losing teams. We look at wins, at leads, at bonus points. But in Ranji, the most interesting thing happens in the losing team's dressing room — there is no camera there, no reporter, just a coach who talks for twenty minutes and a senior player with twenty years of experience who says two words. What I have heard in such dressing rooms is recorded in no scorecard, and perhaps that is Ranji's real weakness — we keep a record of results, not of process. Now the thing that forces me to think anew every time, and which is left out of every Ranji report: fourth-day cricket and fourth-day weather move together. If the morning dew is heavy, the spinner's ball stops and the seamer can find reverse. If the sun is harsh, the wicket starts to crack on a fourth-day afternoon. I have tracked this systematically over recent seasons — and my conclusion is that there is hardly a team in Ranji that plans its fourth day around the weather. Most teams arrive on the fourth day and think about what is happening, when they should have thought before the fourth day about what could happen. Now the counter-intuitive angle, which I write in my notebook after every Ranji report: we use the words "strong position" and "control" so easily that we forget that in Ranji, even the strongest position can change by a fourth-day afternoon. A 311-run lead looks enormous on paper, but if Railways have two sessions left and one batter set, that 311 becomes a challenge, not a guarantee. Ranji's history is full of examples where a 300-plus score was chased or saved on the fourth day — and in most of these cases, the losing team's biggest enemy was its own "safe" play. A team that goes out on the fourth day intending to draw often loses; a team that goes out intending to win often survives. This is my personal experience, not statistical proof, so read it as such. Now the technique, which I reserve one paragraph for in every piece, without a single number. On a fourth-day morning I saw a ball that stayed in my mind. A spinner bowled from outside off, the batter defended, and the ball brushed the outside edge of his bat and went to first slip. The slip fielder took the catch — bending low, one-handed, stretching his body fully forward. It was a catch nobody on the ground saw, because at that moment everyone was watching the batting at the other end. If I added any statistic to this paragraph, that catch would disappear. This is what I like most about Ranji — some things can only be held in words. The biggest entry in my ledger on this day is the question I wrote in the morning and had no answer for by evening: will Mumbai change its line and length for an outright win today? Playing with a big lead is an art in domestic cricket — you have to change your bowling from defensive to aggressive, and if you cannot take early wickets, you watch your lead melt with time. Tanush Kotian's seven wickets have given Mumbai the option of pushing the spin attack forward, but it is their captain's call as to when and how he uses it. I have seen captains who, despite having a good spinner, fail to use him at the right time, and the cost is paid in the next match. Now the thing most missing from Ranji coverage and which I track most: the hour after the match. When the stumps are drawn and reporters get busy writing their stories, I sit with the ground staff. They tell me which batter went to the nets first after the match, which bowler kept bowling for hours, and which player went straight to the bus. This information never gets printed in any report, but it tells you what is going to happen in the next match. In Ranji, form is built not from the scorecard but from habits. Now the thing common to all the reports of this fourth day: every report says "Mumbai are in a strong position" or "this is a massive target." These words build a picture in your mind — a strong team dominating a weak team, a batter challenging an entire pitch. But the real picture of Ranji is very different. On a fourth-day morning, inside the ground, nobody is "dominating." Every bowler is tired, every fielder is looking at his own footmarks, and every captain is counting his options. The team in a "strong position" is often under more pressure because a win is expected of it, and in Ranji, nothing is heavier than expectation. Another thing I have seen this season: in several matches in Round 4, the direction was decided by one over that nobody watched. In one match, on a fourth-day morning, a bowler bowled what looked like a free-hit ball on his very first delivery — no bouncer, no yorker, just a straight ball that hit the batter's pad. And it was not a wicket, but that ball pushed the batter back, and within the next three deliveries he was out. In the scorecard that over is just an over; in my ledger it is the moment the match turned. In Ranji, the balls that win matches are often not the ones that take wickets, but the ones that prepare the ground for the next ball. The biggest lesson of this day, which I find in no scorecard: in Ranji, the difference between winning and losing is often decided in one session, and that session is often the post-lunch one — when the ground's heat, the players' fatigue, and the absence of spectators together bring the game to its rawest form. I have seen this session thousands of times, and every time it teaches me the same thing: in Ranji, no team has fully lost and no team has fully won until the last ball is bowled. Now, forward. As Ranji's fourth round ends, the question is not who built a 311-run lead or who left 208 runs behind. The question is: will these same teams repeat their positions in the next round, or will the pressure of the fourth day change their schedule and their strategy? I am opening a new column in my ledger for the next round — "the day after the fourth day." Because the team that loses on a Wednesday's fourth day steps out to play the first day at another ground on Friday. Ranji's real hero is not the one who wins a match; it is the one who gets up after the fourth day and is ready for the next first day. And I will be looking for that heroism, on the morning of the next round.