Basketball scorekeepers document their work by recording every scoring event as a discrete 1-, 2-, or 3-point action, attaching team fouls to the matching period, and exporting the resulting log as a PNG image or a CSV file that can be opened in any spreadsheet program. A documented workflow turns a stream of tap-actions into an inspectable record, so a coach, a parent helper, or a future you can revisit what actually happened in the game and reconstruct the score without relying on memory. The Basketball Scorekeeper at /productivity/basketball-scorekeeper/ is built around this idea: it accepts only the three legal scoring values, treats each foul as a separate event that does not change the score, and saves every action to a private daily summary inside your browser. Undo restores the prior state, so corrections stay inside the same audit trail rather than scattering notes across scraps of paper. The rest of this article walks through exactly which actions to record, in what order, and how to turn them into a portable document.
Why Documenting Your Scorekeeping Steps Matters
Every basketball game leaves behind a string of small decisions: which team scored, whether the basket was a one, two, or three, when a foul was called, and which period the action happened in. A few minutes after the final buzzer those decisions are already fuzzy, especially for a volunteer who is also watching the play. Documenting the steps solves two problems at once. It records what happened so the result can be defended, and it records how you recorded it, so the same workflow can be replayed for the next game without reinventing it from scratch.
A handwritten tally cannot tell you whether a "5" came from a single three and a single two, or from five free throws, and it loses the fouls the moment you look away. A documented log that names the event type preserves both the total and the path to that total. That distinction is what separates a record from a guess, and it is also what makes the saved file useful when someone other than the original scorekeeper reads it later.
What the Basketball Scorekeeper Logs for You
The tool's job is to convert taps into a written record. Once you enter team names, the screen keeps a running total for each side, the current period, and each side's current team-foul count. Every tap you make is captured, so the saved log is a faithful copy of what you actually pressed, not a later reconstruction.
| Event type | Points recorded | Reference |
|---|---|---|
| Free throw | 1 | FIBA Official Basketball Rules 2024, Article 16 |
| Field goal from the two-point area | 2 | FIBA Official Basketball Rules 2024, Article 16 |
| Field goal from the three-point area | 3 | FIBA Official Basketball Rules 2024, Article 16 |
| Team foul | No point change | Tool design: fouls are tracked separately from the score |
Because the three point values follow the values set out in the FIBA Official Basketball Rules 2024 and are cross-checked by the USA Basketball youth guidelines, the buttons themselves act as the first line of documentation. You cannot accidentally add a four-point event, and you cannot accidentally hide a foul inside the score. The numbers below each team name update live, and behind them the tool is quietly writing the same sequence to a daily summary row tied to your local calendar date.
How to Document Your Basketball Scorekeeper Steps
- Open the Basketball Scorekeeper and type a name for the home team and a name for the away team in the two name fields at the top of the screen. The names appear on every saved row, so spelling them once at the start documents the rest of the game for you.
- Tap the +1, +2, or +3 button under the team that scored for every made basket. Pick the value that matches the actual shot: a free throw is one, a goal from inside the arc is two, and a goal from behind the arc is three.
- Use the Record team foul control on the side that committed the foul so the foul is captured as its own event without altering either team's total. This is the step that keeps fouls visible separately in the saved log.
- Hit Next period at the end of each quarter. The score stays where it is, and the on-screen team-foul counts reset for the next period while the saved daily summary keeps the period history intact.
- Use Undo last event to correct a wrong tap. The tool restores the full prior game and the prior daily summary, so undoing a foul does not accidentally subtract a point and undoing a three-point event restores the right total.
- Tap Start new game when the game ends and you want a clean active board. Saved daily history stays available for export; only the active scoreboard and the current-period foul display clear.
Turning the Log Into Portable Documentation
Once you have run a game, two export buttons convert the in-browser log into files you can keep and share. Export CSV produces a compact file with one row per local date, and the columns are home points, away points, home fouls, and away fouls, so a later reader does not have to guess what a total means. Export PNG produces a 1080 by 1350 visual record with a total and recent days, and the image leaves out team names and a web address so the file carries only the scorekeeping context you actually want to share. Both downloads use native browser APIs, so the files are made locally and never travel through a server.
A quick worked example shows how the log preserves both totals and actions. If a team hits three two-pointers, two free throws, and one three-pointer in a single game, the documented steps read 2, 2, 2, 1, 1, 3 and the saved total reads 11. Anyone reviewing the export can verify the total by adding the values back: (3 × 2) + (2 × 1) + (1 × 3) = 6 + 2 + 3 = 11. The math is simple on purpose; the value of the log is that the original sequence is still there beside the sum. For more on verifying a saved row against what actually happened on the court, see how to check results after using Basketball Scorekeeper.
Limits: What This Tool Does Not Document
The Basketball Scorekeeper is deliberately narrow. It is a score and team-foul ledger for two teams, and it does not provide a game clock, a shot clock, a possession tracker, a player roster, a player-foul ledger, or a rules engine that decides penalties and substitutions. It will not record who took a shot, who committed a foul, or how much time was left on the period when something happened. If your documentation needs include any of those, the tool's saved log is a starting point, not a full scoresheet.
Competition rules vary across FIBA, NBA, WNBA, NCAA, youth, and pickup formats, and the tool does not claim to resolve those differences. Use it where a standard one, two, or three point two-team ledger, a visible period, and a team-foul reminder are the convenience you want. Record each event, correct a mistaken tap with Undo, move the period deliberately, and export only the private history you choose to keep.
Where the Documented Steps Live
Every event you record is saved into a small private daily summary under the tool's local storage key, so the steps you documented stay in this browser on this device. A different device starts empty, clearing site data removes the record, and an unavailable browser storage area is disclosed rather than treated as a hidden backup. If you want to keep your documentation beyond one device or one clearing of site data, run Export CSV or Export PNG as soon as the game ends; the file you download is the durable copy.
Clear local history is the control that removes every locally saved record when you deliberately want a fresh browser state, and it does not touch any exported files already on your computer. Treat the in-browser log as the working draft and the export files as the final document, and the workflow stays clean across games, across weeks, and across devices.