andrew.parlette.net

Introduction

This guide is designed to help official scorers in 10u baseball games ensure consistency and accuracy in box scores and stats, using MLB baseball scoring as the primary source. While most rules are based on MLB scoring rules, this guide highlights specific areas that need attention or clarification due to the skill level and rules of 10u baseball.

The objective is to maintain consistent, accurate, and reliable statistics for our players, team, and coaches. Producing box scores and season statistics is a part of baseball tradition, providing valuable insights and a historical record of the game. Accurate scoring is also crucial during the game for the current score and real-time information like pitch counts and spray charts.

While statistics are a component used strategically and for fun throughout the season, they are not the sole or most important element for player review. Coaches recognize that sometimes a hard-hit ball results in an out, or a little bloop hit results in a base hit. Being present at the games allows us to see these events firsthand, ensuring that statistics are always considered within the context of the game.

By following these guidelines, scorers can help maintain reliable statistics, contributing to a fair and enjoyable experience for everyone involved.

Pregame Preparations

Identify the Opposing Scorekeeper

• Exchange Lineups: Make sure to find out who the other team’s scorekeeper is and exchange lineups before the game. This helps both teams ensure that they have accurate information for scoring.
• Verify Lineups: Verify both teams’ batting orders and starting positions to avoid discrepancies during the game.

Lineup Verification

• Our Team’s Lineup: For our team, verify the batting order and starting positions. If the lineup was sent in advance, ensure it is correctly loaded into GameChanger.
  • Example: If Mike sent Andrew the lineup before the game, it will be loaded into GameChanger already. Verify that this information is correct before the game starts.

Doubleheaders

• Lineup Consistency: For doubleheaders, lineups are usually the same but should be verified with both teams before the start of each game.
  • Example: Even if the lineup remains the same for both games, confirm with the opposing scorekeeper to ensure consistency.

These preparations help prevent errors and ensure that both teams are on the same page before the game begins, leading to a smoother and more accurate scoring process.

Gamechanger Tips

Set Defensive Lineups Each Inning

• Update Defensive Lineup: Ensure you set the defensive lineup for your team at the start of each inning. This involves updating the positions of all players to reflect the current defensive setup.
  • Substitutions: When a substitution occurs, immediately update the defensive lineup to reflect the change. This ensures accurate record-keeping for all plays involving the new players.

Track Opposing Pitchers

• Record Current Pitcher: Focus on recording the current pitcher for the opposing team each inning and on any substitutions. This is crucial for tracking pitch counts and pitcher performance.
  • Missed Changes: If a pitcher change is missed, click on the first play involving the new pitcher and update the pitcher. This will retroactively correct all pitches from that point forward.
  • Example: If the opposing team changes pitchers in the middle of an inning, click on the first play that the new pitcher was involved in, select the correct pitcher, and GameChanger will update all subsequent pitches.

Recording Plays

• Caught Stealing:
  • Tap Both Players: When scoring a caught stealing, tap the catcher first, then the fielder who receives the throw and makes the tag.
  • Example: For a caught stealing at second base, tap the catcher, then the second baseman, and complete the play as “Caught Stealing 2-4.”
• Pickoffs:
  • Tap Both Players: When scoring a pickoff attempt, tap the pitcher first, then the fielder who receives the throw and applies the tag.
  • Example: For a pickoff at first base, tap the pitcher, then the first baseman, and complete the play as “Pickoff 1-3.”
• Relay Throws:
  • Tap All Involved Players: For plays involving relay throws (e.g., from the outfield to an infielder, then to another base), tap each player involved in the relay.
  • Example: For a relay from the center fielder to the shortstop who throws home, tap the center fielder (8), then the shortstop (6), and finally the catcher (2).

General Tips for Accurate Scoring

• Double-Check Lineups and Positions: Periodically double-check the defensive lineup and pitcher information to ensure accuracy throughout the game.
• Communication with Opposing Scorekeeper: Coordinate with the opposing team’s scorekeeper to verify lineups, positions, and any changes. This helps prevent discrepancies and ensures both teams have consistent records.

By following these GameChanger-specific tips, you can ensure accurate and up-to-date records of player positions and plays, leading to more precise stats and better analysis of the game.

Hits vs Errors

MLB Rule Reference

Rule 9.05: Base Hits

