One registration system for several briefing locations
Members will register once, but they must be placed at the right stop with the right seat limit.
The short answer
Set up one registration record per person with a required stop choice, a separate seat limit and waiting list for each stop, and one agreed rule for changes between stops. Decide who sees the data before the form opens.
Test it with the local teams using three or four dummy registrations that cover a full stop, a wrong-stop change and a cancellation.
Decide the model before choosing the tool
Either one event with several sessions, or several events sharing one form. The first makes reporting across stops easier. The second makes separate seat limits and local confirmation messages easier. Ask the registration supplier which model its system supports.
Whichever you choose, each stop needs its own capacity, closing date and confirmation text including venue details.
Rules to agree in writing
- Can an attendee switch stops after registering, and who approves it?
- What happens when a stop is full: waiting list, an invitation to another stop, or closure?
- Is a person allowed to attend more than one stop?
- Who may see registrant lists: central team only, or each local host for their own stop?
- How are duplicate registrations from the same organisation or email detected?
- What are the cut-off dates for changes and for final headcount to local hosts?
Personal data across teams
Local hosts should receive only what they need for their stop, for example names and organisations for a badge list. Ask your privacy or legal owner what notice, consent and sharing arrangements apply before the form is built, and what the supplier's data terms say. A project lead can coordinate those questions but does not decide the answers.
Reconciling counts
- Export registrations per stop on fixed days each week.
- Compare with the local host's own list and resolve differences.
- Send final headcount per stop on the agreed cut-off day.
- After each stop, record who actually attended so the next stop learns from it.
Worked example · Fictional example
A single form for three briefings
Fictional organisation and figures, for illustration only.
A fictional professional body, Persatuan Fiktif Jurutera Perunding, opens one form for briefings in Kuala Lumpur, Shah Alam and Seremban. Seat limits are set at 120, 80 and 60 per stop, illustrative figures, each confirmed by the venue in writing.
A member registers for Shah Alam, which fills. The form offers the waiting list or an alternative stop. The member picks Seremban, the secretariat approves the switch, and the confirmation shows the Seremban venue. A duplicate registration from the same member appears in the Friday check and is merged.
Use this yourself
Multi-stop registration field and rule specification
Copy this and give it to your registration supplier or internal system owner.
- Model chosen: one event with sessions, or several events with one form:
- Stops, venues, dates, and confirmed seat limit per stop:
- Required fields (name, organisation, email, stop, accessibility or dietary needs asked by whom):
- Waiting list rule per stop:
- Switch-stop rule and approver:
- Duplicate check method:
- Confirmation message text per stop:
- Who sees which list, and what privacy notice applies (confirm with privacy owner):
- Export days and final headcount cut-off per stop:
- Test cases: full stop, switch, cancellation, duplicate:
Open the tool: KL-Selangor-Seremban briefing circuit planner
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your registration tool already supports sessions with separate limits.
- One person owns the form and the data.
- The stops are few and attendance is invited, not open.
Outside planning help earns its fee when
- Registration is open to the public and demand differs by stop.
- Several teams edit the form or export data.
- Past events have produced duplicate or misplaced registrations.
Want someone to run the registration rules across all stops?
Recurring programme management can write the registration specification with you, brief the supplier, run the weekly count reconciliation and hand each host a clean list for their stop. Share the stops and your current system. A conference project lead can take this task if recurring support is not available.
Questions organisers ask
Should each city have its own form?
It can work if stops are very different, but one form makes duplicates and reporting easier to manage. Decide based on whether people may attend more than one stop.
How do we avoid overbooking a stop?
Set the limit from the venue's written confirmation, not an estimate, and apply a waiting list when it is reached.
Who owns the data after the programme?
Agree this in advance with your privacy owner, including how long records are kept and who deletes them.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.