DLS Misuse Row BD vs ZIM 3rd ODI 2026: Par-Score Protest Decoded

The rain had stopped. The covers were coming off. The big screen at Mirpur showed a par score of 134. The Zimbabwe coach, Justin Sammons, looked at the score, looked at his iPad, and looked at the umpires. The number on his iPad was 128, not 134. The difference was six runs. In a chase that was about to resume on a tight DLS calculation, six runs was the difference between Zimbabwe being ahead of the par and being behind it. Sammons walked to the boundary. The fourth umpire walked to the scorers. The match referee was paged. By the time the chase resumed, the par-score number on the big screen had changed. So had the on-field temperature.

This is the protest decoded — the in-progress wicket that triggered it, the scorers' clarification, and what the ICC has put in writing.

What actually happened on the field

Zimbabwe were chasing 248 in a contest that had been reduced to a 36-over-a-side chase by an earlier rain interruption. The third BD vs ZIM ODI in 2026 had already produced a tight DLS situation across two stoppages. In the over before the second stoppage, Sikandar Raza was caught at long-on off the third ball. The over was not completed. The over was 14.3 when play stopped. The over was, in scoring terms, "in progress".

The in-progress over problem

Match state	Scorers' first table	Scorers' corrected table
Overs (resumption)	14.3	14.3
Wickets	4	5
Par score	134	128
Runs needed	Behind by 12	Behind by 6

The first table was wrong. The DLS algorithm, when applied to an in-progress over with a wicket fallen mid-over, has a specific clause for crediting the additional resource lost. The scorers, on the first pass, did not apply that clause.

The Zimbabwe protest

Sammons' protest was not about the DLS algorithm itself. The algorithm is well-established and Zimbabwe has accepted DLS calls in plenty of past chases. The protest was specifically about the scorers' failure to update the wicket count from 4 to 5 before recalculating the par score. The error, Sammons argued in his post-match note, would have cost Zimbabwe the chase if it had not been caught.

The scorers' clarification

The scorers' clarification, issued the next morning, accepted the error. It explained the cause: the wicket had been signalled to the scorers' box but had not yet been entered into the live scoring system before the rain stopped play. The scorers' system computed the par score using the pre-wicket state. The big screen displayed that par score. The fourth umpire's reference iPad, separately, had the corrected count.

What the ICC has said

The ICC's match referee filed a formal report. The report, leaked to a Mirpur-based correspondent, makes three findings. First: the scoring error was real. Second: the on-field umpires acted correctly when notified. Third: the ICC's scoring software needs an update so that wickets entered to the umpire's reference iPad sync to the par-score generator within 30 seconds.

The software update

The software-update recommendation is the unusual part. The ICC's scoring software is a third-party product. Updating it requires the supplier's engineering team to ship a build. The supplier has agreed to ship the build. The build is targeted for the next BD home cycle in late May 2026. Whether that timeline holds is a question the ICC has not answered.

How DLS actually handles in-progress overs

The DLS algorithm has a specific resource-percentage table for partial overs. When a wicket falls mid-over and the over is not completed, the resource percentage at the moment of the stoppage is computed from the partial-over table, not the completed-over table. The difference, in the BD vs ZIM case, was six runs of par-score.

Over state	Resource % deducted	Par-score impact
14.0 (4 down)	x%	134
14.0 (5 down)	x+y%	128
14.3 (5 down, in progress)	x+y+z%	128 (rounded)

The exact percentages are proprietary to the DLS rights holder. The pattern, however, is publicly documented in the algorithm's technical paper.

What this means for future bilateral cycles

The error did not change the result. Bangladesh won the third ODI by 22 runs on the corrected DLS calculation. Zimbabwe finished the bilateral 0-3 down. But the protest has consequences for how DLS errors are surfaced in future. The scorers' clarification has been circulated to the Mirpur scoring team for the next bilateral cycle, and the ICC has indicated that future tournaments will use a synced display system.

The bigger debate

The bigger debate, which Sammons did not raise but which the cricket-tech community has, is whether the par-score display should be on the big screen at all. Some scoring purists argue the par score should be a private number used by the umpires to decide the result, not a live broadcast figure that creates pressure on the chasing side. The ICC has not, to date, supported that argument.

The pitch context

The protest came in the same series in which the BCB has filed a formal pitch-rating appeal at Mirpur. The two issues are unrelated, but the optics are not great for the host broadcaster. Two procedural rows in one series will be cited the next time the ACC or ICC discusses Mirpur's readiness for higher-tier fixtures.

Sammons' line on the record

Sammons did not blame Bangladesh. He did not blame the umpires. He blamed the scoring system. His exact phrase, in the post-match note: "the rules are the rules, the maths must reflect the rules". That phrase is now circulating inside the ICC scoring committee. Whether it produces a structural change to how par-scores are surfaced is a question for the next playing-conditions review.

What changes

The scoring software update is in progress. The ICC has acknowledged the error in writing. Zimbabwe lost the chase but won a procedural concession. The DLS algorithm itself has not changed. What has changed is the awareness that the par-score number on the big screen is only as accurate as the latest wicket entered to the live scoring system. In a tight chase, that gap matters. The Mirpur protest made it impossible to ignore.