StakeMarker · Tournaments
Tournament help

Run a tournament

Create the event, add groups, manage the tee sheet, follow live standings, and publish results to spectators.

Access: tournament creation and management require a signed-in Ultra account. If the page says Ultra plan required, upgrade from Manage Plan in the app and return here.

1. Create the event

  1. Open the app hamburger menu, choose Tournaments, and tap + New.
  2. Enter the tournament Name and Date.
  3. Choose a course from Search StakeMarkerDB, or enter the course name and each hole's Par / Stroke Index manually. Optionally enter Slope / Rating for the Course Handicap helper.
  4. Choose the Handicap treatment: Gross, Play Off Low, or Raw Handicap. Then select any combination of event formats: Stroke Play, Stableford, and/or Skins. Each selected game becomes its own field board; Skins exposes the normal per-hole / whole-round buy-in options in Game setup. To add another built-in format later, open Edit Tournament and select it in this same section.
  5. Tap Save Tournament.

2. Add groups and set the tee sheet

Open the tournament and choose Groups & Tee Sheet. Tap + Add Group, enter a group name, choose 1–8 players, enter the roster, and tap Create Group Round. Each group is a linked StakeMarker round, so players score in the familiar scorecard while the tournament page combines the results.

3. Use the tournament tabs

4. Share updates and manage the event

5. Build tournament games

Open the tournament's Game settings tab and choose Manage game plan to edit its pinned game plan. Every competition has a complete set of rules, so the same scoring engine handles field, group, and scheduled-match competitions.

Manage the saved plan separately from authoring: the plan panel shows every selected game and lets an admin add or remove built-in boards, including Stroke Play when another board remains. Use the separate custom-game builder to describe a new game or revise a saved board in plain English. The authoring flow can ask a clarification question when the scoring scope, participants, setup inputs, or presentation is ambiguous. Review the generated rules before saving them; the saved plan is versioned and compiled before it can run.

For team and match competitions, the bindings editor supplies the data the rules explicitly request:

  1. Assign roster players to the teams required by the game.
  2. For scheduled matches, choose the participants without relying on implicit sides or bracket numbers.
  3. Enter any explicit game setup details, such as a bracket value, team choice, or role selection.

You do not need to write a formula or JSON. If a rule cannot be represented by the current rules engine, the authoring flow should say what capability is missing instead of silently approximating the game.

Important rules and troubleshooting