TeeLedger
Verified TeeLedger workflow

Understand TeeLedger product boundaries

See which capabilities TeeLedger provides, handles differently, or deliberately leaves to official personal-handicap and standalone tournament products.

RolesOwner · Admin · Player
Expected resultThe league can make a migration decision without mistaking a separate product, demo, or integration dependency for completed TeeLedger behavior.
Before you start

Have these ready

  • A league workflow or migration requirement to evaluate
Guided workflow

Complete and verify each step

01

Start with the league workflow

Map the requirement to the relevant TeeLedger task guide, then confirm whether the workflow is included, intentionally separate, or requires an approved integration.

Verify

The decision points to a current TeeLedger workflow or a clearly documented product boundary.

Open this exact demo step
TeeLedger guided overview and weekly commissioner checklist
Current TeeLedger guided demo · safe sample data
02

Separate league and personal handicapping

Use TeeLedger for transparent league handicaps and retain an official WHS/GHIN service when the golfer needs an official personal index.

Verify

The league does not represent a TeeLedger value as an official external index.

Open this exact demo step
TeeLedger Rules workspace with handicap and competition settings
Current TeeLedger guided demo · safe sample data
03

Keep standalone tournaments separate

Treat standalone multi-round formats, specialized tournament handicaps and tiebreaks, and tournament collateral as a separately approved product track.

Verify

Tournament-only requirements are not represented as completed league features.

Open this exact demo step
TeeLedger Playoffs workspace with audited seeds and bracket status
Current TeeLedger guided demo · safe sample data