Cricinfo blogs
cricinfo.com About cricinfoblogs
Beyond The Blues Beyond The Test World Different Strokes From the Editor Girls Aloud Iain O'Brien Inbox
It Figures Pak Spin Shot Selection The Buzz The Confectionery Stall The Surfer Tour Diaries
Cricinfo
Cricinfo Blogs Home
Different strokes

« Merry Quizmas | | South Africa is the new Australia »

December 28, 2008

Posted by Michael Jeh on 12/28/2008

Over-rate blues



I read last week that the Bengal tiger is enjoying a brief period of renaissance but it’s long term prospects are still bleak. Likewise Test cricket. The Border-Gavaskar Trophy was riveting at times but was also dogged by slow over-rates and accusations of negative tactics.

Recent series’ involving New Zealand have done little to spark interest either side of the Tasman whilst at the same time, Chennai and Perth produced two of the finest Tests ever witnessed. All of a sudden, everyone was buzzing again. Then along came the Mohali Test and killed off that brief excitement. That last day was a knife through the heart of Test cricket.

What is clear to Blind Freddy though (although not quite as obvious to the ICC) is that we have a major problem with over-rates. It’s almost taken for granted now that we will use up the extra half hour each evening and even then, the 90 overs are often not completed. Even with spinners operating, this problem remains constant.

Cricket now operates in the ‘entertainment’ industry. If you keep cheating the public of value for money, they will vote with their feet (or remote controls). Cricketers keep talking about the value of Test cricket but their actions sometime belie the rhetoric.

There are a number of reasons why this should not be happening.

1. Cricketers are fitter now than they have ever been. They have no other job except cricket. Why are they not fit enough to get through 90 overs in six hours without dragging their feet? They expect to be treated (and paid) like professionals but they do not seem capable of fulfilling their jobs in the allotted time. Remember, 90 overs in a day is the minimum. They're not even meeting minimum workplace standards!

2. Most field placings and strategies are worked out well in advance. Each team has an army of computer boffins and coaches who justify their existence by planning everything down to the last detail. Why then do captains waste time discussing minor field alterations with the bowler? Surely most of this has already been mapped out?

3. Umpires and match referees seem to wait until the last hour to start chivvying the fielding team into catching up. Do they not realise that it’s a day-long exercise that is best managed throughout the day? Some suggest the answer lies in the fielding team having one less fielder for each over that they failed to bowl in the previous session. Unfortunately, that will corrupt the integrity of the contest and is a brave but ultimately futile suggestion.

I’ve been watching Ricky Ponting these last few weeks and his captaincy style contributes to this malaise. Instead of making changes from second slip, he trots over to the bowler, has long discussions, makes minor alterations and trots back. Was this not already discussed at the team meeting? Was it something different to the print-out provided by the coaching staff?

Particularly galling is when captains waste long minutes, setting the field at the start of the session. Surely they knew which batsman was on strike? They must have known the plan of attack before they walked out on the field. Why was this not discussed in the dressing room?

Most international captains have similar tendencies. In an era where the computers make more decisions than the on-field captain, it is hard to understand why they take so long to set a field to a batsman whose every shot has been dissected to the nth degree in the team meeting.

Why is it that it takes repeated breaches before the ICC will take any action on the matter? Think about a speedtrap or speed camera – no warnings – if you break the law, you pay the penalty. No multiple warnings.

When they eventually get punished, the ICC levies small fines, relative to their millionaire salaries. It is a pointless exercise and it does not work. The only language they understand is suspension. The Nagpur Test proved that – faced with suspension, Ponting was prepared to compromise the result for a new-found conscience. Dhoni was no better – on that last day in Nagpur, when Hayden was mounting an unlikely chase, they bowled just 23 overs in the entire first session.

In wildlife conservation, gamekeepers turned poachers can be the most destructive enemies of the beasts they were meant to protect. Test cricket faces a similar challenge to the majestic tiger - both need protection from greed.

 
Feedback Feedback

Comments

Posted by: David Morrison at December 28, 2008 8:17 AM

