Upload your scorebook

If you kept the score on paper at the field and didn’t enter it live in the app, scorebook upload gets your stats into the system with one streamlined flow: photograph the book, review the game overview, check the inning overview, then review and approve the plays.

Who can do this

Every player on the team can view recorded plays. Open the game page and choose View scorebook to see the digital card, including games scored without a paper upload. Subs added to the game can view it too. Book opens by default; use Rows to switch to the play list. Select a play to see its details and, when available, the approved scorebook photo.

Uploading, reviewing draft readings and correcting the saved stats require a coach, captain or scorekeeper (observer) role.

Review notices appear above the scorecard. For saved games, an earlier inning with fewer than three outs is flagged unless it reached a confirmed run limit. The final recorded inning can be shorter.

If a runner is marked stranded but a later batter reaches third or hits a home run, the notice asks whether the runner Scored or was Out on bases. Answer right in the notice, choose the batter responsible (or unknown), then tap Save run or Save out. Check the paper readings first. Nothing is changed automatically; saving updates the recorded stats without opening the play editor.

Coaches and captains can upload a scorebook. It only unlocks for games that don’t yet have any at-bat data — if you’ve already entered some plays, clear them or skip this feature.

Steps

1. Gather your photos

Open the game and scroll to the Scorebook photo card, then tap Upload.

Photograph the page where your team batted — one page per upload.
The app corrects orientation and attempts to straighten the page. Make sure the whole page is in frame.
Include the whole scorebook layout: column headers (innings), row headers (batter names), and all the marks.

2. Upload

Choose an image from your camera roll or take a new photo.

Check the photo preview, then tap Upload and analyze.

The app detects innings that continue across columns automatically. It reads out numbers across the whole inning and checks that the batting order continues. For example, a column whose first out is #2 may continue the previous column. Missing outs alone do not prove a continuation: a run limit or short final inning can end before three outs.

A progress bar near the top follows Game overview → Inning overview → Play overview. When a phase has uncertain details, it asks focused questions and allows about five minutes for answers. You can correct the fields or tap Continue sooner. If your answers agree with the AI and no questions remain, the app continues immediately. Otherwise, a correction restarts the five-minute window. Your answers carry forward into the next read.

After you tap Upload and analyze, the app shows its progress step by step:

Straightening the photos — sideways or upside-down pages are fixed here.
Preparing the sheet — a clear original stays intact; other photos may be cropped and straightened.
Finding the printed cells — the app checks the page’s ruled rows and columns.
Reading the players — the handwritten name column.
Reading the game totals — innings batted and your team’s final score, using the identified batting rows.
Checking unused cells — larger column views help distinguish cancellation scribbles from real plays.
Finding the innings — which part of the sheet holds which inning.

Straightening can also turn a sideways page upright. If the first attempt cannot locate usable corners, the app retries before falling back to your original photo. A later retry keeps an already-straightened photo in the same orientation. If the preview still looks sideways, check it before starting the play reads; discard and upload an upright photo if necessary.

When the printed grid is clear, the app uses its measured cells to keep play snippets aligned with the paper. If it cannot measure the grid confidently, it continues with the image reader. Check the names and inning boundaries either way; finding the printed cells does not establish which cells contain plays. The app checks the original photo before cropping it, so visible row numbers and headers can stay in view. Short totals rows below the batter list are excluded only when the printed borders clearly separate them. If the printed grid is difficult to read, the app tries two more ways to read it automatically. If that still fails, or the inning map looks uncertain, it asks for another read of the innings. An uncertain map opens the five-minute review window before reading plays. These extra checks can make this step take longer.

Players are identified before the innings are read. The detected names appear in Game overview as soon as they are available, and you can correct them while the app continues reading the game totals.

3. Review the game and innings

Game overview comes first. Check the player count, batting-order names, number of innings your team batted and your team’s final score. The AI fills in its estimates as it reads. You can enter any of these details during analysis; your entries stay in place when the AI finishes. If they agree and the player matches are clear, the app moves straight to Inning overview. The opponent’s score is not needed.

