Not 36 Balls, 36 Centimetres: When the Keeper's Boots Stole the Super Over

The night of 4 November 2026, Melbourne Renegades versus Hobart Hurricanes, a WBBL league match. Last ball. Scores level. What the ground saw was a dot ball — Deandra Dottin swung and missed, the ball went into Lizelle Lee's gloves, the bails fell, the commentary box rose in celebration of a Super Over. The score flashed, Dottin's silence in the crowd. But three minutes later the TV umpire watched the replay and delivered a verdict that recalled one of cricket's harshest laws. Lizelle Lee had collected the ball in front of the stumps. Under MCC Law 27.3, that is a no-ball. One extra run. A four-wicket Renegades victory. The Super Over was never born.

I watched this myself, and that is the most interesting part — on first viewing, I too called that ball a dot. Then I slowed the replay, drew a line through Lee's boots on the footage, and had to delete my own comment. A spreadsheet only runs on the arithmetic it shows, and the law of the game says the same thing.

Context: The real debate was not about the stumping

Let me first clean up the mistake I made in the broadcast's first replay. The mind rushes toward the stumping — did Lee break the bails in time? Was the batter out of her crease? On such occasions two separate events happen on one ball and the viewer conflates them.

Event one: the ball touched the stumps and the bails fell — the question was whether Dottin was out, and if she was, what the equation became. Event two, which decided the match: where the wicketkeeper was at the moment the ball passed the striker's-end stumps. The law watches the second event before the first — meaning your position is fixed before the ball arrives.

The text of MCC Law 27.3 is clear: the wicketkeeper must remain wholly behind the stumps at the striker's end, from the moment the bowler releases the ball until the ball touches the batter or their person, passes the wicket, or the batter attempts a run. 'Wholly' means the entire glove, the entire body, every boot. If any part of you is ahead of the stump line at the moment the ball passes, the delivery is illegal — no-ball, one extra run, and the ball does not count normally.

This law is not new. It is a structure like baseball's batter's box, except the penalty lands on the whole team. And in the last over of a T20, that structure breaks at its fastest rate.

Core: The arithmetic of one foot, and the false story of four wickets

The Renegades' win is recorded as four wickets. A reader scanning the scorecard will assume the Renegades were four wickets better somewhere. I have looked at that scorecard and I can tell you three of those wickets never happened. A four-wicket margin does not mean a four-wicket performance gap — it means a single technical run in a tied contest, created by a legal adjustment on the last ball.

Had there been a Super Over, whose side weighed heavier? The answer is not in the full scorecard. The match was 40 overs; both teams reached the same score, meaning 240 balls of data say the decision is even on both sides. Without data I will not say the Renegades were the better team. I will only say what the footage and the text of the law prove: they got the one run that Hurricanes did not give in their sleep, and it came from a keeper's crouch I cannot measure but can see.

Now Nicola Carey's ball. Commentary called it a 'match-winning dot', and I have no trouble believing the ball was good. It was 'good length' — the zone where the batter must get stuck either forward or back. Dottin's swing and miss was born of that dilemma. But if you believe Carey won the match with that ball, you are attaching the wrong cause to the right result. What Carey did was the full extent of her delivery; what happened was not part of it.

This is where I stop myself. Dottin's one miss does not prove a 'weakness against good length'. One ball, not a pattern. I learned this lesson at a price twice over in the transfer market — one match's sample is not a career's.

Lizelle Lee's question, since you will ask: she caught the ball cleanly, the gloves were there, the bails fell too. Technically nothing looked wrong. The error was not of technique but of position. And this is modern cricket's most overlooked skill — coaches teach the catching and glovework part, but no one drills the 'where to stand' part. In T20, when a keeper moves forward anticipating a stumping — and on the last ball, the instinct pulls them forward with exactly that intent — the legal line falls behind faster than the ball's pace.

I borrowed xG for a summer in 2026 and learned then that football hides some things in plain sight; in cricket, the keeper's line is that same place. On the ground no one saw those last three inches; the TV camera did.

Mirror: The convenience of 'cricket is cruel'

The official WBBL handle called it an 'extraordinary fashion', and the media struck the 'cricket is cruel' note. I agree with both, but I pause at the reason they reached those phrases. The word 'cruel' is usually used when a player plays well and still loses. Here the loss did not follow good play; it came in the moment when the gloves were not in the right place. Getting that distinction to the reader matters, because that is the whole lesson.

And one thing that is souring teeth in both media and social media — it is easy to call Lee the culprit, but no single decision on that ball was wrong. The umpire applied the law, not invented it. The TV review checked both the stumping and the keeper's position. I heard 'this should have been a Super Over' many times during the day — but that is the same as saying an umpiring decision 'should not have been' when it is correct in law. People look at the scoreboard and demand a result; the law looks at the ball first.

What troubles me most is that this incident is being presented as a 'paradox'. It is not a paradox, it is a collision: the visual ball delivery and the law written in long form. One viewer watched the last ball and judged a dot. But a match is read in the language of the law, and in that language this was a very clear, exceedingly rare outcome.

Takeaway: Where will you be on the next last ball?

I will not anoint the Renegades as tournament contenders on the back of this win, nor read the Hurricanes as 'in crisis' from this loss. This is one match, one ball, one law's outcome. But I want to leave a question that should be asked in both bowling and wicketkeeping preparation sessions going forward: if your team is bowling the last ball with scores level, who is tracking your keeper's line?

A coach, a captain, or one person in the dressing room — whose only job is to remind that the whole body is behind the stumps, gloves too, boots too. It seems a very small job. But that night in Melbourne, that job was missed and a four-wicket margin appeared that never existed.

I will keep writing my column. The next time a last ball looks like a Super Over, I will look at the keeper's feet first, then the scoreboard. And if I make the mistake again this time, catch me there. That is the spreadsheet promise — the error visible to all, the correction in public too.