Thats a Balk - by the numbers

[Kevin Finnerty]

Oh, okay, I'm shying away from a tough call.

Yeah, I have a toughness problem. And a poor grasp of justice.

Anything else you can draw from your gross oversimplification?

A balk is not a balk like a strike is a strike. For every balk, there are at least 1000 strikes. Sometimes 2000. Or more.

Try another equation.

[Durham]

Umpires learn balks in stages. By this I mean we all go through phases and as we grow as officials our understanding of the game, our role, and what a balk is changes. I don't know everything about umpiring, but I do believe that balks are one of the last things that we master in this trade. I think the reason is we don't see them often enough, and our focus and game awareness grows as we do.

Where I am at now with my officiating I see almost ever balk that happens in a game, but I don't call everyone. I often use some preventative officiating, and I might mention it to a member of the defense that he is getting close, or I might mention it to the pitcher if he is close enough after a play or something. And like a football official giving the coach a chance to take care of an issue with one of his players before the flag flies on a similar event, I will use this approach when I can. If a coach makes mention of it, I will let him know that i will look for it, or ask him to tell me what he saw, if he says, watch the front knee, then the defense will often tell the pitcher to clean it up and the game moves on.

On the other hand, if the pitcher flexes that front knee or closes the front shoulder and freezes R1 for even a split second, I'll bang that thing right away.

There is no right or wrong answer to balks, there is only, what does the guy that signs your checks want you to call. Know that, and know your role in the game, and everything else will work out.

[Kevin Finnerty]

Finally, a serious dose of wisdom on the subject!

Thank you, Durham

[UmpJM]

Kevin,

What's not to like about making balk calls? I think it's fun!

Why would you call an "obvious" balk but not a "subtle" one if you saw it?

I prefer to just call it when I see it & not consider whether or not it was "obvious".

JM

[TussAgee11]

Originally Posted by Kevin Finnerty

Oh, okay, I'm shying away from a tough call.

Yeah, I have a toughness problem. And a poor grasp of justice.

Anything else you can draw from your gross oversimplification?

A balk is not a balk like a strike is a strike. For every balk, there are at least 1000 strikes. Sometimes 2000. Or more.

Try another equation.

Does the rules say one is lesser than the other?

Better to prioritize your responsibilities, and if you end up seeing a balk, call a balk. I don't care if anyone else did. Its my JOB that if I see it, I call it.

An umpire's job is, at its basic element, to enforce the rules throughout the game. Nowhere in the book does it talk about "if the game is close." To me, this issue is similar to the issue at the end of basketball games in terms of the supposed "letting them play," which has become an official faux pas.

I rarely draw comparisons from the pro-game to amatuer ball, particularly because balk problems are much more widespread at the amatuer level. But through the grape vine, I have heard that it is better in the eyes of those who evaluate to have the balls to make a tough, non popular call that is correct in a tough spot than pass on it for whatever reason.

Frankly, other than prioritizing my responsibilities on any given play for mechanical purposes, each rule is just as important as the one that precedes it in the book. Some may come up more often, but they are all to be enforced.

[tip184]

It's challenging enough to identify a balk and call it when you see it. Now combine that with having to make a judgment according to the level of play, inning, score, whether it decieved the runner, etc. I think it is too much to ask an umpire to consider all these factors when a player would learn more from having the balk called.

Many umpires will only call a balk if it is completely obvious. A lot of leagues don't want the "picky" stuff called. Calling the game according to how the team wants it called rather than how the rules state the game actually should be called is a challenge all umpires face.

[MrUmpire]

Originally Posted by TussAgee11

Does the rules say one is lesser than the other?

Better to prioritize your responsibilities, and if you end up seeing a balk, call a balk. I don't care if anyone else did. Its my JOB that if I see it, I call it.

An umpire's job is, at its basic element, to enforce the rules throughout the game. Nowhere in the book does it talk about "if the game is close." To me, this issue is similar to the issue at the end of basketball games in terms of the supposed "letting them play," which has become an official faux pas.

