Keep places and waiting lists in one place. Registration for courses, tournaments and camps.
Paper slips, emails, messages and a request at the end of training can all mean another participant. A shared registration workflow keeps capacity, confirmations and waiting lists together, so organisers can focus on the activity.
Where registration work piles up
One person collects camp forms, another receives messages on their phone, and parents email the office. Once everything reaches the spreadsheet, the course may already be full.
Confirmations, consent forms, payment checks and waiting-list calls follow. Each cancellation creates more messages. A shared system keeps the current state available even when the usual organiser is ill. Paper and telephone registrations can still be entered by authorised staff.
What changes for organisers
Today
Several entry points
Forms and messages reach different people.
Manual counting
Only the person with the latest list knows whether there is room.
Repeated follow-up
Each acceptance or cancellation needs another message.
With a shared workflow
One participant list
Online registrations and checked entries share the same record.
Capacity by fixed rules
Simultaneous registrations cannot bypass the agreed place limit.
An orderly waiting list
The next eligible participant receives an offer with an acceptance deadline.
What the software can handle
Prepare entries from email
AI suggests name, course and contact fields. Missing or ambiguous information is checked before an entry reserves a place.
Manage places and waiting lists
You define capacity, eligibility, queue order and offer deadlines. Fixed rules release cancelled or expired offers and handle simultaneous applications.
Give leaders the right information
Leaders see their own group. Necessary emergency contacts and health notes have restricted access and agreed retention; they are not sent to a general AI prompt.
Start with one event type
-
01
Trace existing registrations
We review forms, inboxes and section lists, including how cancellations and payments are recorded.
-
02
Agree the rules
We select one event and define capacity, member prices, waiting-list offers and exceptions.
-
03
Build and test the full journey
We test full courses, duplicate submissions, cancellations and missing consent. Import, training and operation are agreed before launch.
Connect registrations to rooms and fees
A course needs a room, an event may charge a fee, and members may pay a different price from guests. A connection to membership records avoids a second lookup.
Connections to venue scheduling or payment collection should follow a real need. You can begin with one registration flow and expand after it works.
Venue scheduling Membership fees Association software AI for associations Prices and audit terms Private AI Calculate AI costs
Registration questions
Can non-members register?
Yes, if you choose. Eligibility, required information and member or guest prices are set for each activity.
What about telephone and paper applications?
Authorised organisers can enter them. AI may prepare fields from emails, but uncertain details are checked. Every confirmed registration uses the same capacity rules.
How long does implementation take?
We agree a schedule after checking the scope, existing data and required connections. Starting with one type of activity keeps the first version manageable. The first call is free.
Where is participant information stored?
Before implementation, we agree the storage location, access roles, retention and permitted provider use. This includes checking the contractual terms on using your data for model training. Hosting alone does not settle every data protection requirement. Emergency and health information is limited to authorised people responsible for the relevant group.
Where do your registrations arrive?
Describe one course, camp or tournament and how you handle changes. We can discuss a practical first version.