bcm666
Brian Moore, Ex England International Hooker
- Joined
- May 18, 2009
- Messages
- 178
- Post Likes
- 27
Before you all roll your eyes, I was asked to do this by another bored member. The things i assert are, from my experience, those which will minimise trouble at the scrum; they will not stop all collapses because they can occur accidentally and some props cannot resist the urge to cheat. Nevertheless, I do believe that if you can get these established you will have a much easier afternoon:-
1. Before the game talk to the scrum half and the front row whilst the team is in the changing room. This is so that their peers know what they have been told and they cannot claim afterwards that you did not tell them something. It also helps you on the field because if they give away a number of penalties or free kicks it is highly likely that someone will say "He told you about this before the game - why don;t you listen"
2. I would tell them that whatever has happened previously in this game the ball is going to go in straight and by that I mean down the middle line which is below where the shoulders meet, not anywhere else. Furthermore, if this doesn't happen I will yellow card without hesitation.
3. To the front rows I would say that I will make a long mark where the engagement has to take place and they should use it because from the mark I will judging whether they or the opposition have pushed over it before the ball is put in.
4. Regarding the CTPE I would tell them that they must listen to the timing and do the phases when called. I would also explain that I have to check certain things are right on each stage and I have to have time to do this so the call will not be rushed, but I would try and make the calls without long pauses.
5. I would tell them that on the engagement I will not allow them to drive on impact and they will not be allowed to drive until the ball is fed by the scrum half.
6. The final point I would make is that the law states binding is on the other props shirt and that I wanted long binds. If I catch them binding on the arm they will be penalised, even if the scrum does not collapse.
Thereafter all that remains is to carry out what you say and without exception. I would make sure that I gave the explanation of any sanction sufficiently loudly for most of the miscreant's team to hear because they will help as set out at the beginning of this post. I would also remind them that I told them about whatever was the offence before the game. Finally, if a player continues to offend - one warning to him in front of his captain then yellow card. If he won't play ball when he comes back on - one warning to captain that next time it is red and if he does it is red and he is off.
I do not believe that you will ever need to get anywhere near a red and hopefully few yellows, but you have to carry out a threat or it is meaningless. I also think that this helps your authority generally.
Regarding the number of times you have to blow the whistle. I don't care if it is all the time early on because they cannot claim I did not explicitly tell them beforehand and it is not my fauilt if they are ****ing thick. It won't go on all game because players will be in the bin and they can and do adapt very quickly when they want to. If they don't - that is not my fault.
1. Before the game talk to the scrum half and the front row whilst the team is in the changing room. This is so that their peers know what they have been told and they cannot claim afterwards that you did not tell them something. It also helps you on the field because if they give away a number of penalties or free kicks it is highly likely that someone will say "He told you about this before the game - why don;t you listen"
2. I would tell them that whatever has happened previously in this game the ball is going to go in straight and by that I mean down the middle line which is below where the shoulders meet, not anywhere else. Furthermore, if this doesn't happen I will yellow card without hesitation.
3. To the front rows I would say that I will make a long mark where the engagement has to take place and they should use it because from the mark I will judging whether they or the opposition have pushed over it before the ball is put in.
4. Regarding the CTPE I would tell them that they must listen to the timing and do the phases when called. I would also explain that I have to check certain things are right on each stage and I have to have time to do this so the call will not be rushed, but I would try and make the calls without long pauses.
5. I would tell them that on the engagement I will not allow them to drive on impact and they will not be allowed to drive until the ball is fed by the scrum half.
6. The final point I would make is that the law states binding is on the other props shirt and that I wanted long binds. If I catch them binding on the arm they will be penalised, even if the scrum does not collapse.
Thereafter all that remains is to carry out what you say and without exception. I would make sure that I gave the explanation of any sanction sufficiently loudly for most of the miscreant's team to hear because they will help as set out at the beginning of this post. I would also remind them that I told them about whatever was the offence before the game. Finally, if a player continues to offend - one warning to him in front of his captain then yellow card. If he won't play ball when he comes back on - one warning to captain that next time it is red and if he does it is red and he is off.
I do not believe that you will ever need to get anywhere near a red and hopefully few yellows, but you have to carry out a threat or it is meaningless. I also think that this helps your authority generally.
Regarding the number of times you have to blow the whistle. I don't care if it is all the time early on because they cannot claim I did not explicitly tell them beforehand and it is not my fauilt if they are ****ing thick. It won't go on all game because players will be in the bin and they can and do adapt very quickly when they want to. If they don't - that is not my fault.