Cookie Privacy Preferences
We utilize essential cookies to ensure our website operates effectively and remains secure. Additionally, we'd like to request your permission to use optional cookies. These are intended to enhance your browsing experience by offering personalized content, displaying advertisements that are relevant to you, and helping us to further refine our website.
Choose "Accept all cookies" to agree to the use of both essential and optional cookies. Alternatively, select "Let me see" to customize your preferences.
Privacy Preference Centre
Our website utilizes cookies to enhance your browsing experience and to present you with content tailored to your preferences on this device and browser. Below, you will find detailed information about the function of cookies, enabling you to make informed choices about which cookies you wish to accept. Please note that disabling certain cookies might impact your user experience on our site. It's important to remember that cookie preferences need to be set individually for each device and browser you use. Clearing your browser's cache may also remove your cookie settings. You have the freedom to modify your cookie preferences at any point in the future.
For a comprehensive understanding of our use of cookies, please refer to our complete cookies policy.
These cookies are needed for the website to work and for us to fulfil our contractual obligations. This means they can't be switched off. They enable essential functionality such as security, accessibility and live chat support. They also help us to detect and prevent fraud. You can set your browser to block or alert you about these cookies, but it means some parts of the site won't work.
These cookies allow us to measure and improve the performance of our site. They help us to know how popular pages are, and to see how visitors move around the site. If you don't allow these cookies, we won't know when you've visited our site, and we won't be able to monitor its performance.
These cookies enable us to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we've added to our pages. If you don't allow these cookies, some or all of these services may not work properly.
These cookies collect information about your browsing habits to show you personalised adverts. They may be used to build a profile of your interests and show you relevant adverts on other sites. They don't store directly personal information, but are based on uniquely identifying your browser and internet device. If you don't allow these cookies, the adverts you see will be less relevant.
The Greater Manchester Cricket League | Est 2016 | an accredited ECB Premier League
Mobile
Tablet
WELCOME TO GMCL FOR YOUR MOBILE
GMCL Rules Reviewed & Updated February 2024 |
SECTION G - WEATHER AFFECTED MATCHES | |
G (a) | This section of the rules gives details on what to do when the weather intervenes in your game |
18. | Duckworth Lewis Stern (D/L/S) scoring for weather interrupted matches |
18 (a) | This section of the rules looks at how the Duckworth Lewis Stern method helps determine results in rain affected matches in GMCL competition |
Choose tab and scroll to see results
GMCL Rules Reviewed & Updated February 2024 |
18.1. |
What is D/L/S? |
|
18.1.1. |
D/L/S is a system used in cricket to determine a result to games affected by weather |
|
18.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 |
|
18.1.1.2. |
D/L/S takes into account |
|
18.1.1.2.1. |
how many overs have been used up, |
|
18.1.1.2.2. |
how many wickets have been lost and |
|
18.1.1.2.3. |
also adds different weighting values to overs at different part of the innings |
|
18.1.1.3. |
The professional version of D/L/S is built in to the cricHQ app and any third party D/L/S calculation system should not be used. |
|
18.1.2. |
D/L/S is made up of two elements
|
|
18.1.2.1. |
A D/L/S Revised Target will be calculated for the team batting second to chase |
|
18.1.2.1.1. |
Where overs are lost during either innings after the start of the match |
|
18.1.2.2. |
The D/L/S Par score comes into play. |
|
18.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. |
There is more on the practical use of DLS here https://www.gtrmcrcricket.co.uk/pages/dls
GMCL Rules Reviewed & Updated February 2024 |
18.2. |
How does D/L/S work? |
|
18.2.1. |
D/L/S Revised Target(This section updated Winter 23/24) |
|
18.2.1.1. |
Overs Lost during the first innings |
|
18.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. |
|
18.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. |
|
18.2.1.1.3. |
The Revised Target will be shown on the cricHQ App when restart is activated after the break between innings. |
|
18.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. |
|
18.2.1.2. |
Overs Lost during the second innings |
|
18.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. |
|
18.2.1.3. |
Displaying the Revised Target on the scoreboard |
|
18.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. |
|
18.2.1.4. |
To win the game the side batting second needs only to equal the Revised Target. |
|
18.2.1.4.1. |
Scoring one less than the Revised Target creates a Tie |
|
18.2.2. |
D/L/S Par Score |
|
18.2.2.1. |
A “Par Score” will be shown on the cricHQ app after every ball bowled in the second innings. |
|
18.2.2.1.1. |
The Par Score will only come into play if the game ends abruptly due to weather or bad light. |
|
18.2.2.1.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. |
|
18.2.2.1.3. |
The Par Score should be |
|
18.2.2.2. |
What is the Par score? |
|
18.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. |
|
18.2.2.3. |
How is Par Score used? |
|
18.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 cricHQ App. |
|
18.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. |
|
18.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 |
|
18.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 |
|
18.2.3. |
D/L/S examples |
|
18.2.3.1. |
These are for guidance only and not to be used in games |
|
18.2.3.1.1. |
Where Team A batting first has innings ended at 25 overs when they are 100 for 2 |
|
18.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 |
|
18.2.3.1.1.2. |
Team B batting second will be chasing a Revised Target over 160 if they have 25 overs |
|
18.2.3.1.2. |
Where Team A batting first has innings ended at 25 overs when they are 100 for 8 |
|
18.2.3.1.2.1. |
They have lost all of their highest scoring overs but also lost most of their wickets. |
|
18.2.3.1.2.2. |
The side batting second will only be chasing a Revised Target of around 80 if they have 25 overs |
|
18.2.3.1.2.3. |
This seems low but after batting poorly, Team A have to bowl better than their opponents to win. |
|
18.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. |
|
18.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 on this calculation |
|
18.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. |
|
18.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 |
|
18.2.3.1.4.2. |
The target is higher because of the early loss of wickets at the start of the 2nd innings. |
|
18.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. |
|
18.2.3.1.5.1. |
With 3 wickets lost the DLS Par off Team B's 30 overs is 89-3 so they needed 90 to win, so Team B win. |
|
18.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. |
|
18.2.3.1.6.1. |
With 7 wickets lost the DLS Par off Team B's 30 overs is 137-7 so they needed 138 to win, so Team A win. |
GMCL Rules Reviewed & Updated February 2024 |
18.3. |
How is D/L/S operated? |
|
18.3.1. |
Scorer Requirements |
|
18.3.1.1. |
D/L/S relies on the scorer correctly entering all match delays and interruptions and accurately recording the game scores. |
|
18.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. |
|
18.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. |
|
18.3.2. |
Scoreboard requirements |
|
18.3.2.1. |
A Revised Target must be displayed on the scoreboard as soon as it comes in to play. |
|
18.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. |
|
18.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, |
|
18.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). |