The Day-After Audit: Grading Our Apr 18 Claims | CricketMind.ai

The Day-After Audit · Inaugural Column

We Made Three Predictions. The Scorecard Is In.

48 hours ago, CricketMind published three specific claims about what 7.3 million deliveries would have told the Apr 18 coaches. Today the ball-by-ball from both matches is in our database. We grade every claim. No exceptions.

Ananya Iyer · Stats & Rankings Editor, CricketMind.ai Auditing: M26 RCB v DC · M27 SRH v CSK April 19, 2026

Publishing predictions is easy. The internet is full of people who published predictions on April 17. What's harder is publishing the receipts on April 19 — specifically, returning to every claim you made, checking the actual ball-by-ball data, and telling your readers which ones held up and which ones didn't.

This is the inaugural Day-After Audit. It is going to run every time CricketMind publishes a piece containing specific, testable coaching claims. Karthik Nair's column from April 18 — "The Coach Who Wasn't In The Room" — made three of them. I pulled the live_deliveries table from both matches this morning. I checked each claim against the actual data. Here is what the scorecard says.

Spoiler: the scorecard is not flattering. That is exactly why it has to be published.

Claim 1 · RCB vs DC · M26

Tim David × Axar PatelWe Had the Wrong Batter

Karthik's claim · April 18

"Tim David falls to Axar for 26… The dismissal wasn't bad luck. It was a patterned outcome of two known player signatures meeting each other without forewarning." The implication: David was RCB's problem, and briefing him would have produced 200+.

So I pulled Tim David's full innings from the database. Every ball he faced, every run he scored, every bowler who ran in at him. The table below is the actual data, not a reconstruction.

Tim David · Full Innings · M26 (RCB vs DC)

10.5vs Kuldeep Yadav4

10.6vs Kuldeep Yadav1

11.1vs Lungi Ngidi0

11.2vs Lungi Ngidi6

11.3vs Lungi Ngidi0

11.4vs Lungi Ngidi1

11.6vs Lungi Ngidi4

12.2vs Mukesh Kumar1

13.1vs Axar Patel4

13.2vs Axar Patel1

13.6vs Axar Patel1

14.1 → 14.5vs Mukesh Kumar3 off 4

15.1vs Axar Patel0

15.2vs Axar PatelW

16.2 → 18.6vs Hazlewood, Bhuvi, Rasikh8 off 9

19.3vs Romario Shepherd6

19.4vs Romario Shepherd6

19.5vs Romario Shepherd4

Final: 49 off 27 balls · 4 fours · 3 sixes · Strike Rate 181.5

Forty-nine off twenty-seven. Four fours, three sixes. A strike rate of 181. Three consecutive boundaries off Romario Shepherd in the nineteenth over — six, six, four. This is not the innings of a batter who needed briefing. This is the innings of a batter who was arguably RCB's most productive hitter on the night.

We said Tim David was the problem. The data says Tim David was one of the few batters who showed up. If RCB's death-overs disaster had a scapegoat, the evidence doesn't point to him. It points somewhere else — and our April 18 piece simply did not analyse that somewhere else.

Verdict: MISS

Axar did dismiss David at the moment Karthik predicted — over 15, the same over Karthik named. That narrow element of the claim holds. But the framing — that David underperformed, that a briefing would have unlocked twenty more RCB runs — collapses against a scorecard that shows David outpacing nearly every teammate. The claim did not survive contact with the actual innings.

Claim 2 · SRH vs CSK · M27

Abhishek Sharma × The Bowling PlanThe Factual Error That Falsifies the Counterfactual

Karthik's claim · April 18

"Gurjapneet Singh is left-arm pace. He was in CSK's squad. He did not bowl the second over. Kamboj did — right-arm, different angle, no left-arm disruption. Abhishek got his feet going… ended up on 59 off 22… If Abhishek scores 25 instead of 59, SRH post 165 not 194."

The piece argued that CSK lost because they failed to deploy left-arm pace to disrupt Abhishek Sharma in the powerplay. The data says two things about this claim, and neither is kind.

First, the factual error. The bowler who bowled the second over of the SRH innings was not Anshul Kamboj. The database logs it as Mukesh Choudhary — who is a left-arm pacer. Kamboj bowled the fourth over, not the second. The article's core claim — "Kamboj bowled over 2, right-arm, no left-arm disruption" — is simply wrong on the facts. A left-arm pacer was deployed in the second over. The left-arm angle Karthik said CSK missed was actually present.

Second, and more damaging to the counterfactual: Abhishek Sharma's powerplay numbers against that left-arm attack.

What the piece claimed

With left-arm pace in over 2, Abhishek restricted to ~25 runs in the powerplay. SRH post 165 not 194.

What actually happened

50 runs off 15 balls in the powerplay. Against a bowling attack that included a left-arm pacer in over 2. Strike rate: 333.

Abhishek scored fifty off fifteen in the powerplay. That is not a batter being disrupted. That is a batter disrespecting an entire bowling plan, regardless of arm angle. The premise of our counterfactual — that a left-arm delivery in over 2 would have restricted him — collapses against a scorecard where a left-arm delivery in over 2 did not restrict him at all.

Gurjapneet Singh did eventually bowl in this match. He was deployed in overs 9, 12, 15, and 19 — a middle-and-death role. Whether he would have done better than Mukesh in the powerplay is a question the data cannot answer, because that experiment didn't run. But the stronger argument Karthik's piece made — that CSK ignored the left-arm option entirely — is not what happened.

