Advert

Man-of-the-match selection process set for overhaul at the World Cup

Embarrassing ‘anomalies’ in pool stage

A string of embarrassing “anomalies” in picking the man of the match in Rugby World Cup pool games has led organisers to consider overhauling the selection process for the knockout stages, reports said yesterday.

Under the existing system, three players are short-listed by the tournament’s world feed radio early in the second half before fans vote for their choice on social media, a process tournament director Alan Gilpin admits has resulted in a number of “challenges”.

England lock Joe Launchbury was named man of the match for his performance in the 33-13 defeat by Australia that knocked the hosts out despite Wallabies flyhalf Bernard Foley scoring two fine tries in the game.

Launchbury admitted he was unhappy to get the award.

“It was extremely strange to be named man of the match. It was embarrassing and it definitely won’t go on the mantelpiece at home,” Launchbury said.

“It was a strange award that could have gone to a whole host of guys on their team.

“Individually parts of my game went quite well, but the overriding emotions were hurt and frustration.”

Equally embarrassing for the organisers was the award going to Uruguay’s Agustin Ormae-chea, who scored a try against Fiji but was then sent off after receiving the first red card of the tournament.

“There is a rethink happening because there have been a few challenges,” Gilpin was quoted as saying.

“Any man-of-the-match scenario where you have a public vote and that public vote takes place at a particular point during the tournament game leads to some anomalies.

“We saw that with the Uruguay player who received a red card shortly after being named man of the match and of course the Joe Launchbury situation,” he added.

“We’re looking at that now before the knockout stage and the plan is for the change to be made. We’re adjusting the timing and the way the voting takes place.”

Comments not loading? We recommend using Google Chrome or Mozilla Firefox with javascript turned on.
Comments powered by Disqus  
Advert
Advert