Also called: allowlisted data source, report source
A safe, predefined set of league data available to the report builder.
An approved data source exposes only supported fields for the selected league and report type. It prevents a custom report from running arbitrary database queries or reaching another league's data.
CAlso called: scoring layer
One scoring rule that contributes points or awards to the final result.
A competition layer is one part of TeeLedger's scoring policy, such as match points, Stableford, quota, skins, attendance, or prizes. Layers run in order and their contributions are recorded in the result explanation.
Also called: league-specific player field, profile field, roster field
A league-defined profile item with a separate value saved for each golfer.
A custom player field lets a league record a persistent detail that is not part of TeeLedger's standard player profile. Creating the field defines its label, data type, and visibility; it does not fill in a value. A commissioner enters a separate value by opening each golfer from People. A member-visible field is also available to a signed-in member on their own linked profile, while a staff field is limited to staff views.
In TeeLedger: Custom player fields are shown in Personal details on the organizer-side player record. They are not published on the public player page and do not affect handicaps, scores, or standings. Use Custom statistic in Results for values that change by round or hole, such as putts.
EAlso called: event-opening snapshot, safe snapshot
A saved copy of the rules and participant values used for one event.
An event snapshot freezes the relevant rules, golfers, tees, and handicap values for that event. Later edits to league settings do not retroactively change what the event used.
FAlso called: official result, locked result
The official result created after score review is complete.
Finalization turns reviewed scorecards and competition rules into ranked official results. Finalized values are no longer edited as unfinished event data.
In TeeLedger: Corrections create a linked amendment and a new result version rather than silently changing the original.
GAlso called: ghost score, ghost player
A traceable stand-in score used when a scheduled golfer is absent.
A ghost golfer is not a real roster member. It is an event-only stand-in whose score is generated or entered under the league's policy so a match can be completed when a golfer is absent.
In TeeLedger: TeeLedger stores the source rounds, policy, generated holes, and credited recipient so the ghost result can be audited.
Also called: member role, account role, Commissioner, Assistant Commissioner, Captain, Scorer, Player
The permission level assigned to a person's TeeLedger account for one league.
A league role determines which work an account can perform. The Commissioner owns the workspace; an Assistant Commissioner handles day-to-day administration; a Captain manages only their own team; a Scorer handles league-wide scorekeeping; and a Player manages only their own participation and scores.
In TeeLedger: Roles are assigned per league, so the same person can have a different role in another TeeLedger workspace.
Also called: in-play publication, live results
A public, event-only view that updates while scoring is underway.
The live leaderboard publishes only the event information intended for in-play viewing. It remains separate from unfinished commissioner work and from the final official result version.
RAlso called: saved snapshot, report artifact
A saved report generated from the data available at one point in time.
A report snapshot preserves its selected columns, filters, visibility, and generated output. Later data changes do not silently rewrite that saved artifact.
Also called: visibility
Who is allowed to open a generated report.
Report visibility controls whether an artifact is limited to commissioners, available to signed-in league members, or intended for the public. It is separate from the report's file format.
Also called: audited correction, tracked correction
A documented correction that creates a replacement result version.
A result amendment records what changed and why while keeping the original result version available for review. It prevents corrections from erasing the event's history.
Also called: immutable result version, official result version
A numbered, read-only edition of an event's official results.
A result version preserves the exact ranked results and explanations that were official at a point in time. 'Immutable' means that version is not edited in place; a correction creates a replacement version linked to the original.