Skip to Content
FeaturesPoint Game

Point Game

A strategic team format where captains choose which scores count - the only format with variable score selection per hole.

What is Point Game?

The Point Game (also known as the “40-Point Game” or “40 Score”) is a team-based golf competition where a group must use exactly a set number of individual scores across 18 holes. The captain decides after each hole which players’ NET scores to count toward the team total.

Default Configuration: 4 players x 10 points = 40 total scores required

This format is popular on buddy trips and in casual tournaments because it:

  • Adds strategic decision-making beyond shot execution
  • Keeps all players engaged even after a bad hole
  • Creates dramatic finish-line scenarios on holes 17-18
  • Rewards consistent team play and smart captaincy

Key Differentiator

Point Game is a format that competitors like Golf Genius do not support. It requires real-time score selection with mathematical constraint enforcement - a capability unique to our platform.

Traditional formats like Best Ball automatically select the best score. Point Game puts that decision in the captain’s hands with strategic implications.

How It Differs from Other Formats

FormatScores Per HoleWho DecidesWhen Decided
Point GameVariable (0-4)Captain choosesAfter each hole
Best BallFixed (1)System selects bestAutomatic
ScrambleFixed (1)Team plays same ballPer shot
StablefordAll countN/AAutomatic
1-2-3 Best BallFixed by parSystem selectsAutomatic

Key Differentiator: Point Game is the only format where the number of scores per hole is variable and strategically chosen by the team captain.

Key Features

Constraint Enforcement

The system mathematically prevents teams from reaching invalid states:

Minimum Required = Max(0, ScoresRemaining - (HolesRemaining × TeamSize)) Maximum Allowed = Min(TeamSize, ScoresRemaining)

This ensures teams always hit exactly 40 scores by hole 18.

Real-Time Pace Tracking

Visual indicators show whether teams are on track:

StatusColorMeaning
On PaceGreenUsing scores at sustainable rate
Need MoreBlueShould use more scores soon
CautionYellowGetting tight on remaining selections
DangerRedMust select multiple scores immediately

Pacing Thresholds:

  • After hole 6: Target 12-15 scores used
  • After hole 9: Target 20-24 scores used
  • After hole 12: Target 26-30 scores used
  • After hole 15: Target 32-36 scores used

Live Leaderboard

Teams compete on aggregate NET score:

  • Real-time position updates as selections are confirmed
  • Team total displayed as NET to par (e.g., “Team -4”)
  • Progress tracking shows scores used per team
  • Movement indicators when positions change

Mobile-First Scoring

Designed for on-course use:

  • Large touch targets (44px minimum) for easy selection
  • Clear visual feedback on selected scores
  • Confirmation step prevents accidental submissions
  • Works offline with sync when reconnected

Configuration Options

Points per Player

Default: 10 points per player

Configurable for different experiences:

  • 40-Point Game (standard): 4 players x 10 = 40 total
  • 50-Point Game (more forgiving): 4 players x 12.5 = 50 total
  • 30-Point Game (threesome): 3 players x 10 = 30 total

Team Size Support

Team SizeDefault PointsAverage Per Hole
4 (Foursome)402.22
3 (Threesome)301.67
2 (Twosome)201.11

Handicap Allowance

Default: 100% of course handicap

How NET scoring works:

  1. Each player’s course handicap is calculated from their index and course rating
  2. Handicap strokes are allocated by hole stroke index (1 = hardest)
  3. Players receive strokes on holes where stroke index is less than or equal to their handicap
  4. NET score = Gross score - Handicap strokes received

Example:

  • Player A: 12 handicap, receives strokes on holes with stroke index 1-12
  • On Par 4 (Stroke Index 8): Gross 5, NET 4
  • This NET score is what counts if selected

Scoring Basis

All selections are based on NET to par:

  • Birdie (-1) is better than Par (E)
  • Par (E) is better than Bogey (+1)
  • Team total = Sum of all selected NET scores to par

Competition Structure

Team Formation

Point Game typically runs as:

  • One foursome = one team
  • Teams compete against other foursomes
  • All players from the same playing group

Scoring Flow

  1. Enter Gross Scores: All players submit scores for the hole
  2. View NET Scores: System calculates handicap-adjusted scores
  3. Select Scores: Captain chooses which NET scores count
  4. Confirm Selection: Lock choices and proceed to next hole
  5. Repeat: Continue until hole 18

Winning

  • Lowest aggregate NET score wins
  • Ties broken by: back 9, back 6, back 3, then card-off
  • Complete rounds only (must use exactly target points)

Use Cases

Buddy Trips

Perfect for multi-day trips:

  • Different teams each day
  • Overall trip standings combining daily results
  • Creates memorable strategic moments

Casual Tournaments

Add excitement to corporate outings:

  • Engaging format keeps all skill levels interested
  • Captains feel ownership of team performance
  • More discussion and camaraderie than individual play

Ryder Cup Style Events

Combine with other formats:

  • Point Game for one session
  • Best Ball for another
  • Aggregate team points across sessions

Strategic Depth

Captain’s Dilemma

Every hole presents choices:

  • Use a par now or save capacity for later?
  • Bank a birdie even if pace is ahead?
  • Skip a disaster hole entirely?

Team Communication

Good teams discuss:

  • Current pace vs. target
  • Who’s playing well (favor their scores)
  • Upcoming hole difficulty (save selections for easier holes)

End-Game Drama

Holes 16-18 often force decisions:

  • “We need exactly 3 scores from the last 2 holes”
  • Creates pressure and excitement
  • Strategic errors punished, smart play rewarded

Technical Implementation

Data Model

Point Game selections are stored per hole:

  • Team ID + Round ID + Hole Number
  • Selected player IDs (array)
  • Points used (count)
  • Selection timestamp

Real-Time Sync

  • Selections sync via Supabase realtime
  • Multiple devices see updates instantly
  • Conflict resolution: server state wins
  • Offline support with local cache

Validation

Server-side validation ensures:

  • Selections within min/max constraints
  • No retroactive changes to locked holes
  • Correct player IDs for the team
  • Proper handicap calculations