The Thirty Minute Practice Plan for a Weeknight Range Visit

You finish work at half five, get to the range at quarter past six, and the lights go on at seven. That is the real window. Not the ninety-minute Saturday session you keep promising yourself, but thirty minutes with a bay, a bucket and a phone at 10% battery.

Most golfers fill that time badly. They hit fifty balls with the 7-iron, change club when it goes wrong, and leave with a vague feeling that the low point was “a bit better at the end”. There is no data point in that. You cannot compare it with next Tuesday.

A good golf practice plan in 30 minutes does one thing: it produces a number you can compare. So the plan below is built around ball counts and a fixed clock, and the AI tools slot in at exactly two points: before you go, and when you get home.

Why the count matters more than the clock

Thirty minutes at a typical range is about 40 to 45 balls if you are not rushing and you stop to look at each one. Go over 50 and quality drops. That is not folklore: if you log shots on a Garmin R10 or a Rapsodo MLM2PRO, you will see dispersion widen noticeably in the last third of a long block.

So the plan caps at 42 balls. Fixed ball counts mean every session has the same denominator, which is what turns “felt good” into “6 of 10 started on target”.

The template

Total: 42 balls. The last block is the one that matters. Four balls, target called before you swing, written down. Over a season that becomes a column of numbers.

Step one: let the AI pick the fault (before you leave the house)

This is where the tool question comes in. Filming your swing is only useful if the software reads it correctly, and the honest picture is mixed.

• Sportsbox AI builds a 3D model from a single down-the-line or face-on phone clip. It is good for pelvis rotation, spine tilt and shoulder turn numbers. Treat its “swing score” with suspicion; use the individual metrics.
• OnForm and Hudl Technique are not really AI judges. They are slow-motion and drawing tools, and that is fine. Draw your own lines.
• Rapsodo and Garmin R10 apps give ball data (carry, club speed, smash factor, face angle on some units). They do not see your body, so they tell you what happened and not why.
• Arccos is strongest on-course. Its strokes gained splits tell you which club to prioritise, which phone footage cannot.

Rule of thumb: use the body-reading tool for cause, and the ball-data tool for the effect. If Sportsbox says your pelvis stalls at impact and the R10 shows heel strikes with a face-to-path that is open, you have a consistent story. If they disagree, trust the ball.

Pick one fault. One. A 14 handicap who slices the driver and also fat-strikes irons has two problems, but tonight’s session addresses whichever costs more shots, and Arccos will usually tell you it is approach play.

Worked example: Dave, 16 handicap, early-release iron strikes

Dave films a 7-iron from down the line on Sunday. Sportsbox shows his spine angle standing up by around 8 degrees between top and impact. His R10 data from the last range visit:

7-iron, 20 shots
Avg carry:        131 yds
Carry std dev:    11.4 yds
Smash factor:     1.28 avg
Attack angle:     -1.1 deg

A smash factor of 1.28 on a 7-iron is low (you want 1.32 to 1.36), and a shallow attack angle with high carry spread says thin and fat misses. So the fault is early extension, and the symptom is strike.

Tuesday plan:

• Warm-up (6 balls): half swings, 9-iron.
• Focus (12 balls): the chair drill, with a headcover or the back of a bay chair touching his backside through the swing. Three sets of four. Record smash factor on each.
• Transfer (10 balls): full 7-iron, same feeling. Pass means smash factor 1.30 or better.
• Driver (10 balls): 5 on the tee, 5 with a fairway target. Count hits that land inside a 40-yard-wide imaginary corridor.
• Test (4 balls): pick a 130-yard target, call the shot shape, score it.

Dave’s result that night: transfer block 6 of 10 at 1.30 or better, driver 4 of 10 in the corridor, test 2 of 4. Those are three numbers. Next week he can beat them or not.

Step two: the five-minute review at home

Don’t skip this, because it is where the AI earns its keep. Export the session from the launch monitor app and look at three things only:

1. Pass rate in the transfer block (target: add one pass per week).
2. Driver corridor hits.
3. Test score out of 4.

If you want to feed the CSV into ChatGPT or Claude, give it a narrow question: “Here are 42 shots. Compare block 2 and block 3 carry deviation and tell me whether the focus drill carried over.” A vague prompt such as “analyse my session” will return a vague paragraph. The tool is good at arithmetic on a table and mediocre at coaching.

Rotating the focus without going mad

Run the same fault for three visits before switching. Here is a four-week example:

Three weeks on one thing feels slow. It is the point. Changing faults every session is how people stay at the same handicap for five years.

When you have a monitor but no bay

Budget units like the Garmin R10 need a bit of space behind and a net or open range. If the range is busy, drop the driver block to 6 balls and add 4 to the test. Keep the total at 42, because the denominator matters more than the split.

If you have no launch monitor at all, use the phone alone and swap the metrics for something countable by eye: the number of strikes that leave a divot starting after the ball, or shots finishing inside a pair of range markers. It is cruder, but still a number.

For the wider process of turning swing analysis into drills week after week, the pillar guide on turning analysis into a practice plan covers how to choose faults and build a longer block around them.

Last practical bits

Take a pencil and a card, not just your phone. Writing “2/4” on the way out of the bay takes ten seconds and survives a dead battery. Put the card in the car door. On the following Tuesday, you read it before you hit a ball, and that is the whole system.