A Ground Up Baseball site · GloveCode · ArmRules · BatCode · BatRules · Deals · News · Arm Care Training · Tournaments

GameChanger Scorekeeping for Parents

How to score hits, errors, wild pitches and passed balls at youth games, using the ordinary effort standard, with the rules linked.

Start with how hard the ball was hitThe play that taught us the ruleAn overthrow past first base is an error, not a hitWild pitch or passed ball? One question sorts itWhat changes by age, and what doesn'tEnter the play before the next pitchScore it straight, then keep it smallPractice it before it counts

A Ground Up parent guide. Rule quotes link to the official rulebooks and to GameChanger’s own help pages.

The short version
  • Every hit or error call comes down to ordinary effort: could a typical player at that age and position have made the play? Start with how hard the ball was hit (Official Baseball Rules, Definitions of Terms).
  • A ground ball thrown past first base is an error on the throw, not a hit, unless the batter would have beaten a good throw anyway (Rule 9.12).
  • Wild pitch means the pitch itself was too tough to handle. Passed ball means the catcher should have had it. If it bounced in the dirt before it got to the catcher and got past him, it's a wild pitch (Rule 9.13).
  • Enter the play before the next pitch. GameChanger builds its automatic video clips from what the scorekeeper logs, and a late entry can hand you a clip of the next batter (GameChanger).

Somebody on your team is going to keep score in GameChanger this season, and there is a decent chance it's you. You will be standing behind the fence with a phone in one hand, a scorebook app in the other, and about four seconds to decide whether the ball that just skipped off a glove was a hit or an error.

Most parents learn this by getting it wrong in front of everybody. That's fine. It's a volunteer job, and the app will let you fix almost anything afterward. But there are a few calls that come up in nearly every youth game, and knowing them ahead of time makes the whole thing much less stressful.

Here is how we handle hits, errors, wild pitches and passed balls, using the actual scoring rules and the way GameChanger wants the plays entered.

Start with how hard the ball was hit

The rulebook gives you one standard for every judgment call, and it is not "did the kid try hard." It is this:

ORDINARY EFFORT is the effort that a fielder of average skill at a position in that league or classification of leagues should exhibit on a play, with due consideration given to the condition of the field and weather conditions (Official Baseball Rules, Definitions of Terms).

That is the whole test, and it is deliberately about an average player rather than the particular kid in front of you. So when a ball is in play, work through it in this order:

  • How hard was it hit, and where? A slow roller or a soft liner gives the fielder time to get there. A ball hit on the screws does not.
  • Could a typical player at this age, at that position, have made the play with ordinary effort? A 9-year-old shortstop and a 13-year-old shortstop are not the same fielder, and the rule is written to account for that.
  • If yes and the play wasn't made, it's an error. If no, it's a hit.

Both halves of that have rule language behind them. A hit is credited when the batter reaches first on a fair ball "hit with such force, or so slowly, that any fielder attempting to make a play with the ball has no opportunity to do so" (Rule 9.05(a)(2)). On the other side, the comment to Rule 9.12(a)(1) says the scorer "shall charge an infielder with an error when a ground ball passes to either side of such infielder if, in the Official Scorer's judgment, a fielder at that position making ordinary effort would have fielded such ground ball and retired a runner." The same comment adds that the fielder does not have to touch the ball to be charged. A ball that goes under a glove is still an error if the play was there to be made.

There is one more piece you should know, because it comes up constantly on close plays. The comment to Rule 9.05(a) says the scorer "shall always give the batter the benefit of the doubt," and that "a safe course for the Official Scorer to follow is to score a hit when exceptionally good fielding of a ball fails to result in a putout."

That sounds like it contradicts everything above. It doesn't. It means that when you genuinely cannot tell, the hitter gets the hit. It does not mean a routine ball that was booted becomes a hit because the fielder tried hard. "Close" is still measured against ordinary effort, not against effort.

The test in one line: could a typical player at this age have made that play without doing anything special? If yes, and it wasn't made, score the error.

The play that taught us the rule

Our own son was playing shortstop at 13U. A ball was hit up the middle and he went and got it, ranging all the way behind second base, far past where a shortstop has any business being on that play. He got there, at the very end of his range, and the ball hit his glove, just out of reach.

He was the only player on the field who came close to it. Nobody else had a chance. It was, honestly, a spectacular piece of fielding that just missed.

We scored it an error, and it took us a while to understand why.

The reason is in the ordinary effort definition itself. The comment to that definition says the standard "is an objective standard in regard to any particular fielder. In other words, even if a fielder makes his best effort, if that effort falls short of what an average fielder at that position in that league would have made in a situation, the Official Scorer should charge that fielder with an error" (Definitions of Terms).

