oh FFS ...
Specifically What would you do if a team don't comply with 20.5 ?
Ping them under 9.7.4 for time wasting - free kick to opposition.
oh FFS ...
Specifically What would you do if a team don't comply with 20.5 ?
It happened today! Touring Colts team awarded PK in front of posts. 7 pts ahead in a to and fro game, so indicated to take another 3. Kicker ran up, tapped it almost without breaking stride, picked up, passed and 'scored' a good 'Barbarians' tactic' try. Sorry guys, scrum to other team at point of PK (they certainly weren't going to be given a re-take!). .
[LAWS]8.20 If the team indicates to the referee the intention to kick at goal, they must kick at goal. [/LAWS]
I think they must kick at goal
And the tap was a very bad miss! Now what is the restart?
If he hasn't kicked it ?
Then he hasn't yet taken the PK .. so take the PK
But he had kicked it!
Yes,
Bring back the tap
Now kick at goal ... And you don't have much time left...
Scenario 2
Apply Law 10 .. Blue 14 is offside , continue to move forward and interfere with play
But 20.10 says there is no sanction
But Law 10 applies .. right ?
What would you do ? (with Law reference)?
Well it used to be a scrum, then they apparently dropped the sanction for being in front of the kicker but now you’re thinking of going with a PK.
My point is that the laws, in some instances, have become less clear as a result of the 2018 rewrite.
If a player is in front of the kicker at a kick-off, even if he jumps to contest the ball with a defender, we come back to the centre for a scrum.
So now we have inconsistencies for sanctions/non-sanctions for similar infringements.
Personally, I think the 2017 sanction of a scrum should still be in the book. It would certainly look funny to call the winger back and just say to the kicking team, “The kickoff hasn’t been taken correctly so come back and do it again”. That would mean there’s no consequence for infringing and they are likely to try it on again next week with a different ref
Being offside in front of a kicker is not necessarily sanctioned at all ..only if you interfere with play , as in your example.
But being in front of the kicker at a kickoff or restart IS sanctioned regardless of whether the infringing player/players carry on to interfere with play and the sanction is a scrum.
But being in front of the kicker at a kickoff or restart IS sanctioned regardless of whether the infringing player/players carry on to interfere with play and the sanction is a scrum.
Put simply, the crux of the whole argument for me is that the so called "simplified" Law book is not necessarily clearer or more simple to understand. Some infringements/non-compliances in Law 20 no longer have sanctions listed, not complying with the time requirements when taking a PK has been moved from the PK section of the book to the Scoring section (Law 8), as you have pointed out we can now find a PK sanction for things that were clearly labelled a scrum (and in my opinion should still be a scrum).
A big part of the rewrite centred around reducing the size of the Law book. Grouping a couple of infringements and adding one line i.e. Sanction: Scrum, would not have caused a blowout in size, production costs or ink usage. But it would have made the Laws simpler and clearer. Oh wait...….. that was the whole point of their rewrite exercise.
this example really isn't a 2017 v 2019 issue... the only scenario that has actually changed is the quick tap that isn't a proper tap
campaign to keep on topic!
yes. I undertake to play my part going forward