Easy way to solve the problem. At the end of each session and the scheduled close of play the Match Referee and 4th umpire allocate responsibility for how far behind the required number of overs (30 per session without weather interruption) play is. If the bowling side is responsible for a three over shortfall, the first three overs of the next session are 'free' overs to the batting side, with same rules to the free hit in place for one day internationals. If the side responsible for the shortfall is the batting side, they are essentially 'free' overs to the bowling and fielding side ie the batting side cannot score any runs for the same number of overs. This would be on top of any scale of match fees and suspension the Match Referee has it in his power to impose.

It sounds ridiculously artificial and contrived but a side would not bowl 25 overs in a session if they knew it meant the first 5 overs of the next session would be free runs for the opposition!

Posted by: Richard Heller at December 28, 2008 8:44 AM

When I first started watching Test cricket in the 1950s (yes, that makes me 60+) I expected to see 20 overs an hour and 120 in the day. When spinners bowled maidens in tandem you could get 25 or more in an hour. An obituary of the great Alf Valentine said that he bowled a Test maiden in less than 90 seconds. Of course those sorts of over rates would be bad for commercial breaks on TV, and it is TV that drives the modern game.

Posted by: AP at December 28, 2008 9:54 AM

David Morrison's Free overs suggestion is very interesting, and certainly worth a try. But what if the team falls behind in bowling the free overs? (This is very likely because captains will take even more time during the free overs, especially if aggressive batsmen like Sehwag or Flintoff are batting)

Posted by: Sagar Sanghvi at December 28, 2008 9:56 AM

Another reason why captions and teams go with lighter fines are extra minutes added for wickets and drinks breaks in calculating over-rates. I have heard on commentary, that 2 minutes are added for every wicket and 4 minutes for drinks break. That essentailly means, in a day with 10 wickets, they would get about 32 minutes extra for bowling their overs (20 for wickets, 12 for 3 drinks breaks). This essentially takes the whole of extra half an hour. And we have 6 1/2 hour day. Add time for 3rd umpire referrals, 'unofficial drinks break' and batsmen, fielder changing equipments, fielding sides rarely gets punished.

And hence captians are not punished heavily, as they are let of with monetary fines only, since only 2 offences of 5 overs not bowled leads to ban of caption.

If nothing else, calculation for over-rate can be tighter with stricter definition of law and punishment.

contd ...

Posted by: Sagar Sanghvi at December 28, 2008 9:58 AM

Contd...

Another point that I wanted to ask was whether 'heat and humidity' should be a factor in calculating the over-rate. If yes, how can it be reasonably applies. Also, are there any other factors considered while calculating the over-rate.

Posted by: Tarun at December 28, 2008 10:28 AM

Yeah I agree with richard.
I think players tend to be wasting 6-8 overs thats hell lot of an air time.

Posted by: John S at December 28, 2008 10:45 AM

If the fielding team aren't bowling their allotted overs, the batting team should get extra runs for the overs they should've faced (i.e. the "lost" overs), without taking the number of wickets lost into consideration. For example, if a team scores 255 in a day's play with only 85 overs bowled (run rate = 3.00), they should be given an extra 15 runs which, on average, they would've gotten had they faced the 5 overs that should've been bowled to them on the first place. These should count as penalty runs against the bowling side, and should also reward quick run-scoring (which is more exciting Test cricket to many) if the fielding team should fail to meet their over quota.

Posted by: bluerpk at December 28, 2008 11:41 AM

I think over rates are an overrated problem (sorry about that). The blame for the Mohali test is surely to be placed at the authorities for scheduling it there in spite of knowing that Mohali, as well as other test centers in North India, would be severely affected by fog and short days. Surely other centers, like Bangalore, Hyderabad or Kolkatta could have been employed.

Another point is how people say that the last Mohali test kills test cricket when there is no mention of the Ind/Aus Nagpur test. Ponting's "tactics" to speed up the overrate did more to kill off test cricket by robbing an absorbing contest. I think the spirit of any sport is that all teams would strive to win (or draw if that is not possible) at all times. When a team like Australia does not do it when there was a distinct possibility, it does a lot of harm.

Disclaimer: This comes from an Indian supporter. Even to me it was plain obvious that the tactics resulted in India escaping making the result frivolous.