• Rule 9.05(a): A hit is scored when a batter reaches base safely on a fair ball that any fielder cannot put out the batter-runner with ordinary effort.
• Rule 9.05(b): A hit is scored when a fair ball is hit with such difficulty that a fielder cannot make the play with ordinary effort.

Rule 9.12: Errors

• Rule 9.12(a): An error is charged to a fielder whose misplay prolongs the life of the batter or runner, or enables a runner to advance.

Adjustments for 10u Players

1. Base Hit Determination:
   1. Criteria: Credit a hit if the ball is beyond the ordinary effort expected of a 10u player to field.
   1. Example: A hard-hit ground ball that gets past an infielder who had to dive should be credited as a hit.
   1. Judgment Call: When in doubt, err on the side of crediting a hit, considering the developing skills of 10u players.
2. Error Determination:
   1. Criteria: Charge an error if a fielder misplays a ball that should have been handled with ordinary effort.
   1. Example: A ground ball rolling directly to an infielder who fumbles it should be charged as an error.
   1. Fielding Errors: Errors can occur on fielding, throwing, or catching.
      1. Fielding: If a player fails to field a routine ground ball cleanly, it is an error.
      1. Throwing: If a throw is off-target and pulls the receiver off the base, the error is on the thrower.
      1. Catching: If the receiver has to dig the ball out of the dirt or make a significant reach and misses, the error is on the thrower.
3. Bad Bounce Exception:
   1. Criteria: Do not charge an error if a bad bounce is due to field conditions beyond the fielder’s control, such as a rock in the infield or the lip of the grass.
   1. Example: A ground ball takes a sudden, unexpected high hop due to hitting a rock, causing the fielder to miss it. This should be scored as a hit.
4. Extra Base Hits Involving Errors:
   1. Criteria: When a batter gets a hit and advances extra bases due to a fielding error, credit the initial hit appropriately and then charge an error for the additional bases.
      1. Example: A batter hits a ball to the outfield and reaches second base safely (double). The outfielder misplays the ball, allowing the batter to advance to third. Credit the batter with a double and charge an error for the advancement to third.
   1. Multiple Errors: If multiple errors contribute to the advancement, record each error.
      1. Example: A batter hits a ball and reaches first base. A bad throw allows the runner to reach second, and another misplay allows the runner to advance to third. Credit the batter with a single and charge two errors for the advancements.
5. Fielder Diving Attempt:
   1. Criteria: If a fielder attempts a diving play and misses, resulting in the ball getting by and allowing the batter to take extra bases, score the initial hit based on where the ball would likely have been fielded without the dive, and do not charge an error for the missed attempt. If the batter advances further due to a clear fielding misplay after the dive, charge an error.
      1. Example: The batter hits a line drive to the outfield. The outfielder dives and misses, and the ball rolls to the fence, allowing the batter to reach third. Credit the batter with a triple, as the extra bases were gained due to the dive attempt. If the fielder had a routine chance to stop the ball after the dive and failed, charge an error for additional advancement.

Summary

By applying these criteria and considerations, scorers can ensure fair and accurate recording of hits and errors, reflecting both the effort of the players and the conditions of the game.

Stolen Bases, Wild Pitches, Passed Balls, and Defensive Indifference

MLB Rule Reference

Rule 9.07(e): A stolen base is credited when the runner advances without the aid of a hit, a putout, a fielding error, a force-out, a fielder’s choice, a passed ball, a wild pitch, or a balk.

Rule 9.07(f): Defensive indifference is when the defense does not attempt to put out the runner, making the runner’s advance inconsequential to the game’s outcome.

Criteria for 10u

1. Stolen Bases:
   1. Criteria: Credit a stolen base if the runner advances due to their effort and intent as the ball crosses the plate, even if the catcher does not make a play.
      1. Example: A runner leaves immediately as the ball crosses the plate and advances to second base, regardless of whether the catcher catches the ball or not.
   1. Catcher Catches the Ball: If the catcher catches the ball and the runner successfully steals the base, it is clearly a stolen base.
      1. Example: The runner leaves the base after the ball crosses the plate, the catcher catches the ball cleanly, and the runner is safe at the next base.
   1. Wild Throw by Catcher: If the catcher makes a wild throw attempting to catch the stealing runner, the base is still credited as a stolen base. If the runner advances an additional base due to the wild throw, the advancement is scored as an error.
      1. Example: The runner steals second base, and the catcher’s throw goes into the outfield, allowing the runner to advance to third. Credit a stolen base for reaching second and an error on the throw for advancing to third.
   1. Good Throw, Missed Catch: If the catcher makes a good throw but the fielder misses the ball, and if the fielder had caught the ball it would have resulted in a caught stealing, it is ruled as an error on the fielder.
      1. Example: The catcher makes a good throw to second, but the second baseman misses the catch, allowing the runner to advance. Credit the runner with a stolen base and charge an error to the second baseman.
