Recently, when I’ve been scoring baseball games, I’ve preferred to use the Project Scoresheet notation.  Like just about any scoring system, Project Scoresheet has its pros and cons, but I like the way that score cards in this notation can be easily input and analyzed by a computer.  The tradeoff is that it can be difficult, at times, to look at the score card and get a quick idea of the current state of the game.  At first, the notation can be a bit difficult to learn, but once you get the hang of it, you can score games quite efficiently.

I won’t even try to do as good (or as thorough) of a job describing this scoring notation as Alex Reisner.  Check out his description of Project Scoresheet and example score card here.  Alex Reisner’s Introduction to Project Scoresheet Scoring (PDF)Alex Reisner’s Project Scoresheet score card (PDF). Also,  check out his website at  He has some pretty interesting scorecards and player performance graphs on there. 

To give a quick overview: a Project Scoresheet score card has three lines for each at-bat.  The top line is for anything that happened “before the play” (stolen bases, wild pitches, passed balls).  The middle line is for what happened during the play itself (single, double, strike out, ground out, etc.).  The bottom line is for the actions following the play (base runner advancements).

All on-field actions are abbreviated by short codes.

Single, Double, Triple, Home Run, Strikeout = S, D, T, HR, K

To code outs where the ball was put into play, you record the fielders who touched the ball.

A flyout to center = 8/F

A groundout to the shortstop = 63/G

Again, the main advantage to this type of scoring is that the score card can quickly be entered into a computer for analysis.  All of the game files at use this notation.


no comment until now

Add your comment now