The Baseball Scorekeeper Grew Up: Lineup Cards, the Diamond, Pitch-by-Pitch, and a Watch Link for the Stands

I have spent eleven years running an athletic department and most weekends since officiating, and the question I get from product teams more than any other is some version of "why won't coaches use the app for the real game?" The answer was never that coaches dislike phones. It was that a baseball book is not a scoreboard. A scoreboard holds runs, hits, errors, and a count. A book holds the batting order, who is playing where, which runners are on which bases, and what each pitcher has thrown — and until recently the baseball scorekeeper held the first list and not the second.

That is fixed now. Over the last few weeks the tool picked up a full lineup card with positions and a DH, a live diamond that draws runners and their advances, pitch-by-pitch logging with a strike-zone heat map, and a public watch link that a parent in the stands can open without an account. Those are not cosmetic. They are the difference between a glorified clicker and something you can actually keep a book on. This is a walk through what each piece does and how I tell coaches to use it.

Open the baseball scorekeeper and the first thing worth doing is the lineup. You set a batting order, and next to each hitter there is now a position column — P, C, 1B, 2B, 3B, SS, LF, CF, RF — so the card reads the way a paper book reads, with each player in their slot and their spot on the field. A DH toggle adds the designated-hitter row for the leagues that use it and leaves it off for the ones that don't.

This matters for a reason that has nothing to do with looking official. When the order is in the tool, the batter auto-advances after every plate appearance, so you are never the scorekeeper squinting at a clipboard trying to remember whether it's the seven-hole or the eight-hole up next. You tap the result, the order turns over, and the next name is already on screen. Substitutions and pinch-hitters go through a bench picker: you choose the slot the new player is taking, the swap lands on the game log, and the order keeps walking from there. That last part — the swap landing on the log — is what makes the book defensible later, when somebody asks who hit for whom in the sixth.

The diamond view is the piece I was waiting on the longest. It shows the fielders laid out with names and numbers at each position, and it shows base runners as you put them on. Tap an empty base and a small modal asks how the runner got there — single, walk, hit-by-pitch, reached on error, or a generic placement. Tap an occupied base and it asks what happened — stole the next base, caught stealing, picked off, or a correction. Every one of those choices writes a line to the game timeline instead of silently moving a dot, so the play log actually reads back like a game later.

When a play moves runners, the diamond animates the advance — curved arrows trace each runner's path, amber for a normal advance and a heavier green for a run that scored. A bases-loaded single shows three arcs at once. A home run traces the full lap. It sounds like decoration, and on a quiet groundout it is, but on a busy play with three runners moving it is the fastest way I know to confirm the tool understood what you tapped before you commit to it. And the guard rails are sane: try to steal a runner into an occupied base and it tells you to advance the lead runner first instead of quietly overwriting him.

Underneath the at-bat, every pitch is recorded as a ball, a strike, or a foul, and the count behaves the way the rules read — four balls walks, three strikes is a strikeout, a foul with two strikes stays at two. The play-ending pitch counts too, so the pitcher's total matches what actually came off the mound rather than undercounting the pitch that got hit.

What is new is the location layer. After a pitch you can tap where it crossed on a 21-cell strike-zone grid — in the zone, off the corners, or well outside — and you can scale the zone to the batter at the plate so a tall hitter gets a taller box. Add a velocity if you have a radar reading or a stadium-board number, by numpad or slider. Turn on Track swings and a Swing button appears next to Ball / Strike / Foul for one-tap swing-and-miss logging. All of that feeds a pitcher heat map: where the pitches went, which corners hitters chased, and the average and max velocity across the outing. For a parent tracking a young arm, or a coach building a book on a pitcher, that is the genuinely new capability — and it pairs naturally with the dedicated pitch counter when all you need is the count and the rest-day math.

The spectator view is the feature that earns its keep at a real game. You mint a watch link and share it, and a parent in the stands — or a grandparent two time zones away — opens it in a browser with no signup and no app install. They see a broadcast-style view: the score and the BSO, the current pitcher with pitch counts, the batter with a season average and recent at-bat outcomes, the diamond with the defensive alignment, and an Up Next strip. Each pitch flashes its result, each at-bat closes with an outcome banner — single, K, ground out, sac fly, with the RBI count when runs score.

The practical effect is that the scorekeeper stops being interrupted. Nobody is leaning over the bench asking what the count is, because the count is on every phone in the bleachers. The same link carries the lineup and the diamond, not just the score, so a parent who knows the game can follow the actual game and not just the number. This is a Pro path because it runs through the server, but the watch link itself costs the viewer nothing and asks them for nothing.

Not every game needs the whole book. If your only job is keeping a pitcher under the league's daily limit and tracking rest days, the standalone pitch counter is the lighter tool — per-pitcher counts, a clean game log, and no lineup to set up. It is the right call for a parent volunteer whose entire assignment is "don't let our kid throw seventy-five."

If you are keeping a real book — order, positions, runners, the works — the baseball scorekeeper is the tool, and the pitch logging inside it does the counting too. The rule-heavy details of pitch limits don't change either way: the same daily caps and rest tiers apply, and the guides on Little League rest-day math, high-school state rules, and the NCAA's 110-pitch cap walk through the numbers level by level. Use the counter for the count, the scorekeeper for the book, and read the rules once before the season so the threshold conversation is already settled when it comes up.

Load the baseball scorekeeper before the leadoff hitter steps in, not in the bottom of the first. Enter the order with positions while you have a quiet minute — real names, not "Batter 1," because a week later the names are what make the log worth keeping. Decide whether you're scoring for yourself or sharing the game; if parents are going to follow along, mint the watch link early and put it in the team group chat before the anthem.

Then score the game the way you always have — tap the result, let the order turn over, put runners on the diamond, log the pitches if you're tracking an arm. The tool holds the state; you decide what to do with it. That has always been the deal with a good scorebook, paper or digital. The difference now is that the digital one finally holds everything the paper one did, and hands a copy to everyone in the stands while it's at it.