Just a question ? Should plate umpire indicate to the batter that on a dropped third strike he is not entitled to the run to first base if it is occupied ? I've always felt that it is not my job to instruct the batter, just make the right calls. There is no concensus among other umpires I've spoken to, some say telling batter he can't run is "preventative" umpiring, others say its coaching and not fair to either team. Thoughts ?????

"Strike Three, Batter's out". You've done enough telling there. The defense should know the situation.

I just call it and signal it, "he's out". If he starts to 1B I say again only louder "he's out, he's out" and signal again. It's my job to signal outs when I see them. It is also preventive.

The probability that I will say something to a batter is inversely proportional to his age.

That is, it depends on the level: I won't remind a "shaving-aged" batter that he's out, nor will I prevent such a catcher from making a pointless throw down to first. They need to know the rules.

You mention "preventive officiating," which is something I subscribe to for safety issues. I don't regard the batter taking off for first when he's not entitled to it as a saftey issue.

It might prevent an unpleasant visit from the O coach, if R1 gets picked off thinking he has to run, but then the coach should yell at R1. It might prevent an unpleasant visit from the D coach if his catcher throws the ball pointlessly into RF, but at that level chances are just as good that he'll yell at the catcher, not me.

But that's not what preventive officiating should be about. So what if they yell at me? *I* didn't screw up, so that conversation won't last long. Mistakes are part of the game, and it's not my job to prevent those, only to enforce the rules as tradition and local association dictate.

That is also what I do. "He's out. He's OUT!"

DG, what do you do for a dropped third strike when he can run?

[/B][/QUOTE]DG, what do you do for a dropped third strike when he can run? [/B][/QUOTE]I call "strike" and signal a strike, and wait to see what happens next. If it was an almost checked swing I point at the batter, say "he went" and signal a strike and wait to see what happens next.

I'm the forum's odd man out on this one. I call the strike if the batter was not swinging or just signal the strike if he was. If the defense doesn't know the rule or the situation and chooses to make a play, that's part of the game.

Look at this way, when first is not occupied and the batter could run but doesn't, do you help the offense by telling the batter to run? Of course not. Similarly, I see no reason to protect the defense from their own stupidity.

I should add, I don't work little boy ball. If I did, I might think differently,

[QUOTE]Originally posted by GarthB

Quote:

I see no reason to protect the defense from their own stupidity.

How is calling an out protecting the defense from their own stupidity?

In the absence of a call in this situation, the defense may be perfectly smart, but they may have concern that the plate umpire is the "stupid" one, who may actually allow the batter to advance even though by rule he can't.

A simple "he's out" called only loud enough for F2 to hear it is all that is needed to keep the play, and possibly the game, from degenerating into a Keystone Cops skit.

On a swinging strike 3 when the batter can't run, I point at the batter, signal the out while yelling "batter's out, batter's out"!

If not swinging, and I hate when this happens, I will bang batter out, and then yell "batter's out, batter's out" if he begins to run.

9.99% of the time, if the catcher cannot catch a strike, it's a ball to me.

IMO, as PU, you bang out the batter and the ball ends up at the backstop, you look like a clown and not the catcher. And I'm gonna do it anymore!

We should not be directing play here. If you're normal call on a 3rd strike is "Strike Three! Batter's Out!", don't yell it extra times based on batter's actions.

<i> I'm the forum's odd man out on this one. I call the strike if the batter was not swinging or just signal the strike if he was. If the defense doesn't know the rule or the situation and chooses to make a play, that's part of the game.

I should add, I don't work little boy ball. If I did, I might think differently, </i>

Garth, I've seen PROS run to first on a dropped third strike with 1st base occupied and less than 2 outs. Therefore, IMO, this question has nothing to do with the age of the players.

The umpire MUST be clear on this. By simply signally strike three, you have done nothing.

Do we have an out?, etc.

Even in the BIGS I've seen the PU call the batter out.

Pete Booth

As I said, I realize that I am the odd man out here.

To answer one of the questioners, I never say "Strike three, he's out" on called strikes or swinging strikes. I say simply say "Strike three" on called strikes and signal on swinging strikes.

To answer another, when I said I don't do little boy ball, I didn't mean to imply that only they mistakenly ran to first. When I did mean to imply is that the older players should know better.

And finally, using exta mechanics to call attention to the batter running when he is "not supposed to" does protect the defense from making a play and possibly throwing the ball away and allowing other runners to advance or score. If they are that dumb, so be it.

