Home / Resorts
Resort management software for golf and leisure
The stay is the record. Golf, spa, food and beverage and the room folio settle together.
The checkout reconstruction
Nobody owns the whole stay
The property system knows the room. The tee sheet knows the round. The spa knows neither. The folio is assembled by hand at checkout, and the resident rate is applied from memory.
A resort sells one experience and records it in five places. Each system is confident about its own line and silent about the rest, so the guest's total exists only in the moment somebody types it out at the desk.
Property system
Knows the room, the rate and the nights. Does not know the guest played twice and ate in the brasserie on both evenings.
Tee sheet
Knows a four-ball went out at 10:20. Does not know two of them are resident and should not have paid the visitor rate.
Spa diary
Knows a treatment was taken at 15:00. Does not know the guest is in room 214, so the charge waits for someone to notice.
Restaurant POS
Knows a table spent an amount. Does not know whether to charge the room, and asks the guest to decide.
Retail POS
Knows a jumper was sold in the golf shop. Does not know it can be posted to a folio at all.
The folio
Knows only what has been typed into it, by the person on the desk, at the moment the guest is standing there.
The record is the stay
Everything between arrival and departure reaches one folio
The stay is the account. A round, a treatment, a dinner and a purchase are entries on it, posted at the moment they happen and priced by who the guest is, so the folio is correct continuously rather than at the end.
Charges post as they happen, from every outlet, without a nightly transfer
Rates applied by guest status rather than by which system took the booking
The guest can see the running folio rather than discovering it at the desk
Departure is a settlement, not a reconstruction of four days
Golf and leisure on one grid
Tee times, spa treatments, courts, tables and bays are the same kind of inventory with different durations. Running them in separate systems means a guest who wants a round, a treatment and a table has three conversations, and the resort has three chances to double-book its own day.
In Fescue they share one grid. The guest books in the app, the desk books on the same view, and both are writing to the same inventory, so an early tee time and an afternoon treatment can be sold as one plan rather than as three hopeful bookings.
- Tee times, treatments, courts and tables against shared inventory
- Booked by the guest in the app or by the desk on the same grid
- Duration, turnaround and resource rules per activity
- No system holds inventory the others cannot see
Resident and visitor pricing
The resident rate is the commercial center of a golf resort and, in most operations, the least reliably applied part of it. When the tee sheet does not know who is staying, the rate is applied by the person on the desk from memory, and the difference falls out of margin quietly.
Fescue holds one rate card and decides the rate from the guest. A resident is a resident whether they book online at midnight or at the desk after breakfast, and packages, twilight rates and stay-and-play terms are conditions on the same card rather than parallel price lists.
- One rate card covering resident, member, visitor and package rates
- The rate follows the guest, not the booking channel
- Stay-and-play packages priced as a whole, posted as parts
- No manual adjustments at checkout, so no discretionary discounting
Groups and buy-outs
Group business is where resorts make their year and where spreadsheets are still doing most of the work. Held rooms, held tee times, a rooming list, pairings, a deposit schedule and a final invoice usually live in one workbook owned by one person, and the systems find out late.
In Fescue a group is a record that holds real inventory. Rooms and tee times are held together, the rooming list and pairings sit on the record, deposits post to it, and the whole thing settles once at the end rather than as a set of individual bills to be matched afterwards.
- Accommodation and tee time inventory held on one group record
- Rooming list and tee pairings attached to the group, not to a workbook
- Deposit schedules and staged payments posted as they are taken
- One settlement at the end, itemised by day and by outlet
The folio at checkout
Checkout is where the cost of separate systems is finally paid, in front of the guest. Somebody collects the round, the treatment, the dinner and the golf shop purchase, applies the rate they believe was agreed, and hopes nothing arrives after departure.
Because every outlet posts to the folio as it happens, there is nothing to assemble. The desk confirms a total the guest has already been able to see, and late charges are the exception rather than the working assumption.
- Every outlet posts to the folio in real time
- The guest sees the running total during the stay
- Departure settles in one movement, by card or on account
- Revenue reports by outlet, by night and by segment from the same ledger
What Fescue replaces at a resort
The list below is what we typically remove or absorb during migration. Where a property system is being retained, we integrate with it instead and the rest of the list still applies.
| What it replaces | What it becomes in Fescue |
|---|---|
| Property management system | Rooms as inventory on the stay, or an integration where you keep yours |
| Tee sheet | Course inventory posting to the folio at the resident rate |
| Spa diary | Treatment inventory on the same grid, charged to the stay |
| Restaurant POS | A window onto the same ledger, posting to the folio |
| Retail POS | Golf shop and retail on the stay rather than on a separate sale |
| Groups spreadsheet | A group record holding rooms, tee times, deposits and pairings |
| Manual folio reconciliation | Not required, because nothing was ever separate |
Questions
Asked by committees.
Does Fescue replace our property management system or sit alongside it?
Either. Resorts that want one system run rooms in Fescue, and everything a guest does posts to the folio directly. Resorts with a property system they intend to keep run Fescue for golf, spa, food and beverage and retail, and we post charges to the existing folio so the guest still settles once at checkout. We confirm which of the two applies during the specification meeting rather than assuming.
How are resident and day-guest rates handled?
One rate card carries every rate, and the rate applied is decided by who the guest is rather than by which system took the booking. A resident booking a tee time in the app, at the desk or over the telephone pays the resident rate in all three cases, and there is no manual adjustment at checkout.
Can groups hold rooms and tee times together?
Yes. A group holds inventory across accommodation, the course and the spa on a single record, with rooming and tee pairings attached to it. Deposits and staged payments post to that record, and the group settles once at the end rather than as a series of separate bills that have to be matched afterwards.
What happens at checkout?
Nothing is assembled, because everything posted as it happened. The folio already holds the round, the treatment, the dinner and the retail purchase at the correct rate, so checkout is a settlement rather than a reconstruction of the stay.
See it at your venue
Request a demonstration
We will come to your club, with a blank notepad, and show you your own Saturday in Fescue.
HELLO@FESCUE.CLUB
Other venue types
The same platform, arranged around the thing your venue actually counts. Pricing is the same in every case, and is set out on the pricing page.