MetriQ GolfEvery Shot. Optimized
Guides

How to record second balls in your golf stats

A second ball can be useful practice, but it answers a different question from the first attempt. Record both, label their roles, and keep them separate when reviewing on-course performance. Otherwise, a round with repeated approaches can appear better simply because the dataset includes extra chances.

Picture a dedicated on-course practice session where extra shots are permitted: the first approach finishes short, you adjust, and the next ball lands on the green. Both shots contain information. The first records your initial response to that situation; the replay records what happened after you had already seen a result. Replacing the first with the second removes the very observation that prompted the adjustment.

Decide what the record is meant to describe

Before starting, choose the question. Are you recording a round played under its applicable rules, observing initial attempts during an on-course practice session, or testing repeated shots? These records can all be useful, but their totals describe different activities. Even first attempts made during an experimental session are not automatically equivalent to tournament shots.

For this article, a practice replay means an extra attempt made for learning, not a ball played under a Rules of Golf procedure. A provisional ball, stroke-and-distance relief, and two balls played to resolve a rules uncertainty in stroke play have their own status. Record those correctly rather than labeling every additional ball a replay. See Rules 18 and 20 in the sources.

Nine situations can produce eighteen attempts

Here is a hypothetical example, invented only to explain the counting. In a permitted on-course practice session, a player faces nine approach situations and makes one initial attempt plus one practice replay from the same starting area in each. Every attempt is recorded. The observation is whether the ball finishes on the putting green; this is not a carry measurement or a full-round greens-in-regulation statistic.

Initial attempts: 4 green finishes from 9 attempts, or 44.4%. Practice replays: 7 from 9, or 77.8%. All attempts pooled: 11 from 18, or 61.1%. Percentages are rounded to one decimal place.

The pooled figure is correct for all eighteen attempts. It is misleading if presented as the player's first-attempt result. Comparing it with a previous first-attempt-only session would change the measurement halfway through the comparison. The higher replay result does not establish learning, a better club choice, or a coaching effect. The player has seen the initial shot, and other factors can differ too.

Nine situations is an illustration, not a recommended session size or a reliability threshold. Keep the counts visible. A neat percentage cannot make a small, selected set of shots representative.

Give each attempt a place in the record

A simple companion log can use one row per attempt: situation identifier, attempt role, club, starting distance and lie, intended target, result, and relevant changes. Write the target before the shot if you want to evaluate it later. Do not infer it from where the ball stopped. Record a changed club, moved ball, new target, advice, or altered lie on the replay.

Keep the original attempt even after a poor strike. If a replay is made only after a miss, say so: that replay group contains only situations where the first attempt missed and should not be compared as though every first attempt had a matching second ball. If you keep whichever ball looks best, label the activity accordingly and do not present that chosen-ball total as an ordinary round score.

Handle a missing observation without inventing a miss

Suppose one initial result in the example was not observed. Among the other eight, four finished on the green. Report 4 of 8 observed attempts, with coverage of 8 of 9 planned initial attempts. The missing result is unknown, not automatically a miss. Nor does excluding it make the observed percentage representative; the reason for the missing observation may matter.

If you stop a hole early or skip part of the sequence, preserve that fact. Useful shot observations can remain in a practice log without becoming a complete hole score. Do not invent the remaining strokes to fill an analytics report.

Keep handicap posting as a separate decision

Your practice label does not determine whether a score must be submitted for handicapping. Apply the relevant association's requirements and consult the Handicap Committee when rules breaches or unusual formats create uncertainty. Likewise, this logging example is not permission to hit extra balls: follow the facility's restrictions and the applicable Rules of Golf, including Rule 5.5 during a round.

Bring the right record into MetriQ

MetriQ's public product information describes round analysis and practice records. Base that analysis on a clearly identified record: which attempts were included, what the outcome means, and which observations are missing. The companion log proposed here is an editorial workflow, not a claim that MetriQ automatically detects replays or offers a particular exclusion filter.

Before comparing two sessions, read the labels and denominators aloud. If one result means initial attempts and the other means the best of several balls, rebuild the comparison before interpreting the change. For the next step in evaluating a lesson, the guide to checking progress after a golf lesson explains why a later independent check asks a different question from an immediate replay.

Related reading

Sources

The counting example is hypothetical. It illustrates record keeping, not a validated practice protocol or a guarantee of improvement.

Bring the analysis into your coaching.

See MetriQ for your program