All that said, yes I know judging from all you others my opinion is wrong. I have given it, I know it is not popular, I'll live.

GB:
 

Not that odd.

I have never, nor would I ever, say "Batter's Out!" in games played by shaving aged players.

All players have the responsibility to understand rules and happenings on the field.

I simply signal the strike.

Tee:
 

<B>"All players have the responsibility to understand rules and happenings on the field."</B>

You'd think, wouldn't ya?

I had a coach ask me on Saturday to please hurry my strike three calls so their batters would know to run to first base. I just looked at him a bit dumbfounded. I had no idea how to respond to that.

I kind of agree with Garth and Tee as well.

My point was that we are not there to direct either team. Whatever your NORMAL mechanic on strike three, DON'T change it between a normal D3K and a D3K with someone on first. Use the exact same mechanic for both. If it's "Strike Three!" or just your strike signal. Do that. If you yell Batter Out when a batter is out, then do that, but don't yell it again and again when you see a retired batter running.

Changing things up alerts one team or the other inappropriately.

I too, never say "batter's out". The only thing I do differently on a dropped third strike where a batter can, by rule, run to first, is to not make the out signal. I purposefully do not use the closed fist to signal strikes. To me, that signals an out. A strike is a point of the hand in some manner. This avoids confusion on the dropped third strike.

Assuming first base is open or two are out, if the dropped third strike is looking, I'll verbalize strike and point. If it's swinging, I'll just point.

I had the defense throw the ball away this weekend on a dropped third strike with first base occupied and 1 out. The coach asked me about the rule and I had to explain it to him. Oyyy! No wonder the kid's didn't know...

If a batter swings and misses the 3rd strike and it's caught by the catcher, do you not signal and vocalize the batter out?

I signal and vocalize that the batter is out. If it is dropped and the runner cannot advance to 1st by rule, I will vocalize that the batter is out.

To each his own.

I thought it is our job to call fair/foul, balls/strikes, safes/outs.

Why would you not call an out when you have one?

6.05
A batter is out when_ (b) A third strike is legally caught by the catcher;
(c) A third strike is not caught by the catcher when first base is occupied before two are out;

JMO

Kaliix, I can identify.

Couple of weeks ago, 2 outs, bases loaded, D3K gets away, F2 picks it up and touches home. Out. Inning over.

Couple of innings later, the other team batting this time, 2 outs, Runner on 2nd only. D3K. Coach is yelling "Touch Home Plate!!! Touch Home Plate!!!", so catcher touches home plate. Of course, I make no signal at all, play evolves and R1 ends up on third, with BR at 2nd. Coach calls time and rips me for not giving him an out when her catcher touched the plate, when just two innings ago I'd called his team out in "exactly the same situation". This included such nonsense as him jumping up and down on the plate (reducing this man to "The artist formerly known as Head Coach") and, "How can you stand there at home and make no call!"

wow MC how do you deal with coaches that are that stupid. So with bases juiced, he could not understand the force at the plate? No force with only R2. I bet you are thinking "what an idiot", while he was doing his jumping routine.

I do FED games and I am often surprised by coaches that ask questions about re-entry, batting order, etc. Isn't it important to them to understand the rules of the game they are trying to coach??

Not to whip a dead horse,
 

"If a batter swings and misses the 3rd strike and it's caught by the catcher, do you not signal and vocalize the batter out?"

I signal the strike just as I did the first and second strike. If it is a called third it is more demonstartive but means the same thing.

No, I have never said, "Batter's Out"

Weak kneed analogy:

If I am a BU and the Batter-runner is out by ten feet I have never said, "He's Out!" or "Out" that is a given -- I simply signal the out.

I am not sure this fits with what we are talking about but IT IS another time that you do not verbalize the out.

Re: Not to whip a dead horse,
 

"If a batter swings and misses the 3rd strike and it's caught by the catcher, do you not signal and vocalize the batter out?"

I signal the strike just as I did the first and second strike. If it is a called third it is more demonstartive but means the same thing.

No, I have never said, "Batter's Out"

Weak kneed analogy:

If I am a BU and the Batter-runner is out by ten feet I have never said, "He's Out!" or "Out" that is a given -- I simply signal the out.

I am not sure this fits with what we are talking about but IT IS another time that you do not verbalize the out.
[/QUOTE]

