Tim David Fined for Refusing to Hand Ball to Umpire — Twice in the Same Match

Ball-retention is a minor but recurring issue in franchise T20 cricket. The phenomenon has a straightforward tactical logic: in the death overs of an innings, a fielder who holds onto the ball after the umpire calls a ball change can slow the restart sufficiently to disrupt the batting side's rhythm, give the bowling captain a moment to reset field placings, or — at worst — allow the bowling team's management to relay instructions from the dug-out. None of these are expressly prohibited by the Laws, but they are procedurally non-compliant when the umpires have formally called for the ball.

Article 2.4 targets this behaviour directly. Its application against a batter — rather than a fielder — is less common, because batters do not typically handle the match ball. David's situation arose because he was involved in fielding at the time of both ball-change calls. The procedure requires any player in possession of the ball to hand it to the on-field umpire on request; the fact that the player is primarily a batter does not change the obligation.

RCB batter Tim David received a Level 1 Code of Conduct charge after the IPL 2026 match between Mumbai Indians and Royal Challengers Bengaluru at the Wankhede Stadium in April 2026, having failed on two separate occasions in the same innings to comply with an umpire's instruction to hand over the ball.

The first incident occurred at the 17.2 over of RCB's batting innings, when the umpires decided to change the ball under the IPL's standard ball-change procedure. Ball changes in T20 cricket are routine: the umpires call for the match ball, inspect it, and may request a replacement if the ball has lost its shape or surface condition in a way that makes it unfit for play. David, who was fielding near the bat at the time, had the ball in his possession. The umpire requested it. David held onto it, apparently wanting to inspect the replacement ball or simply slow the process, and did not comply with the request despite being asked multiple times.

The second incident came in the 20th over (at 19.2), under nearly identical circumstances. Again David retained the ball after the umpires called for it. Again he did not hand it over when requested. The match officials noted both incidents in their reports.

Article 2.4 of the IPL Code of Conduct covers "disobeying an umpire's instruction during a match." The provision exists to ensure that umpires can manage ball changes, over-rate compliance, player positioning and similar procedural matters without fielding players using ball retention or other forms of non-compliance as tactical tools. A single offence under 2.4 is a Level 1 breach; two occurrences in the same match, as here, still constitute a single Level 1 charge rather than escalating to Level 2, but they demonstrate a pattern that influences how the match referee characterises the conduct.

David accepted the charge and the sanction of 25 per cent of his match fee plus one demerit point.

“Tim David has been fined 25% of his match fee after being found guilty of breaching Level 1 of the IPL's Code of Conduct for Players and Team Officials.”

The charge received relatively modest media attention — a 25 per cent fine and one demerit point is among the lighter sanctions available under the IPL Code — but it added to the accumulating picture of RCB's discipline record in IPL 2026. David's demerit point was the first of his IPL career. With four points in a 24-month rolling period triggering a match ban, David remained well clear of that threshold.

Commentators noted that ball retention is easier to get away with in T20 cricket than most other procedural non-compliance, because the umpire's call for the ball is verbal and off-microphone. The David case was notable precisely because the umpires had documented it as a repeated instruction in their match report, elevating it from an informal exchange to a formal Code breach.