That is the part parents get wrong, and it is worth stopping on. The question is not whether this particular player could make the play. It is whether an average player at that level could have made it with ordinary effort. No other shortstop in that league gets to that ball, and that does not matter, because the standard is not built around the best player on the field. It is built around the average one.

To a parent watching from the fence, it looked like a great play that barely failed, and it did not feel like an error because nobody else was close. The scorer saw a ball that got to the glove, and a catch at that level that gets made. The distance he covered to get there is the impressive part, and the rule does not credit it in the stat line, because the rule is not scoring the effort. Both readings are honest, and the rulebook breaks the tie with the average player at that position rather than with what this particular player did to reach the ball.

There is a real debate inside youth baseball about whether that is the right way to score a 13-year-old's great effort, and we are not going to pretend the rulebook settles anybody's feelings about it. What it does settle is the entry in the app. If the ball got there and the catch was routine, it is an error.

The practical version for a scorekeeper: when a kid lays out and the ball gets to the glove, don't upgrade it to a hit because the effort was spectacular. If the ball never reached the glove at all, that is a different question, and it is usually a hit unless an average player at that age would have gotten there.

One caveat worth knowing, since we cited it above: the rulebook also tells scorers to give the hitter the benefit of the doubt when they genuinely cannot tell. That guidance is for plays where the answer really is unclear. It is not a rule that a great effort turns a muff into a hit.

An overthrow past first base is an error, not a hit

This one comes up constantly at the younger levels, and it is the call we most often see entered wrong.

A ground ball is hit to an infielder. The throw to first is high, or wide, or in the dirt, and the batter ends up safe. Parents see the runner on first, see that the throw was bad, and click something like "single" because it feels like the kid hit his way on.

The rule is clear the other way. The comment to Rule 9.12(a)(1) says: "If a throw is low, wide or high, or strikes the ground, and a runner reaches base who otherwise would have been put out by such throw, the Official Scorer shall charge the player making the throw with an error." Rule 9.12(a)(5) charges the error for a wild throw that "permits a runner to reach a base safely, when in the scorer's judgment a good throw would have put out the runner" (both from Rule 9.12).

Notice what the rule is actually asking. It is not asking whether the throw was ugly. It is asking whether the batter would have been out if the throw had been good. Those are different questions, and the second one is the only one that counts.

So the way to enter it:

  • If a good throw beats the runner, it's an error on the thrower, and the batter is out of the hit column. He reached because the throw missed, not because he beat it. GameChanger has an Error button for exactly this: tap the pitch, tap Ball in Play, pick the type of ball in play, tap Error, then tap the fielder who made the throw and Done (GameChanger).
  • If the batter would have beaten a good throw anyway, it's a hit. The overthrow did not cost the defense an out, because the out was never there. Rule 9.12(d)(2) says the scorer shall not charge an error on a wild throw "if in the scorer's judgment the runner would not have been put out with ordinary effort by a good throw," unless the wild throw let a runner take a base he would not otherwise have reached (Rule 9.12(d)).
  • If a good throw would have had him and the throw was fine, but the first baseman dropped it, that's an error on the first baseman. Same standard, different fielder. The rule about ordinary effort applies to the catch as much as to the throw.

On a bang-bang play where you truly cannot tell whether a good throw gets him, take the hitter's hit. That is the benefit of the doubt the rulebook tells you to give.

One housekeeping note that saves arguments later: only one error is charged on a wild throw, no matter how many bases the runners take (Rule 9.12(b)).

Wild pitch or passed ball? One question sorts it

These two look identical from the bleachers. A pitch gets past the catcher, a runner moves up. The difference is who gets charged, and it comes down to the same ordinary effort idea.

A wild pitch is the pitcher's. Rule 9.13(a) charges it "when a legally delivered ball is so high, so wide or so low that the catcher does not stop and control the ball by ordinary effort, thereby permitting a runner or runners to advance." The definitions section puts it more simply: a wild pitch is "one so high, so low, or so wide of the plate that it cannot be handled with ordinary effort by the catcher" (Rule 9.13 and Definitions).

A passed ball is the catcher's. Rule 9.13(b) charges it "when the catcher fails to hold or to control a legally pitched ball that should have been held or controlled with ordinary effort, thereby permitting a runner or runners to advance."

Here is the test we use, and it takes about a second:

Did the pitch make it hard, or did the catcher make it hard? If a decent catcher at this age catches that pitch without moving his feet, it's a passed ball. If the pitch itself made a routine catch into a hard one, it's a wild pitch.

The rulebook also gives you one automatic answer that settles most of the arguments. Rule 9.13(a) says it is a wild pitch when "a legally delivered ball touches the ground or home plate before reaching the catcher and is not handled by the catcher." So if it bounced in the dirt before it got to him and got past him, it's a wild pitch, even if he should have blocked it. That single line gets you out of most of these calls.

