The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Ways not to call a tech (https://forum.officiating.com/basketball/14404-ways-not-call-tech.html)

ReadyToRef Wed Jun 30, 2004 03:03pm

Again at camp, one of the clinicians mentioned something about ways not to call (or ways to avoid giving) a tech. Does anyone have a copy or a resource for this? Thanks for any help.

JRutledge Wed Jun 30, 2004 03:09pm

Need more information
 
I am assuming that they are talking about using your voice instead of just T'ing up players and coaches for behavior.

I do not know if there is a specific article or site that I can reference, but there are technics you can use.

One is just simply talking to players and coaches in a calm tone. Use the FT line as a place to make a point. Use dead ball situation when you see players getting out of hand. But I am assuming what you are talking about.

Peace

ref18 Wed Jun 30, 2004 03:49pm

I know what you're talking about. The 10 ways to call a tech and the 10 ways not to call a tech. Try searching the web, I remember getting it off a loacl board site, but that was a year or two ago, and i don't remember what site i got it from.

Lotto Wed Jun 30, 2004 04:10pm

Quote:

Originally posted by ref18
I know what you're talking about. The 10 ways to call a tech and the 10 ways not to call a tech. Try searching the web, I remember getting it off a loacl board site, but that was a year or two ago, and i don't remember what site i got it from.
Let's hear it for Google....


The Technical Foul, By Kathy Jenkins

Top Ten Reasons To Not Give A Technical Foul

1. You can address a coach before it becomes a problem. A quiet word can go a long way in preventing.

2. Coaches are competitors they love challenges. Don't back yourself into a corner by saying be quiet or else. Instead offer a reason why you might be right.

3. When coaches complain ask yourself, is the call questionable, is the call wrong. If they have a legitimate grip then allow them some latitude.

4. If you know a coach is upset then move out on to the floor when in front of their bench.

5. Don't tolerate a lot before a warning. Warnings can be very effective in preventing situations from escalating.

6. Lend and ear. Coaches like to be heard. If you ignore them then they become more frustrated and are more likely to lose control.

7. If a coach says something and you are the only one who hears it, if you T them while they are sitting on the bench, then you get the worst of the situation.

8. If an assistant is out of line then you can speak to the head coach ask them to help you out.

9. If a player is out of line then let the coach know. Tell them you've warned their player. That way it you do give a T then the coach isn't surprised. Most good coaches will speak to the player first.

10. If you have had a rough day and know your fuse is short. Keep it in mind before you do anything rash. Ask yourself, does the situation come under one of the top ten reasons to give a T.

The Top Ten Reasons To Give A Technical Foul

Knowing when the right time to call a technical foul is half the battle.

There are many different factors to consider, when deciding to give a technical. Flow, time and score, language, the number of times a coach has complained, what the coach is complaining about, whether or not the coach wants one are all things that should be given consideration before calling a technical.

Generally there are three areas of coach's behavior that need attention:

When a coach makes it personal.

When a coach draws attention to himself or herself.

When a coach' s complaints are persistent.

Some technicals are easy. They are black and white situations that leave little room for negotiations.

1. Leaving the confines of the coaching box and complaining.

2. Using profanity or language that is abusive, vulgar or obscene.

3. If coach or player has been warned and has not heeded the warning.

4. A coach demonstrates displeasure with your partner and their back is turned.

Other technical fouls are not as black and white. In some situations a warning may be appropriate before the technical foul is given.

5. A coach or player continually demonstrates signals or asks for calls.

6. If you are being embarrassed.

7. If giving a T will help give structure back to the game. Will it have a calming effect on things.

8. A coach questions your integrity.

9. If they have interfered with the game or your concentration then usually they have gone to far.

10. Inciting an undesirable crowd reaction.

Top Ten Ways to Give a Technical Foul

1. Calling a technical foul should be no different then calling any other violation. Maintain a pleasant attitude, have poise and presence. Don't embarrass them by being demonstrative.

2. Call the Technical. Report to the table and leave the area.

3. Explanations, it need should be done by partner.

4. Never look at a coach when you give a T.

5. When you give a T walk away. Find your partner.

6. After technical fouls get the ball in play immediately.

7. If you T a coach, after the T come back even stronger. Don't back off. Come back with the tough call that goes against that coach if It Is there.

8. Don't go to coaches after your partner has given them a T. Let your partner give any explanations needed.

9. Make them earn the second one. Don't be reluctant to give the second one if it is warranted.

10. Explain technicals on players to coaches: "Taunting and Baiting", "Cussing", Too much mouth."

Schmidt MJ Wed Jun 30, 2004 05:40pm

Am I misreading something or do #3 and #8 contradict each other under "Top 10 ways to give a Technical".

BktBallRef Wed Jun 30, 2004 10:50pm

Quote:

Originally posted by Schmidt MJ
Am I misreading something or do #3 and #8 contradict each other under "Top 10 ways to give a Technical".

Sure seemed that way to me.

blindzebra Thu Jul 01, 2004 01:16am

I really have a problem with number 4 under not to give.

No way I'm letting a coach influence my postioning, EVER. I'm going where I need to be. If that's onto the floor, fine. If that's right in their lap, I'll be there regurdless of their temperment.

Nevadaref Thu Jul 01, 2004 03:26am

My general opinion is that I don't like lists like this for officiating. People are different and they will do things differently. For someone to tell others how to or how not to do such and such on a basketball court seems awfully presumptuous. You will attend many camps and get many DOs and DON'Ts from various officials. Take what you want, junk what you wish. In the end, you'll do it your way (or your assignor's way) anyway.


