About Services Tools Blog Contact us

Event Booking and RSVP

Runs a dated event from one brief: a guest list with a capacity cap that doubles as the mailing table, plus an invitation, a public page and an RSVP export.

  • Booking & Scheduling
  • Leisure and visitor attractions
  • Productised service
  • Productised
  • Cloud
  • 2026

The problem

Guest lists, invitations and the public events page were built as separate tables. A date change meant editing each one again. The booking form also stayed open after the room was full.

What it does

One event record holds the date, the capacity and the copy. Bookings fill the guest list and the mailing table together. The invitation, the page and the RSVP use the same fields, so they follow when the date moves.

Outcomes

  • A full event stops taking bookings.
  • The mailing table matches the guest list without a second export.
  • A late date change updates the invitation and the page together.
  • Staff can read who is coming on the day.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Autumn lantern evening

20 places
Bookings
4
Places held
16
Remaining
4
16 of 20 places held
New booking
Desk

The same row is written to the guest list and the mailing table.

Ready to book
Guest list Friday 13 November 2026
NameContactPlaces
Helen Crowe[email protected]4
James Adeyemi[email protected]4
Priya Shah[email protected]4
Owen Blake[email protected]4

Invitation and page

The invitation and the events page read this same field.

Invitation

You are invited

Autumn lantern evening

Friday 13 November 2026

The Orchard Room. Doors at 18:30. A short talk, then supper on the lawn. Please book only the places you need.

Events page

Autumn lantern evening

Friday 13 November 2026

The Orchard Room · doors 18:30

Lanterns on the lawn, a short talk, then supper.

4 places remaining of 20.

Uses the places still open, then closes the form.

Mailing table

These rows are the guest list. Export does not build a second table. Date: Friday 13 November 2026.

NameEmailPlaces
Helen Crowe[email protected]4
James Adeyemi[email protected]4
Priya Shah[email protected]4
Owen Blake[email protected]4

How it works

  1. Create the event with a date, a capacity and the public copy.
  2. Add bookings with a name, a contact and a place count until capacity is reached.
  3. Close the form automatically when the remaining count reaches zero.
  4. Publish the invitation and the events page from the same fields.
  5. Export the RSVP rows, which are already the mailing table for that date.

Pipeline

flowchart LR
  A[Brief] --> B[Event]
  B --> C[Booking]
  C --> D[Capacity]
  D --> E[GuestList]
  E --> F[Mailing]
  B --> G[Invite]
  G --> H[RSVP]
  H --> E