Posted by: Andrew at December 28, 2008 1:45 PM

Simple way to get over rates up. At the end of the days play for every over the bowling team are behind the over rate fine them 10 penalty runs per over. These penalty runs to be added to the batting sides score, That would increase over rates dramatically.

Posted by: Atul at December 28, 2008 2:25 PM

This is regular problem now with all teams, so it has to do with the lot many things. Batting has improved and ball reaches boundry far tom many times. There are awful less maidens in test these days compared to when it was invented or say in 50s, 60s.. 90 over a day is asking bit more. I this its time it goes down a bit in number of overs, but then I agree with the fine systemm monetory fine are useless. Ban captains from matches is best way...Overall Good writup MIke..

Posted by: Nish at December 28, 2008 5:14 PM

Perhaps 90 overs is too many? Reducing it to something more manageable like say 84 overs would be a good idea.

Posted by: Blanch at December 28, 2008 5:33 PM

It seems you all would have captains in an untenable position these days! It's clear that there are fewer dot balls and more boundaries in modern play, requiring longer overs. However, if a captain (fearing a fine or suspension) plays spinners in a holding role he is accused of unsportsmanly behaviour or not playing within the spirit of the game. We must all accept that it longer in the modern game to play through 90 overs, with drinks breaks, intervals, fewer maidens and field changes than it has done in previous years. The solution? Instead of sacrificing the spirit of the game with penalty runs or suspension of the captain, perhaps it is time to accept that 6 hours a day is not enough time to play a test, and play needs to start earlier.

Posted by: R Sivasubramaniam at December 28, 2008 7:01 PM

There was a time when 20 overs per hour was the norm and I am told that when the Don scored over 300 runs in a day at Leeds, England were bowling at an average of 23 per hour.
While the number of overs has progressively decreased, the money we pay to watch has increased, overall therefore, the cricket watching public are paying more to watch less! And then we moan that less people are watching Test Cricket.

Don't tell me that the pre-war cricketers were fitter than the current genertion.

The solution, raise the penalty for low over rates. It should be 5 percent for every over below the quota. Hit them where it hurts - just like the free hit has reduced the number of no-balls in ODIs

Posted by: Clive Jackson at December 28, 2008 10:06 PM

This business of slow over-rates is just bunk. It is a solution waiting for a problem. This whole idea about overs per hour was just developed at a time when West Indies with their four fast bowlers dominate the world. This was just a ploy to blunt them because the powers that be (Australia and England) could not compete with them. What is all the fuss about? How many test matches these days are ending in predictable draws like when was a boy In the 1970's? Not many. So if we were getting the establishe 90 overs per day most Test matches would end in three days. People would still miss two days of cricket and the various boards would cry foul. Let the game remain,let the captains, captain by whatever he wants to do on the field. This is one of the charms of the beautiful game. Too much reliance on computers, team meetings and off field stuff. Let the game be played on the field. Too much tampering with the game. It seems some people get their kicks from messing with the game. Just coo

Posted by: jalps at December 28, 2008 10:39 PM

Firstly, for John S and Andrew, see law 42 parts 9 and 10. Essentially, if their is time wasting by either side then 5 penalty runs are awarded to the opposition. What is the point in having this law if it's never used?

Personally I would take a less match changing approach. How about allotting time for each delivery, accounting for drinks breaks and likely wickets, and put a count down on the big screen that's present at most matches. During the allotted time it counts down in green but as the time runs out it turns red. You may even be able to get the fans to get a slow hand clap going. By putting the responsibility on individual balls you'll see exactly where the problem lies, be it Ricky spending five minutes moving fine leg slightly squarer or Nasser stepping away from the crease because a fly flew across the sight screen.

Posted by: Simon at December 28, 2008 11:50 PM

Have to agree with Atul, there's a lot said about the slower over rates, but comparing to the times when spinners would bowl maidens in tandem isn't helpful, as that simply doesn't happen any more. The average run rate for test teams has gone up by more than 1 run per over in the last 30 years, which in 90 overs 90 or more runs. Boundaries add a lot to the time it takes to bowl an over, and even normal runs add a lot more than a dot ball. If each additional run adds 10 seconds, then 90 runs is 900 seconds. 15 minutes. Add to this the drinks breaks that didn't used to happen, and you easily make up for the shortfall in modern test cricket. I regularly go to test matches, and would much rather see both teams playing as well as possible rather than a few extra overs at the expense of performance.