The app reads written game totals and uses an existing reported team score when available. It asks when those sources disagree. An unknown value stays blank. These review fields guide the scorebook read; they do not change the game’s reported result.

After this checkpoint, Inning overview reads the sheet using those game facts and player rows. Each inning has its number of plays, first and last batter, and runs. You can edit those values directly. The saved batting order and scoring conventions remain available under All player matches, inning count and scoring conventions.

A score mismatch stops the next phase. If inning runs add up to 9 but your team’s final score is 10, the app stays at Inning overview. Correct an inning’s runs or expand Game overview to correct the final score. An inning-count mismatch also needs correction. Neither Continue nor the five-minute deadline can bypass these contradictions. Unreadable values remain unknown and can continue after the review window; they are never silently treated as zero.

The app also checks the inning map against itself before you confirm, and warns you in amber about the two things that can’t be right:

A player who bats in no inning. They’d finish the game with no at-bats — this is what once cost a sheet seven players without anything on screen saying so.
An inning that doesn’t pick up where the last one left off. Your order runs straight through and comes back around to the top, so if inning 2 ended on Jeff, inning 3 starts with whoever bats after Jeff. Anything else means a boundary is off at one end.

Both are warnings, not blocks — a short last inning or a late arrival can look the same. They’re telling you where to look.

How your book marks results. Every scorebook prints the options — 1B, 2B, 3B, HR, BB — somewhere in each box, and you circle one. Where they sit differs by book: some print them across the top of the box, some down the right side. The app reads that once per sheet and then works out a circled result from where the circle is rather than trying to read the tiny printed label under your pencil — which is usually the hardest thing on the page to read.

You’ll see what it found (“each cell lists the results along its top”) with the order it read. If that’s wrong, fix it here: it’s used for every play in the book, so an order that’s off would affect the whole sheet.

Fixing a boundary. Tap ✎ on an inning in the grid for its First and Last batter pickers. If inning 3 should start with Jeff and the app thinks it starts with Corinne, change it here — this is the most valuable fix on the page, because a boundary that’s off at either end makes every stat read from that inning wrong.

The editor highlights the selected area on the full photo, so you can compare it with the column position and batter rows. If it points at a neighboring column, use One column left or One column right. A wrapped inning has a separate highlight and controls for each part. Check the highlight after moving it; adjusting the first or last batter changes its vertical range.

Innings spanning columns show a continuation label. The grid’s inning editor also shows the full Batting sequence, including repeated appearances. Check every highlighted area in order: an inning can start partway down a column, return to its top, and use another column when a batter comes up again. Changing the first batter preserves the already-located continuation cells.

You can also change it after the parse: the same ✎ carries a Re-read this inning button, so you fix the range (or the runs) and have just that inning read again. While the plays are actively being read the editor is locked — an edit then would be overwritten as each inning lands.

Crossed-out boxes. After straightening the photo, the app checks for blank cells and long cancellation scribbles across unused boxes. Clear unused cells are skipped when their position agrees with the inning, so they do not create plays or warnings about missing appearances. A filled run diamond stays a play. A lone X, an isolated scribble, or marks over a real play need review. The app does not stop at a circled third out alone: it may describe an earlier runner, with real plays recorded below it.

Open Unused-cell review above the grid to see the source areas. Each row has three choices: Automatic, Read for a play, and Unused — skip. Use Read for a play if an area was mistakenly excluded. Use Unused — skip when you recognize a cancellation the app was unsure about. These choices apply to this photo only. After changing a choice on an already-read book, use Re-read this inning. Existing plays remain visible until the new read; if an automatic exclusion conflicts with saved appearances, the app keeps them for you to check. Approved game stats are unchanged.

Does your league limit runs per inning? Open League inning rules above the grid and enter the limit for this game. If applicable, select No run limit in the last inning. Leave the limit blank if none applies or you are unsure; the app does not assume a ten-run rule. These settings help the next read interpret an inning that ended before three outs. For an already-read inning, use Re-read this inning after saving the rules.

