Skip to content
Tee sheet & booking

One tee sheet, every way a tee time gets booked

A fast visual sheet built for the Saturday-morning rush, with drag-to-move groups and a live WebSocket layer so every screen in the building agrees. Members book on your own domain in your own colours. Lottery, waitlist, recurring times, guest policies, and demand-based pricing are built in. Whether a time came from the portal, the pro shop, the phone, a lottery draw, or a society block, it lands in the same data model and posts to the same ledger.

The tee sheet is the heart of every golf operation, and it is the system that breaks first when a club outgrows its software. Most platforms give you one of two things: a static booking widget staff cannot manipulate, or a desktop grid that does not survive a Saturday morning. Links Meridian was built for both on the same engine, because they are the same sheet seen from two sides.

The thing that matters underneath is that there is only one booking. A member booking in the portal, a walk-up at the pro shop counter, a phone reservation typed in by the secretary, a lottery allocation, a society block, a competition field: all of them create the same row, enforce the same rules, and post to the same ledger. Staff see every change the moment it happens because the sheet runs over a WebSocket layer rather than polling. Slot identity is the course, the date, the time, and the starting hole, which is what makes a shotgun or a two-tee start a real pattern instead of a workaround.

Access is where members judge a club, so the rules are properly configurable. Who may book, how far ahead, how many times, with how many guests, and at what price, all keyed to membership category. Peak Saturday times can go to a lottery with priority you define. The waitlist offers a cancelled slot automatically instead of waiting for someone to notice. Members can hold a standing time each week, or ask to be alerted the moment a preferred time frees up.

The awkward parts of the day are handled, not improvised. A frost delay pushes the whole sheet forward and notifies the field. Maintenance windows and course conditions publish to staff and members together. A cancelled round becomes a rain check that carries its value properly. No-shows are tracked against your cancellation policy, not remembered. And because the sheet sits on the same data as the till, the accounts, and the member record, a green fee taken at 7am is in the day's revenue before the first group reaches the turn.

Two surfaces

One sheet, seen from both sides

Your staff get an operational tool. Your members get a booking experience that keeps them inside your brand.

For your staff

The operational sheet

Built for the counter on a busy morning, not for a demo. Everything is one drag or one click from where you already are.

  • Drag to move a group, swap two groups, or change a time, with the whole building updating live over WebSocket
  • Sequential, shotgun, crossover, and two-tee starts, because slot identity includes the starting hole
  • Book for a member, a guest, a walk-up, or a society block from the same sheet
  • Frost delay that pushes the sheet forward and notifies the field
  • Blackout dates, maintenance windows, and course conditions published to staff and members together
  • Starter sheet with pace-of-play, and a self-service check-in kiosk
  • Rain checks, no-show tracking against your cancellation policy, and deposits
  • Every staff change written to a hash-chained audit log

For your members

The Digital Clubhouse

Booking lives in the same app as their account, their competitions, and the club feed, on your own domain.

  • Book in a few taps on mobile, in your branding, never redirected to a third-party site
  • See only what their category may book, at the price that applies to them
  • Enter the lottery for peak times, and get the result without chasing it
  • Join the waitlist and be offered a cancellation automatically
  • Hold a standing weekly time, or set an alert for a time they want
  • Bring guests under the club's own guest policy and pricing
  • Add a buggy, trolley, or club set at the point of booking
  • Subscribe the tee sheet to Apple, Google, or Outlook calendar, plus reminders at 24 and 2 hours
Why it matters

The outcome for your club

The Saturday rush stops being a scramble

Groups move with a drag. Every screen in the building updates in the same beat, so the starter, the counter, and the office are never working from three different versions of the morning.

Nobody rings up to book

Members book on your own domain, in your colours, on their phone. The calls that remain are the ones that actually need a person, which is the point.

Cancellations refill themselves

A slot given back is offered to the waitlist automatically. Peak times that would have gone empty at 6am on a Sunday get taken while your staff are still asleep.

The access rules stop being arguments

Advance windows, guest limits, and category restrictions are enforced by the system, so the answer to "can I book that?" is consistent whoever is on the counter.

Empty midweek tee times earn something

Pricing keys off real occupancy, not a hunch. The demand engine tracks fill rates and flags where a rate change or a flash sale would move the needle.

The money is already reconciled

A green fee, a buggy, and a guest fee taken at the counter post to the ledger as they happen. Nothing waits for an evening of keying in.

Every channel