2. Wild Pitches:
   1. Definition: A wild pitch is a pitch that is so erratic that the catcher has no reasonable chance to control it, allowing runners to advance.
   1. Criteria: Record as a wild pitch if the pitch is uncatchable and the runner advances.
      1. Example: The ball bounces in the dirt or is thrown significantly outside the strike zone, allowing the runner to advance.
3. Passed Balls:
   1. Definition: A passed ball is a pitch that the catcher should have handled with ordinary effort but does not, allowing runners to advance.
   1. Criteria: Record as a passed ball if the catcher should have caught the pitch with ordinary effort but fails to do so.
      1. Example: The ball is within the catcher’s reach but gets by the catcher, allowing the runner to advance.
4. Defensive Indifference:
   1. Definition: Record as defensive indifference if the defense makes no effort to put out the runner because the game situation makes the runner’s advancement insignificant.
      1. Example: A runner on first base advances to second base without a play being made by the catcher or infielders, typically late in a game where the steal does not impact the outcome.
   1. First and Third Situations: In a first and third situation, if the runner on first advances to second and the catcher does not throw due to the risk of the runner on third advancing home, it should still be recorded as a stolen base. The defense is making a strategic choice rather than ignoring the runner.
      1. Example: With runners on first and third, the runner on first advances to second base, and the catcher holds the ball to prevent the runner on third from scoring. This is a stolen base because the defense is still trying to prevent advancement but is prioritizing the lead runner.
   1. Appropriate Use of Defensive Indifference: Use defensive indifference sparingly, typically only when the defensive team is up significantly in the last inning and is solely focused on the batter.
      1. Example: Late in the game with a large lead, the runner on first base advances to second without a throw from the catcher, and the defense is clearly indifferent to the runner’s advancement.

Special Considerations for 10u

• Immediate Departure: If the runner leaves immediately as the ball crosses the plate with clear intent to steal, it should be ruled a stolen base.
• Reactive Moves: If the runner advances due to the ball getting by the catcher, it should be recorded as a wild pitch or passed ball, depending on the quality of the pitch.
• Strategic Non-Throws: Recognize the difference between a strategic non-throw to prevent further advancement and genuine defensive indifference.
• Game Situation: Evaluate the game situation carefully to determine if the defense is truly indifferent or making a tactical decision.

Example Situations

1. Runner Steals Second:
   1. Scenario: Runner on first base leaves as the ball crosses the plate and advances to second.
   1. Ruling: Stolen base.
2. Ball Bounces in Dirt:
   1. Scenario: Pitch bounces in the dirt and gets past the catcher, allowing the runner to advance.
   1. Ruling: Wild pitch.
3. Catcher Misses Catchable Ball:
   1. Scenario: Pitch is within reach but the catcher misses it, allowing the runner to advance.
   1. Ruling: Passed ball.
4. Wild Throw by Catcher:
   1. Scenario: Runner steals second base, and the catcher’s throw goes into the outfield, allowing the runner to advance to third.
   1. Ruling: Credit a stolen base for reaching second and an error on the throw for advancing to third.
5. Good Throw, Missed Catch:
   1. Scenario: Catcher makes a good throw to second, but the second baseman misses the catch, allowing the runner to advance.
   1. Ruling: Credit a stolen base for reaching second and charge an error to the second baseman for the missed catch.
6. No Effort by Defense:
   1. Scenario: Late in the game with a large lead, the runner on first base advances to second without a throw from the catcher.
   1. Ruling: Defensive indifference.
7. First and Third, Strategic Hold:
   1. Scenario: With runners on first and third, the runner on first advances to second, and the catcher holds the ball to prevent the runner on third from scoring.
   1. Ruling: Stolen base.

By following these criteria, scorers can accurately distinguish between stolen bases, wild pitches, passed balls, and defensive indifference, ensuring consistent and fair scoring.

Sacrifice Flies and Sacrifice Bunts

MLB Rule Reference

