Quote:
|
Quote:
|
Quote:
If they're even partly paying attention, it's only partly, and they're only going to hear enough to confuse them about your intention. Like a doctor: do no harm. This can only do harm. |
I'm with the others. I can think of a whole lot of reasons not to do it and not one good reason to do it. Coach be offended cause thinks he knows rule...coach just immediately gets bad impression about you--weird..nobody else says that...and on and on..
|
I heard from a ref who worked one of the other championship games and he said the guy they were trying to foul got bumped twice while standing there....said the first bump probably should have been called common before the 2nd/3rde happened.
I see both sides of the argument. On one hand, the winning team shouldn't leave a crappy FT shooter on the floor. On the other hand the foul, while perhaps intentional in nature was not your typical "take foul", which would involve wrapping up a player with arms while clearly trying to foul that specific player off the ball. The bumping is less clear....which is why we get paid for our judgement. I'm not sure what the correct call is here, but if you call INT I think it has to be REALLY obvious that's what they are trying to do. |
Quote:
Peace |
To the earlier reply about "explaining" to a coach about take-foul scenarios: This is not the time for a rules clinic. It's ok to explain a ruling after the fact but not before. It's also imperative when you know a team MAY be fouling to get the FIRST foul. Some coaches will be asses no matter the outcome.
I had a game where the coach pretty much told me what they were about to do. At the first sign of contact I blew my whistle which came just a fraction of a second before a second defender stole the ball (which if the coach didn't tell me what he was doing and the primary defender had been .5 seconds later it would have been a no call and steal). The coach "questioned" the call 30 feet away, and I responded with a T (not like he was a saint all game either). If he didn't tell me what he did I may not have T'd him for his behavior, but the fact that he did and then acted that way is the behavior that, I think, as officials we don't do a good enough job of addressing. |
Quote:
We would tell coaches to use some other word. Then that stupid policy went away and they went by what they did before. I never remember such a policy before that one year. Peace |
Quote:
|
Quote:
Peace |
Quote:
Not really sure what I could have done better. Should I have immediately gone and talked to the A coach after his player told me their plan? Should I have said nothing and just called an INT when they tried hugging B55? What do you guys think? |
Quote:
It's 7th grade ball. In varsity or higher, INT all the way. |
Quote:
|
Quote:
|
Quote:
Officials shouldn't alter what a foul is near the end of the game. Call the contact the same as you did earlier in the contest. There is a proper way to foul for a strategic purpose. If the team cannot do that, then officials shouldn't be rewarding their poor execution. More importantly to this story, slight contact which would not have been deemed a foul previously in the game should not be whistled at this point. To do so is unfair. The camp advice of "call the first foul" does not equate to whistle as soon as someone breathes on the opponent. See an actual foul before calling anything. |
All times are GMT -5. The time now is 04:59pm. |