Two players with the same first name? If your book just says “Brittany” and you have two Brittanys on the roster, the app now uses that game’s RSVPs to work out which one played — if exactly one of them RSVP’d yes, it picks her. It’s only a hint, not a rule: someone who never RSVP’d can still show up in the list if they’re written on your sheet, and someone who RSVP’d yes but isn’t written on your sheet won’t be added. When it still can’t tell — because neither of them RSVP’d, or both did — the row is flagged for you to pick, exactly as before. RSVPs are how it tells them apart, so the more of your team that RSVPs, the fewer of these you’ll have to fix.

The name shown is the ink, not the match: if your sheet says “James” you’ll see “James”, even when the app is sure which James it is. That’s deliberate — seeing the surname it filled in would hide the very ambiguity you’re being asked to check.

A wrong name here would be used for every play in that row. Correct it once before selecting Continue to play overview. Uncertain boundaries, unmatched players and difficult grid measurements are highlighted for the five-minute review window. Unanswered details stay available for review after reading. Score and inning-count contradictions require correction before continuing.

Saved notation hints. The app remembers conventions such as circled out numbers and shaded scoring diamonds for your team’s next upload. Details about which innings were blank or what happened in one game are not reusable hints; the current photo’s printed headers and marks take precedence.

If this step fails outright (rare — the app couldn’t make sense of the names or the innings at all), you’ll see a red banner. Tap Retry to try again, or Discard to remove this attempt and upload fresh photos — maybe the photos were too blurry or the angle too skewed.

Changed your mind mid-read? You don’t have to wait for the app to finish. A Discard button sits at the bottom of the page the whole time the book is being read — while the names and innings are being found, while you’re checking them, and while the plays fill in. Tapping it asks you to confirm (it throws away everything read so far), then removes the attempt so you can upload again. Once you’ve approved the plays, Discard is gone; fix individual plays instead (step 8).

4. Watch the plays fill in

Once you continue (or the five-minute review window ends with no blocking contradictions), the AI reads the actual plays — one inning at a time instead of all at once. Each inning shows a small status chip (waiting, reading, done, or failed) so you can watch your game fill in as it happens; you don’t need to keep the page open, but if you do, you’ll see it happen live.

The digital scorecard has a diamond in every square, with batters down the side and inning totals below. Squares fill in as each inning finishes reading. When the paper columns have been identified, the card preserves their positions, including innings sharing a column and innings continuing into another column. Older uploads show inning columns, with extra columns for repeated appearances.

The result stays on the square while dark basepaths show recorded advancement. A filled diamond means the runner scored; a number inside means the runner was stranded at that base. A red circled 1, 2 or 3 shows the out number. Each R at the bottom right is an RBI credited to that batter: RR means two, RRRR means four. Each × at the bottom left marks a runner retired while that batter was up. The retired runner’s own square has the circled out number. When multiple outs happen on one play, a range shows the possible out numbers; ? means the saved plays don’t establish their order. The exact retirement base is not recorded. Walks display as BB. Amber question marks identify readings to check, and Check runs highlights a disagreement with the book’s inning total.

The card follows your site colors, including dark mode. Player rows use a single dropdown while you’re matching names. On smaller screens, use Previous columns and Next columns to move across the book; the inning totals follow along. The whole page scrolls vertically, without a separate scrollbar inside the card.

Select any play to see its Paper book crop beside the Recorded reading and edit it there. On phones, this comparison opens above the card. Corrections redraw the diamond and totals immediately and save automatically. Use Previous play and Next play to continue reviewing. If no source location was saved, the comparison says so. Readings whose square is uncertain remain available under Plays without a confirmed square.

Tap the little ✎ next to an inning number to fix where it starts and ends, or to correct its runs. The runs total gives the app a cross-check: if the plays disagree, it takes another look and flags anything unresolved. It is instructed to keep the visible evidence rather than invent or remove plays to match a total. Uncertain details receive a five-minute review window; clear phases continue automatically.

You’ll get a second notification once every inning has been through (“N plays ready for review.”), even if one or two needed a retry. If any inning still shows failed at that point, tap Re-parse on just that one to try it again without touching the rest of the sheet — nothing else is lost.