Rule 9.08(d): A sacrifice bunt (SH) or sacrifice fly (SF) is credited when the batter’s action advances a runner while making an out.

Criteria for 10u

1. Sacrifice Fly (SF):
   1. Definition: A sacrifice fly is credited to the batter when a fly ball is caught and a runner scores after tagging up.
   1. Criteria: Credit the batter with a sacrifice fly if a fly ball is caught and the runner scores.
      1. Example: A batter hits a deep fly ball to the outfield, it is caught by the outfielder, and the runner on third base tags up and scores. Credit the batter with a sacrifice fly (SF).
2. Sacrifice Bunt (SH):
   1. Definition: A sacrifice bunt is credited to the batter when a bunt advances a runner while the batter is put out.
   1. Criteria: Credit the batter with a sacrifice bunt if the bunt successfully advances a runner.
      1. Example: A batter bunts the ball, and the runner on first base advances to second while the batter is thrown out at first base. Credit the batter with a sacrifice bunt (SH).

Special Considerations for 10u

• Intent to Advance Runner: Recognize the batter’s intent to advance the runner, even if the play does not result in an out for the batter.
• Score the Play Correctly: Ensure that the scoring reflects the batter’s contribution to advancing the runner, not just the result of the play.

Example Situations

1. Sacrifice Fly:
   1. Scenario: A batter hits a fly ball to center field. The outfielder catches it, and the runner on third base tags up and scores.
   1. Ruling: Credit the batter with a sacrifice fly (SF).
2. Sacrifice Bunt:
   1. Scenario: A batter bunts the ball toward the third baseman. The third baseman fields the ball and throws to first, putting out the batter while the runner on first advances to second.
   1. Ruling: Credit the batter with a sacrifice bunt (SH).
3. Advancing Multiple Runners:
   1. Scenario: A batter bunts the ball, advancing runners from first and second to second and third while the batter is thrown out at first.
   1. Ruling: Credit the batter with a sacrifice bunt (SH).

By following these criteria, scorers can accurately credit batters for their strategic plays that advance runners, ensuring fair and consistent scoring.

Fielder’s Choice vs. Hit

MLB Rule Reference

Rule 9.05(b): A hit is scored when a fair ball is hit with such difficulty that a fielder cannot make a play with ordinary effort.

Criteria for 10u

1. Fielder’s Choice:
   1. Definition: A fielder’s choice occurs when a fielder attempts to put out a different runner instead of the batter, allowing the batter to reach base safely.
   1. Criteria: Score a fielder’s choice if the fielder chooses to make a play on another runner rather than the batter.
      1. Example: A ground ball is hit to the shortstop, who throws to second base to get the lead runner instead of attempting to throw out the batter at first. The batter reaches first base safely. Score this as a fielder’s choice (FC).
2. Hit:
   1. Definition: A hit is credited when a batter reaches base due to the force or difficulty of the ball, beyond ordinary effort by the fielder.
   1. Criteria: Credit a hit if the ball is hit in a way that a 10u fielder cannot reasonably be expected to make the play.
      1. Example: A line drive that the outfielder dives for but misses, and the ball rolls to the fence. Credit the batter with a hit based on where they would have reasonably ended up without the missed dive (e.g., double or triple).

Special Considerations for 10u

• Skill Level: Consider the skill level of 10u players when determining if a play should be ruled a hit or a fielder’s choice.
• Benefit of the Doubt: When in doubt, give the benefit of the doubt to the batter and credit a hit.

Example Situations

1. Routine Ground Ball, Fielder’s Choice:
   1. Scenario: A ground ball is hit to the third baseman, who throws to second base to get the lead runner instead of throwing to first.
   1. Ruling: Score this as a fielder’s choice (FC).
2. Hard-Hit Ball, No Play Possible:
   1. Scenario: A sharply hit ground ball gets past the diving shortstop and rolls into the outfield.
   1. Ruling: Credit the batter with a hit (single, double, etc., depending on the outcome).
3. Line Drive to Outfield:
   1. Scenario: A batter hits a line drive to the outfield, and the outfielder makes an unsuccessful diving attempt to catch it, allowing the ball to roll to the fence.
   1. Ruling: Credit the batter with a hit (double or triple, depending on where the batter ends up).
4. Bunt with Play at Another Base:
   1. Scenario: A batter bunts the ball, and the catcher throws to third base to get the lead runner, allowing the batter to reach first safely.
   1. Ruling: Score this as a fielder’s choice (FC).

