A Season ties several tournaments together into one long-run points race. Golfers earn points based on where they finish in each event, and those points accumulate into standings kept separately for each season flight.
Seasons are entirely optional — if you only run standalone tournaments you never need to open this area. Posting season points never changes a tournament; seasons only read finished tournament results.
Once created, the season opens on its Overview tab with a horizontal tab bar: Overview, Schedule, Golfers, Flights, Points, Standings, Ledger, Activity, Reports, Settings. A Help button on every screen opens context-sensitive guidance for that tab.
On the Schedule tab, build the season out of your tournaments in play order.
| Action | Description |
|---|---|
| Add tournament | Pick one of your tournaments to add it as an event. |
| Multiplier | Weight an event (e.g. 2× for a major); base points are multiplied by this before posting. |
| Up / down arrows | Reorder events. Locked once an event is posted. |
| Event menu → Mark ready | Required before points can be previewed or posted — tournaments have no automatic “finished” flag. |
| Event menu → Preview & post | Compute and commit points for that event. |
| Event menu → Reverse points | Undo a posted event. Asks for a reason, logged to Activity. |
Only individual-scoring formats are eligible: Stroke Play, Stableford, Modified Stableford, and Best Ball. Twosome, Foursome, Match Play, Skins, Wolf, and Nassau formats contribute nothing to season points.
For each scheduled event the season reads that tournament’s individual cumulative standings — the same net score or Stableford totals shown on the tournament leaderboard, summed across every day — and ranks golfers within each tournament flight, not across the whole field.
The Overview tab shows the current top three in each flight.
The Settings tab holds:
A brand-new season shows in-screen setup checklists on the empty Standings, Golfers, and other tabs, pointing to the task that will populate them, so you never land on an unexplained blank tab.
The dashboard sidebar shows an always-visible, auto-checking progress rail on every season page. Every step verifies itself from your data — there are no manual checkboxes and no sequential locking. It has three collapsible sections:
| Section | Covers |
|---|---|
| Season setup | Create flights, enroll golfers, assign golfers to flights, set the points table, add events. |
| Current event | The pipeline for the first non-posted event — tournament linked, format eligible, scores entered, flights mapped, golfers matched, marked ready, preview clean, points posted. |
| Close out | All events played and posted, no events stuck at “ready”, no unbroken tie for 1st, and Finalize season. |
The rail only reflects status — it does not gate the Finalize button. Its Finalize season step links straight to Settings with the finalize dialog open.
When a season flight has a tie for 1st on counted points, Tourlyx resolves it objectively:
counted points → most wins → most top-3s → event-points countback (newest event first) → co-champions
The Finalize Season dialog suggests the winner and shows the reason line (e.g. “won on more wins (2 vs 1)”). You can override the suggested winner; the reason then carries “· adjusted by director”. A genuine dead heat is recorded as co-champions.
The public season leaderboard shows the tiebreak reason under a flight’s champion — “Tiebreak: won on more wins (2 vs 1)”, “· adjusted by director” for an override, or “Co-champions — identical record” for a dead heat.
When a golfer played a linked event off a handicap index that differs from their season handicap of record by 2 or more strokes, the preview flags it as a warning. This is the sandbagging signal. It is informational only — it does not block posting or change scoring. Gross-basis seasons are skipped entirely.
Finalizing a season writes a frozen standings snapshot, including each member’s event-by-event breakdown, so the final result never shifts if underlying data changes later. Finalized seasons read this snapshot everywhere. Un-finalize from Settings to make changes, then re-finalize.
When a season write action fails, instead of a cryptic red error, a guided dialog explains the problem in plain language and offers a one-click fix with chained auto-retry. Its flagship use is the “Resolve N issues →” walk-through in the Preview & post dialog, which steps through each blocking error (unmapped flights, unmatched golfers, and so on).