Verified TeeLedger workflow

Understand TeeLedger product boundaries

See which GolfSoftware capabilities TeeLedger replaces, handles differently, or deliberately leaves to personal-handicap and 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

Use the coverage index

Search every captured source topic and open the canonical TeeLedger task, documented alternative, or exclusion.

Verify

Every source record has exactly one reviewed disposition.

Open this exact demo step

TeeLedger guided overview and weekly commissioner checklist — Current TeeLedger guided demo · safe sample data

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

Keep Tournament Manager separate

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

Verify

No tournament-only source page is claimed as league parity.

Open this exact demo step

TeeLedger Playoffs workspace with audited seeds and bracket status — Current TeeLedger guided demo · safe sample data

Check feature coverage