For example, I point out that the author states one reason for calling a technical foul is:
2. Using profanity or language that is abusive, vulgar or obscene.

However, not only is this a technical foul, but according to NFHS rules it is also flagrant. The words chosen by the list writer even match those in the definition.

4-19-4
A flagrant foul may be ... If technical, it involves ... extreme or persistent, vulgar or abusive conduct.

That being said, I'd be willing to bet that the author is not advocating calling this flagrant. For many others, I'm sure that it would be.


PS And our esteemed author missed my favorite: The coach argues and is wrong about the rule. Not what happened on the play, not the judgment, just the plain and simple rule. = Whack!

tomegun Thu Jul 01, 2004 05:41am

These are some very good posts. I have mixed feelings about this list. I think experience is the main factor to determine the time or reason for a T.

I was having a discussion with an official at a camp about giving the coach a second T. He is of the opinion that it is voodoo for the same official to give a coach a second T at any level. He said he would go to his partner, grab (or hold, not really hard) them on the arm and tell them "look at me." It sounded very storybook/corny the way he said it. I told him that I'm of the opinion to avoid "I will never...." because a coach can attempt to make a fool out of us if we follow this "rule" and our partners do not have our back. I haven't given a coach two technicals in a game before (rec league/summer doesn't count :) ) but if the situation really warranted it, see ya! I'm curious to know what others would say.

cmathews Thu Jul 01, 2004 09:08am

try to avoid it..but if need be
 
In our area, we try to avoid giving the second T fromt he same official. However, if I T a coach up, and the next time down the floor he deserves another one, granted he has to earn it, I would not be afraid to whack him again. I agree with the posts that mention experience and personal style/preference...

[Edited by cmathews on Jul 1st, 2004 at 10:11 AM]

Dan_ref Thu Jul 01, 2004 10:00am

Quote:

Originally posted by Nevadaref


PS And our esteemed author missed my favorite: The coach argues and is wrong about the rule. Not what happened on the play, not the judgment, just the plain and simple rule. = Whack!

Why is this automatic?

Aren't coaches allowed to be wrong about a rule?

Can't you think of better ways to handle this than a T?

JRutledge Thu Jul 01, 2004 10:33am

Quote:

Originally posted by Dan_ref
Quote:

Originally posted by Nevadaref


PS And our esteemed author missed my favorite: The coach argues and is wrong about the rule. Not what happened on the play, not the judgment, just the plain and simple rule. = Whack!

Why is this automatic?

Aren't coaches allowed to be wrong about a rule?

Can't you think of better ways to handle this than a T?

I would have a T every game if I did that.

Better yet, I would not have any coaches and I would have to forfeit all the games. :D

Peace

Nevadaref Fri Jul 02, 2004 09:13pm

Look at the positive side, Dan. There is a big motivation for the coaches to learn the rules; or at least not to argue them. 9 out of every 10 coaches out here know how I handle this and accept what I tell them when it comes to the rules. That tenth coach learns the hard way.

Dan_ref Sat Jul 03, 2004 10:16am

Quote:

Originally posted by Nevadaref
Look at the positive side, Dan. There is a big motivation for the coaches to learn the rules; or at least not to argue them. 9 out of every 10 coaches out here know how I handle this and accept what I tell them when it comes to the rules. That tenth coach learns the hard way.
I guess it's just a difference in our philosophy.

I don't see myself as being the motivator for coaches or players to learn - hard or easy way. If a coach or player questions a rule I'll explain. If the coach doesn't want to accept my explanation I'm usually able to end the discussion quickly enough without a T. If there is a T it's usually because that's what the coach wanted the result to be anyway. It's never because it's an automatic.

Hawks Coach Sat Jul 03, 2004 12:43pm

Examples of Nevada's automatic Ts from games that I have coached in during the spring.

"Player didn't control the ball - Travel!" (this is how the call was made during the run of play!

Player dropped the ball while picking it up. I simplyt asked wasn't that a fumble. Response: "She fumbled it coach - that's a double dribble!"

Situation where A had ball in front court, B tapped a pass, A tapped it and recovered in backcourt. I tell ref that's a backcourt because A was last to touch in f/c. "Your player touched it coach, they didn't have control - that's not a backcourt!"

If this passes for rules knowledge from refs getting paid to ref a game, how can a coach that has these same understandings get a T for not knowing the rules?

And where is that T covered in the rulebook? It is somehow more unsporting to ask for a call when you have the rule wrong than when you have it right? Sorry Nevada, but this has to be one of the more ludicrous reasons for an automatic T that I have read.

blindzebra Sat Jul 03, 2004 01:25pm

Quote:

Originally posted by Nevadaref
My general opinion is that I don't like lists like this for officiating. People are different and they will do things differently. For someone to tell others how to or how not to do such and such on a basketball court seems awfully presumptuous. You will attend many camps and get many DOs and DON'Ts from various officials. Take what you want, junk what you wish. In the end, you'll do it your way (or your assignor's way) anyway.


For example, I point out that the author states one reason for calling a technical foul is:
2. Using profanity or language that is abusive, vulgar or obscene.

However, not only is this a technical foul, but according to NFHS rules it is also flagrant. The words chosen by the list writer even match those in the definition.

4-19-4
A flagrant foul may be ... If technical, it involves ... extreme or persistent, vulgar or abusive conduct.

That being said, I'd be willing to bet that the author is not advocating calling this flagrant. For many others, I'm sure that it would be.


PS And our esteemed author missed my favorite: The coach argues and is wrong about the rule. Not what happened on the play, not the judgment, just the plain and simple rule. = Whack!

I can't see that as an automatic, as described. The coach could very calmly question the rule application and you'd whack them?

If they are yelling, " That's not the rule, you got that wrong," across the court at us, then I'd be whackin' the coach right with ya, but that is not what you said.;)

