I started scoring this way when I was coaching 13U and I’ve stuck with it ever since.

Basically, it gives the pitch sequence and the result of any on-field event.

So for example:

CBBSFFBX

Would be a pitch sequence, where C is ‘called strike’, B is ‘ball’, S is ‘swinging strike’, F is ‘foul ball’, and X is ‘ball put into play’.

So this batter hit a 3-2 pitch into play.

That would be accompanied by an event:

D7/L7;B-2;1X(75)

Would be a double to left field on a line drive fielded by the left fielder, with the batter reaching second. The runner on first was put out 7-5.

Obviously this is not an extensive list of the pitch codes or the event codes, but you get the idea.

The major advantage compared with standard scoring is that it allows you to recapitulate the game pitch by pitch, and is much easier to extract situational stats from. For example, in standard scoring you might indicate a 3-2 count (some scorecards have little boxes to indicate balls and strikes), but you wouldn’t know what order those balls and strikes came in, nor would you know how many total pitches were thrown during the plate appearance.

For plays on the base paths that don’t involve a ball hit into play (eg. a stolen base), you indicate with a “.” after the pitch:

Pitch sequence: CBB.

Event: SB;1-2

Then you start a new line with “CBB.” and continue from there. For example:

Pitch sequence (on new line): CBB.CS

Event: K;BX(23);2-3

In that case, it’s a strikeout (K) with an uncaught third strike, with the batter retired on the throw from the catcher to the first baseman. The runner on second advanced to third on the throw.

Admittedly, this sounds complicated. But once you learn the process, it’s very simple and is very well suited to reviewing the game (from a statistical POV) afterward.

Does anyone else score like this (Retrosheet format)?