The Official Forum  

Go Back   The Official Forum > Basketball

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #16 (permalink)  
Old Sat Jul 01, 2006, 12:51pm
certified Hot Mom tester
 
Join Date: Aug 1999
Location: only in my own mind, such as it is
Posts: 12,918
Exclamation

Quote:
Originally Posted by Kostja
Some of these answers are no brainers, but very valuable ones, so to say Someone wrote that good coaches wouldn't try to complain about every call or put a lot of pressure on the referees. That's where I can't agree. In the past two years I met a lot of very experienced and knowledgeable coaches while refereeing on a semi-professional and professional level here in Europe.
They may be "very experienced" and/or "knowledgeable" but if they complain about every call, they aren't "good".
__________________
Yom HaShoah
Reply With Quote
  #17 (permalink)  
Old Sat Jul 01, 2006, 01:01pm
Do not give a damn!!
 
Join Date: Jun 2000
Location: On the border
Posts: 30,463
Quote:
Originally Posted by Kostja

A very popular move was to question a close call (block-charge or something like that) in a way that one could not ignore the coach, and as soon as you moved towards him to handle the situation coach turned around and walked away from you ... What is the referee supposed to do? Follow the coach who will probably pretend he can't hear the ref and finally give him a surprised "What do you want from me?" look with the ultimate power shrug of his shoulders while looking at his assistant coach for help, or just turn away and let it go? Both ways, you don't look very good in this situation, which is of course what the coach tried to achieve. I think it is part of the game, coaches try to get to know their refs, they try to influence our decision making and this does not only apply to bad coaches.
I will say that you do not have to explain every call. Just because a coach complains, does not mean you have to give an answer or answer right away. If a coach really wants to know what you called, they will ask later.

Quote:
Originally Posted by Kostja
From my own experience a couple of years ago I know that at least in highschool in Canada referees were treated with more respect then in youth basketball here in Europe. Would you say this is also true for College basketball? And how would you react to the situation described above?
We also must understand that what works in one area might not work in another area. I know having worked inner-city schools, there is a different way you have to talk to coaches than a suburban school. Then there is a totally different way to talk to participants if you are dealing with a rural school. Now this is just in my state, I know when I see teams that are from outside of the state, they act differnet as well. And everything I just said was related to HS, college is another story as well.

Peace
__________________
Let us get into "Good Trouble."
-----------------------------------------------------------
Charles Michael “Mick” Chambers (1947-2010)
Reply With Quote
  #18 (permalink)  
Old Sat Jul 01, 2006, 03:42pm
Official Forum Member
 
Join Date: May 2006
Location: NH
Posts: 87
I did an AAU U-17 tournament in Las Vegas Easter weekend where every coach thought they were the best coach and knew everything there was to know about basketball. Most coaches also thought their players were the best players the sport of basketball has ever seen. Although this was a high profile Div 1 scouting tournament, very few players will really go on to play big games in Div 1 hoop. I have never seen so many T's assessed ever than in this tournament, but it was stressed to us before the tournament that a technical foul is merely a penalty for a violation of the rules - which it is.

I think referees - especially newer referees - tend to forget that a technical foul is just that, a penalty. It should not be used as a personal attack to get back at a coach or a player, but used when a coach or a player violates the rules.

When I took the IAABO course a while back, game management was stressed as a critical component of refereeing. And although I agree game management is very important, I also agree that if a coach's behavior and/or statements are worthy of a technical foul; then give it to him/her – regardless if it is early in the game, late in the game or before the game even starts. With the exception of the three (four in the 06-07 season) NFHS rule book reasons for warnings – throw in plane violations, huddling by either team and contact with the free thrower, interfering with the ball following a goal and water on the court – no where in the book does it say we as referees are to issue warnings to coaches and players for misbehaving and breaking the rules. When we as referees start issuing warnings that the rules say don’t exist, we have just bent the rules set forth by the rules committee and have then put ourselves in a weak position for any sort of valid response to a coaches concern – you as a referee already broke the rules once.

Some people call me a stickler and last year I ejected one coach and issued a handful of well deserved T's, but I am still one of the most requested referees among coaches in the area. Coaches remember referees and the calls they make. Expect a coach to remember you, but if you are consistent in your calls, they know that if they break the rules (good coaches know the REAL rules) they will receive the penalty.