[Edited by blindzebra on Jul 3rd, 2004 at 02:28 PM]

Jurassic Referee Sat Jul 03, 2004 02:12pm

Quote:

Originally posted by blindzebra
Quote:

Originally posted by Nevadaref
PS And our esteemed author missed my favorite: The coach argues and is wrong about the rule. Not what happened on the play, not the judgment, just the plain and simple rule. = Whack!
I can't see that as an automatic, as described. The coach could very calmly question the rule application and you'd whack them?

If they are yelling, " That's not the rule, you got that wrong," across the court at us, then I'd be whackin' the coach right with ya, but that is not what you said.

[/B]
By definition, a technical foul is an unsporting foul, and every official has their own definition of exactly what "unsporting" is supposed to mean. In my experience, very few officials set the bar that high that simply questioning a call is deemed "unsporting". Very, very few. Too each their own, I guess though. To be quite honest, if one of my guys was this thin-skinned, I might suggest that another line of work might maybe be more appropriate for them- like possibly in a complaint department or sumthin':
http://www.gifs.net/animate/nsmail4k.gif

blindzebra Sat Jul 03, 2004 02:31pm

Quote:

Originally posted by Jurassic Referee
Quote:

Originally posted by blindzebra
Quote:

Originally posted by Nevadaref
PS And our esteemed author missed my favorite: The coach argues and is wrong about the rule. Not what happened on the play, not the judgment, just the plain and simple rule. = Whack!
I can't see that as an automatic, as described. The coach could very calmly question the rule application and you'd whack them?

If they are yelling, " That's not the rule, you got that wrong," across the court at us, then I'd be whackin' the coach right with ya, but that is not what you said.

By definition, a technical foul is an unsporting foul, and every official has their own definition of exactly what "unsporting" is supposed to mean. In my experience, very few officials set the bar that high that simply questioning a call is deemed "unsporting". Very, very few. Too each their own, I guess though. To be quite honest, if one of my guys was this thin-skinned, I might suggest that another line of work might maybe be more appropriate for them- like possibly in a complaint department or sumthin':
http://www.gifs.net/animate/nsmail4k.gif [/B]
To me it is the HOW they are questioning part that matters.
Like I said if it's calm and conversational, I've got no problem. If it is loud, demonstrative, and includes the words," You don't know the rule," then a whacking I will go.:D