Verdict: MISS

One factual error at the core, one counterfactual undermined by the actual powerplay numbers. We took a position. The data did not support it.

Claim 3 · SRH vs CSK · M27

Eshan Malinga × The Slower-Ball SignatureThe One That Half-Held

Karthik's claim · April 18

"Eshan Malinga took three wickets… He dismissed Matthew Short… He dismissed Sarfaraz Khan. The ball that got both of them — the same delivery — was a full-length slower ball… Ball-by-ball data on Malinga's wicket deliveries from this season marks this delivery type as his primary dismissal tool in overs thirteen through seventeen."

This one is the closest we came to getting it right, and it's still a partial.

Eshan Malinga · Wickets · M27 (SRH vs CSK)

6.1Ruturaj Gaikwad (powerplay)W

11.4Sarfaraz Khan (middle overs)W

16.4Matthew Short (death)W

Figures: 3.5 overs · 28 runs · 3 wickets

The names were right. Malinga did dismiss both Matthew Short and Sarfaraz Khan. But the phase claim does not survive the data. Karthik placed his dismissals in the 13-to-17 over window. The Short wicket at 16.4 lands inside that window. Sarfaraz at 11.4 does not — that is middle overs, not death.

And there is a third wicket the April 18 piece didn't mention at all: Ruturaj Gaikwad, dismissed by Malinga at 6.1 — in the powerplay. That is arguably the most match-defining wicket of the three. CSK were chasing 195; losing their captain in the powerplay to a part-time death-specialist is not a footnote. It is the moment the chase got harder.

We identified Malinga as a threat. We named two of his three victims correctly. We got the over window partially wrong, and we missed his most important wicket entirely. The delivery-type claim — the "slower ball that looks like a yorker" — remains unverifiable from the database. Sportmonks ball-by-ball data does not annotate delivery type. That part of Karthik's piece is a claim we cannot check, which means readers are being asked to trust it on credibility alone.

Verdict: PARTIAL

A half-credit. The thesis that Malinga was the CSK-chase-breaker is supported. The specifics beneath it — phase window, full wicket list, delivery type — do not fully hold.

The Scorecard

What the Data Actually Says

Day-After Audit · M26 + M27 · April 18 claims

Tim David × Axar (framed as RCB's problem) MISS

Abhishek × left-arm bowling plan MISS

Malinga's slower-ball signature PARTIAL

Final grade 0.5 / 3

This is not a good score. It is worse than I wanted it to be when I started pulling the data this morning. I expected one miss, two partials. I got two misses and one partial. The piece that CricketMind published on April 18 — a piece that argued ball-by-ball data could have saved coaches from specific decisions — had specific decisions of its own that ball-by-ball data does not support.

The moral authority to argue that coaches should be accountable to data is earned in exactly one way — by being accountable to data yourself. This is that week's instalment. Ananya Iyer · Stats & Rankings · CricketMind.ai

Here is what changes from this audit, specifically and publicly:

One. Any claim about bowler deployment in a specific over will be cross-checked against live_deliveries before the piece ships, not after. The Kamboj / Mukesh Choudhary factual error in the Abhishek claim should have been caught at draft stage. We built the database precisely so this kind of error is preventable.

Two. Counterfactuals that rely on a specific player not performing a specific action — "if Gurjapneet had bowled over 2" — need to be tested against the full data, not just against the claim's own logic. Abhishek's powerplay strike rate of 333 means the "left-arm angle disrupts him" signal is weaker than the piece implied. Future pieces will show the phase-and-handedness split before asserting a counterfactual.

Three. Any claim about "the signature delivery" that cannot be verified from the database — because the database does not annotate delivery type — must be flagged explicitly in the piece as a credibility-based assertion, not a data-based one. Readers should know which claims are receipts and which are interpretations.

The Weekly Wrap

This is the first Day-After Audit. It will not be the last. Starting this week, CricketMind publishes a Monday column that grades every testable claim from the previous week's editorial across the site — Karthik Nair's counterfactuals, the Fantasy Edge picks, the CM AI match predictions. We already publish the Accuracy Tracker for winner predictions. The Day-After Audit is the same idea extended to every piece with a checkable hypothesis.

If you read a CricketMind article that makes a specific claim, you should be able to find the receipts — including the ones that didn't hold up — within 48 hours. That is the standard. This column will enforce it.

A note on the methodology. The ball-by-ball data for this audit was pulled from the live_deliveries table, populated by our Sportmonks ingest pipeline. For claims that cannot be verified against this data — delivery type, field placement at wicket, coach conversations that did or didn't happen — we say so explicitly rather than assuming the original piece was correct. Sample sizes for a two-match audit are small by definition, but the specific claims made in the original piece were specific enough that small samples are appropriate. Read the original column here.

About this column. Ananya Iyer is Stats & Rankings Editor at CricketMind.ai. She writes the methodology pieces and runs the Accuracy Tracker. The Day-After Audit is a new recurring column that grades every testable claim from the previous week's CricketMind editorial. The grading is public. The methodology is public. The misses are public.

cricketmind.ai/blog · IPL 2026 · Day-After Audit · April 19, 2026

Next: Monday's Weekly Wrap — every claim from Apr 18 - Apr 20, graded.

Want deeper analysis?