Zubdazubdaزبدة

Concerts and events

A 30-seat concert with individual seat tickets

A concert is not a departure, but the structure is the same: capacity, bookings, ticket labels and an event project for cost and margin.

Business profile

Business
Event promoter or venue
Sells
Seats and tables
Operating model
Section capacity with assigned seats
BookingsTicketsProjectsPOSExpensesSales analyticsBusiness agentBI
Zubda bookings agenda showing capacity, party size and balance

The challenge

  • Seat allocation on paper
  • No check-in record
  • Event costs separated from ticket revenue
  • No view of sold versus available seats

How it is set up

  1. Create the section resource

    Concert Section A, capacity 30. Use one resource per section or table layout.

  2. Create the event project

    Artist, venue, sound, security, marketing and staff costs. Ticket revenue is the project revenue.

  3. Issue tickets

    Enter seat labels such as A12, A13. The booking creates one ticket per seat with a unique code.

  4. Check in

    At the gate, open the booking tickets and mark each ticket checked in. A cancelled ticket cannot check in.

Daily routine

  • Sell seats against the section
  • Issue and check tickets
  • Track remaining capacity
  • Reconcile ticket revenue and event costs

Worked numbers

Seats

30

Ticket

A12

Price

KES 5,000

Deposit

KES 1,000

Sold

27

Remaining

3

Controls that matter

  • One ticket per seat
  • No duplicate seat labels
  • Checked-in tickets cannot be removed
  • Cancelled bookings release seats
  • The event project shows ticket revenue against tagged costs

Related guides

Cookie preferences banner is now visible.

We use cookies

Essential cookies keep Zubda working and can't be switched off. With your permission, we'd also like to use analytics cookies to understand how the site is used: we only turn these on if you say yes. See our Privacy Policy.