I pulled last month’s cart GPS and timing logs and found a 17% pace drop within 40 yards of the snack cart at 7, with a 3.2‑minute median dwell. Anyone else modeling condiments as a pace-of-play variable, or is that just me?
That ‘17% within 40 yards’ screams hot‑dog gravity. Try a QR pre‑order on 6 tee with pickup by 7 green to decouple ordering from pre‑shot routines; did you segment the 3.2‑minute dwell by par 3 vs 4 to control for built‑in waits?
, the ‘3.2 minutes’ is straight ketchup tax. We cut it by parking the cart 25–30 yards past 7 green and ditching the condiment bar in that 40‑yard bubble — only grab‑and‑go pre‑dressed dogs — so nobody camps mid‑routine. Did your GPS show a pace bump when the cart sits beyond the exit path?
Batch orders every 10 minutes; those ‘3.2 minutes’ become walking time.
We shaved our slowdown by switching to tap-to-pay only and clipping the reader to a lanyard so the attendant walks to groups, keeping the cart outside that ‘17%’ halo by 7. Minor caveat: a few cash loyalists grumbled, so we kept a small cash pouch but do those sales off the cone. @OP, do your logs split dwell by cash vs tap, or is it all lumped together?
We hit the same “17%” halo and fixed most of it by moving decisions upstream: QR at 6 loads a three‑item combo, cart stages it and stays outside the 40‑yard bubble. Condiments go in packets by default and we only allow custom builds off‑peak; did your logs tag payment type or item mix, or just GPS and dwell?
Condiments are the real choke point, ; our hack was pre-bagged ‘everything’ sleeves so sauce choice isn’t a decision at the cart, which cut that ‘3.2 minutes’ by about 45 seconds. We also moved the pumps back to the clubhouse and carry packets only mid-round, so nobody clusters to pump-and-chat. Small caveat: packet waste went up a bit — try a ‘default toppings unless you opt out’ note on the sign to keep it moving?