Quote:
Originally Posted by deecee
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.
|
This is exactly why such situations shouldn't be handled in the described manner.
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.