Bookings and events

Manage requests, confirmed places, capacity, changes and on-site check-in as separate steps.

A pottery classroom prepared before participants arrive

A submitted form does not automatically mean a confirmed booking. Separate requests, availability checks, confirmation and changes so that participants and organisers see a consistent status.

The workflow

  1. Define one registration

    Decide whether each registration covers a person or a group. Keep headcount separate from response count and assign a registration reference.

  2. Control capacity and confirmations

    Check capacity using confirmed attendance. If you keep a waiting list, record its order and the response deadline for offered places.

  3. Carry changes through to check-in

    Match changes to the original registration reference, checking that old calendar entries are removed and new ones created. Keep attendance records separate on the day.

Choose your starting point

Templates for this workflow

Preview the examples before editing, copying or downloading.

Tools for preparing your data

Build a field mapping table

Map source fields to destination fields and record conversions.

Open tool →

Related guides

Automation & websites · Buying guides

Collect workshop applications with Tally

Collect applications for scheduled workshops with a clear session, party size and contact route.

Read the guide
Automation & websites · Buying guides

Collect customer change requests with Tally

Use Tally to receive a requested change to registered details, while keeping identity verification and the actual customer-record update in the management process.

Read the guide
Automation & websites · Buying guides

Manage event registration and a waitlist with Make

Collect workshop applications and separate provisional seat candidates from a waitlist.

Read the guide
Automation & websites · Buying guides

Track event attendance in Airtable

Separate registration from actual attendance.

Read the guide
Automation & websites · Buying guides

Create Google Calendar bookings with Make: event IDs, changes and cancellations

Turn booking records into Google Calendar events with Make. Map start and end times, retain event IDs, and handle schedule changes and cancellation before inviting real attendees.

Read the guide
AI coding & development · Buying guides

Build a booking-request app with AI

Build a booking-request app that separates intake, confirmation, capacity and cancellation.

Read the guide
AI coding & development · Buying guides

Build an event check-in app with AI

Build event check-in with event-specific admission IDs, atomic entry records and an outage procedure.

Read the guide
Automation & websites · Buying guides

Manage workshop session transfers without losing a seat

A workshop transfer affects two sessions. Build a request log that checks the original booking, reserves a destination place, and records the confirmed change before releasing the old seat.

Read the guide
Automation & websites · Buying guides

Reconcile missing event confirmation emails

A missing confirmation message does not establish that registration failed. Reconcile the stored submission, destination address and notification history before resending or asking the attendee to register again.

Read the guide
Automation & websites · Buying guides

Close event registration and preserve the final roster

Closing a form and freezing an event roster are different actions. Define the cut-off, reconcile accepted submissions, and keep later exceptions separate from the version used on the day.

Read the guide
Automation & websites · Buying guides

Track event refunds from request to confirmed completion

Build an event refund register that distinguishes a received request, an authorised action and the payment provider’s result. Keep registration, payment and refund references separate throughout.

Read the guide
Automation & websites · Buying guides

Prevent workshop room and equipment booking conflicts

Room bookings overlap when preparation and clearing time are omitted. Track room and shared equipment as resources, then review their full occupied intervals before confirming a workshop.

Read the guide
Automation & websites · Buying guides

Notify participants when a workshop instructor changes

A changed instructor needs more than a website edit. Build a session-specific notice list that preserves message versions, verified recipients and unresolved attendee questions.

Read the guide
Automation & websites · Buying guides

Route event accessibility requests to the right organiser

An accessibility request needs a clear organiser and a confirmed response, not an unrestricted note on the attendance sheet. Collect the requested arrangement and share only what each role needs.

Read the guide
Automation & websites · Buying guides

Set retention and deletion checks for event attendee records

Attendee information persists in forms, registers, exports and email after an event. Inventory those copies, assign a retention decision and verify cleanup without confusing a deleted row with complete erasure.

Read the guide

Explore another task