Jurassic Referee Sat Jul 03, 2004 03:02pm

Quote:

Originally posted by blindzebra
[/B]
To me it is the HOW they are questioning part that matters.
Like I said if it's calm and conversational, I've got no problem. If it is loud, demonstrative, and includes the words," You don't know the rule," then a whacking I will go.:D

[/B][/QUOTE]Agree. The one way of questioning you is unsporting; the other one really isn't.

Of course, then you also might have to factor in the odd occasion when you're being questioned about a call that you, yourself, maybe aren't that sure that you got right either. The length of the rope just might vary with those different circumstances also. In that case, I'll let a coach maybe be a l'il bit more demonstrative. Once/iffy call only though. He doesn't get instant replay on his opinion ever. I don't wanna hear the same thing from him on my next trip by his bench. In my experience, most good coaches will give you their rant, mutter to themselves a little, and then after they've got it out of their system, they forget about it and go back to coaching. If they don't, then they probably wanted the T anyway.

Nevadaref Sat Jul 03, 2004 09:19pm

Quote:

Originally posted by Hawks Coach
Examples of Nevada's automatic Ts from games that I have coached in during the spring.

"Player didn't control the ball - Travel!" (this is how the call was made during the run of play!

Player dropped the ball while picking it up. I simplyt asked wasn't that a fumble. Response: "She fumbled it coach - that's a double dribble!"

Situation where A had ball in front court, B tapped a pass, A tapped it and recovered in backcourt. I tell ref that's a backcourt because A was last to touch in f/c. "Your player touched it coach, they didn't have control - that's not a backcourt!"

If this passes for rules knowledge from refs getting paid to ref a game, how can a coach that has these same understandings get a T for not knowing the rules?

And where is that T covered in the rulebook? It is somehow more unsporting to ask for a call when you have the rule wrong than when you have it right? Sorry Nevada, but this has to be one of the more ludicrous reasons for an automatic T that I have read.

Coach, That is great stuff! :)
I'd have to say that it sounds like these officials deserve a few technical fouls.
If anything, your post only serves to strengthen my position that poor rules knowledge is unacceptable and should be punished. The coaches who inflict their lack of understanding upon the officials should receive technical fouls. That is the only thing that will force these coaches to change. The officials who are as wrong as those in the examples you have provided should have games taken away. That is the most effective punishment for them.
I understand that a lack of other (quality) officials and availability problems pose serious challenges to what I advocate, but if I were in charge of the officials for a tournament, I could guarantee you that you wouldn't have to put up with those guys. I could also guarantee that poor conduct from coaches would hurt their teams.
The bottom line is that neither the refs nor the coaches should have these misconceptions about the rules. That is one of the goals of this forum. I feel obligated when I step on the court to do something about this problem.

PS Where is the T in the rules book? 10-4-1 (b) (also a, e, and f may be applicable)

Hawks Coach Sat Jul 03, 2004 10:00pm

Nevada
If the refs in my cases used your rule, I would have had two Ts, because in their rulebook, they were right.

As for 10-4-1b, why does it matter if the rule reference is right or wrong? It is the act of trying to influence the decision, not rules knowledge that matters here. Same could be said for any other provision.

If the coach is repeatedly disagreeing with calls, repeatedly questioning your judgment, does it really matter if he knows the rules or not? Likewise, if he only asks about one call, does it matter if he is ignorant of the rulebook? Nothing in any of those rules implies that it is ok to engage in this activity if you have rules knowledge.

And your argument that you train coaches to meet a higher standard than some of the referees we have doesn't wash with me. I know that you know I make the effort to know the rules. But refs are paid to know the rules, and I know them as well or better than many sub-varsity refs, and better than a few varsity refs that I personally know (not many - that seems to be a pretty good cut-off point around here). Most coaches don't know the rules that well. But depending on what level you are reffing, you frequently have a volunteer part-time coach who has to know a lot that you do not need to know (how to run a practice, manage parents, schedule a season, set up offense and defense, etc.).

Is it right to hold these individuals to that standard of knowledge of the rules, rather than work to get them to a better level?

My first time coaching, my team got a 5 seconds call and I never knew the rule had changed since I was in HS. My player was dribbling and got the ball below the hash mark - we were good from my perspective. If I had gotten Td rather than educated when I questioned the call, I would have left with nothing but disrespect for the refs and no greater rules knowledge then I entered the gym with. Instead I learned how much I didn't know, and started working to know the rules better.

