A workshop registration form needs to tell you who has booked, which session they will attend, and how to contact them. If places are paid, it also needs a clear way to connect registration with payment.
Start with the editable template below. It works as a planning sheet or a paper registration form. It is not a hosted online form, and downloading it does not register anyone for a workshop.
Download the free registration template
No email needed. Open the text file in an editor, replace the example details, and remove fields you do not need.
Choose fields that support the workshop
Start with the essentials. A long form creates more work for the person booking and more information for you to maintain.
| Field | Why it is useful |
|---|---|
| Workshop name and session date | A person should know which session they are booking before they enter their details. Include the start time, time zone and location. |
| Buyer name and email | This is the person responsible for the booking. Use the email to send the receipt and practical information. |
| Number of places | A buyer may book for more than one person. Count places, not just orders, when checking capacity. |
| Attendee name for each place | Separate the people attending from the person paying. This helps when one buyer books for colleagues or friends. |
| Ticket type and total price | Make the selected option and total clear before payment. Explain any extra processing or booking charges. |
| Booking reference and payment status | These are organizer records, not details for the attendee to invent. They let you connect a registration with the correct order. |
Add another question only if its answer changes how you prepare. A ceramics workshop may need a participant's experience level; an online session may need none of those extra details. Explain why you ask, make nonessential questions optional, and keep sensitive information out of a public attendee list.
Do not put card numbers, security codes or bank details into a general registration form. Paid bookings should use the payment provider's checkout.
A filled example: one buyer, two attendees
Introduction to bookbinding
- Session: November 14, 2026, 10:00 a.m.–1:00 p.m., local venue time.
- Location: Example Studio, Room 2. This is a fictitious venue.
- Buyer: Alex Example, using a fictitious email address.
- Attendees: Alex Example and Sam Example.
- Places: 2. Ticket price: $35 each. Listed ticket subtotal: $70.
- Organizer record: booking reference DEMO-104; payment status recorded after checking the payment provider.
These are demo details, not a customer booking. Fees or applicable taxes may change the checkout total; show that total before the buyer confirms.
The useful distinction is two places, one buyer. A spreadsheet with only one row per order can hide the number of people you expect at the door. Keep an attendee list as well as an order record.
Connect registration with payment
A form submission and a successful payment are different events. Decide when a place is confirmed and explain that rule beside the registration step. A message saying “we received your form” should not imply “your place is paid and confirmed” unless that is true.
If you collect registrations manually, reconcile them with payment records before confirming places. Do not rely only on a screenshot sent by the buyer. Check the payment record itself and record a reference you can find again.
Set a capacity for each session. If one order reserves two places, subtract two places from availability. For several dates, keep the session date on every attendee record so a person does not appear on the wrong list.
Give the buyer a clear confirmation
Once the booking is confirmed, send the workshop name, date, start time, address or joining instructions, number of places, and booking reference. Say what to bring and how to contact you about a change.
If attendees need to check in separately, explain how they receive or share their tickets. Read the confirmation on a phone: a street address hidden in a long paragraph is easy to miss on the way to an event.
Keep your change and refund instructions visible before purchase. A template is a prompt to write those instructions, not a promise that every booking tool can enforce your rules automatically.
When a form is enough, and when ticketing helps
For a small free session, a simple form and a checked attendee list may be sufficient. For paid workshops, managing payment, place counts and check-in separately can make it harder to see which bookings are ready.
CrabGate's workshop ticketing brings ticket sales and door check-in into one shop. Each workshop date is its own event. The current product does not promise an automatic repeating schedule, waiting lists, class passes or memberships.
If you need those features, compare a class booking system before choosing. If you want to sell places for specific dates to your own audience, a simple ticket shop may fit.
Check this before opening registration
- Read the workshop details as if you have never visited the venue.
- Book one place, then check a booking for more than one attendee.
- Confirm that capacity counts people rather than order rows.
- Open the confirmation and ticket on a phone.
- Check how staff find a booking and who handles changes.
Next, read how to sell tickets for a small event for a complete launch checklist.
Put your next event on sale
CrabGate is a ticket shop for organizers who already have an audience. It costs $99 a year, with no CrabGate per-ticket fee. Stripe processing fees still apply.
No card is needed to create your shop. Confirm your email to open your Back Office. You pay the annual subscription when you put your event on sale.