Everywhere
Clubhouse screens and the modules you turn on.
Everywhere
The club, present without intruding.
Leaderboards on the clubhouse screens, the club's own website, the events diary, a live salesroom for the auction. All drawn from the same data the general manager is looking at.
Modules
Turned on, one at a time.
The club's own website, a live salesroom, who is on site, the ballot and the events diary. Each one is a module the club turns on, reading and writing the records the rest of the system already holds.
- The club's website. Designed, built and maintained in-house, not a template. Visitor bookings, society enquiries and member login share one spine with the club system.
- The salesroom. A live salesroom with proxy bidding, released for one club's event. Bidders are registered by the club, never by themselves.
- Presence. Who is on site now, from arrivals at the gate through to the first tee. ClubOS reads the gate; it cannot open one.
- The ballot. A prototype Studio only: a rule written as a sentence, a painted calendar, and a run-through. No engine, no tables, no ClubOS screen.
- Events. Function sheets: rooms, run sheet, catering, billing and who is coming, for every event the club runs.
- In design at the App Library: Agronomy, Compliance, Access control.
Answers to thirty questions clubs ask before they change system