I know a lot of referees out there don’t agree with my grasp on technical fouls and I am sure there will be many comments posted in response to my post. To end, I have copied a piece of the IAABO Midseason Interpreter’s Memorandum from Peter Webb (who by the way was recently inducting into the HS Basketball Hall of Fame - Congrats Peter!):

Enforce the rules, all rules. That is what fair play is all about. Officials don't set aside the travel rule, why set aside the disconcertion rule, the player appearance rule, the behavior rule, grasping the ring rule, etc.? When those rules are not met by players or coaches, apply the penalty. Do it now, don't fret, don't put it on hold and don't worry about it. Eliminate the issue, the game will be better for it. While being "good" (by warning, ignoring, etc.) to that particular team ask what about the opposing team who is adhering to the rule(s)?

There are only three rules-approved warnings and they are delay warnings - boundary plane, huddle or contact with free thrower and interfering with the ball after a goal. The rules do not provide for any other warnings. Although officials may think they are “helping,” “using common sense” or “being reasonable,” a warning can upset coaches and players. Warnings can upset opposing players and coach. When warning, the official is setting aside a rule that is expected to be enforced. Seldom can a warning be FAIR as there are two teams.”
Reply With Quote
  #19 (permalink)  
Old Sat Jul 01, 2006, 03:50pm
Official Forum Member
 
Join Date: Aug 2003
Posts: 2,557
Biggest problem I see with officials is they ignore the coach. If the coach is asking a question then answer, talk to him. If you ignore him he's just going to get even more mad. Take care of your business.
Reply With Quote
  #20 (permalink)  
Old Sat Jul 01, 2006, 03:54pm
Official Forum Member
 
Join Date: Aug 2001
Location: Western Mass.
Posts: 9,105
Send a message via AIM to ChuckElias
Quote:
Originally Posted by Official99
I know a lot of referees out there don’t agree with my grasp on technical fouls
I'm not sure who would disagree with your "grasp" of saying that T's are merely a penalty, not a weapon. Officials who use T's that way don't last very long.

Quote:
There are only three rules-approved warnings and they are delay warnings
This is no longer true, btw. . .

"Beginning next season in high school basketball, only one warning will be given for any of the four delay situations before a technical foul is assessed, including the newly approved delay situation for water on the court following a
time-out."
__________________
Any NCAA rules and interpretations in this post are relevant for men's games only!
Reply With Quote
  #21 (permalink)  
Old Sat Jul 01, 2006, 04:17pm
Do not give a damn!!
 
Join Date: Jun 2000
Location: On the border
Posts: 30,463
Quote:
Originally Posted by Official99
I think referees - especially newer referees - tend to forget that a technical foul is just that, a penalty. It should not be used as a personal attack to get back at a coach or a player, but used when a coach or a player violates the rules.
I am not sure what you mean by this statement. But to be fair anytime a player or coach wants to question judgment calls (which happens all the time) we have the right under the rules to give a technical foul. Now to be real official use a great deal of judgment and do not call as many Ts as the rules allow. So I am not quite sure how officials are getting back at coaches and players when we use great restraint and not call anything.

Quote:
Originally Posted by Official99
When I took the IAABO course a while back, game management was stressed as a critical component of refereeing. And although I agree game management is very important, I also agree that if a coach's behavior and/or statements are worthy of a technical foul; then give it to him/her – regardless if it is early in the game, late in the game or before the game even starts. With the exception of the three (four in the 06-07 season) NFHS rule book reasons for warnings – throw in plane violations, huddling by either team and contact with the free thrower, interfering with the ball following a goal and water on the court – no where in the book does it say we as referees are to issue warnings to coaches and players for misbehaving and breaking the rules. When we as referees start issuing warnings that the rules say don’t exist, we have just bent the rules set forth by the rules committee and have then put ourselves in a weak position for any sort of valid response to a coaches concern – you as a referee already broke the rules once.
There is a difference between an "official warning" that goes into the book and a warning for conduct which might not be that bad. Sorry, we should give warnings to try to prevent further action when warranted. It is not good common sense to just give out Ts for a minor and hardly understood infraction. And if you want to work higher levels, you better learn to communicate to players when appropriate and I have never heard a college assignor say the things you claim. I could even say the very same with HS assignors as well.