The difference is, IMO, everyone in the world knows he is out by ten feet.

The same with a caught line drive and runner is going on the pitch, throw to the base, easy DP. No need to vocalize.

I see your point, but I feel it is different when so many things are happening in a split second. Batter swings misses, catcher drops the ball, runners take off, BR takes off, coaches are screaming, etc.

The batter is out, call him out!

Just to further try and prove a point, lol, when a runner passes another, do you not call that runner out and identify him?

Or, would you just signal an out and let the runners continue their escapade around the bases and have the defense figure out which one they need to tag?

Not to mention your partners confusion!

Is there no set mechanic for this situation?

If strike three is dropped and the batter starts to run, I will yell "the batter's out, the batter's out" no matter what level of ball I do (and all I do is College and Independent Pro). It solves more potential problems than it can lead to if nothing is said.

Lets look at the other side of the coin. 1-1 count, 1 out, runners on first and second. Batter swings at a ball in the dirt that gets by the catcher. R2 and R1 now move up and become R3 and R2. Counts now 1-2. He swings at another ball in the dirt. You now say "Strike 3, batters out" batter hearing this, he stops running, the catcher tags him easily. Now the O coach is climbing in your a$$ because your actions put his runner in jeopardy.

Make the players and coaches responsible for knowing the rules. Everyone on that field should know that he can't run when there are less than 2 outs and first base is occupied.

JJ, if you do that level ball, then surely you've seen plays where BR runs on the dropped 3rd, and the other runners try to move up. You're additional commentary tells defense what to do - which is not your job. Hell, you might as well yell, "Get him at third, catcher!!!" while you're at it.

Call the game. Officiate the game. Don't EFFECT the game.

Re: Re: Not to whip a dead horse,
 

If a batter swings and misses the 3rd strike, I signal a strike/out by a closed fist. No need to say anything, everyone knows he's out. If a batter swings and misses the 3rd strike and the catcher drops the ball (and the batter can run), I vocalize the strike but with a point signal, not a fist, as the batter needs to be put out and fist signal would be inappropriate.

It's the same reason I don't say "take your base" on ball four or point. Everyone knows you get first on ball four.

The appropriate established mechanic for calling a runner out when he passes a lead runner is to point at him and call him out for passing.

As aevans410 said It's the players job to know the rules, it's my job to officiate them.



The difference is, IMO, everyone in the world knows he is out by ten feet.

The same with a caught line drive and runner is going on the pitch, throw to the base, easy DP. No need to vocalize.

I see your point, but I feel it is different when so many things are happening in a split second. Batter swings misses, catcher drops the ball, runners take off, BR takes off, coaches are screaming, etc.

The batter is out, call him out!

Just to further try and prove a point, lol, when a runner passes another, do you not call that runner out and identify him?

Or, would you just signal an out and let the runners continue their escapade around the bases and have the defense figure out which one they need to tag?

Not to mention your partners confusion!

Is there no set mechanic for this situation?

[/QUOTE]

I may not always call the batter out when he is out, such as an obvious swinging strike 3 when the catcher does catch the ball, or a popup to the pitcher, but I always call him out when he is and there is some question about it, such as dropped 3rd strike. I see this as my job to remove all doubt about a call that is not obvious. I have also never said "strike three" or "ball four", etc, I also don't say "foul ball". I use the words "strike", "ball" and "foul".

Agreed.

And, (I think this came up in this thread), I give the "safe" sign and some verbal (I think it's either, "the ball's down" or "no catch") if there's a question that the strike was not caught (and it's a situation where the batter can run).

DG - the reason I've been taught to say FOUL BALL instead of just FOUL is that a loud FOUL call sounds just like a loud OUT call. FOUL BALL is unmistakeable.

<i> ]Originally posted by mcrowder

kind of agree with Garth and Tee as well.

My point was that we are not there to direct either team. Whatever your NORMAL mechanic on strike three, DON'T change it between a normal D3K and a D3K with someone on first. </i>

There's a difference between a "Normal" strike three and an uncaught third strike. In a "Normal" strike three mechanic, everyone in the park knows it's strike three and the batter is out. No need to add insult to injury by vocalizing. The batter along with everyone else knows he/she is out.

Now the dropped third strike.

As a former player, insticts take over regardless of the situation. When you as a batter see F2 drop a third strike, instictively you start to run towards first. This happens at every age level even in the BIGS.