I rarely draw comparisons from the pro-game to amatuer ball, particularly because balk problems are much more widespread at the amatuer level. But through the grape vine, I have heard that it is better in the eyes of those who evaluate to have the balls to make a tough, non popular call that is correct in a tough spot than pass on it for whatever reason.

Frankly, other than prioritizing my responsibilities on any given play for mechanical purposes, each rule is just as important as the one that precedes it in the book. Some may come up more often, but they are all to be enforced.

This post, unless I misunderstand it, makes you appear to be a "black and white" rules umpire.

Would that be correct?

Do you have this same philospohy, "Its my JOB that if I see it, I call it.", with every rule?

[TussAgee11]

Originally Posted by MrUmpire

This post, unless I misunderstand it, makes you appear to be a "black and white" rules umpire.

Would that be correct?

Do you have this same philospohy, "Its my JOB that if I see it, I call it.", with every rule?

Here's my deal. I will prioritize my responsibilities in accordance with my anticipation for a particular play. For example...

I'm PU, R3, 1 out. Fly ball down the LF line. Guess what will be last on my priority list. The tag up at 3rd. I got a fair/foul and then a catch/no catch on my plate first. So when I get to my tag responsibility, how could I still be "black and white" with the rules? Unless I see something glaring here, R3 ain't getting called out, even if I suspect it was a second early.

Same idea goes for balks. Am I going to get balks that I am 80% certain about? Heck no. Only 100%. And if I'm 100% about it, chances are it was what some other posters claim would be "obvious." Maybe it won't be, but to me it was, and that's all I care about.

I'm talking JV/Vars and up.

[Blue37]

Originally Posted by Blue37

What about #9? I am at work without books, so I cannot look it up. I did not know that was a balk. It is one of the "technical" balks that is not called?

Guys, can you help me with this one? I got the books out when I got home and must be overlooking something, 'cause I could not find it. In 26 years I have never seen anyone call this or complain when it was not called.

[BigUmp56]

Originally Posted by Blue37

Guys, can you help me with this one? I got the books out when I got home and must be overlooking something, 'cause I could not find it. In 26 years I have never seen anyone call this or complain when it was not called.

From the J/R:

Balks

It is a balk if a pitcher:


9. Does not step to a base in throwing (or feinting a throw) to such base.


Tim.

[MrUmpire]

Originally Posted by BigUmp56

From the J/R:

Balks

It is a balk if a pitcher:


9. Does not step to a base in throwing (or feinting a throw) to such base.


Tim.

From the OP:

9. after a feint or throw to a base from the rubber, fails to disengage
the rubber before reengaging and pitching;

[tip184]

Originally Posted by TussAgee11

Same idea goes for balks. Am I going to get balks that I am 80% certain about? Heck no. Only 100%. And if I'm 100% about it, chances are it was what some other posters claim would be "obvious." Maybe it won't be, but to me it was, and that's all I care about.

If you are 80% sure about it, then it probably was a balk. Trust yourself.

[TussAgee11]

If I make 3 80% balk calls over the course of a week, I have a pretty low chance of getting them all right.

Baseball, most of are calls, there has to be a call (ball/strike, safe/out, fair/foul). Things like balks, OBS, INT, we make either a call or a no call, very similar to basketball. Basketball guys will tell you, only call what you know you have. Its not a trust issue, its an understanding of yourself and the limitations that surround you on the field.

Dissent within balk philosophy isn't anything new, I don't suspect we'll clean it up in this thread.

[tballump]

Dyou see it, dyou call it, dyou splain it. Thats all you have to do.

[TussAgee11]

Originally Posted by tballump

Dyou see it, dyou call it, dyou splain it. Thats all you have to do.

What if you think you saw it, but can't be sure? I'm thinking about something that may happen in the corner of your eye or just out of your vision (perhaps a front side balk that your pard' may have missed from behind the plate). Just askin'