Quote:
Originally Posted by Official99
Enforce the rules, all rules. That is what fair play is all about. Officials don't set aside the travel rule, why set aside the disconcertion rule, the player appearance rule, the behavior rule, grasping the ring rule, etc.? When those rules are not met by players or coaches, apply the penalty. Do it now, don't fret, don't put it on hold and don't worry about it. Eliminate the issue, the game will be better for it. While being "good" (by warning, ignoring, etc.) to that particular team ask what about the opposing team who is adhering to the rule(s)?
You are right we should not set aside a rule, but we should not be so technical that there is no room for judgment or common sense. I know I do not call travels that no one can clearly see. I try to call what is obvious and violations and fouls that most people can see took place. I am not going to nit pick a rule like the coaching box rule and give a T for a coach with a toe on the line. That is not good officiating in my opinion and it is not going to make you popular the higher you go up the latter.

Quote:
Originally Posted by Official99
There are only three rules-approved warnings and they are delay warnings - boundary plane, huddle or contact with free thrower and interfering with the ball after a goal. The rules do not provide for any other warnings. Although officials may think they are “helping,” “using common sense” or “being reasonable,” a warning can upset coaches and players. Warnings can upset opposing players and coach. When warning, the official is setting aside a rule that is expected to be enforced. Seldom can a warning be FAIR as there are two teams.” [/I]
It is fair if you are giving both teams the same benefit of the doubt. You have every right to let a coach know they are getting out of hand so when you do give them a T, they know they were already close to the line. If a coach complains about the first call you make and by rule you give them a T, you will not be around very long as an official. And the rules committee wants us to enforce the spirit of the rules, not the letter. It is in their literature in both NF and NCAA rules.

Peace
__________________
Let us get into "Good Trouble."
-----------------------------------------------------------
Charles Michael “Mick” Chambers (1947-2010)
Reply With Quote
  #22 (permalink)  
Old Sat Jul 01, 2006, 04:55pm
In Memoriam
 
Join Date: Aug 2001
Location: Hell
Posts: 20,211
Quote:
Originally Posted by JRutledge

There is a difference between an "official warning" that goes into the book and a warning for conduct which might not be that bad. Sorry, we should give warnings to try to prevent further action when warranted.

You are right we should not set aside a rule, but we should not be so technical that there is no room for judgment or common sense.

It is fair if you are giving both teams the same benefit of the doubt. You have every right to let a coach know they are getting out of hand so when you do give them a T, they know they were already close to the line. If a coach complains about the first call you make and by rule you give them a T, you will not be around very long as an official. And the rules committee wants us to enforce the spirit of the rules, not the letter. It is in their literature in both NF and NCAA rules.
Agree.

Most good, experienced officials imo know when to warn and when to "T". You can't really set definitive rules either. Warnings are very appropriate in some situations; in other situations, a "T" without a warning might be appropriate also. You simply do what you think is warranted and necessary in each individual situation.

Of course, what you don't do is warn and then not follow through if someone chooses to ignore that warning.
Reply With Quote
  #23 (permalink)  
Old Sat Jul 01, 2006, 05:22pm
Official Forum Member
 
Join Date: Feb 2006
Posts: 52
Quote:
Originally Posted by Mark Padgett
They may be "very experienced" and/or "knowledgeable" but if they complain about every call, they aren't "good".
They don't complain about every call, they pick their spots, only some of them pick too many
By the way, I wouldn't say a coach, who doesn't know the subtleties of every rule that's ever been written and therefore starts complaining, is necessarily a bad coach. He just doesn't qualify as a referee coach
Reply With Quote
  #24 (permalink)  
Old Sat Jul 01, 2006, 07:05pm
certified Hot Mom tester
 
Join Date: Aug 1999
Location: only in my own mind, such as it is
Posts: 12,918
Lightbulb

Quote:
Originally Posted by JRutledge
Sorry, we should give warnings to try to prevent further action when warranted.
If I can just comment on Rut's point - a very well respected referee once said that the purpose of a technical foul was to stop bad behavior, and if you could stop it without having to give the technical, you were just that much ahead.
__________________
Yom HaShoah
Reply With Quote
  #25 (permalink)  
Old Sat Jul 01, 2006, 08:56pm
Official Forum Member
 