Six ways a tee time gets booked, one row in the database

This is the part that decides whether a club's numbers reconcile at the end of the month.

Member portal
Who starts itThe member, on their phone
What is enforcedTheir category's advance window, booking limits, guest allowance, and member pricing
Public web booking
Who starts itA visitor, on your own domain
What is enforcedVisitor rate, advance limits, and any members-only window on that slot
Pro shop counter
Who starts itStaff, on the sheet or the till
What is enforcedStaff may override with permission, and the override is written to the audit log
Lottery draw
Who starts itThe member enters, the draw allocates
What is enforcedYour priority rules, then unsuccessful entries drop into the waitlist
Recurring time
Who starts itA standing weekly group
What is enforcedRegenerated ahead on schedule, and it still respects blackout dates
Society or competition block
Who starts itStaff, or the competition draw
What is enforcedSlots claimed atomically so no member can book over a held field

All six create the same booking row, hold capacity in the same transaction, and post through the same ledger. Multi-course clubs run this per course under a Portfolio and Property hierarchy, with its own configuration, pricing, and sheet for each.

The shape of the day

How a tee time moves through the day

  1. Rules first

    Set who may book what and when, per membership category: advance windows, booking limits, guest allowances, and members-only slots. Pricing rules layer on top by day, time, category, and occupancy.

  2. The sheet fills

    Bookings arrive from the portal, the public page, the counter, a lottery draw, a standing time, or a block. Capacity is held in the same transaction that creates the booking, so the sheet cannot oversell.

  3. It changes, constantly

    Groups move, players are added, someone cancels. Staff drag instead of retyping, and every screen in the building follows in the same beat.

  4. Gaps refill

    A cancellation is offered to the waitlist automatically. Members holding an alert on that time hear about it. Slow midweek stretches surface in the demand engine as a rate or flash-sale candidate.

  5. The morning of

    Reminders go out at 24 and 2 hours. Weather sits on the booking screen. A frost delay pushes the sheet and notifies the field. Players check in at the kiosk or the counter, and the starter works from a live sheet with pace-of-play.

  6. It settles itself

    Green fees, guest fees, and rentals post to the ledger as they are taken. No-shows are recorded against your policy. Cancelled rounds become rain checks that keep their value.

Head to head

The booking layer: a bolted-on widget vs one sheet

Feature
Widget on top of a legacy sheet
Links Meridian
Where members book
Redirected to the vendor's domain
Your domain, your branding, inside the member app
Staff view of an online booking
Appears after a sync, or a refresh
The same instant, over WebSocket, on every screen
Moving a group
Cancel and rebook
Drag it
Shotgun and two-tee starts
Worked around by blocking slots
A real pattern: slot identity includes the starting hole
Cancelled peak slot at 6am Sunday
Stays empty until someone notices
Offered to the waitlist automatically
Access rules
Enforced by whoever is on the counter
Enforced by the system, per membership category
Dynamic pricing
A separate rate card, edited by hand
Keyed to day, time, category, and live occupancy
Guest handling
A name typed into a notes field
A real guest record, deduplicated, under your guest policy
Where the money lands
Exported and reconciled later
Posted to the ledger as it is taken
The platform

What's included

Fast visual tee sheet with drag-to-move groups
Live WebSocket updates across every staff device
Online booking on your own domain, in your branding
Member, guest, visitor, and walk-up booking flows
Sequential, shotgun, crossover, and two-tee starts
Slot identity by course, date, time, and starting hole
Lottery draws with priority rules you define
Waitlist that offers cancellations automatically
Recurring tee times for standing weekly groups
Tee time alerts when a preferred time frees up
Group and society block bookings as a first-class shape
Competition fields held atomically so nobody books over them
Advance booking windows and booking limits per membership category
Members-only windows and restricted slots
Guest records with deduplication, guest policies, and guest pricing
Pricing rules by day, time, date range, membership category, and player type
Occupancy-based pricing with an advance-booking window
Demand engine with fill-rate snapshots and flash-sale suggestions
Promotions, packages, and group rates
Pre-payment, deposits, and card capture at booking
Rain checks that carry their value
No-show tracking against a configurable cancellation policy
Frost delay that shifts the sheet and notifies the field
Blackout dates, recurring or one-off
Maintenance windows and course conditions published to staff and members
Weather forecast on the booking screen
Reminders by email and SMS at 24 and 2 hours
Subscribable calendar feed plus per-booking .ics for Apple, Google, and Outlook
Starter sheet with pace-of-play, and a self-service check-in kiosk
Equipment rental (buggies, trolleys, club sets) attached at booking
Bookable amenities on the same engine: simulators, courts, coaching, function rooms
Multi-course under a Portfolio and Property hierarchy, each with its own sheet
Per-course configuration, pricing, and booking rules
Booking history and analytics by member, course, and slot
Hash-chained audit log across staff changes
Green fees, guest fees, and rentals posting to the ledger as taken
REST API and webhooks for integration
Responsive across desktop, tablet, and phone
Questions

