← App

How Markdowns Work

How Handicap "Markdowns" Work — and How They Map to Our Edge

This page separates documented mechanics (with primary sources) from our own analysis/inference. Don't conflate the two.


Part 1 — DOCUMENTED (sourced)

A. The USGA automatic "markdown": Exceptional Score Reduction

Built into the World Handicap System. When you post a round whose Score Differential is meaningfully better than your Handicap Index, the system reduces your index automatically:

Sources: - USGA, Exceptional Score Reduction - USGA Rules of Handicapping, Rule 5.9 — Submission of an Exceptional Score

Takeaway: a player who fires a round far under his number gets mechanically docked — GHIN-wide, any round, tournament rounds included. This is the formal "hit."

B. Cap Patrol — the club-level flagging layer

A third-party algorithm (separate from USGA) that clubs use to spot sandbaggers and vanity handicaps.

Sources: - Golf Digest, How to catch a sandbagger - cappatrol.com

Takeaway: Cap Patrol's flag is driven by the competition-vs-casual gap plus a fast-dropping or lagging index — the textbook sandbagger fingerprint.


Part 2 — OUR ANALYSIS / INFERENCE (not a published fact)

The following is our read of the data we pulled, not documented by USGA or Cap Patrol. Treat it as a working hypothesis, not a citation.


Bottom line

The mechanics of how golfers get marked down are real and sourced (USGA Exceptional Score Reduction; Cap Patrol's 5 criteria). The mapping of those mechanics onto our clutch column and the specific named players is our edge work — defensible, cross-validated across methods, but ours, not a published ranking.

To get a true "who's been marked down" list, the clean path is a fresh Cap Patrol token → sort our field by clutch/ability and cross-reference high tournament-finish history. That combination is the markdown signal. (Headless re-pull: src/calcutta/cappatrol.py.)

← Back to Calcutta Live