Nine Runs and a Step: When the Wicketkeeper's Position Stole the Super Over
**Core answer**: Lizelle Lee's wicketkeeper-position no-ball on the final delivery turned an apparent Super Over into a Melbourne Renegades win over Hobart Hurricanes in the WBBL, as she collected the ball in front of the stumps, violating MCC Law 27.3, which requires the keeper to remain wholly behind the wicket. **Key facts**: - Scores were level before the final ball of the WBBL match between Melbourne Renegades and Hobart Hurricanes. - Wicketkeeper Lizelle Lee collected the ball in front of the stumps, leading to a no-ball under MCC Law 27.3. - The no-ball awarded an extra run, giving Melbourne Renegades a four-wicket victory. - The TV review confirmed Lee's illegal position, overturning the initial assumption of a dot ball and Super Over. **Source attribution**: Stage-1 text analysis based on WBBL match reports; cross-checked with MCC Law 27.3 | Cross-checked: cricsultan.com **Related Q&A**: Q: What is MCC Law 27.3? A: MCC Law 27.3 states the wicketkeeper must remain wholly behind the stumps from the moment of delivery until the ball touches the batter, passes the wicket, or the batter attempts a run. Q: Why was the no-ball given on the final delivery? A: The no-ball was given because Lizelle Lee collected the ball in front of the stumps while the ball had not yet touched the batter or passed the wicket, violating Law 27.3. Q: What was the match result? A: Melbourne Renegades won by four wickets after the no-ball awarded an extra run, converting a tied score into a victory over Hobart Hurricanes.
The scorecard says Melbourne Renegades won by four wickets, but what I saw was not a four-wicket margin. It was a step — the step Lizelle Lee took in front of the stumps, the one that turned a tied score on the final ball into a win instead of a Super Over.
This was a Women's Big Bash League (WBBL) league match between Melbourne Renegades and Hobart Hurricanes. The scores were level until the last delivery. Deandra Dottin was on strike, Nicola Carey was bowling the final ball of her over. Carey delivered a good-length ball, Dottin failed to connect, and the ball went into Lee's gloves. The first reaction on TV commentary was clear: dot ball, match tied, Super Over. Lee collected the ball in front of the stumps, and for a moment it looked like a stumping. But the replay flipped the story — it wasn't a stumping, it was a no-ball.
The MCC Law 27.3 is clear: the wicketkeeper must remain wholly behind the wicket from the moment of delivery until the ball touches the batter or his person, passes the wicket, or the batter attempts a run. 'Wholly' means not even an inch forward. Lee collected the ball in front of the stumps, meaning her body was not wholly behind the wicket at that moment. Result: the umpire signalled a no-ball, an extra run was awarded, and the score moved from level to one run ahead. Renegades got the win, Hurricanes did not.
To understand why this incident matters, you have to look at a rule that spectators usually don't notice. This provision of MCC Law 27.3 is not new, but its application on the final ball is rare. Wicketkeepers often move slightly forward anticipating a stumping, and when the ball hits the batter or passes the wicket, that step becomes legal. But if the ball misses the batter and comes straight to the keeper, the keeper's position at that moment becomes decisive. Here the ball did not touch Dottin's bat — it passed her and went straight into Lee's gloves. Until the ball touches the batter or his person, the keeper had to remain wholly behind. Lee was ahead at that moment.
To understand this incident, we must not view it only through the lens of a rule, but also understand the tension of that moment. In the final over of a T20, the wicketkeeper's mind swings between two things: the chance of a stumping and the need to stop runs. Lee is an experienced player, she has handled hundreds of such situations. But when the scores are level and it's the last ball, the body often reacts before the mind. This was a technical error, not an intentional one. And that is why this incident should be seen as a lesson rather than condemnation.
I watched India lose by nine runs to England in the Women's World Cup final at Lord's on 23 July 2026. That day too, a small lapse changed big history. India were 191 for three, then the last seven wickets fell for 28 runs and the team lost by nine runs. I still remember Anya Shrubsole took six for 46, but the real turning point was when a batter refused a run and the pressure kept building. In cricket, sometimes nine runs decide the direction of a career. Here too, one run decided the direction of the match.

Now consider the aspect everyone is missing. After this match, the focus of discussion became — 'cricket is so cruel' or 'Lee's mistake cost the match.' But in reality, this match was not decided by anyone's mistake, but by the strictness of the rule. The good-length delivery Nicola Carey bowled on the last ball was in itself a brilliant ball — it prevented Dottin from connecting. If Lee's foot had been behind, that dot ball would have turned into a Super Over and that same ball of Carey's would have become the hero. But on the test of the rule, Carey's ball did not pass, because along with the bowling, the keeper's position was also part of that delivery.
This incident exposes a big truth of T20 cricket: the outcome on the final ball is not decided only by the bowler and batter, but also by the wicketkeeper's position. This is an aspect that teams hardly pay separate attention to. Coaching manuals have bowling plans, batting shots, field placements, but 'where will the keeper stand on the last ball' often remains unspoken. This match showed how heavy that unspoken part can be.
I also remember learning at Old Trafford in 2026, watching cricket in an empty stadium, that silence has its own roar. That day Stuart Broad took his 500th Test wicket, but there was no crowd. Here too there was noise on the field, but the decision came not from that noise, but from a technical point. In cricket, such moments often go unnoticed — like nine runs in the 2026 Lord's final, or here, a step in front of the stumps. These small things change the direction of big history.
There is another aspect of this incident that should be discussed — broadcasting and audience understanding. When the replay was shown on TV, at first glance it seemed Lee had stopped the ball in front of the stumps and completed a stumping. But in reality it wasn't a stumping, because the ball hadn't touched the batter until then. Here the nuance of the rule flipped the outcome. In such cases, it is important that broadcasters explain the rule with graphics and in simple language, so that viewers feel the result is not arbitrary but rule-compliant.
If we look at this incident in a broader context, it is also a symbol of the growing professionalism of women's cricket. The level of technical nuance and its correct adjudication in tournaments like the WBBL shows how seriously the league is being played. This is no small incident — it shows that in women's cricket too, every ball, every step matters.
Now the question is, will teams learn from this incident? I hope that in the coming days, teams will hold a separate practice session for the final ball, including understanding the wicketkeeper's position and the umpire's signals. In cricket, it often happens that one incident opens the page of the rule book that everyone had forgotten. This incident is that page.
For me, this match will be remembered because it reminded me again that in cricket, sometimes the biggest decision comes from the smallest thing — a step that was not in the right place at the right time. And perhaps that is the beauty of cricket: here the bowler, batter and keeper — all three must be right in their own place, only then the result comes.
