Season points races

A points race ranks players across a whole season by how they finish in your sanctioned events — the winner of each event earns the most, with descending points down the standings, accumulated over the season. Bigger events can be worth more, and you keep only each player's best results. It's the kind of season-long chase a sanctioning organization runs alongside its skill leaderboards.

Points races belong to an organization season, so you'll first want a sanctioning organization with at least one season. See Sanctioning organizations and Seasons.

1. Define your event tiers

Points are weighted by event tier — a Local event can be worth less than a Regional or a Major. Define your tiers once under Organization → Manage → Event tiers. Add a tier per sport (for example Local, Regional, Major), set the sort order, and archive any you stop using.

2. Configure points on the season

Open Organization → Manage → Seasons, find the season, and click Points on its row. Choose a Points template:

  • Flat — one points table per event tier, the same for every skill division.
  • Division-weighted — the table varies by tier and skill division, so a more competitive division can earn more for the same place. (Uses your divisions.)

Then, for each tier, set:

  • Best-N finishes that count — only a player's top N results in that tier count toward the season (leave blank to count them all).
  • Participation points (optional) — a flat amount for entering, which is never capped by best-N. Turn this on with the Award flat participation points checkbox.

And season-wide:

  • Membership bonus (optional) — a one-time amount added to anyone with at least one counted result.
  • Minimum entrants to count (optional) — events smaller than this don't award points.

Finally, fill in the points table for each tier (or each tier × division in weighted mode). Use Load a starter table to drop in an editable template, then adjust the value for each finishing band. Click Save points config. A Points: Flat (or Division-weighted) badge appears on the season row once it's set.

Note

Points are paid by finishing band: 1st, 2nd, 3rd, 4th, then 5th–6th, 7th–8th, 9th–12th, and so on. Everyone who lands in the same band earns the same value — there's no tiebreak within a band. The bands line up with how a bracket eliminates players round by round.

3. Tag events with a tier

When you create or edit a sanctioned event, pick its Event tier (next to the "Sanctioned by" picker). An event only earns season points if it's sanctioned by the organization, attached to that season, and tagged with a tier.

For a bundle (divisions or multi-event), the tier applies to the whole bundle. Edit it on the bundle itself — Edit bundle → Sanctioning — and saving applies the new tier to every event inside it. You don't tag the divisions one by one.

Once an event is tagged, its tier is shown wherever the event appears: on the 🏅 sanction line on the event page, and on the event's card in any list.

4. Points are earned on completion

When you Complete a sanctioned, tagged event, Skoryd reads its final standings and awards each finisher the points for their band — automatically, from your own brackets, with no separate data entry. In doubles, both partners earn the place's points.

On the completed event you'll see a Season points card listing each finisher and what they earned. As the organizer you can:

  • Recompute — rebuild the points from the current standings and config (handy after you adjust the config or fix a score).
  • Edit place — pin a finisher to a corrected placement (for example when a consolation match was actually played); their points re-derive from that place. Reset returns them to the bracket result.

5. Where players see the standings

The season points board lives on the season's standings page as a Points tab. The public path is Organization → Leaderboard → Season points standings, then pick the season — or organizers can open it from Manage → Seasons → View standings.

The board ranks every player by total season points. Click Details on a row to see that player's per-event breakdown — which results counted, which were dropped by the best-N cap or fell below the minimum-entrants threshold, and how many more events they can play before their lowest score starts dropping.

Note

The best-N cap, the minimum-entrants threshold, and the membership bonus are applied when the board is read, so you can tune the configuration anytime and the standings update without re-running every event.