Rules-5-2

5.2. WEATHER AFFECTED MATCHES & D/L/S

This section of the rules looks at how the Duckworth Lewis Stern method helps determine results in rain affected matches in GMCL competition

In weather affected matches and rules relative thereto the following shall apply: (revised 2025)

Grace Period – in league matches in all Saturday divisions, the umpires shall permit a cumulative period of 30 minutes delay or interruption to the game (whether at the start or during a game, and whether in one or more occurrences) before there are any overs reductions.

Example 1: a Saturday Championship league game due to start at 1230pm is delayed by weather until 1250pm. The game starts at 1250pm and a full 50 over game can continue

Example 2: a 50 over league game is due to start at 1230pm. It is delayed due to weather by 15 minutes until 1245pm. The game then starts at 1245pm and is still a 50 over game. During the first innings however, there is a further weather delay of 75 minutes (so the game has been delayed by 90 minutes in total). At that point the number of overs in the game is reduced as follows, namely 90-30(grace) = 60 minutes = 8 overs per side, a 42 over game.

Any Grace Period shall be counted in calculating time allotted and scheduled time for an innings cessation for the purposes of the slow over rate rules.

Minimum Overs – 

in Saturday League matches the minimum is 20 overs per innings, 

In Sunday League matches the minimum is 15 overs per innings (new for 2025 season)

in Cup matches the minimum is 10 overs per innings,

in GMCL20 the minimum is 5 overs per innings.

5.2.1. What is D/L/S?

5.2.1.1. D/L/S is a system used in cricket to determine a result to games affected by weather

5.2.1.1.1. Duckworth Lewis Stern (D/L/S) is an internationally approved method to determine a result in a weather affected limited over cricket match, based on resources available against runs required and generally considered an accurate way of testing both sides

5.2.1.1.2. D/L/S takes into account

5.2.1.1.2.1. how many overs have been used up,

5.2.1.1.2.2. how many wickets have been lost and

5.2.1.1.2.3. also adds different weighting values to overs at different part of the innings

5.2.1.1.3. The professional version of D/L/S is built in to the Play Cricket app and any third party D/L/S calculation system should not be used.

5.2.1.2. D/L/S is made up of two elements

5.2.1.2.1. A D/L/S Revised Target will be calculated for the team batting second to chase

5.2.1.2.1.1. Where overs are lost during either innings after the start of the match

5.2.1.2.2. The D/L/S Par score comes into play.

5.2.1.2.2.1. Where the second innings comes to an early end due to bad weather or bad light after the Minimum Overs for the competition or  more have been played.

5.2.2. How does D/L/S work?

5.2.2.1. D/L/S Revised Target

5.2.2.1.1. Overs Lost during the first innings

5.2.2.1.1.1. After the start of the game (or application of the Grace Period if it applies to the match in question),where weather interrupts the first innings on one or more occasions AND overs are lost, D/L/S will provide a revised target for the team batting second at the start of the second innings. 

5.2.2.1.1.2. Each break in play and the overs lost must be recorded on the scoring app at the resumption after each break in order that the revised target is calculated correctly. 

5.2.2.1.1.3. The Revised Target will be shown on the Play Cricket App when restart is activated after the break between innings.

5.2.2.1.1.4. The revised target will be a whole number and may be higher or lower than or equal to the first innings score.

5.2.2.1.2. Overs Lost during the second innings

5.2.2.1.2.1. If overs are lost during the second innings the Revised Target for the second inning after resumption of play and shown on the scoring app.

5.2.2.1.3. Displaying the Revised Target on the scoreboard

5.2.2.1.3.1. The D/L/S Revised Target must be posted on the scoreboard throughout the second innings and updated after any further delay.

5.2.2.1.4. To win the game the side batting second needs only to equal the Revised Target.

5.2.2.1.4.1. Scoring one less than the Revised Target creates a Tie

5.2.2.2. D/L/S Par Score

5.2.2.2.1. What is the Par score?

5.2.2.2.2.1. The Par Score will be a whole number and is calculated to reflect where a team should be with the number of balls used from the number available and from the number of wickets lost to be on target to meet the score needed.

5.2.2.2.2. A “Par Score” will be shown on the Play Cricket app after every ball bowled in the second innings.

5.2.2.2.2.1. The Par Score will only come into play if the game ends abruptly due to weather or bad light.