Posted by: Westy at December 29, 2008 12:41 AM

It was interesting attending day 2 of the Boxing Day test in Melbourne. There are delays caused by both the batting and bowling teams. Players seeking new gloves twice in an hour including the over before the drinks break (Michael Clarke), players not keeping their eye on the captain between balls for field changes (Michael Hussey), throwing the ball back to the keeper most balls (most of the Australian team), drinks coming onto the field every time there was a wicket.
At least we didn't have a sightscreen malfunction (for once). Just keep them white all day.
Imagine how few overs would be bowled if the players didn't jog between overs.

Posted by: Matt Jones at December 29, 2008 2:24 AM

Equal division of 90 into 30 over session for regulating overrate would kill cricket with no tactics to employ. Another solution could be
Min 20 at session 1 end, min 50 at session 2 end and 90 (85 is could do lot of good to cricket) at session 3 end. Add runs to batting team for each session 1 and 2 in next session and bans fine if its end of the inning / gmae or whatevver...

Ciricket was a simple game making it complicated will be bad idea I simply think making it 85 over game a day would do a great deal of things.

Mohali was blumder schedule. Add to it decision of not using lights, Lunch break not flexile at all. well when you see that fog is foggoing almost till hour befoire lunch, have anounce ment of 2 session play with no lunch, player coul dhave had lunch before they start.

Posted by: Dan de V. at December 29, 2008 4:05 AM

I wholeheartedly agree that over rates should be monitored closely and enforced. How? I am not sure. Though I see some good suggestions have been made and each should be trialed and refined with practice to come up with something that works. I am sure it will not be perfect but it will be better than nothing (like Duckworth-Lewis ;o).
As an avid west indian supporter it makes me smile to see this problem is a global one many years after WI cricket was heavily criticised for slow over rates at the height of their dominance...check teh over rates and you will see they were still generally over 15 overs per hour! People complained because it was less than 20!

Posted by: Michael Jeh at December 29, 2008 5:00 AM