A few more things that matter in the app:

  • Nobody advanced, nobody gets charged. The comment to Rule 9.13 says the scorer shall not charge a wild pitch or passed ball "if the defensive team makes an out before any runners advance." If the catcher blocks it, picks it up, and throws out the runner at second, you do not also log a wild pitch.
  • On a dropped third strike, the app makes you choose. GameChanger puts "Safe on First (WP)" and "Safe on First (PB)" on the dropped third strike menu, and its help page notes that you cannot also apply an error if the runner only reaches first (GameChanger). Pick the one that matches the pitch.
  • The runner options only show up after a pitch. In GameChanger, "On Wild Pitch" and "On Passed Ball" appear after a pitch has been thrown to the current batter, and you get them by dragging the runner to the base and dropping him in the safe box (GameChanger).

What changes by age, and what doesn't

The standard is the same at every age: ordinary effort, measured against a typical player at that level. What changes is what ordinary effort actually looks like, and how much ground a kid has to cover to show it.

The field dimensions are the clearest reason. In Little League, the infield is a 60-foot square for the Major division and below, 70 feet for the Intermediate (50-70) division, and 90 feet for Junior and Senior (Little League Rule 1.04). Travel ball runs its own ladder: USSSA lists 60-foot bases for 7U and 8U, 65 feet for 9U and 10U, 70 feet for 11U and 12U, and 80 or 90 feet at 13U and up (USSSA National By-Laws, Chart 7.01.A-1). So depending on where you play, your 11U or 12U team may be on 70-foot bases while a Little League Majors team down the road is still on 60.

Those numbers tell you most of what you need:

  • Younger kids, roughly 7U through 10U. The bases are short, so a routine ground ball is genuinely a routine play. Fielding it and throwing accurately across 60 or 65 feet is still a skill these kids are building, which means the play is there to be made and the throw often isn't. Score the error when the play was there. Do not turn a routine ground ball into a hit because the throw sailed.
  • 11U and 12U. On 70-foot bases the game speeds up, and the extra ten feet is real. A ball that a shortstop would have gotten to on a 60-foot diamond may now be through the hole, and that is a hit rather than a lapse. This is also the age where the throws get harder, so overthrows stay common and the first-base drop becomes a bigger share of the errors you record.
  • 13U and up. At 80 or 90 feet, everything takes longer. Throws are longer, so overthrows are longer, and a ball hit up the middle that used to be an out is now a hit. Ground balls that are fielded cleanly but arrive late at first are hits, not errors on the infielder; the comment to Rule 9.12(a)(1) says the scorer "shall not charge a fielder with an error if such fielder fields a ground ball cleanly but does not throw to first base in time to retire the batter," and that slow handling "that does not involve mechanical misplay shall not be construed as an error." The hit comes from Rule 9.05(a)(2), for a ball hit "so slowly" that the fielder had no opportunity.

We are not going to hand you error-rate or batting-average benchmarks by age level, because we could not find any published by a rules body that would hold up, and making one up would be worse than saying nothing. If your league keeps stats, ask your board how it wants judgments handled.

One thing that does not change with age: the scorekeeper has the authority to make the call. Little League's definition of Official Scorer says the scorer "shall have sole authority to make all decisions involving judgment, such as whether the batter's advance to first is the result of a hit or an error," and that the scorer is a designated volunteer of the league (Little League 2025 rulebook, Definitions). In the pros, Rule 9.01(a) gives the official scorer until "no later than the start of the next plate appearance" to make a preliminary judgment (Rule 9.01). In GameChanger, you have less time than that, which is the next section.

Enter the play before the next pitch

This is the part that has nothing to do with the rulebook and everything to do with the app, and it is where we cost ourselves the most.

GameChanger builds automatic video clips from the plays you log. Its help documentation says clips are generated for games that are both streamed and scored, from hits (single, double, triple, home run) and most out types, and that "once a play is logged we generate a clip off of that data, so scoring in real time is essential to ensure accurate clip creation" (GameChanger).

The FAQ is blunter about what late scoring does: "If the scorekeeper scores the play more than 20 seconds after it happens, the clip may be catching some of the next play as opposed to your player" (GameChanger).

We learned that the hard way. There was a whole stretch of games where we were scoring a beat or two behind, entering the last play while the next pitch was already on its way, and we ended up with clips of our son's hit that showed the next batter's at-bat instead. Some we fixed later by hand. Others we never got around to, and by then the clip had sat there for a month pointing at the wrong ten seconds. It is a small thing in the scheme of a season, and it still stings.

