GPS is the easy part

Team sports adopted GPS tracking a long time before golf did, and spent a decade learning an uncomfortable lesson: the generic metrics that come out of the box are mostly not the ones that matter. Total distance, top speed, accelerations — all measurable, all standard, and all close to meaningless until someone translates them into the demands of the specific sport being played.

Jo Clubb makes the point plainly in her guide to GPS monitoring: the useful metrics depend on the playing surface, the playing area, the structure of the game, and the movements that actually decide outcomes in that sport. Distance covered means one thing to a footballer and something close to nothing to an ice hockey player on a skate. The practitioner’s job is to be the translator between the raw feed and the sport.

Golf needs the same translation. The sport-specific question on a golf course is not how far anyone walked. It is whether a group is holding position in a queue of other groups moving through the same eighteen holes in the same order.

1. Jo Clubb, Sportsmith: An Essential Guide to GPS Monitoringsportsmith.co

You can calculate a great deal from a position trace. Distance travelled, average speed, time stationary, movement patterns, where a group lingers. Almost none of it belongs at the centre of a pace product.

A group covering 6.8 kilometres is a fact. A group sitting seven minutes behind the one in front is a decision waiting to be made. Golf gives us something most sports don’t: a fixed sequence, a known route, and a field of groups progressing through identical ground. That structure is what lets a position become a judgement.

The shift is small to describe and large in practice. Instead of asking where a group is, ask where it should be — and if it isn’t there, whether something is happening that will stop it catching up.

A group has stopped moving. The GPS reading is the same in every case; what it means is not.

Three situations, three different correct responses, one identical data point. That gap between signal and meaning is exactly where a pace system either earns its place or becomes another dashboard nobody opens. More data doesn’t close it. Context does: the sequence of holes, the position of the group ahead, the state of the field behind, and what normally happens on that hole at that time of day.

The goal is to take a fairly complicated underlying dataset and produce a very small amount of information that a person can act on. In practice that’s a ladder, and most systems stop one rung too early.

From position fix to next action

Each rung is more useful than the one below it, and only the top one changes anyone’s afternoon. "Group 12 is 147 metres behind" is data. "Group 12 is seven minutes behind" is information. "The gap has grown on every hole since the 6th — go and look at the 6th" is an instruction.

The "so what" test

A useful filter for any pace metric is to say it out loud and then ask: so what? If nobody can name what they’d do differently, the number doesn’t belong on the screen. It can still exist in the data. It just shouldn’t take up attention that a marshal needs for something else.

The same test cuts through course analytics. Telling a club that the 7th plays in an average of seventeen minutes describes the hole. Telling them the 7th is where the field first backs up on two Saturdays in three identifies a problem — and points at the setup, the tee interval, or the walk onto it.

The other lesson worth stealing from sports science is about who receives the information. The strength coach and the head coach do not want the same file. Neither do the marshal and the general manager — and putting everything in front of both makes the product worse, not better.

The closer someone is to the action, the more immediate and narrower the answer has to be. The further away they sit, the more the context and the trend matter and the less any single group does. Same GPS traces underneath; five presentations on top.

That spread of questions gives pace data a natural hierarchy. A system that only works at one level answers one person’s question and leaves everyone else guessing.

1. Live: who is on pace right now, and where are gaps opening

2. Round: where did this round lose its time, hole by hole

3. Hole: which stretch of the course did the delay actually start on

4. Day: what happened across today’s field, from first tee to twilight

5. History: which parts of the course cause problems every week, and has anything we changed made a difference

The point isn’t to expose all of it at once. It’s to make it possible to move between levels — to see a group falling behind, ask whether that hole does this every Saturday, and get an answer without exporting anything.

Continuous tracking makes something possible that a single check-in at the turn never could: seeing how a group fell behind, not just that it did.

Two groups can both be ten minutes down and represent completely different operational problems. One has been leaking a minute a hole for nine holes. The other played fine until they hit a wall on the 7th. Reduced to a single number, they look identical. They aren’t, and they don’t need the same response.

• Gradual deterioration — a group that loses a little on every hole

• Sudden bottleneck — a clean round until one hole stops the field

• Recovered pace — a gap that opened and then closed on its own

• Persistent gap — behind from the first tee and never caught up

• Course-wide congestion — everybody queuing, nobody at fault

Naming the shape is what turns "the round took 4:22" into something a course can act on. It also settles arguments, because most of these patterns have nothing to do with the group getting the tap on the shoulder.

There’s a sequence to how courses get value out of position data, and most tools stop at the first step.

1. Visibility — you can see where every group is

2. Understanding — you can see where a problem started and how it spread

3. Management — you get told what to do about it, early enough to matter

That last step is the one that changes a day. A marshal doesn’t need another screen; they need to know that this group needs attention and why. A course manager doesn’t need thousands of traces; they need to know where the course consistently loses pace. A general manager doesn’t need a prettier map; they need to know whether anything got better.

That’s the line we’re trying to hold in WayFairer. Compare each group to the one ahead rather than to a target time. Surface the gap while it’s still four minutes. Point at the hole where it opened rather than the hole that phoned it in. And keep the number of things on the screen small enough that a marshal can read it from a cart.

1. GPS is the input, not the product. The product is the judgement built on top of it

2. The right metric is relative, not absolute — position against the field beats anything measured in metres

3. If a number doesn’t change what someone does, it doesn’t need to be on their screen

4. The shape of a delay explains more than its size, and usually points somewhere other than the group being blamed