Turning member feedback into a greens-team plan

From a flood of reports to a workable list

When members can report a problem in seconds from their phone, you stop hearing about the course once a year at the AGM and start hearing about it every single day. That's exactly what you want — but a busy week can land fifty or sixty reports across eighteen holes, and a head greenkeeper staring at that list on a Monday morning needs more than a pile of grievances. They need a plan.

The job, then, isn't to collect feedback — it's to convert it. Every useful course-condition report carries three things: where the problem is, how many distinct members have noticed it, and whether it's a one-off or something that keeps coming back. Those three signals are enough to turn an unsorted inbox into a ranked work list that the greens team can trust and the committee can stand behind.

Rank by reach and recurrence, not by volume

The instinct is to act on whatever you heard about most recently, or most loudly. Resist it. The member who emails the secretary three times about the bunker by their own ball isn't telling you that bunker matters most — they're telling you they're persistent. Counting raw messages just rewards the noisy.

A fairer measure is reach: how many distinct members flagged the same thing. One issue raised once by twelve different people is a far stronger signal than one issue raised twelve times by the same person. Layer recurrence on top — a problem that reappears month after month is structural, not cosmetic — and you have a priority order built on evidence rather than volume.

• Distinct members affected — count people, not reports, so one persistent voice can't inflate a problem's apparent size.
• Recurrence over time — flag anything that returns after being marked fixed; it usually points to an underlying cause, not bad luck.
• Severity and safety — a slippery step or exposed irrigation head jumps the queue regardless of how many noticed it.
• Effort to fix — when two issues score equally on reach, do the cheaper, faster one first.

Use per-hole hotspots to see the course as members do

Numbers in a spreadsheet tell you what; a map of the course tells you where. When reports are tagged to the hole — or even the specific green, tee or bunker — patterns appear that no amount of reading individual messages would reveal. Suddenly it's obvious that the 7th green has drawn nineteen reports this month while the rest of the course is quiet.

Hotspots like these are gold for planning. They let you batch work geographically, so a greenkeeper fixing the 7th green also deals with the worn approach and the unraked greenside bunker in the same visit. They also expose the difference between a hole members complain about and a hole that's genuinely failing — which are not always the same hole.

Balance quick wins with the long agronomic game

Not every priority belongs in the same plan. Member feedback is brilliant at surfacing the visible and immediate — divots, unraked bunkers, broken markers, a path that floods — and these quick wins matter enormously because members can see you acting. A morning spent on twenty of them buys more goodwill than almost anything else you'll do.

But the work that decides how the course plays in August — aeration, drainage, sward composition, the slow rebuild of a struggling green — runs on an agronomic calendar that no volume of reports should override. The skill is holding both: a fast lane for visible fixes that keeps members feeling heard, and a protected long-term programme that the greens team plans on agronomy, not on this week's mood.

Protect the greenkeepers from being driven by noise

A greens team chasing every fresh complaint is a team that never finishes anything. One of the quiet benefits of structured feedback is that it gives the head greenkeeper cover. When the chair asks why a particular member's pet issue hasn't been touched, the answer is data: it was raised by two people, it scores low on reach, and here are the eleven higher-impact jobs in front of it.

Set the rhythm deliberately. Triage reports once or twice a week rather than reacting hour by hour, agree the ranking with the greens chair, then let the team work the list without interruption. Reserve interruptions for genuine safety issues. A platform like GoodGreens helps here by putting every report in one place with the member-reach and recurrence already counted, so the prioritising is done before anyone picks up a rake.

Report progress back to the committee and members

A plan you can't measure is just a wish list. Track two simple numbers and you can prove the operation is working: your fixed rate — the share of reported issues resolved within a set window — and the trend in reports per hole over the season. A falling report count on the holes you've worked is the clearest evidence your prioritisation is right.

Share that story in two directions. The committee wants assurance the greens budget is well spent, so give them the fixed rate and the hotspot trends each month. Members want to know they were heard, so a short 'you reported it, we fixed it' note — by hole — closes the loop and quietly encourages the next round of useful reports.