The habit that fixed it, and the one we would give any new scorekeeper:

  • Enter the play before the next pitch. Not after the inning, not on the walk back to the car. Watch the play, tap it in, look up. If the pitcher is already in his windup, you're late.
  • Set the lineup before the first pitch. GameChanger lets you enter your starting lineup ahead of time (GameChanger) and add lineup placeholders to fill in the opponent fast (GameChanger), which removes the fumbling that puts you behind in inning one.
  • Assign the play to a player, never "Assign Later." The FAQ is explicit that a play left on "Assign Later" produces no clip at all, and that reassigning a play to a different player afterward will not generate a clip for the new player.
  • Use the faster input path. On iOS, GameChanger moved balls, strikes, swing and miss, foul balls, undo and redo out of the pitch menu and onto an always-visible scoring bar, so you can stay in the field view instead of hopping between menus (GameChanger). Fewer taps is the whole game here.

If you do get one wrong, it isn't permanent. You can edit a past play from the Plays tab while the game is being scored, and the outcomes you can change include error, fielder's choice and single, plus wild pitch, passed ball and stolen base (GameChanger). Just do it before the game is finalized, because the app only syncs while the game is live.

And if a clip comes out wrong anyway, you can trim or extend it. Clips can be edited to run from 5 to 90 seconds, by staff, a confirmed player, or a confirmed parent or guardian (GameChanger). That is the safety net. Try not to need it.

Score it straight, then keep it small

Here is the part we feel most strongly about.

If it's an error, score it an error. Not a hit, not a fielder's choice, not a generous single. Inflating a kid's stats to protect his feelings does three bad things at once. It makes the team's numbers meaningless. It teaches the kid that the record bends when things get uncomfortable. And it is unfair to the pitcher, who gets charged with a hit he did not give up.

The rulebook actually backs the scorekeeper here. Judgment calls belong to the scorer, and the whole point of the ordinary effort standard is that it applies the same way to everybody.

But do the other half of the job too, because this is youth baseball and not a scouting service:

  • A stat line is a record of a game, not a report card on a kid. Nobody's future is decided by a 12U error. Kids develop at wildly different rates, and the shortstop who boots one in April is often the one making that play in June.
  • Talk about the play, not the player. "That one got under your glove, you'll get the next one" is a completely different sentence than anything with the word "error" aimed at a nine-year-old.
  • Say the quiet part out loud to your own kid. We tell ours that the error in the book is just the book's way of saying the play was there to be made, and that the book does not know he was the only one on the field who could even get near it. Both things are true.
  • Remember that every adult on that field is a volunteer. The coach is somebody's dad who took a Tuesday off work. The scorekeeper is somebody's mom squinting at a phone in the sun. The umpire is a kid in high school or a retired guy doing it for gas money. Nobody is getting paid to be right, and everybody is doing their best.

That is the balance. Score the game honestly, then keep the number in its place. We wrote more about the parent side of this, including the ride home and when to talk to a coach, in our travel ball parents guide.

Practice it before it counts

One more thing that makes all of this easier: GameChanger has a practice mode, and it is easy to skip.

You can open it from the login screen with Explore Scorekeeping, or from your team page under Team Settings and Practice Scoring a Game. Nothing you enter is recorded (GameChanger).

Spend fifteen minutes in it before your first real game. Score a ground ball with an overthrow. Score a pitch in the dirt. Score a dropped third strike. Score a foul pop that gets dropped. By the time you are doing it for real, with a runner going and a parent asking you what the count is, your thumbs will already know where the buttons are.

That is the whole job. Ordinary effort, one honest answer, and the play entered before the next pitch.

Sources

Links were checked on October 30, 2026. Read in full: the 2026 Official Baseball Rules, including the scoring rules quoted above; the 2025 Little League rulebook, including its definitions and Rule 1.04; the USSSA by-laws chart; the MLB glossary entries; and GameChanger's help pages on automatic video clips, video clip editing, scoring errors, advancing baserunners, editing past plays, dropped third strikes, basic scorekeeping, practice scorekeeping and scorekeeping and stats. Little League's current rulebook is distributed through its Rulebook app and a printed 2026 edition; the free PDF we cite is the 2025 edition. Little League's book runs through Rule 9.00 (The Umpire) and carries the definitions we quote but no full official-scoring section, so the scoring rules quoted here come from the Official Baseball Rules. If your league publishes its own scoring guidance, that is the version that governs your games.

The story about the 13U shortstop is our own, from our own family, and we left out names, teams and locations on purpose. It is the play that taught us the ordinary effort rule.

Judgment calls belong to the scorekeeper or official scorer your league designates. Confirm with your league, and treat youth stats as a record of the game, not a verdict on a kid.

More for parents: the Travel Ball Parents’ Guide covers the sideline, the ride home and talking to the coach.