Pitch Counter for High School Baseball: One Tool, Fifty Different State Rule Books

In 2017, the NFHS — the National Federation of State High School Associations, which writes the rule book that almost every American high-school baseball program plays under — replaced the old innings-pitched limit with a pitch-count framework. The change was driven by what every working coach already knew: a pitcher who throws ninety pitches in three innings is more taxed than one who throws sixty pitches in five, and counting innings was the wrong unit for protecting young arms.

What the NFHS did not do was write a single national pitch limit. Each state association was directed to develop its own pitching-restriction policy: a daily maximum, a rest-day table, and any cumulative-week limits the state wanted to add. Every state association then went off and wrote one. Most of them adopted similar shapes — daily cap, four or five rest tiers — but the actual numbers differ enough that a varsity pitcher at the top of his state's table in one place would be illegal in another.

This is the situation the high-school scorekeeper is working in. A pitch counter on the phone or the tablet at the dugout has to count pitches, attribute them to the right pitcher, and then leave the rule application to a human who knows which state's number applies. The tool that assumes the wrong rule is worse than no tool at all.

A varsity pitcher at the end of a complete-game performance is rare in modern high-school baseball. The pitch count cap is meant as a ceiling, not a target — and most coaches will pull a starter well before he hits it. The 105 in North Carolina, the 120 in Alabama, the 110 in Utah are the worst-case numbers, the rules to keep you from doing something obviously irresponsible.

The rule that does daily work is the rest-day tier. A starter who throws 80 pitches needs more days off than one who throws 60, and the schedule for the next week is built around that. A pitcher who threw 95 on Saturday is not pitching on Monday. The conversation between the head coach, the pitching coach, and the scorekeeper after every game is about which arms are available three, four, and five days from now — and that conversation runs on the daily totals from the pitch counter.

If the scorekeeper has accurate per-pitcher numbers in the book at the end of the game, the rest-day math is something the coaching staff handles. If the count was sloppy or attributed to the wrong arm, the staff is making decisions on bad data. That is the failure mode the tool exists to prevent.

Several states have added a cumulative weekly cap on top of the daily cap and the rest-day tier. Delaware's 205 over seven days is a representative example — a pitcher who throws 100 on Monday and 90 on Friday is at 190 going into the weekend, and the staff has to know that before they pencil him in for Saturday. Even if the rest table technically clears him, the cumulative limit can lock him out.

The cumulative trap is the part of the rule book that most often catches good coaches. It is not in front of you during the game; it lives in the previous six days of scorebooks. A scorekeeper who is only tracking today's count is missing the conversation entirely.

The practical fix is to keep last week's pitch counts visible to the staff at every game. Some teams write the rolling total on a whiteboard in the dugout, updated after each appearance. Some keep a spreadsheet. The pitch counter's game log saves to the device — at the end of each game, write the per-pitcher final counts in the scorebook against the calendar date, and the rolling seven-day window is two minutes of arithmetic on a Sunday afternoon.

Several state associations have different daily caps for different levels. Alabama's varsity 120 / JV 100 / middle school 85 is the cleanest example, but variations exist in other states too. The implication for a scorekeeper or athletic director who covers more than one level — which is most of them — is that the rule changes with the team you are working.

The pitch counter does not tag a game as varsity or JV; that distinction is something the scorekeeper carries in their head and confirms before each game. What the tool does is count pitches accurately so that whichever rule applies, the number you are checking against is correct. A JV game and a varsity game look identical on the screen — the difference is which line of the state rule book you are reading after the final out.

This is also where the at-bat-completion clauses become relevant. Some states (Utah is one) allow a pitcher to finish the current batter even after hitting the daily limit. Others enforce a strict cap. If your state has the completion clause, your scorebook needs to record when the pitcher crossed the limit and whether he finished the at-bat — useful evidence in any post-game protest.

Before first pitch, both lineups go into the Pitch Counter's team setup. High-school programs usually run with set roles, so the pitching staff for the game is two or three named arms — the starter and one or two probable relievers. Enter all of them at the start, even if they don't appear in the game. It is faster to ignore the unused names than to interrupt the seventh inning to add a reliever you didn't expect.

The DH toggle matters at the high-school level. NFHS rules allow a designated hitter for any defensive player, not just the pitcher, in most state associations — the DH bats for one defensive player, who does not bat for himself. Most varsity rosters use it for the pitcher, but you should confirm before tapping the DH toggle on. Once it is on, the lineup runs nine batters; once it is off, it runs eight position players plus the pitcher, with the pitcher hitting in his slot.

A mid-game pitching change runs the same as the lineup auto-advance. The starter's count locks at his last pitch, the new pitcher takes over from whatever BSO state the at-bat is in, and the next pitch goes to him. If the swap is between innings (which most are at the high-school level), the count for the new pitcher starts at zero on the screen as expected.

The pitch count rule that applies during the high-school season does not necessarily apply during summer travel ball. Most travel organizations and showcase events publish their own pitch-count policies, and they vary as much as the state association rules do. A pitcher who threw 70 on Friday in a high-school playoff game might pitch in a Saturday-morning showcase under a completely different rule, and the coach's job is to apply both.

The simplest way to handle this: every appearance gets logged with the date, the pitcher, and the final count, regardless of which season or organization it was for. The cumulative arm load on a teenager does not care which league wrote the rule book. By the end of June, a varsity arm who has been pitching travel ball every weekend has a much heavier total than the school season alone would suggest, and the only way to see it is to keep the log going past the end of the school season.

The pitch counter does not formally separate seasons or organizations — every game is just a game, and the per-pitcher counts are per-game. But the device retains a game log that you can pull up later, and a season-long view of one pitcher's appearances is the most honest version of his actual workload.

High-school junior and senior pitchers being recruited at the Division I or II level should expect a recruiting coordinator to ask for game-by-game pitch counts. A college pitching coach evaluating a prospect wants to know how the kid was used — and how he was protected — over the course of his junior and senior seasons. That conversation goes better when the answer is a clean per-game log than when it is a coach's recollection.

The scorebook is the artifact. A high-school staff that has been running an accurate pitch counter all season can hand over a complete record at the end of the year. A high-school staff that has been guessing in good faith hands over a sheet of approximations and asks the recruiter to trust the numbers. Both work; the first one builds more trust with the program.

This is not the headline reason to keep accurate pitch counts at the high-school level — the headline reason is the rule book and the kid's arm — but it is one of the under-the-radar payoffs. A junior whose sophomore-season log is on the team scoresheet has answers to questions a recruiter has not asked yet.

Three things to do before opening day. First, pull your state association's current pitch-count policy and verify the daily cap, the rest-day tiers, and any cumulative weekly limit. Print it; tape it to the inside cover of the scorebook. The numbers I cited in the callout above are accurate as of when this article was written, but state associations update their rules — check the current version against Baseball America's by-state summary and your state association's website.

Second, identify who is doing the actual counting. The roles section above is a starting point — most programs have an official scorekeeper plus a bench tracker, with the pitch counter running on the bench-tracker's phone. If you only have one person, make sure that person is not also the head coach.

Third, set up the team list and the DH preference in the tool before the first plate meeting. Two minutes during pre-game saves you a scramble in the middle of the second inning when a reliever comes in earlier than planned. Then keep the log going past the end of the school season — travel ball, showcases, summer leagues all add to the same arm. The roll-up is what protects the player.

For the broader scoring conversation across other high-school sports, the scorekeeper hub has companion tools for basketball, football, soccer, and a half-dozen others. Same design philosophy: count the state, leave the rule application to a human who knows which book is open.