An inning that comes back with no plays at all is treated as a problem, not as an empty inning. Usually it means the app looked at the wrong column of your sheet, so it automatically takes a second look at that inning across the full width of the page before giving up. If it still finds nothing, the inning is marked failed rather than quietly showing zero plays — so a batter who is on your sheet can’t disappear from the review without you being told. If the inning really was blank (nobody batted), just ignore the chip and approve as normal.

You can start correcting while it reads. Each inning appears in the play list as soon as it’s finished, so you can work through the early innings while the later ones are still being read. An inning that’s still being read says still reading… and can’t be edited yet — it would be overwritten the moment it lands.

RBIs fill themselves in. The app works out who drove in each run from the order of the plays — if someone kicks a home run with two on base, all three runs get credited without anyone marking it. It only fills in blanks: anything already read off your sheet is left exactly as it is.

Incomplete or inconsistent innings get flagged. The app checks for missing batters in the selected row ranges, gaps in the full batting order, a runs total that disagrees with the book, too many outs, and fewer than three outs in an inning followed by another inning. A short final inning is allowed, as is an inning that reached the run limit you confirmed. The reader uses this context to interpret ambiguous marks and keeps unclear results flagged.

It takes a bounded second look when needed, then shows unresolved warnings beneath the sheet grid. If selected continuation columns contain a gap in the batting order, it can check the other measured cells in those same columns for missing players. Any recovered range stays flagged for your review; blank cells are not automatically turned into plays. Checks run again after close-up corrections and update as you edit. The plays stay editable; warnings do not block approval, since a shortened inning can be intentional.

5. Review the plays

Use Book / Rows near the top of the page to choose the digital scorecard or the play list. Book opens by default. This toggle remains available after approval, so you can return to the same page to compare and correct the recorded game. Both views show your current saved plays, including corrections made since the upload. In Book view, select a diamond to compare its photo and edit the play.

The review page shows the photos at top and the parsed plays below, grouped by inning. Each play reads as a short sentence:

“Marty — single, stranded at 3rd”
“Casey — out”
“Jordan — double, scored”

Plays that need your attention (amber or red) show a small snippet of the scorebook photo they were read from — glance at the handwriting to confirm or correct without scrolling the photos. Opening any play’s editor shows a larger snippet of its square on the sheet. Snippets keep the handwriting centered and true to shape, whatever part of the page they come from.

Scan for errors: plays with low confidence appear highlighted in amber. Unmatched player names (the app couldn’t find them in your roster) appear in red and block approval — you must fix these before approving.

Fix a player once, not per play. In the sheet grid, every batter row now carries a player dropdown during review. If a row came through unmatched — say the sheet just reads “Brittany” and the app couldn’t tell which Brittany — pick the right player on the row and every play read from that row updates at once. A banner above the grid counts the rows still needing a pick. The per-play player dropdown remains for genuine one-off fixes, but you should never need to correct the same name play by play.

Runs check: a line above the innings totals the plays and the runs the AI read (every play marked “scored”). If the game already has a reported final score, the page compares the two automatically — a green check means the read matches; an amber warning shows the reported final so you can judge how far off the read is. It updates live as you edit, so it also confirms your corrections landed. Each inning heading shows that inning’s run count too — compare against the totals row on your paper book to jump straight to the inning that’s off.

Batting order card: Above the innings, a “Batting order from the sheet” card lists the order players first appear across the plays — this updates live as you fix names. A checkbox, “Set as game batting order on approve” (checked by default), controls whether that order gets saved as the game’s official lineup when you approve. If the game already has a different lineup saved, the card notes that it will be superseded — your prior lineup isn’t lost, it stays in lineup history.

6. Edit plays (optional)

Tap any play sentence to open the structured editor:

Player: Select the correct roster member (dropdown)
Result: 1B / 2B / 3B / HR / W (walk) / OUT / FC (fielder’s choice)
Scored?: Toggle if this runner came around. A home run always counts as scored — picking HR checks it for you and locks it on.
RBI: If scored, who drove them in? (roster dropdown)
Runner out on bases?: Toggle if this runner was put out during a later at-bat
Who was batting? when the runner was retired (only if runner-out is on)
Stranded at base?: Override where they ended up (1st / 2nd / 3rd) if the app’s guess is wrong
Note: Free text — “sac fly”, “forced at 2nd on Anthony’s FC”, etc.

Add plays: Tap the + at the bottom of an inning to add a play in order.

Delete plays: Open the play’s editor and tap Delete.

Reorder: Open the play’s editor and use the ↑ / ↓ buttons to move it within its inning.

All edits save automatically as you go — you can close the page and come back later.

6½. Re-read an inning that came out wrong (optional)

If one inning drifted — wrong batters, a missing at-bat, an out in the wrong place — you don’t have to re-do the whole review. In the Reading innings strip at the top of the review page, an inning that failed shows a Re-parse button: tap it and the AI re-reads just that inning’s part of the photo. Everything in the other innings, including your own edits, stays exactly as it is.

Re-parse starts only once the whole book has finished reading (the button is greyed out while other innings are still being read), and it takes about a minute. If it fails, that inning keeps the plays it already had.

Save any edits first — tapping Re-parse saves your pending changes before it starts.

7. Approve

Once all players are matched (no red highlights), the Approve button lights up. Tap it and confirm — the app will show you the play count and run total.

Approving turns the plays into official at-bats: your box score populates and stats flow into league standings. The scorebook itself is finished at that point — but the plays aren’t locked (see the next step).

8. Fix a play after you’ve approved

Spotted a wrong play in the box score a week later? Open the game and tap Open on the scorebook card (or Edit on the Recorded plays card, if the game never had a scorebook) to get the same inning-by-inning list — now editing the game’s real stats.

Tap any play to change the result, whether the player scored, and who drove them in. The photo snippet next to an open play has an Ink button — it fades the printed form and shows the pen strokes in red, which makes a half-legible circle much easier to call. Tap Photo to flip back. Each change saves on its own and updates stats straight away; there’s no second approval to give. Innings that can’t be right — four outs, a batter after the third out — carry the same warning here, which is usually where the wrong play is hiding.

This works for any past game, not just ones that came from a photo: a game you scored live at the field gets the same editor.

Good to know

No merge/replace: If you’ve already entered some plays by hand, you’ll need to clear them before uploading. The app won’t let you upload if there’s any existing at-bat data for the game. (You can still correct those plays one at a time — see step 8.)
Unmatched players: The AI does its best to match handwritten names to your roster, but handwriting varies. Always scan the review page for red highlights — these block approval and must be fixed by hand.
Scorekeeper dialect: Different coaches use different notation (circled digits for outs, shaded diamonds for runs, X’s for stolen bases or baserunning outs, etc.). The AI has seen many styles, but unusual notation might need a correction or two.
Photos quality matters: Well-lit, straight-on photos with readable handwriting parse best. Very skewed, blurry, or low-contrast photos may fail or need manual fixes.
Photo storage: Your photos stay attached to the game after parsing — they aren’t deleted, so you can refer back to them later. Once you approve, your reviewed plays become the official at-bats; the photos remain alongside them.
Sideways or upside-down photos are straightened automatically before the AI reads them. If a photo is too skewed for that to catch, the read may come back wrong or fail outright rather than asking you to retake it — if that happens, retake it as straight-on and right-side-up as you can and upload again.

Keep score on game day — Live at-the-field scoring for coaches who enter plays as they happen

Uncertain plays get a second look

When the parser isn’t sure about a play, it automatically re-examines just that batter’s square with a focused follow-up question before you ever see the result. If the second look confidently disagrees with the first read, the play is updated — and it stays amber-flagged in your review with a note showing both reads, so you always see that the parser changed its mind and why.

Wrong inning count? Fix it at the check step

If the parser saw the wrong number of innings, use the Innings stepper on the check screen before plays are read: trim extras off the end, remove a specific inning with its ×, or add one (it appears over the next column for you to fine-tune). Getting the inning count right here is worth far more than fixing misplaced plays afterward.