5.2.2.2.2.2. The Par Score should be updated after every ball on electronic scoreboards linked to the app or updated at the end of the over on traditional scoreboards.

5.2.2.2.3. How is Par Score used?

5.2.2.2.3.1. To determine the result, the actual score and the par score are compared after the outcome of the last ball bowled has been entered into the Play Cricket App.

5.2.2.2.3.2. At the point of an abrupt ending, a 2nd innings score (after more than the minimum overs have been faced) above par is a win for the team batting second, equal to par is a tie, below par is a loss for the team batting second.

5.2.2.2.4. The benefit to both sides is that they can see the trend in where they stand as the Par score changes after each ball or each over

5.2.2.2.4.1. but remember that the actual comparison for a result can only be made after the last ball is bowled and not the par at the end of the previous over

5.2.2.3. D/L/S examples

5.2.2.3.1. These are for guidance only and not to be used in games

5.2.2.3.1.1. Where Team A batting first has innings ended at 25 overs when they are 100 for 2

5.2.2.3.1.1.1. They have lost all of their potential highest scoring overs at the end of their innings with lots of wickets available

5.2.2.3.1.1.2. Team B batting second will be chasing a Revised Target over 160 if they have 25 overs

5.2.2.3.1.2. Where Team A batting first has innings ended at 25 overs when they are 100 for 8

5.2.2.3.1.2.1. They have lost all of their highest scoring overs but also lost most of their wickets.

5.2.2.3.1.2.2. The side batting second will only be chasing a Revised Target of around 80 if they have 25 overs

5.2.2.3.1.2.3. This seems low but after batting poorly, Team A have to bowl better than their opponents to win.

5.2.2.3.1.3. Where Team A batting first scores 175-6 off 50 overs and Team B only has 30 overs after a delay in the restart.

5.2.2.3.1.3.1. Team B batting second will be chasing a Revised Target around 130 off 30 overs, the wickets lost in the first innings have little impact because they are neither high or low.

5.2.2.3.1.4. Where Team A batting first scores 175-6 off 50 overs and Team B bats 10 overs scoring 50-3 but then lose 20 overs and only has 20 overs available after the restart.

5.2.2.3.1.4.1. Team B batting second will be chasing a Revised Target of around 140 off their 30 overs, the wickets lost in the first innings have little impact on this calculation because they are neither high or low.

5.2.2.3.1.4.2. The target is higher because of the early loss of wickets at the start of the 2nd innings.

5.2.2.3.1.5. Where Team A batting first scores 175-6 off 50 overs and Team B bats 30 overs scoring 125-3 but then the game is rained off.

5.2.2.3.1.5.1. With only 3 wickets lost the DLS Par for Team B's 30 overs is 89 so they needed 90 to win, this has already been reached so Team B win.

5.2.2.3.1.6. Where Team A batting first scores 175 -6 off 50 overs and Team B bats 30 overs scoring 125-7 but then the game is rained off.

5.2.2.3.1.6.1. With 7 wickets lost the DLS Par for Team B's 30 overs is 137 so they needed 138 to win, so Team A win.

5.2.3. How is D/L/S operated?

5.2.3.1. Scorer Requirements

5.2.3.1.1. D/L/S relies on the scorer correctly entering all match delays and interruptions and accurately recording the game scores.

5.2.3.1.1.1. If the scorers do not correctly record interruptions at any point of the game for any interruption, the Revised Targets and Par Score will be wrong.

5.2.3.1.1.2. It is imperative that the Umpires communicate with scorers to verify overs lost and check that the scoring app has been updated before every restart.

5.2.3.2. Scoreboard requirements

5.2.3.2.1. A Revised Target must be displayed on the scoreboard as soon as it comes in to play.

5.2.3.2.1.1. We recommend that all clubs, whether they have electronic scoreboards, flip numbers or tins look for solutions around their own scoreboard functionality to display “Revised Target” alongside the first innings score and be ready to amend this should overs be lost.

5.2.3.2.2. Where the “Par Score” is likely to be relevant (in that weather is threatening and so the game may come to an abrupt end) or the umpires or batter request it,

5.2.3.2.2.1. all clubs must be able to share the D/L/S Par at the end of each over on the scoreboard (or the ultimate solution to display it after each ball).