TE · Club OS module

Sell and run club events without a side ticketing spreadsheet.

Tickets & Events is how Club OS runs presentation nights, trivia, finals functions and gate sales: events, ticket types, checkout, attendees, check-in and fulfilment. These are event tickets with buyers and seats — not canteen order numbers on the trading board.

The job

What Tickets & Events is for.

Give event leads, treasurers and door volunteers one place to set the event, sell tickets, manage comps and waitlists, check people in, and leave a record finance can reconcile.

Who uses it

Built around real club roles.

Event coordinator

Builds the event, ticket types and capacity without a separate ticketing login.

Treasurer

Sees paid, unpaid, comps and refunds against the same event the door is running.

Door / check-in volunteer

Works from a live attendee list instead of a printed PDF that is already wrong.

Secretary

Knows who bought, who transferred and who is still on the waitlist.

Social / comms volunteer

Points families at the right event link instead of a Facebook comment thread.

Inside the module

The functionality committees actually run.

Events, ticket types and checkout

Set what the club is selling before the first sale hits the inbox.

01

Events the club can reopen

Create a presentation night, trivia, finals function or gate sale with dates, venue and capacity. Next year starts from last year’s shape, not a blank form.

02

Ticket types with rules

Adult, junior, member, table and early-bird each have a price, limit and eligibility. The club is not inventing a new spreadsheet column for every category.

03

Checkout tied to Payments

Buyers pay through the same Square and Stripe layer as the rest of Club OS. Paid, unpaid and refunded sit on the order — not only in a processor dashboard.

04

PDFs, invoices and receipts

Issue ticket PDFs and invoices families can keep. Treasurers get a cleaner trail than screenshots in Messenger.

05

Eligibility that matches membership

Member-only or season-linked tickets can check People & Teams instead of honouring a first name someone typed on a form.

Attendees, door and fulfilment

The night should run from a live list — comps, transfers and waitlists included.

01

Attendee list as the operating view

See who bought, who is checked in, who is complimentary and who still owes. Door and finance work from the same record.

02

Check-in that survives the queue

Mark arrivals at the door without rebuilding the list on a phone notes app. Status stays visible to the coordinator.

03

Comps and guest tickets

Issue complimentary tickets with a reason and an owner. Comps are club decisions, not silent gaps in the cash count.

04

Transfers without a group-chat deal

Move a ticket to another person when rules allow, and keep the trail. The door should not argue about whose name is on a screenshot.

05

Waitlist when capacity fills

Take a waitlist, promote when seats free up, and stop the “any tickets left?” inbox after sell-out.

06

Not a canteen ticket number

Event tickets are for buyers and attendees. Canteen Management keeps its own order numbers for the trading board — two different jobs, two different queues.

How it runs

A path volunteers can repeat.

01 · Create the event Set date, venue from Facilities, capacity and who it is for.
02 · Configure ticket types Price, limits, eligibility, comps and waitlist rules before sales open.
03 · Sell and collect Checkout through Payments; invoices and PDFs go to buyers.
04 · Run the door Check attendees in, honour transfers, and close with a list finance can trust.
What it replaces

The hidden systems clubs already have.

  • Eventbrite plus a bank rec
  • Printed guest lists that go stale
  • Comps nobody recorded
  • Transfer deals in Facebook comments
  • Waitlists in a secretary’s inbox

See Tickets & Events in a walkthrough.

We will show the working screens, the volunteer path, and how this module connects to the rest of Club OS for your club.

Ready when your committee is

Give the club a system that outlasts the season.

Start with the workflows causing the most pressure, then grow into a full Club Operating System.