How to manage workshop registrations when places are limited

For a workshop with limited places, registration is a promise about space, equipment, and instructor attention. Choose the capacity you can actually deliver, explain what a booking includes, and make each registration's status unambiguous.

This matters whether you teach ceramics, cooking, painting, or professional skills. A waiting-list entry, a payment, and a confirmed place can mean different things. Your website and records should agree about what the customer has.

Set capacity from the practical constraint

Start with the smallest resource limit: workstations, equipment, seats, or the number of people the instructor can support. Check venue requirements as well.

Imagine a pottery session with eight wheels and one instructor. If each participant needs a wheel for the whole session, eight is the maximum under that setup. Selling ten registrations because ten chairs fit in the room does not solve the equipment constraint.

If a booking can include several attendees, confirm that capacity counts people rather than orders. Two orders for four people each fill that eight-person session. A system supporting only one place per account needs a different registration process.

Describe what the attendee is choosing

For each session, publish its date, time, location, duration, skill level, and included materials. Tell people what to bring, how to arrive, and how to ask about access requirements.

Distinguish a single workshop from a course. “Three-week ceramics course” should explain whether one registration covers all three dates and what happens after a missed session. Repeating a workshop on a calendar is not automatically the same as selling the series as one product.

Decide when a place becomes confirmed

Write a simple status model before configuring tools: for example, requested, confirmed, cancelled, or waitlisted. Use only the states your process needs.

If you collect payment online, check the relationship between checkout and reservation. A cancelled checkout should not appear as a paid booking. A payment success screen should not be the only evidence that a place has been reserved: verify the customer and administrator records too.

If people pay at the venue, say so before they book. Keep “reserved” and “paid” separate in your own records to avoid chasing people who followed your instructions correctly.

Make the waiting list understandable

Explain whether joining the list requires payment, how people are contacted, and what happens when a place opens. Automatic promotion and an invitation to book are different processes.

For an invitation-based process, decide how long someone has to respond and who gets the next invitation. For automatic promotion, make sure the attendee knows they can become booked without another action. Verify which model your software actually supports.

Reopen places consistently after cancellations

Set a cutoff and describe refund or credit rules. Include who to contact if someone cannot use the online cancellation flow. The public policy and the software settings should agree.

Try two customers requesting the final place. Then cancel the successful booking and check whether the available-place count updates correctly. Repeat the journey on a phone. These checks matter more than adding another paragraph of promotional copy.

Keep a useful session-day list

Before the workshop, check that the list identifies each attendee, their booking status, and any information genuinely needed to run the session. Limit sensitive information and access to what staff need. Establish a fallback way to check reservations if your connection fails.

Collect preparation questions deliberately. An open text field for every possible preference is harder to review than a few clearly explained questions.

A practical registration checklist

• Capacity reflects equipment, space, and teaching limits.
• Dates and what the price includes are clear.
• One session versus a complete series is unambiguous.
• Confirmation and payment status can be checked independently.
• Full-session, waitlist, and cancellation behavior have been tried.
• Attendees can find preparation details and a contact method.

Cronvy can help build a workshop booking website through AI chat. Use the preview to assess your own registration requirements and enabled features. For the wider setup process, read how to create a class booking website.