jma.events

Case study

Ticketing and guest management for an annual dinner

Our client holds a black-tie dinner once a year. We built their booking platform, which sells seats and tables, lets bookers add their guests, and handles check-in on the night.

Confidential client · Membership organisation · 2026

A booker’s My booking page with the event photo, Table 5 with 7 of 10 seats filled, a paid Table of 10 ticket and a personal check-in QR code

Every ticket buyer gets their own booking page. Demo data.

The brief

Sell seats and tables

Single tickets, tables of 10 or 12, member and non-member prices, and discount codes.

Let bookers add guests

The person who books a table invites their guests, and each guest answers their own RSVP.

Check everyone in

Every guest has their own QR code, which is scanned at the door to show them their table.

From booking to table

Each purchase creates a booking, which follows the guest from checkout through to their seat.

  1. 1

    Buy tickets

    Lead bookers buy seats or tables

  2. 2

    Pay

    Into the client’s own Stripe account

  3. 3

    Add guests

    From the booker’s own dashboard

  4. 4

    RSVP

    Each guest answers for themselves

  5. 5

    Get a QR code

    On their RSVP page and by email

  6. 6

    Arrive

    Scan in and find your table

Spotting overbooked tables early

Tables are labels rather than a fixed floor plan, so a large party can be split across two. The occupancy chart shows named guests and unnamed tickets for each table.

Table occupancy chart with named guests and unnamed tickets for tables 1 to 12

A clear record of every ticket

Seat counts are never typed in by hand. They come from each booking’s ticket lines, covering online payments, invoices, complimentary and unpaid tickets.

A booking’s ticket lines: two singles and a table of ten, both paid, adding up to 12 seats held

Payments go to the client’s own Stripe account

The client connected their existing account with a one-off link, so no passwords were shared. Ticket income goes directly to them.

Guest
Pays at checkout
Client’s Stripe
Receives the money
Platform
Confirms the seats

A check-in code for each guest

We first gave each booking a single code, then changed to one per guest so people arriving at different times can check in separately. Guests find their code on their RSVP page and in their emails.

A guest’s RSVP page on a phone showing they’re attending and their personal check-in QR code

Results

536
guests checked in
52
tables seated
100%
of bookings paid online

Built with Laravel, Filament, Stripe Connect and Laravel Forge.

Planning a ticketed event?