Common questions

What is the best tee sheet software for a golf club?

The question worth asking is whether the booking layer and the sheet are the same system. Where members book through a widget bolted onto a legacy sheet, staff see bookings after a sync, moving a group means cancel-and-rebook, and the money reconciles later. Links Meridian runs one sheet: every channel creates the same booking row, holds capacity in the same transaction, and posts to the same ledger, with staff screens updating live instead of on a refresh.

Does it work for daily-fee courses, or only private members' clubs?

Both, and for hybrids. Pricing rules, advance windows, and restrictions are configured per membership category, so a members' club with a Saturday lottery, a pay-and-play course selling visitor rounds, and a resort doing all of it run the same engine with different rules. You can shift model without changing platform.

Can members book on our own domain?

Yes. The member portal and public booking page are hosted on your domain in your colours and fonts, as part of the Digital Clubhouse. Members are never redirected to a third-party site, which matters both for how the club looks and for who owns the traffic.

How does the tee time lottery work?

Members enter for peak times inside a window you set before the day. The draw runs automatically and allocates on the priority rules you configure, then notifies everyone of the result. Entries that miss out drop into the waitlist, so a later cancellation is offered to them without anyone at the club doing anything.

What happens to a cancelled peak tee time?

It is offered to the waitlist automatically, in your priority order, and any member holding a tee-time alert on that slot is notified. This is the single biggest source of recovered revenue on most sheets, because the cancellations that matter happen at times nobody is watching.

Can we run a shotgun start or a two-tee start?

Yes, as a real pattern rather than a workaround. A slot is identified by course, date, time, and starting hole, so a shotgun genuinely occupies all eighteen tees at once and a two-tee start is two sequences on the same sheet. Competition fields are held atomically, so a member cannot book over a draw while it is being built.

How does dynamic pricing decide the price?

Rules key off day of week, time of day, date range, membership category, player type, rate type, how far ahead the booking is, and live occupancy on the slot, with a cap you set so nothing runs away. Alongside that, the demand engine takes fill-rate snapshots and suggests where a rate change or a flash sale would earn something, so quiet midweek stretches surface while you can still sell them.

Do guests get handled properly, or typed into a notes field?

Guests are real records, deduplicated as they return, attached to the member who signed them in. Guest policies control how many a category may bring and how often, and guest pricing applies automatically. That means guest revenue and guest frequency are both reportable, not buried in free text.

What happens on a frost delay?

Push the start forward by an interval and the whole sheet shifts. The field is notified by email and SMS if you have that switched on. Maintenance windows, blackout dates, and course conditions work the same way: set them once and they publish to staff and members together.

Can members add the tee sheet to their calendar?

Yes. There is a subscribable calendar feed as well as a per-booking .ics download, so bookings appear in Apple Calendar, Google Calendar, or Outlook and stay current. Reminders also go out by email and SMS at 24 hours and 2 hours before the tee time.

Does it handle more than one course?

Yes. Courses sit under a Portfolio and Property hierarchy, each with its own sheet, configuration, pricing, and booking rules, while members and reporting stay unified across the estate. Billing for multi-course operations is per course rather than per member.

Can we keep our existing POS and accounting?

You can, though most clubs replace them, because the point of one sheet is undone if the money leaves it. POS and accounting are both included. If you want to keep QuickBooks or Xero as the general ledger, daily journals export to both. Stripe handles card processing, including Apple Pay and Google Pay.

How long does it take to go live?

The migration plan runs two to four weeks. Existing members, future bookings, tee-time history, and pricing rules are imported as part of onboarding, and the two platforms can run in parallel while you check the numbers agree. The 30-day trial does not begin until you go live, so migration does not eat your evaluation.

See the sheet running on your own tee times

Ask for a demo loaded with your courses, your categories, and your booking rules. Free 30-day trial when you are ready.