How tee-sheet syncing works

GolfPass checks your tee sheet on a short cycle rather than the instant a booking changes — what that means for timing, and why one bad booking never blocks the rest.

Updated 7/27/2026

GolfPass stays in step with your tee sheet by checking it regularly — every few minutes — rather than the exact moment a booking is made or changed. Understanding this one thing explains the small, normal delays you'll occasionally notice, and saves you worrying that something's broken when it isn't.

The cycle

On each cycle, GolfPass:

    1. Reads the current bookings from your connected provider (ChronoGolf or Lightspeed Golf).
    2. Issues a pass (and sends the email) for any new booking that doesn't have one yet.
    3. Updates the pass for any booking whose details changed since the last check.

Because this runs on a short, repeating cycle, a brand-new booking usually becomes a pass within a few minutes — not the same second it's made.

Why changes aren't instant

When a tee time moves, the golfer's pass updates on the next cycle after that change appears in your tee sheet. So a reschedule might take a few minutes to reach the phone. This is by design and completely normal — it's the same way airline boarding passes refresh.

If you change a booking and immediately check the golfer's pass, you may still see the old details for a moment. Give it a few minutes and look again before assuming anything is wrong.

What to expect, in numbers

  • New booking → pass + email: usually a few minutes.
  • Booking change → pass update on the phone: usually a few minutes after the change saves in your tee sheet.
  • You connect for the first time: existing upcoming bookings are picked up over the following cycles, so passes start flowing shortly after connecting.

One bad booking won't stop the rest

If a single booking has a problem — a malformed field, a missing detail — GolfPass notes it and keeps going. The rest of your bookings still sync and still produce passes normally. A problem with one reservation never blocks the others, so you won't lose a whole morning's passes over one odd row.

When something genuinely seems stuck

If a change still hasn't appeared after a reasonable wait, it's worth a quick check:

  • Did the change actually save in your tee sheet?
  • Is the integration healthy, or showing an error on the Integrations page?

The full walkthrough is in Why isn't a pass updating?.

More in Integrations