The Kotla Notebook: The Tempo Trapped Between a Ranji Morning and an IPL Window

Wednesday morning, Arun Jaitley Stadium. The haze had not lifted by half past eleven, voices from the upper tier carried all the way to the pitch, and the first session was still young. An opener was on 19 off 42 — no shot was bad, no shot was memorable either. My notebook has three columns: the ball, the first bounce, the backlift. After that over I wrote it down — same backlift, release half a second later, and the batsman had already begun his footwork. He had not read the ball; he had guessed at it. The next twelve deliveries produced no run.

That morning belongs to a past domestic season, it lives in my notebook, and that is exactly why I trust it above the scorecard. Across those 28 overs the run rate was 1.46 and 61 per cent of deliveries were dots. The scorecard files it away as 19 off 42. The notebook filed it as the end of a tempo. That difference decides the direction of the whole argument.

The domestic calendar debate usually stops at an embarrassment of talent — this many batsmen, this many quicks, this much bench strength. My ledger asks the reverse. The Ranji Trophy's first block sits in October-November, the Syed Mushtaq Ali Trophy and Vijay Hazare Trophy compress into the same window, and then two claims arrive together for a February date. Since 2026 the Women's Premier League wants the February-March slot; Ranji knockouts sit in the same month. The mega-auction cycle has added pressure to November-December as well. This is not politics, it is arithmetic: whichever window the bigger tournament takes is the number of days cut from domestic preparation.

My method rests on two dates. May 2026, Feroz Shah Kotla — a borrowed media pass, eyes off the big screen, on the batsman. Rishabh Pant made 97 off 43 against Gujarat Lions that evening and I wrote down a clock rather than a match: the length of his walk to square leg between deliveries, the count of bat taps, the sound of the stadium exhaling when he holed out. I closed the Kotla notebook after that 97, while the ground staff were still dragging the covers.

The second date is February 2026, the Under-19 World Cup in New Zealand. From a Delhi hostel room I tracked Shubman Gill's 372 runs — the piece that opened with the sound of bat on ball in an empty Mohali net is still the first page of my ledger. Gill's 372 was not a score; it was a rhythm I followed. After that tournament I opened a separate register for net routines and team travel, because a scorecard does not show you the travel, and the travel is what builds tempo.

I measure tempo in four numbers. First, strike rotation: how many singles arrive between every ten dot balls. Second, the boundary-to-dot ratio — how many deliveries were spent to earn one four. Third, the run rate by five-over block, because an innings changes tempo in blocks, not over by over. Fourth, balls per session and the gap between a bowler's load-up and release. When a batsman's backlift stays the same but the release shifts half a second, that is the story — not the average.

Test cricket's tempo band generally runs between 2.7 and 3.2 runs an over. A batsman who builds his Ranji innings at 3.0 has room to land at 2.9 in a Test. A batsman who plays at 4.5 and tries to play at 3.9 ends up at 2.4, because his strike-rotation habit is built on clearing the spinner rather than leaving him at cover. Yashasvi Jaiswal is a case of that translation working: his 171 on Test debut in Dominica in July 2026 was possible because his domestic tempo already sat inside the Test band, not outside it.

There is a further layer that usually gets skipped. Since 2026 the Indian Premier League has used the Impact Player rule, handing every side an extra specialist — which means the need for a sixth bowler or a seventh batsman has shrunk. The domestic all-rounder market narrowed and demand shifted to players who do one job with expertise. The tempo cost is simple: a two-job player learns the rhythm of forty overs; a one-job player learns the rhythm of twenty balls.

The clearest example of this tempo argument sits in my notes from June 2026. June 29, Bridgetown — India 176/7, South Africa 169/8, a seven-run margin. Jasprit Bumrah took 2/18 and Hardik Pandya 3/20. The tempo of that match did not shift on the pitch; it shifted after the timeout, when the bowling plan stopped being about taking wickets and became about breaking the breath of an over. Hardik walked slowly back to his corner after the last ball, and I stopped writing ball-by-ball because the score was made, though the rhythm had not yet finished. A security guard blocked the tunnel; I did not argue, and got in through a team staffer.

The Dubai final of November 10, 2026 sits in a different drawer of the ledger — Mumbai Indians beat Delhi Capitals by five wickets in front of no spectators at all. The empty-stadium IPL final taught me that silence has its own scorecard. The delay in a call on the stump mic, a bowler's breathing, the single voice rising from behind the stumps — these are signals that get buried in a full house and can be read plainly in an empty one.

A home tournament has a different tempo, and I saw that in Ahmedabad on November 2, 2026, when India beat South Africa by 52 runs in the Women's World Cup final. The Women's Premier League, running since 2026, did not merely hand domestic players a stage; it taught them strike rotation and the habit of absorbing pressure through the middle overs. A home crowd accelerates your tempo, and a faster tempo is not free for everyone. Whoever holds it plays finals; whoever does not converts pressure into dot balls.

From the outside this looks like a surplus of talent, but the real bottleneck is tempo translation. And here the other side appears: data analysts now sit inside dressing rooms. They can measure outcomes — averages, strike rates, match-ups, venue splits. They cannot measure why a batsman changes his backlift in the 47th over, or why a spinner delays his release by half a second. That is the difference: a model gives you the answer after the match; the batsman only has the question at the time.

Football's five-substitution rule does something similar. It benefits squads with depth, and the price is that the final twenty minutes turn from an ordered game into a war of attrition. In cricket, the Impact Player and the deep bench of a mega-auction do the same job — they break the game into neat fragments, in which every fragment looks good and nobody owns the tempo of the full ninety.

One ledger entry, without anger: two claims exist on the February window, and the BCCI's domestic calendar committee gives a date to one of them each season while the other gets told it comes later. That happened in the 2026-25 cycle. The bill is paid by the batsman playing at 1.46 an over on a cold December pitch whose name appears on no awards list and in no auction conversation. I will not make a speech about it. I will only record that the body is the BCCI, the decision belongs to the calendar, and the cost is paid by that December batsman.

The next signal will come from the December Ranji round. I will watch two things in it: the strike rotation of the batsman nobody is naming yet, and the over-render of the spinner who bowls the same way on the fourth morning. The notebook is my quiet drum; every over keeps time. The tempo that holds in December's haze will be the tempo that gets a price at the next auction, and one day reaches a Test morning. The question now is who stands at the Kotla on the next Wednesday morning, and how early his backlift begins.