As an umpire IMO we should tell everyone what is going on. A simple batter is out is all that is needed. No need to go crazy but a verbalized out call is appropriate. IMO we are not "intervening" ourselves into the game.

Side Note: Papa C et al, IMO this topic would make for a good series of articles. Perhaps the topic could read Verbalization of Calls or something along those lines.


Pete Booth

pardon my petrusion
 

Just visiting from the Softball board, but couldn't help mentioning something here since it seems relevant.

Last Saturday, I'm a spectator but sitting at the official scorer's table (new scorer's first game). One out, bases loaded, D3K: everyone goes hard. F1 comes in and gets the ball from catcher while standing on the plate: Blue gives R3 out on the force.

Hold on... At the scorer's table everyone is confused. Why a force with less than two outs? Did the umpire see something else? Maybe a fair hit ball that somehow rebounded behind the catcher? (Is this even possible? I don't think so.) Or were there already 2 outs, and had the scorer missed one? (Much more likely.) But play continued after the out. I argued (with the scorer) that there was no possibility other than a D3K. But the scorer tells me there was only one out. We discuss during the rest of the inning.

After the inning ends, the scorer calls the Umpire to the table for an explanation. Says he had 3 outs altogether. That means there was no mistake on the scorer's part that there had only been one out (otherwise he would have ended up with 4.) Why the D3K with less than two outs? There were two outs, says he! I argue (in no official capacity whatsoever) had there been two outs the force at home would have been out 3, inning over. (Three more runs scored afterwards.)

Long story, but I hope my point is clear: confusion ruled in this sitch. Both umpires had brain farts. Why? Because everyone went, and went hard, and the umpires had been trained to wait and see how the play develops. So put me in the camp who says, when BR can't go because the rules won't let him, call him out.

I think that when confusion rules, the umpires have not done their jobs. In this situation, and this situation ONLY--D3K with less than 2 outs--the umpire should call the batter out. It doesn't lead to an advantage of either team. It does avoid confusion.

jeffstone
goettingen

Re: pardon my petrusion
 

This had more to do with the umpire screwing the pooch than a dropped third strike. If everyone is going hard that means all the runners are unaware of the rule as they should know with the bases loaded and 1 out that the BR can't advance to first. If they are running, it may be because of a passed ball more than a D3K. The umpire should have never called an out on the force, that messed everything up. He should have ruled the runner safe, no tag. And if he called an out on the force at home, how come the inning continued? Two umpires didn't catch this???

Thinking on the original issue more, there is one time where a signal other than strike seems appropriate. What about a thrid strike where the BR could advance on a D3K and pitch is close to the ground but the catcher did catch it and not short hop it? Shouldn't there be some signal made to confirm that the catch was clean and there was no D3K?

Re: Re: pardon my petrusion
 

Indeed, I think that was the case...but BR went hard as well...otherwise there wouldn't have been a force.

Indeed, two umpires screwed the pooch. But, again, as I said in my post, I think it happened because the umpires were waiting to see how the play developed, because that is how they have been trained and that is their habit. At the scorer's table the PU explained that "everybody went." He was no longer thinking about how many outs or anything else; he was just looking at the play as it unfolded. He screwed up, no doubt. The question is: would he have screwed up IF he were in the habit of making sure that when BR cannot run on a D3K he should call the batter out. That's my only point.

jeffstone
goettingen

Re: Re: Re: pardon my petrusion
 

Everybody went. Smart catcher tags the runner from 3B for the 3rd out. Batter is already out.

Dropped third strike
 

AS I said in my original post, there is no clear consensus on what to call (or not call)

From a coach's perspective....

(Oops, most of the readers have just skipped this post)

I think Kaliix has the best mechanic, and in his most recent post, articulates the reason why - that <b>low</b> third strike that maybe <b>is</b> caught by the catcher, or, maybe it <b>isn't</b>. Actually, it doesn't even really <b>matter</b> whether the catcher legally "caught" it or not. What <b>really</b> matters is whether or not the umpire <b>judged</b> that he caught it.

It seems that there is a <b>wide</b> variety of opinion and practice in regard to this particular question.

We have:

1. Signal the strike, nothing more - the players are supposed to know the rules and whether or not the batter has become a runner.