By following these criteria, scorers can accurately differentiate between hits and fielder’s choices, ensuring fair and consistent scoring based on the effort and decisions of the fielders.

Consistency and Communication

Consistency

1. Apply Rules Uniformly:
   1. Criteria: Ensure that all scorers apply the same rules uniformly throughout the game and across different games. Consistency in applying the rules helps maintain reliable statistics and fair comparisons between players and teams.
   1. Example: If one scorer rules a play as a fielder’s choice in one game, similar plays should be ruled the same way in subsequent games to ensure consistency.
2. Regular Review:
   1. Criteria: Periodically review the scoring guidelines with all scorers to ensure everyone is on the same page. This helps address any discrepancies or misunderstandings about the rules.
   1. Example: Conduct a brief review session before the season starts and check in periodically throughout the season to ensure consistent application of the rules.

Communication

1. Coordinate with Opposing Scorekeeper:
   1. Criteria: Ensure clear communication with the opposing team’s scorekeeper to verify lineups, positions, and any changes. This helps prevent discrepancies and ensures both teams have consistent records.
   1. Example: Before the game, exchange lineups and confirm any changes during the game, such as pitcher substitutions or defensive shifts.
2. Routine Score Checks:
   1. Criteria: Routinely check the score with the opposing team’s scorekeeper to ensure agreement. This can be done by checking the other team’s GameChanger feed or occasionally checking with their scorer.
   1. Example: After each inning, briefly check with the opposing scorekeeper to confirm that both teams have the same score and agree on key plays.
3. Runs Scoring on Third Out:
   1. MLB Rule Reference: Rule 5.08(a): “No run shall be scored in a half-inning until after two are out if the third out is a force out or if the third out is made by a preceding runner who is forced out.”
   1. Criteria: Consult with the umpire to determine if a run that crosses the plate during a play that results in the third out counts or not. Both teams should be made aware of the ruling.
      1. Force Play or Double Play: If the third out is a force play or part of a double play, the timing of the runner crossing the plate does not matter, and the run does not count.
      1. Non-Force Play: If the third out is not a force play, the run counts if the runner crosses the plate before the out is made.
   1. Example: If a runner crosses the plate during a play and the third out is a force out at another base, the run does not count. If a runner crosses the plate during a tag play and the tag is applied after the runner scores, the run counts. Confirm with the umpire and ensure both scorekeepers are in agreement.
4. Address Discrepancies Promptly:
   1. Criteria: If any discrepancies arise, address them promptly and respectfully with the opposing scorekeeper to resolve any issues.
   1. Example: If there is a disagreement about a scoring decision, discuss it with the opposing scorekeeper to reach a consensus and correct any errors.

Example Situations

1. End of Inning Check:
   1. Scenario: At the end of each inning, the scorer checks with the opposing scorekeeper to ensure that both teams have recorded the same score and key plays.
   1. Ruling: Confirm that the scores match and resolve any discrepancies before the next inning begins.
2. Mid-Game Lineup Change:
   1. Scenario: The team makes a mid-game lineup change, such as a new pitcher or a defensive substitution.
   1. Ruling: Communicate the change to the opposing scorekeeper and update the GameChanger app accordingly.
3. Discrepancy in Scoring:
   1. Scenario: There is a disagreement between the scorers about whether a play should be ruled as a hit or an error.
   1. Ruling: Discuss the play with the opposing scorekeeper, refer to the guidelines, and reach a consensus on how to score the play.

By following these guidelines, scorers can ensure consistent and accurate recording of plays, maintain reliable statistics, and foster good communication and cooperation between teams.

Conclusion

By adhering to the guidelines outlined in this guide, scorers can help ensure that the recording of plays is consistent, accurate, and fair. Using MLB baseball scoring as the foundation, with adjustments for the unique aspects of 10u baseball, helps maintain the integrity of the game and provides reliable statistics for players, coaches, and teams.

Remember, while statistics are an important part of the game, they should always be considered within the context of the actual play and the developmental level of the players. Consistent and accurate scoring not only contributes to strategic decision-making but also enhances the enjoyment and tradition of baseball for everyone involved.

Thank you for your commitment to providing accurate and reliable scoring for our 10u baseball games. Your efforts are invaluable in helping our players learn, grow, and enjoy the game.