Last updated: September 2, 2026
Progress on a launch monitor shows up as a tighter strike pattern and a repeating smash factor, not a bigger carry number. To see it you need a short log after every session, trimmed block averages read over weeks instead of one number, and a clear picture of where your data lives and what forgets it.
Progress shows up in strike quality first, then dispersion, then delivery numbers, and carry comes last. Most golfers read it backward, watching the carry column and missing the thing that actually moved.
The order matters. A well struck 7 iron produces a smash factor in the low to mid 1.30s (the Trackman tour average is about 1.33). A smash of 1.40 or higher on a 7 iron usually means a thin or delofted strike, not a better one. So the first sign of real improvement is the smash factor settling into a narrow, repeatable band rather than climbing higher.
Once strike quality stabilizes, dispersion tightens. The spread between your best and worst carry in a ten ball set shrinks. This is the second signal, and it is the one that actually translates to scoring: a tighter pattern means a more predictable club, which means you can trust a number on the course.
Delivery numbers (club path, face angle, angle of attack) come third, because an off center strike bends every number downstream of it. A face and path read on a toe hit is not the delivery your swing actually produced. Delivery data only starts meaning something once the strike is centered. Which delivery numbers your unit actually measures is a per number question, not a per unit one: face angle is estimated or absent on nearly everything affordable, while club path and attack angle are measured on several units at that money, camera and radar alike. The accuracy tool shows the split for your specific device.
Carry comes last, and this is the part that makes people quit a fix early: when a strike fix works, the carry number usually goes down while dispersion tightens. You were used to a thin, hot, low spinning shot that rolled out. Now the ball launches higher, spins closer to the 6,000 to 7,500 rpm window a 7 iron should produce (the Trackman tour average sits inside it), and lands shorter. That is the fix working, even though it feels like losing distance.
The numbers never lowered my scores until I quit grading my swings with them and started using them to grade my practice.
Log the conditions you practiced in and a trimmed average for each club you worked, plus your one goal and one keep or revert decision. That is the minimum that makes a trend readable a month later.
The within session loop is covered step by step in the practice plan guide. This section covers what goes in the log itself, the part that connects one session to the next.
A carry number is only as good as the conditions you can still describe. Record these every session:
Without the conditions, a carry number from February and a carry number from July cannot be compared. Method plus condition, or it is a memory rather than a number.
For each club you worked in the session, log:
Only trend numbers your unit actually measures. A number it estimates (spin on some radar units, face angle on nearly all affordable ones) cannot carry a trend because you would be trending the estimate, not the swing. The accuracy tool tells you which numbers are measured and which are computed for your specific device.
One session is noise. Whatever survives two or three sessions is real.
What that looked like for me: my March yardage card said 185 for my 7 iron, the club I then spent two months doing contact work on. Thirteen measured blocks across five sessions ran 142 to 178 and never touched 185, while the 9 iron on the same card at 150 pooled to 150.5 across thirty raw shots because I had never run a swing change on it.
Three lessons come out of that:
Zero is a reference, not a target. A dead 0.0 club path with the face a touch open still slices. A golfer playing a draw on purpose should not be aiming for 0.0 either. What you want trending is a face to path relationship you can repeat, not a number sitting on zero.
And here is the single session limit that most people run into: a single session read stops at the bands. It can tell you that your 7 iron smash was 1.34 today. It cannot tell you whether 1.34 is new or normal for you. Only your own history across sessions can answer that question, and only if you logged the conditions alongside the numbers.
Your data lives in the launch monitor's own export, not in the sim. Of the platforms I have checked, GSPro keeps nothing between sessions and the others each forget something you would expect them to keep. The rows below were verified in July and August 2026.
| Platform | What it keeps | What it forgets |
|---|---|---|
| GSPro | Shot table and CSV export in practice range and on course practice modes (on course practice records the club with every shot) | Everything, between sessions. A scored round or tournament exports nothing. Close without exporting and the shots are gone. |
| Awesome Golf | Insights builds a sessions list and per club stats from Shot by Shot, Coaching, and Club Distances modes | Course play goes to a separate virtual rounds dashboard of score, fairways, greens, and putts. The round is graded as golf, not logged as shots. |
| Trackman (consumer app) | Only what the app itself displays; nothing leaves it | Cannot export data at all. Real exports come from TPS, the software in bays, studios, and fitting carts. |
| Uneekor VIEW AI report (Swing Optix beta) | Reports and swing videos generated during the beta. This row says nothing about VIEW's own shot history. | Swing videos held 30 days. Reports generated during the beta may not survive its end. The report you most want to compare against is the one that ages out first. |
None of the sim platforms treat a round as a data source. That is a design shape, not a missing setting.
Two rules follow from this:
Pasting a launch monitor CSV into an AI gives you a useful single session read, and the limit is what the file does not contain.
I read my own exports by pasting the file into an LLM. I hit into a Uneekor Eye Mini Lite in a garage shared with two cars, and that unit has been in the garage since December 2024. The honest limit is this: my Eye Mini Lite file carries no impact location anywhere. The one thing that skews a path and face read, where on the face the ball was caught, is invisible to whatever reads the numbers. The AI will still hand back a clean root cause chain built on top of that gap. It will sound confident, and the foundation it reasoned from has a hole in it.
Two consequences:
Chip, the AI coach I built, keeps every session you log and reads the trend across them, so the log on this page happens without a spreadsheet. Disclosure: I am the founder of Fore-ward Thinking. I built Chip to solve this exact problem for myself. It tells you which number deserves the next practice hour and whether the number that jumped out today is new or normal for you, and keeps the bookkeeping across weeks so practice time goes on practicing instead of spreadsheets. It builds a Golfer DNA profile you can export and hand to a real coach or fitter, which makes that coach more useful, not obsolete. It coaches from data, not from swing video. Free to try, 3 messages, no card, then $19.99 a month.
How many sessions before a change counts as real?
Two to three sessions with the same protocol is the minimum. One session is noise regardless of sample size within it. If a number moves the same direction across three measured blocks on different days, the change is probably real. If it bounced back by session two, it was setup, fatigue, or randomness.
Why did my carry drop after a lesson?
A strike fix often reduces carry before it improves it. A thin or delofted strike is hot and low spinning and runs out, so it posts a flattering carry. A centered strike launches higher, spins more, and lands shorter. That is the fix working, not a regression. If dispersion tightened at the same time, keep going.
Should I track club path and face angle?
Only the ones your launch monitor measures directly, and that is a per number question rather than a per unit one. Face angle is estimated or absent on nearly every affordable unit, while club path and attack angle are measured on several of them, camera and radar alike. Even on a unit that measures them, an off center strike bends both readings, so path and face numbers are only trustworthy once the strike is centered. The accuracy tool on this site shows the split for your device.
Does GSPro save my sessions?
No. GSPro keeps the shot table and CSV export only during the active session in practice range and on course practice modes. A scored round or tournament exports nothing. If you close the session without exporting, the shots are gone. Export before you close, every time.
Can I just paste my CSV into ChatGPT?
Yes, and it will give you a useful read, up to a point. The limit is that every paste starts from zero. The AI does not know what your typical 7 iron looks like or what changed since your last session. It also cannot see what the file does not contain. My own Eye Mini Lite export carries no impact location at all, so the AI builds a root cause chain without knowing where on the face I caught the ball. Check your own export for that column, and check the strike before you trust the chain.
Keep going:
A measured loop of baseline, work, retest, and log, with beginner, intermediate, and advanced versions and a printable session template.
How to build a dispersion picture from your carries, why the spread decides which gaps are real, and why the tightest pattern of the day can still be the worst one.
Paste a CSV export and get a plain English read of smash factor, spin, launch, and descent against well struck windows. Tell it your lofts and it reads a strong lofted set against the right window instead of the number stamped on the sole. Tell it your device and it refuses to grade a number your device only estimated.
Pick your launch monitor, your setup, and your software. See which numbers it measures, which it computes, which it models, and which it never produces, with the maker's own accuracy figures where they publish any. Of fifteen setups, only one maker publishes real numbers.