To set up online booking for a workshop or class, decide how your sessions repeat, then make each seat a ticket that someone books and pays for on one link. That first decision matters most. Laces treats a booking as a ticket on an event, and it has no class calendar, recurring schedule, membership pass or waitlist. So a repeat class needs a plan, and this guide gives you one.
Match the setup to your schedule
Most classes fit one of four shapes. Find yours before you create anything.
| Your class | How to set it up | Your link | What check-in tells you |
|---|---|---|---|
| One session | One event, one ticket type | One | Who arrived |
| A choice of sessions, such as morning or afternoon | One event, one ticket type per session | One | Who arrived, and staff read the session from the ticket name |
| A course with the same people every time | One event, one ticket for the whole course | One | The first arrival only |
| A repeat class with new people each time | A separate event for each run | One per run | Who arrived at that run |
Check-in shows on the scan screen, one person at a time. Laces gives you no attendance list. Two of these need a closer look.
A choice of sessions. Put the time in the ticket name, such as “Saturday 9am”, and give each ticket its own number of places. When one fills up, it stops selling and the others carry on. The catch is at the door. A scan confirms the ticket is valid for this event, whichever session it is for, so whoever is scanning has to read the ticket name and turn away the wrong session.
A course. Sell one ticket and list all the dates in the description or agenda. A second scan doesn’t turn red. It stays verified and shows the time of the first check-in. That means Laces won’t tell you who came to week three, and the export has no check-in data either. If attendance counts, say for a certificate, keep a register in the room.
Repeat classes: clone, don’t rebuild
If you run the same class again with new people, make each run its own event. The Laces word for this is cloning. A finished or cancelled event has a clone button, and the create screen offers it too once you have an eligible event.
What comes across: your ticket types, questions, what each ticket includes, and your policy wording.
What starts fresh: the sold counts, the participant list, orders and money. Nothing about a person is ever copied.
After you clone:
- Fix the name. Laces adds a year to the end, which may not suit a class.
- Fix the dates. A clone starts about a year ahead, so set the real date and time. This is the step people miss.
- Check your places and price before you open it.
- Publish. A clone begins as a draft and doesn’t sell anything until you open it.
Each run gets its own short link, list and earnings. So give people your organization’s page, laces.run/org/yourname, as the address that doesn’t change. It lists all your events, and you can put it on a poster.
This is fine for a monthly class or a term of weekly sessions. It is also real work, one clone per run. If you run several classes a week with drop-ins and class packs, a dedicated class-booking tool is likely to suit you better than Laces, and it is worth choosing one.
Set your places and a closing date
Set the number of places to what you can actually teach, not the number of chairs. Our workshop planning guide shows how to work that out from your facilitator’s time.
Next, set “Registration closes” if you need notice. If you must buy materials or print handouts two days ahead, close bookings then. It’s optional, and checkout enforces it.
When a session sells out, there is no waitlist. Have the next date ready to announce, and say so on the page.
If you want a lower first price, create a separate ticket with limited places and a clear name. Laces does not change a price on a date.
Ask what the teacher will use
Name, phone and email are always asked. Gender, age group and an emergency contact can be switched on or off. Owners and admins can add their own questions, and each can be required or optional.
Two limits shape what you write. Answers are free text, and they are asked once per order, not per person. A company booking five staff gets one answer to “What is your experience level?” If you need details for each person, ask the company to send them by email.
Good questions for a class include what people want to learn and any access or dietary needs. Skip anything the teacher won’t read. For more on this, see our guide to registration forms.
Take the booking and the money together
A seat is booked only once it’s paid for. Each country has its own payment methods:
- Uganda: MTN MoMo, Airtel Money and cards
- Kenya: M-Pesa and Airtel Money
- Ghana: MTN MoMo, Telecel Cash and AT Money
- Rwanda: MTN MoMo and Airtel Money
- Zambia: MTN MoMo, Airtel Money and Zamtel Kwacha
Outside Uganda, the number field starts with the country code, so people type their number without the first 0. Tell your class that if they ask.
Your organization needs payment clearance before any bookings open, free classes included. Apply from the Earnings tab, well before your first poster.
Tell people what to expect
The confirmation takes care of itself. The ticket and receipt go out by email once payment is confirmed, and Laces sends paid participants a reminder two days before the event, with their ticket link and your contact details.
That reminder can’t carry your own notes. So put “bring a charged laptop” or “wear old clothes” in your event description, and repeat it in your group chat or by email if you keep one.
Write your rules down too, before anyone pays:
- What happens if you cancel or move a session
- Whether someone can get a refund if they can’t come
- Whether someone else can take their place
A refund policy is optional. Write yours in the event description, and without one, the Laces refund policy applies. There is no button that moves a booking to a later session, so rescheduling someone usually means a refund and a new booking. Refunds you owe remain your responsibility, so keep your takings available until the class has run.
Check people in
For a small class, the app lets you search by name, phone or order code. For a bigger one, scan the QR ticket. Either way, the phone needs a data connection, so check the signal in the room beforehand. Our guide to QR code tickets explains what each result means.
Frequently asked questions
Can Laces run a weekly class automatically?
No. There is no recurring schedule. Each run is its own event, cloned from an earlier one.
Can someone pay once for a whole course?
Yes. Sell one ticket for the course and list the dates. Check-in records the first arrival only, so keep your own register for later sessions.
Can I accept bookings for a paid masterclass?
Yes. It runs the same way as a workshop, with a ticket and places. The Uganda guide to paid workshops and masterclasses walks through it there.
Can someone book without an account?
Yes. Participants book from a link in their browser, with no app and no account.
What happens when a session is full?
That ticket stops selling. Other tickets on the event carry on, and there is no waitlist.
A booked seat should be a paid seat
Create your workshop or class, cap your places, and let people book and pay on one link.
Read next
For organizersHow to Organize a Workshop, Masterclass or Paid Seminar in 2027Organize a workshop, masterclass or paid business seminar in 2027: design the session, size the group, find your minimum, and make claims you can stand behind.5 Nov 2026 · 9 min read
For organizersHow to Organize a Paid Workshop or Masterclass in UgandaPlan a paid workshop in Uganda: set your seats and price, take registration and payment in one step, confirm attendees by email and check them in by QR.4 Nov 2026 · 6 min read
For organizersHow QR Code Event Tickets Work: Creation, Scanning and Check-InHow QR code event tickets are issued and scanned, what each result at the gate means, how repeat scans show up, and how to prepare your check-in team.5 Nov 2026 · 8 min read