Join Date: May 2006
Location: NH
Posts: 87
Quote:
Originally Posted by Mark Padgett
If I can just comment on Rut's point - a very well respected referee once said that the purpose of a technical foul was to stop bad behavior, and if you could stop it without having to give the technical, you were just that much ahead.
I like that comment a lot!

When I said there are only three reasons to issue warnings, that is what I meant reasons. Yes, collectively there is only one warning to be issued, but three (and now four this coming season) reasons to issue the warnings.

I like everyones comments and expected this much response. I appologize if I don't respond right away to all of them. Please remember, the last two sections of my post is taken from a memo distributed by IAABO.

SnakeEye's comment about talking to coaches is probably the best comment posted yet. Most coaches don't want anything from an official than to be heard. I refer back to Las Vegas this past April. I had a coach who just wanted to be heard. All I had to do was listen to him and he smiled and I was able to walk away. I very rarely had to say anything with him and never had to warn him or give a T because I listened.

Thanks again.
Reply With Quote
  #26 (permalink)  
Old Sun Jul 02, 2006, 09:15pm
Official Forum Member
 
Join Date: Mar 2004
Posts: 2,193
Here's a few things that have worked for me, though nothing is foolproof or works all the time:

1. The phrase "OK coach," in response to complaints and requests tends to do wonders.

2. Pick your spots if you must, but in general, don't argue. The exception might be to clarify that there was no contact (when he complains about a foul not called) or something similar. When he wants to argue, see number 1.

3. If he's getting beligerant: "coach, I need your cooperation and this behavior/comments isn't/aren't helping..." Try to do this when only he is around or within hearing distance.

4. When he gets personal or stupid, if you choose not to give him a T, just say something like, "coach, we are done talking." If he asks further, you might add that he's being disrespectful and unreasonable or whatever, but keep it short and get away from him. If he comes after you or keeps talking, you have no choice as to what to do next.

You can also do a lot of talking to a coach while keeping your eyes on the court -- say, during a free throw or a sub situation. Most of the time nobody except those in close proximity even know you both are talking to each other. Even the other coach may not know, but you can do the same with him later. I'm not saying initiate the discussion, but if the coach wants to talk and he's not out of control, engage him, but keep your eyes focused on the court. If he asks why you aren't looking at him, tell him "I know you are there, but I must keep focused on the floor." He should understand that.
Reply With Quote
  #27 (permalink)  
Old Mon Jul 03, 2006, 12:08pm
Official Forum Member
 
Join Date: Feb 2005
Location: Palmyra, VA
Posts: 245
Send a message via AIM to drothamel
My experience has been that 99% of the time, coaches want to be heard, they do not want answers. When they ask questions, they usually have their answer already. What I try to do is find out what that answer is so that they can vent it properly. Example:

Coach: "Why did my kid get called for a block down there?"

At this point, the coach could care less about "legal guarding position," he wants to complain about the call.

Me: "Which play was that coach?"

I just want him to come out and say what he has to say, appropriately.

Coach: "The one a few seconds ago, when white just ran my kid over."

Ta-Da! Coach obviously feels his player was fouled, he disagrees with my judgement. He doesn't want to hear a reason for it.

Me: "We must have seen that one differently coach. I'll make sure to look for it in the future."

Now the coach has gotten out his complaint, he feels better about it, and we can move on with the game.

Of course, you should always pick your spots. Free throws are the best time to make yourself available to coaches, especially if you see one of them stewing on the sidline. Anything you can do to recognize a coach is something positive. If the coach chooses to turn that into a negative situation, then you will have to deal with it; but coaches deserve approachability from officials.
__________________
-RESPECT THE GAME-
Reply With Quote
  #28 (permalink)  
Old Mon Jul 03, 2006, 01:32pm
Official Forum Member
 
Join Date: May 2005
Posts: 3,505
Quote:
Originally Posted by Kostja
Some of these answers are no brainers, but very valuable ones, so to say Someone wrote that good coaches wouldn't try to complain about every call or put a lot of pressure on the referees. That's where I can't agree. In the past two years I met a lot of very experienced and knowledgeable coaches while refereeing on a semi-professional and professional level here in Europe. Almost all of them where focusing on coaching their teams most of the time, but I think every single one of them tried to get me or one of my partners at one point in the game and then it wasn't about asking a question and wanting to hear about a different angle or something like that. These situations were about giving the ref a hard time, get inside his head, or at least see to which of the above mentioned categories the ref belongs (hard a**, entertainer, or whatever).