Wow, some really interesting suggestions. Really got me musing on the various options. Thanks everyone for the sensible words and the lateral thinking.
Re the Mohali Test, I'm not denying the fog, bad weather etc. I was just keen to see India win another Test and I was surprised to see them take such a conservative approach. There's no way England could have chased that total against the quality Indian attack.
Back to the over-rates issue though, I still think the cricketers need to take more responsibility themselves. Even the batsmen spend far too much time stretching, squatting, patting down pitch, asking for gloves, drinks etc. The time wasted by all players is at odds with their so-called "super fit" status as elite athletes. Mind boggling to think that when Australia chased 400+ at The Oval (Bradman's era), England bowled 120 overs AFTER batting a bit themselves on the last day. Even allowing for modern interruptions, that says something!

Posted by: Oliver Chettle at December 29, 2008 2:33 PM

I'm appalled that some people are suggesting that 90 overs is too many. The original article spells out how much time is wasted. When the minimum was introduced it was 96, and the plan was to increase it to 108, but instead it was cut to 90. If it is cut to 84, the number actually bowled will fall even further. The problem is that cricketers have no respect for the people who pay their wages, and cannot be bothered to make an effort to entertain them. It is the same with so-called "bad light", which they use to go off the field at every opportunity. I detest Twenty20, but I'm at the end of my tether with test cricket as well. The authorities never do anything to make it better entertainment. We should get 108 overs a day, and if a team fails to deliver that the captain should be banned for the next match. For a second offence he should be banned from all international cricket for a year.

Posted by: Charles Davis at December 29, 2008 11:09 PM

A few more stats for readers. The most overs in a Test day was 162 at Lord's in 1946 (6.5 hours). If you think that fast scoring makes high over rates impossible, consider that when 588 runs were scored in a day at Manchester 1936, there were still 140 overs in 6.5 hours. When Don Bradman scored 309 in a day, he faced 153 balls in 2 hours in the pre-lunch session alone!
One thing I have noticed is that modern pace bowlers usually run most of the length of the pitch in their follow-through, perhaps in an attempt to intimidate the batsman, and pause to glare before turning to walk back. If this adds just five seconds to each ball, this alone can add up to 45 minutes per day.
One suggestion - eliminate scheduled drinks breaks. Today's supposedly super-athlete players routinely stop for a drink whenever they feel like it, so why do they need an organised break. On second thoughts, the TV broadcasters would hate that: fewer ads.

  Post your comment
Posting Guidelines
Name:
Email Address:
Comments:
characters left
Contributors
Samir Chopra
Samir Chopra lives in Brooklyn and teaches Computer Science and Philosophy at the City University of New York; his academic interests include the philosophical foundations of artificial intelligence and the politics of technology. In his third undergraduate year, he captained Mathematics in the departmental cricket competition (and lost to Chemistry in the first round). Samir played C-grade cricket in Sydney and makes guest appearances for his old club when possible (and desirable). Samir runs the blog Eye on Cricket and the cricket page at The Faster Times.
Paul Ford
Paul Ford is a co-founder of the New Zealand cricket supporters' cult, the Beige Brigade. He was once described by a current New Zealand cricketer as "looking spastic" even mucking about with an Excalibur and a tennis ball in the backyard. Paul bowls right-armed Nathan Astlesque "nudes", his batting would make Ewen Chatfield look elegant, and he is a committed fielder. He sometimes grows a beard to hide his double chin and inhabits a periphery of cricket that Cricinfo is proud to be glimpsing through this blog.
Stephen Gelb
Stephen Gelb grew up in Cape Town, a short walk from the beautiful Newlands ground. Always a better student of the game than player, his passion for cricket survived eight years as a student in Canada, where he learned to love baseball too. He lives in Johannesburg doing economic research at The EDGE Institute and teaching at Wits University.
Mike Holmans
Mike Holmans, a database consultant by profession, has spent thirty summers (and a few winters) going to the cricket. Brought up in one and working in the other, his dearest wish is for a season to end with Yorkshire winning the county championship by beating runners-up Middlesex by one wicket with five minutes to go. If it’s also a summer when England win the Ashes, so much the better.
Michael Jeh
Born in Colombo, educated at Oxford and now living in Brisbane - Michael Jeh (Fox) is a cricket lover with a global perspective on the game. An Oxford Blue who played first-class cricket, he is a Playing Member of the MCC and still plays grade cricket. His views on cricket might best be described as those of a "modern traditionalist". Michael now works closely with elite athletes in his job as a manager at Griffith University in Queensland.
Saad Shafqat
Saad Shafqat takes special pride that his cricket-watching life began during the three-month interval between Javed Miandad's debut Test in Lahore and Imran Khan's 12-wicket haul at Sydney. Although a practicing neurologist based in Karachi, cricket has never been far from his activities. He has co-authored Javed Miandad’s autobiography Cutting Edge and has been a contributor to Cricinfo since 2005. His regular column Reverse Swing appears fortnightly in Dawn, Pakistan’s leading English daily.
View posts by author
Michael Jeh (71) Mike Holmans (88) Paul Ford (11) Saad Shafqat (5) Sambit Bal (1) Samir Chopra (58) Stephen Gelb (14)
Recent Posts
The age of innocence and marketing Flat foot stooges Wanted: More aggression from England Why Mohammad Yousuf never learns Go well, workhorses Of fielding and statistics Valete - I Why 'they' can't do without 'us' Time for four-innings one-dayers What's the point of the Champions Trophy?
Archives
November 2009 (4)October 2009 (5)September 2009 (17)August 2009 (17)July 2009 (9)June 2009 (15)May 2009 (15)April 2009 (11)March 2009 (11)February 2009 (13)January 2009 (13)December 2008 (16)November 2008 (17)October 2008 (19)September 2008 (14)August 2008 (19)July 2008 (23)June 2008 (10)
RSS FeedsRSS Feed
© Cricinfo 2009