2. Signal the strike and vocalize/signal the out if the batter has <b>not</b> become a runner - just as you normally would. Otherwise, signal/vocalize the strike, but <b>not</b> the out, since the batter <b>has</b> become a runner.

3. Signal/vocalize the out in a way that is dramatically more <b>emphatic</b> than your normal mechanic if the batter has <b>not</b> become a runner; indicate "no catch/safe" if the batter <b>has</b> become a runner.

In my opinion, #2 is the proper and superior mechanic. The reason I believe this is that there is no way for either the defense <b>or</b> the offense to know whether or not the batter has become a runner without the "batter is out" indication from the home plate umpire. I'm specifically referrring to the case that Kaliix highlighted where the catcher's glove is "in the dirt" as he cleanly gloves the pitch. Did the catcher "catch" the pitch <i>in the umpire's judgement</i>? Without the "out" indicator, there's no way for <b>anybody</b> (other than the umpire) to know. I would suggest that both teams have a <b>right</b> to know what the umpire's judgement was in this case.

If you agree that they do, then you should <b>always</b> indicate the out <b>anytime</b> there is the possibility of ambiguity. Otherwise, you are calling "unnecessary attention" to the "special case" where the batter has or has not become a runner.

I agree with those that suggested approach #3 is excessive and borders on "coaching". It's my responsibility to teach my players the rules and it's my legitimate advantage if my opponent has not taught his players as well.

To me, the most important thing is the <b>visual</b> indicator.

I'm going to let you guys in on a little secret. No matter what you say, and no matter how loudly you say it, on "exciting" plays like this, usually nobody on either team actually <b>hears</b> it. Its kind of like talking to your children.

So, on a strikeout, indicate the strike, indicate the out (if there is one) - <b>always</b>! If your "style" is to do so both visually and audibly, then do so. Don't do <b>anything</b> differently because the conditons were such that the batter became a runner because, in your judgement, te 3rd strike was not legally caught.

JMO

JM

If a batter swings at a third srike that is dropped, in a situation where he can not attempt to run to 1B, and he attempts to run, he will know very quickly, along with everybody else in the park, that he is out.

Pete: I'm surprised that no one has bothered to point out that as far as the NFHS is concerned, the correct mechanics for this play are covered in the case book. It's 8.4.1 SITUATION K, and I explain in the new section "Mechanics" (329) in the 2005 BRD.

I won't spoil anybody's fun by quoting the book here.

I feel vindicated in my position as far as FED is concerned, but I would probably make the same call/mechanic at any level since habits are, habitual.

I'm with Bob and JJ. It's preventive and good officiating at ALL levels. Had it happen in a men's game on Sunday. Three "batter's out"s after the ball bounced and the batter started for first.

Of course, the offense argued that the runner was STEALING so first base wasn't occupied. Ri-i-i-i-i-ght.

I say more than once that the batter is out. The players do not listen to you anyway. The defense still throws the ball in many cases. What the umpire says is really not that influential. I also do this regardless of level.

Peace

regardless of the situation, it seems the BR always runs, since everyone is screaming at him to run everytime. Theres no penalty for running (for him), so why not run? Only penalty is that R1 (if present) starts for 2B and gets trapped. But even with the BR ineligible to run on a D3K, Ive never *not* had everyone and his cousin scream at him to run, and he's never failed to run at least 3/4 of the way to 1B before he realizes hes out. Of course, I work a much lower level of ball than you guys, which is a large part of it.

In a similar situation, do you quickly and emphatically announce ball four if R1 is stealing? Or do you simply use your normal timing and call ball while the catcher is throwing to second?

How is that similar?

A ball is a ball!

An OUT is an OUT!

Stop reaching! What would you suggest, "that's ball four, don't throw catcher"! Gimme a break!

Even if the catcher throws, what are the odds that R1 is going to get to third?

I'm talking players who play and are coached baseball!

It's EXTREMELY similar.

It's an example of the umpire changing the way he calls his play because of subsequent action. It's an example of an umpire saying or doing things he shouldn't be saying or doing that could have an effect on action, when he should NOT be affecting action.

This is a GREAT example.

99% of you out there would NEVER yell "Ball Four, Ball Four!!!" if you saw a catcher trying to throw R1 out when stealing on a base on balls. (Those that would can remain at their respective levels, and hope they never do such a thing in front of an evaluator or assignor).

Yet many of you who see why you should not make THAT call are proponents of "Batter's Out!! Batter's Out!!" as "preventative umpiring".

