Ranji Day Three: The Follow-On Line Is 150, Not 200 — and Declaration Maths Wrote the Verdict

The final session of day three at Chepauk was almost silent on the broadcast. Three numbers sat on the scoreboard — 313, 134, 113. One pitch, one match, three innings, three separate worlds. R Sai Kishore's 6/34 folded an innings inside a single session, and on a surface dusted with spinners' footmarks the batters looked as if they were playing a different sport.

I was in a room in Liverpool with two screens: one for the stream, one for my ledger. The ledger did not record 313 or 113. It recorded one number — 150.

Keeping that ledger is an old habit. In 2026 I started logging every penalty decision across 380 Premier League matches: 92 penalties, 14 of which I graded wrong by my own threshold. The following year I watched all 64 matches of Russia 2026 twice and built a ledger of 455 VAR checks. The habit has not changed: I do not count checks to find blame. I count them to find patterns.

The Ranji Trophy's Elite Groups A to D came to me as an agency round-up of six fixtures on day three. Fifty-five information points. Beside every one of them: no source.

The biggest event of this round is not a score. It is that blank. A scorecard without a source is not information — it is a claim. And cricket still writes its verdicts on claims, years after football changed the measuring instrument.

On 1 December 2026 I was on the data floor in Qatar for Japan versus Spain. Kaoru Mitoma's cutback for Ao Tanaka's winner was measured at 1.88 millimetres inside the line. Every frame carried a timestamp, the operators carried an audit signature, the whole check ran 2 minutes 12 seconds. If anyone questioned it later, I could show the log rather than the score.

Domestic cricket's scorecard still stands where football stood in 2026: the numbers exist, the audit trail does not. A blockchain-based ball-by-ball log — a hash for every delivery, signatures from scorer and match referee, a time stamp — would have made those 55 data points citable instead of anonymous. The agency round-up would have been a verifiable record rather than a reconstruction.

Hold the format in mind. This is four-day first-class cricket, six Elite Group fixtures, two innings per side. Five-day Test habits do not transfer. Declaration and follow-on enforcement are the decisive tactical levers here; scoring rate is not.

That is exactly where the round's first pattern emerges. Mumbai 528/8d, Delhi 648/6d, Maharashtra 527/5d, Hyderabad 306/7d. Four dominant first innings, all four closed by declaration. Declaration arithmetic wrote this round's verdict, not the quality of the batting.

Take Mumbai. Having declared at 528/8, they had Himachal at 144/3 at stumps: three wickets down, seven standing. To win a four-day match you need twenty wickets; they had eight. On the remaining timeline that is roughly three to four sessions. The arithmetic was not on the side of a win.

I am not going to insist the declaration timing was wrong, because the round-up does not state when any of these declarations were made. My confidence here is medium — the pattern is clear, the decision is inference. That distinction matters, because collapsing the two is the most common offence in cricket analysis.

Now the fact that resets the whole discussion. Under Law 14, the follow-on requirement is 200 runs in a match of five days or more, but 150 runs in a match of three or four days. The Ranji Trophy is a four-day competition. The line here is 150.

I am not asserting this from memory. The scorecards testify to it in three separate fixtures. Chhattisgarh were bowled out for 206, trailing by 250 — and batted again. Jharkhand made 169, trailing by 358 — and batted again. Odisha made 225, trailing by 179 — and batted again. All three second innings. That sequence is impossible without enforced follow-ons, and under a 200-run threshold neither Chhattisgarh nor Odisha would have qualified.

Three independent scorecards, one clause of the law, one consistent outcome — confidence now high.

The implication for Himachal is large. From 144/3 in reply to 528, they need 378 to erase the follow-on risk: 94 more runs with seven wickets in hand, not 234. Anyone still calculating on the old 200-run habit will read Himachal as a side under siege. On the 150 line, they are alive in the match.

Gujarat's picture is different. Replying to 498 they have made 363, already past the follow-on mark and trailing by 285. The follow-on question no longer exists for them; the question is time.

The base case in both marquee fixtures is therefore a draw with a first-innings-lead points split. One day remains in each, and at both stumps the arithmetic points the same way. Mumbai's and Delhi's realistic ceiling is not victory. It is the clock.

Venue variance is the structural signature of this round. Chepauk produced 313, 134 and 113 — a match broken by spin. Delhi, Pune, Jaipur and Mullanpur produced first innings between 456 and 648. One tournament, one week, effectively two different sports.

Here the pitch is not the variable; it is the constant. The declaration mathematics of a side at Chepauk is not the declaration mathematics of a side posting 648 at Mullanpur, yet the same rulebook governs both.

Environmental data is largely absent. No toss, no weather, no pitch report appears in the round-up. My judgement on that dimension is therefore explicit: insufficient information, assessment not possible. The only quantifiable pressure is time — one day remaining in each of the two marquee games.

Now the conventional explanation. The story that returns every season about Ranji draws is a story about pitches: flat decks, dying bowlers, defensive batting.

My ledger says otherwise. Across these six fixtures first-innings totals ran from 313 to 648. That spread is proof the surfaces were not uniform. What was uniform was the decision script. A five-day Test script is being run on four-day matches: big totals, late declarations, no time left.

Enforcing the follow-on is also a cost decision, and almost nobody prices it. Sending the opposition in again means another innings on your bowlers' legs and another block of sessions off the clock. Chhattisgarh, Jharkhand and Odisha all incurred that cost — and no scorecard shows where the time to win was supposed to come from.

Why that matters is best explained by those 1.88 millimetres. In Qatar the decision rested on a measured frame with a timestamp attached. Here the decision rests on a declaration clock that appears nowhere in the record. When the frame rate decides a season, the frame rate is a moral position. In Ranji cricket, nobody is keeping that clock.

So the blockchain question here is not fashion. It is necessity. If every delivery, every declaration and every follow-on decision entered an immutable, time-stamped log countersigned by scorer and referee, then three days later an agency round-up would not be carrying 55 unsourced data points. Each number would be checkable, and each critique would land harder, because nobody could ask where the figure came from.

Note that the problem is structural, not corrupt. Ball-by-ball data from a domestic match passes through many hands — scorer, broadcaster, agency, fan page — and a root source exists nowhere. In a cricket economy where the scorecard is the currency, the absence of an audit trail is also a commercial risk.

Since I started a page called BDCricTeam in 2026 I have watched the same thing across Bangladesh and England: domestic cricket's data is the most weakly preserved data in the sport, and it is precisely the data on which careers are decided. A declaration can move a player's milestone; a vague scorecard can write an eligibility verdict.

So day three reads on two levels. On the field: four-day declaration maths is still being done on a five-day template, and the 150 line is known but not internalised. In administration: we are arguing about the finest tactical margins of matches whose underlying record is unauthorised.

One recommendation, because a piece like this is incomplete without one. Mandate a ball-by-ball log for every domestic first-class match, recording each delivery, declaration and follow-on decision with a timestamp, countersigned by both scorer and referee. The technology is not expensive. The expensive part is arguing three days later over a scorecard with no source.

In the end my question is not about the cricket. It is about the ledger. Who writes this scorecard, who verifies it, and who decides which number survives into the record? I count checks to find patterns, not to assign blame — and this round's pattern is plain: the table is a verdict, not a story.

Next round I will watch two things. First, whether Mumbai and Delhi can step out of the five-day template inside a four-day match. Second, whether time enters the calculation when captains enforce the follow-on. In a competition where points arrive through the first-innings lead, the clock is the real scoreboard.