A very popular move was to question a close call (block-charge or something like that) in a way that one could not ignore the coach, and as soon as you moved towards him to handle the situation coach turned around and walked away from you ... What is the referee supposed to do? Follow the coach who will probably pretend he can't hear the ref and finally give him a surprised "What do you want from me?" look with the ultimate power shrug of his shoulders while looking at his assistant coach for help, or just turn away and let it go? Both ways, you don't look very good in this situation, which is of course what the coach tried to achieve. I think it is part of the game, coaches try to get to know their refs, they try to influence our decision making and this does not only apply to bad coaches.

From my own experience a couple of years ago I know that at least in highschool in Canada referees were treated with more respect then in youth basketball here in Europe. Would you say this is also true for College basketball? And how would you react to the situation described above?

Cheers,
Kostja
unless the coach asks me a direct question i have nothing to answer... why follow him anywhere -- once he turns his back after asking a question once the next time he asks a question i will make it clear if he asks a question one more time and turns around i will not answer any of his questions for the remainder of the game. Dont play his stupid games, let him act like an idiot. Then if i feel like hes showing the officials up i will also let him know one more act like that will cost him more than a block/charge would. but thats just me -- if he wants to make a scene and look like an idiot thats fine / if he wants to mock us and make us look like idiots than that is not.
Reply With Quote
  #29 (permalink)  
Old Wed Jul 05, 2006, 07:47am
Official Forum Member
 
Join Date: Jan 2003
Posts: 944
Quote:
Originally Posted by JRutledge
But to be fair anytime a player or coach wants to question judgment calls (which happens all the time) we have the right under the rules to give a technical foul.
I don't seem to recall reading that rule. Maybe it's time for me to have a refresher. Questioning judgment doesn't per se prove unsporting conduct, IMHO. Did I miss something?

If you're talking about someone questioning your judgment, rather than the call, I might see that. But questioning a call in an appropriate manner is part of the game. Obviously, your judgment and a player or coach's judgment will differ because of different training and experience. As long as they are not unsporting about it, I think they should have the right to question your call, as long as they are not trying to show you up.
Reply With Quote
  #30 (permalink)  
Old Wed Jul 05, 2006, 09:11am
In Memoriam
 
Join Date: Aug 2001
Location: Hell
Posts: 20,211
Quote:
Originally Posted by Jimgolf
I don't seem to recall reading that rule. Maybe it's time for me to have a refresher. Questioning judgment doesn't per se prove unsporting conduct, IMHO. Did I miss something?

If you're talking about someone questioning your judgment, rather than the call, I might see that. But questioning a call in an appropriate manner is part of the game. Obviously, your judgment and a player or coach's judgment will differ because of different training and experience. As long as they are not unsporting about it, I think they should have the right to question your call, as long as they are not trying to show you up.
By strict reading of NFHS rules, a head coach is definitely not allowed to question anything. A head coach is allowed, by rule to coach- period.

Rule 3-1-2 says that the captain is his/her teams representative, and is allowed to ask for an rules interpretation or get essential information. There is no mention of a coach anywhere in the rules being allowed to question anything, unless it's one of the listed errors. Captains certainly aren't allowed to ever question the judgement involved in a call either.

From an old POE in the 2001-02 book -- "Coaches must stay within the confines of the optional coaching box and are ONLY permitted to give instructions to players and substitutes. Coaches using the optional coaching do not have implied permission to roam the sidelines, attempt to influence the decision of an official, or conduct themselves in an unsporting manner." Iow, by rule, the head coach is not allowed to ask questions; he has to get his captain to do that.

Of course, in real life it's a whole lot different. The point is that a coach questioning an official's judgement sureasheck is leaving hmself open to get whacked.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
line up card managment goldcoastump Softball 9 Fri Apr 07, 2006 08:46pm
Managment seems to be ok with Replacements: Read! MrB Baseball 11 Fri Apr 07, 2006 01:23pm
Coach was right Cyber-Ref Basketball 2 Sun Jan 29, 2006 09:39am
Violence towards officials---data managment survey. kristal_15 Basketball 9 Tue Nov 15, 2005 02:05pm
A coach by any other name Back In The Saddle Basketball 17 Wed Jul 20, 2005 02:41pm


All times are GMT -5. The time now is 06:04am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1