It's the SAME - and you should not do anything different on this play than you would normally.

If you disagree --- tell me WHY "Ball Four!! Ball Four!!" is the wrong thing to do, but "Batter's Out!! Batter's Out!!" is the right thing to do. I sit prepared to be dazzled by your logic.

my logic is, on a ball four/R1 stealing, even if the throw guns R1 out, hes still safe due to the walk (theres a case play on this, IIRC). Therefore, whether the catcher throws down there or not is irrelevant to the play. If its an overthrow and the stealing runner tries for third, *thats irrelevant to the ball four call.* Hes at risk no matter how loudly I call "ball 4," or if it was a strike.

OTOH, the BR erroneously running to 1B on a D3K (usually) impels R1 to advance, which puts him (R1) at serious risk. Of course, this can still happen since if they dont listen to you and advance anyway, and R1 goes, he is risking a putout.

Plus, my Ump's manual instructs me to call this "forcefully", so I do. It says nothing about calling "ball 4" forcefully. So thats what I do :)

I disagree!

And I'll tell you why.

IT'S AN OUT!!!!

THAT'S WHY! JEEZ!

Other experienced and respected officials on this site have given their view on this, which is to declare the out. "Batter's out"! Even saying it twice.

Have you not read the entire thread?

I don't see it as preventive officiating, I see it as calling an out when I see it.

I edited this to ask: how do you quote various parts of a post without it seeming as one, like I just did?

Sorry bout that! I'll get it sooner or later.





[Edited by thumpferee on May 4th, 2005 at 07:48 PM]

I hever say Ball Four. All balls are called "BALL". What if BR was called out at 1B on a close play but made a sharp turn and started for 2B? Would you call him out again forcefully or stand there amused that he would attempt to do something he is not entitled to do?

Why should logic play into this? Why would we make a safe call on a BR at first when we know he missed the bag only to call him out when an appeal is made, but yet when same play happens at home we don't make a call until something else happens? It's because both are accepted mechanics. I was taught to forcefully call out a BR who can not advance to 1B on a dropped third strike, and it has never caused me a problem, so I keep doing it this way. You may have been trained differently. Don't expect a logical explanation for everything.

[Edited by DG on May 4th, 2005 at 11:00 PM]

This situation reared its ugly head last night for me.

Reserve game, home team was up to bat. This school is known for its creative baserunning.

Bases loaded, 1 out. 3rd swinging strike is dropped. After reading Papa C's post about the proper mechanic in the case book, I loudly declared (multiple times mind you) Batter's out!

Low and behold, the defense STILL starts throwing the ball around like trained monkeys. The ball didn't get away, it was just mishandled. The runner takes off for first, R1 starts baiting the catcher, who makes a throw. He gets back, but R2 takes off. The throw goes to 3rd and they get R2 in a rundown. As soon as the ball is thrown from the plate, D coach is going nuts. He can't believe his players are doing this. "You should know better than to throw the ball around" and "You just gave em a run".

So what have we learned, even though we anounce that the batter is out, the defense still doesn't listen. No advantage gained and we cover our butts as PU by announcing the out.

Now coaches need to start teaching their batters to just head to the dugout if they cannot advance.

Let me ask you aevans, did it feel funny to you announcing the batter's out, or did it seem natural?

It felt odd. I definitely had to think about it. Thats the way NFHS wants it called though, thats the way I'll call it.

With regards to ball four - when I call a pitch a ball I say, "Ball" UNLESS it's ball four, then I say, "Ball four". Every now and then, with a runner on first and a full count, a catcher will ask me to "give me a quick and loud "ball four" if that's what the pitch is" - so he doesn't have to make a quick throw to second if it's not necessary. I oblige as best I can (that timing thing is involved...). If that makes me "umpirically" (yes, I made that word up) incorrect, I don't care.

exactly
 

I always say the same "ball four". I want them to know so the game keeps moving.

But even better, when there are three balls I will say the count to batter and catcher. 3-1 or 3-0 etc.,

I've found that anything I can do to inform will only help keep the game smoother and that makes it better for the umpires.

I don't assume that players know anything, and I know for certain that coaches DO NOT know anything.

Call the batter out and if they want to run around let them, but I've covered myself and my partners.

Same as the infield fly, call it and then when all kind of mess happens, you've done you're job.

I guess I would put these under preventive officiating.

Thanks
David