leaguesevents
The Golf League Spreadsheet: What Works and Where It Breaks
How to build a golf league standings spreadsheet that holds up — the four sheets, the formulas that matter, and the five places every one of them breaks.
Almost every golf league in the world runs on a spreadsheet, and most of them run on it fine. If you have twelve regulars, one format and a season that ends in September, a spreadsheet is not a compromise — it is the correct tool, it costs nothing, and everybody already knows how to open it.
So this is not a post about how spreadsheets are bad. It’s the honest version: here is the spreadsheet that actually works, and here are the five specific places it stops working, so you can tell which side of the line your league is on.
The spreadsheet that works
Four sheets. Not one — one sheet is where leagues go wrong, because scores, handicaps and standings all want different shapes.
Sheet 1 — Players. One row per golfer, and it is the only place a name is typed. Name, index,
tees, email, and an Active column you can flip when somebody drops out mid-season. Everything
else looks a name up from here, so a typo is fixed once.
Sheet 2 — Weeks. One row per week: date, course, tees, format. This is the sheet nobody builds and everybody needs, because in October somebody will ask what you played on week 6 and the answer should not be “I think Steve remembers”.
Sheet 3 — Scores. One row per player per week. Long, not wide. A wide sheet — a column per
week — looks tidier for a month and then you are inserting a column in the middle of eighteen
formulas. Long is: Week | Player | Gross | Course Handicap | Net | Points.
Sheet 4 — Standings. Entirely formulas. Nothing is typed here, ever. If you find yourself typing a number into the standings sheet, the spreadsheet has already broken and you have patched it by hand.
The formulas that matter
Course handicap, not index. Your players have an index; what they get on a given Thursday depends on the tees and the course. Course Handicap = Index × (Slope ÷ 113) + (Course Rating − Par), rounded to the nearest whole number. Put slope, rating and par on the Weeks sheet so the Scores sheet can compute it rather than you re-typing strokes every week.
Then the allowance. The course handicap is not what everybody plays off. Individual stroke play runs at 95%, four-ball match play at 90%, a scramble is a percentage of each team member’s handicap — and if you skip this step your league is subtly unfair all season in a way people feel but can’t name. The full table is in golf handicap allowances; it is the single highest-value formula in the whole file.
Points, one formula, decided before week 1. Whatever you choose — by finish, a table, net score against par — write it once in the Standings sheet and never override it. The most common league failure is a points rule that got adjusted in July.
Best-N. =SUMPRODUCT(LARGE(<that player's points>, ROW(INDIRECT("1:"&MIN(N, COUNT(range))))))
is the ugly, load-bearing formula: count each player’s best 10 of 14 so a missed week doesn’t sink
a season. If you want the reasoning rather than the syntax, it’s in
how to run a weekly golf league.
A tiebreak that resolves. “Most wins, then countback on the last counting round” beats “we’ll figure it out” — because you will be figuring it out in front of the two people it’s between.
Where it breaks — the five, in the order they bite
1. Distribution. This is the big one, and it is not a formula problem. A spreadsheet is a file. To show the standings you export a PDF, or screenshot it, or share a link that asks for a Google account, and at that point most of your field stops looking. A league where nobody checks the table feels dead by mid-season even when it isn’t — the golf is identical and the league is worse. That is the failure that actually kills leagues, and no amount of formula work touches it.
2. Score entry on the night. Someone has to key eighteen numbers per player. In practice one person does it at home on Thursday from photos of the cards, which is a volunteer spending an hour a week and a single point of failure. Every league eventually has the week where that person is on holiday.
3. Handicaps that moved. Indexes update. A spreadsheet holds the number you typed in April. By August you have a column of stale indexes and somebody who has genuinely improved four shots is still getting them — which is also the mechanism people mean when they say somebody is sandbagging, except it’s usually the file, not the golfer.
4. Formats that aren’t stroke play. The moment you run a week of four-ball, a scramble, a
Stableford night or a match-play ladder, the Scores sheet’s shape is wrong. Most leagues respond by
adding a second sheet with different columns, and the standings formula now has an IF in it that
only one person understands.
5. The file has an owner. When they move club, change job, or just get tired of it, five years of league history leaves with them. Ask any club secretary what happened to the standings from 2019.
So which side of the line are you on?
A spreadsheet is genuinely the right answer if: one format, under about twenty players, everyone sees each other weekly anyway, and the person maintaining it enjoys it. That’s a real league and it does not need software.
You have outgrown it when any of these is true:
- People ask you where the standings are. That’s a distribution problem and it is terminal.
- You run more than one format, or the league feeds a season-long order of merit alongside a championship and a member-guest. See running an order of merit.
- Scores get disputed and there is no record of who entered what.
- You want the money handled — weekly skins, a season pot — without a second spreadsheet.
- It is one person’s hobby and that person wants a night off.
What Swilkin does about it
Every week is a round like any other round: one person per group taps scores in on their phone while they play, or a volunteer keys a paper card at the turn. The season table rolls up on its own — points your way, best-N-of-M for the weeks people miss, countback tiebreaks — and the standings are a link, so a member checks them from a text message with no account and no login. Course handicaps and allowances are computed from the tees actually played rather than a column you maintain.
And plainly, what it does not do: it is not a handicap authority and does not post scores to GHIN. It does the course-handicap math on the index you give it, which is exactly what your spreadsheet was doing — but it cannot be the place your index lives. If your league needs scores posted to a handicap authority, that requirement decides your software before any other feature does.
It is free for golfers, and the club tools are free today too; paid plans for clubs are planned, not live. Here is exactly what that means, and here is the league side of it.
The test worth running: take last season’s week 6 — the one with the weird format and two no-shows — and set it up. If it comes out right without a manual adjustment, you have your answer either way.
More for organizers: how to run a weekly golf league · shotgun, split tee or one tee · what to look for when an enterprise platform is too much.