Hawks Coach Sat Jul 03, 2004 10:09pm

Just read other thread
 
If this is what you mean, where coach complains, you tell him the rule, he says you are wrong - I can see where you are coming from. Still not sure you need to be instant with it, but I can understand that point a bit better.

If he just complains and is wrong, that is much different.

Nevadaref Sat Jul 03, 2004 10:53pm

Re: Just read other thread
 
Quote:

Originally posted by Hawks Coach
If this is what you mean, where coach complains, you tell him the rule, he says you are wrong - I can see where you are coming from. Still not sure you need to be instant with it, but I can understand that point a bit better.

If he just complains and is wrong, that is much different.

Yes, Coach, Chuck stated my position very well. I'd bet that when you got the 5 second call, you didn't continue to press the issue, you just accepted that things might have changed and that you were probably incorrect. I have no problem with that kind of question or conduct. Ask, get your answer, and then let it go. It is the next step beyond this line that is the automatic T for me. This is because now that I have told you what the rule is, by continuing to disagree, you are either questioning my integrity (calling me a liar about what the rule says) or just being disrespectful and a nuisance.

As for why I feel that coaches should be forced to have better rules knowledge (and the T is the penalty which will force them to go this route); I firmly believe that it would eliminate most of the confrontations in a game.
I contend that most problems at the HS level happen because the coach is ignorant of the rules and gets into a petty argument with an official about a call. Or the coach doesn't teach his players the correct rules (because he doesn't know them) and the player yells at the referee.
(I'm assuming quality officiating here, not your goofball guys. :))

Either way, the whole mess wouldn't have happened if he would just spend an hour or two with the rules book during the summer. The coach would then know the call was correct and focus on handling his team. Especially, for coaches that come back year after year, is it really too much to ask that they upgrade their rules knowledge as well as their coaching techniques?

You do this, and you should be applauded for it. You certainly wouldn't hurt your team with me on the court.

Jimgolf Mon Jul 05, 2004 05:38pm

Question for Nevadaref
 
Quote:

Originally posted by Nevadaref
For example, I point out that the author states one reason for calling a technical foul is:
2. Using profanity or language that is abusive, vulgar or obscene.

However, not only is this a technical foul, but according to NFHS rules it is also flagrant. The words chosen by the list writer even match those in the definition.

4-19-4
A flagrant foul may be ... If technical, it involves ... extreme or persistent, vulgar or abusive conduct.

That being said, I'd be willing to bet that the author is not advocating calling this flagrant. For many others, I'm sure that it would be.


Doesn't the sentence structure of 4-19-4 indicate that it has to be both "extreme or persistant", and "vulgar or abusive" to warrant a flagrant technical? Otherwise it would read "extreme, persistent, vulgar, or abusive".

rainmaker Mon Jul 05, 2004 07:54pm

Re: Question for Nevadaref
 
Quote:

Originally posted by Jimgolf
Quote:

Originally posted by Nevadaref
For example, I point out that the author states one reason for calling a technical foul is:
2. Using profanity or language that is abusive, vulgar or obscene.

However, not only is this a technical foul, but according to NFHS rules it is also flagrant. The words chosen by the list writer even match those in the definition.

4-19-4
A flagrant foul may be ... If technical, it involves ... extreme or persistent, vulgar or abusive conduct.

That being said, I'd be willing to bet that the author is not advocating calling this flagrant. For many others, I'm sure that it would be.


Doesn't the sentence structure of 4-19-4 indicate that it has to be both "extreme or persistant", and "vulgar or abusive" to warrant a flagrant technical? Otherwise it would read "extreme, persistent, vulgar, or abusive".

You are giving the Rules Committee way too much credit if you think that they have carefully weighed the grammar and vocabulary they use, and considered what the possible different meanings could be. If they'd only do it the way you are thinking, we'd have far fewer problems interpreting and explaining the rules.

Nevadaref Tue Jul 06, 2004 12:24am

I agree with rainmaker. It think that the sentence structure is really awkward and that we shouldn't make too much out of it. I also believe that it is intended to be exemplary and supplementary. Most important for me is the line above that states, "a technical noncontact foul which displays unacceptable conduct."

Hawks Coach Tue Jul 06, 2004 10:00am

I read that as two categories - you can be just a general pain in the (insert vulgarity here) or you can fall into the instantly vulgar or abusive category. either way, you can be Td.


All times are GMT -5. The time now is 05:09pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1