As part of my research for my third baseball novel (working title Big Ed Delahanty: Goliath of Baseball's Gilded Age) I am reading Napoleon Lajoie: King of Ballplayers. The author writes that in one of Nap's (they called him Larry) first games, September 1st, 1896 the home team Phillies batted first against the visiting Reds in the early game of a doubleheader.
Not quite true. Further research revealed that it was really September 2, but that's not the point. The point is that, as is often the case, it sent me scurrying to find out how often that happened in those days.
For the record, it was not until 1950 that The Official Rules of Baseball set out in Rule 4.02 that "The players of the home team will take their defensive positions, the first batter of the visiting team shall take his position in the batter's box, the umpire shall call "Play" (not "Play Ball" for all you amateur umpires out there) and the game shall start."
After a loss to the Anaheim Angels in 2002 Yankee skipper Joe Torre told reporters, "It's tough to lose an extra-inning game at home because you have the advantage of batting last, but we didn't get the hits when we needed them." Conventional wisdom I think you would agree. But not always.
Twirler John Richmond of the Worcester Ruby Legs pitched baseball's first perfect game in 1880. Note below that while Worcester was the home team, they batted first.
Originally - as on the sandlot - the first team to bat was decided by a coin toss. But as of 1887 the National League permitted the home team manager to decide who would hit first. As late as 1894 the home team batted first 41 per cent of the time.
|Cap Anson's Chicago Colts|
A February 3, 1911 piece in the Milwaukee Sentinel explained why things had been different back in the day. Managers believed that if they could get first crack at the new ball (only one would be used - if a ball went into the stands it was retrieved) before it had been blackened and softened and "harder to see and land upon" they could grab the lead and demoralize the visitors.
An article in the Detroit News three years later agreed. "Right now all the clubs go to the field first when on their home grounds, the custom has become firmly rooted and no manager thinks of changing. Yet many years ago it was equally the rule for the home team to bat first and the argument on which the managers maintained the system was the supposed advantage of getting first crack at the new ball."
So, is the now accepted wisdom correct? The most scholarly piece I could find on the subject was a 2008 dissertation called "Last-Ups Advantage in Baseball: A Game-Theoretic Approach" for the Texas A &M Department of Economics by Theodore L. Turocy. After revealing the results of calculations I couldn't fathom in a month of no ball games allowed Sundays he concludes, "There is a way in which an errant belief in an advantage to batting last might have a negative effect on a team's chances of winning. The quantitative results of the model suggest that a manager would do well in ignoring whether it is the top half or the bottom half of the inning and basing tactical results on the inning, configuration of baserunners, and number of outs. If a manager believed in an advantage to batting last he might not behave in that way; in fact a common saying is to play for the tie at home, and the win on the road. If in fact batting last is not an advantage, this would be poor advice." So there.
Back to a world most of us can understand. Has there been any recent game in which the home team batted first? Well, it turns out there was. Due to a large number of rainouts in 2007 a Cleveland Indians home game scheduled for April was played later in Seattle and - as a result of mutual agreement and a recent rule that allowed it - the visiting Indians were given the option of batting last, which they did. And now you have "the rest of the story."
|Big Ed Delahanty|