Originally Posted by M&M Guy

I have yet to see anyone show a memo, case play, rule, POE, interp, something scribbled on a napkin, whatever, to show that we should call a foul just because we know the other team wants to commit one.

Originally Posted by Ch1town

I recently heard Mr. Rush, Sr. & Mr. Clougherty discuss "take" situations.

According to those two extremely knowledgeable sources, the team behind is taking a foul in the end of game situation.

"Put your hand on 'em & it's a foul."

"You have to know TIME, SCORE & FOULS ."

"You have to know if a team is taking a foul... end of game situation I'm behind by 2 & you have the ball with less than 5 seconds is a take si?uation."

"You have to have your anttena up & be mentally ready."

Apparently the amount of contact that constitutes a foul does change from the beginning to the end of a game.

Originally Posted by M&M Guy

If you mean call the foul that happens on the obvious contact, then we agree.
"Trying to foul" is not a reason to blow the whistle. In fact, aren't you justifying the reason to no longer make those tough decisions, and bailing out the defensive team by doing what they want? Cool, "everyone knows" the team is trying to foul. That's not why I'm blowing the whistle. I'm blowing the whistle because the team did foul.
If you're calling your game based on what you think the fans/coaches think, you're on the wrong track.

Why should we take the easy way out and guess on contact, or allow any contact to be a foul at the end of the game, instead of working to be in position to make the proper call?

Originally Posted by btaylor64

If it looks like a duck and sounds like a duck then it probably is a duck. Everyone sees the team is trying to foul and you as the officials are attempting to justify a way to not call what is obvious to everyone else.

Originally Posted by M&M Guy

...working to be in position to make the proper call?