Handling repeat attendees without collecting unnecessary data again
The same members attend most of your sessions, and every registration form asks them for the same details again.
The short answer
Decide what you need once, what you need each session and what you do not need at all. Ask for the first group at first registration, reuse it for returning attendees, and ask the second group only when a session requires it.
Questions about personal data law and your own notices belong with your data protection lead. This page helps you prepare those questions and structure the form.
Sort every field into three groups
| Group | Example fields | Rule |
|---|---|---|
| Needed once | Name, organisation, membership number, email | Collect at first registration, reuse for the series |
| Needed per session | Question for the speaker, session-specific preferences, attendance confirmation | Collect only for sessions that need it |
| Not needed | Fields kept only because they were in last year's form | Remove from the form |
How to recognise a returning attendee without asking again
Use a key you already hold, such as a membership number or the email used before, rather than asking people to re-enter everything. Ask the person to confirm their details rather than retype them, and give a simple way to correct them.
Agree who in the secretariat can see the list, and who can edit it.
What to ask your data protection lead and platform supplier
- Does the notice on the first form cover reuse of the details for later sessions in the same series?
- Does it cover use for other events? If not, do not reuse the list for them.
- Where are registration records held, and who can export them?
- How long should records be kept after the series, and how are they deleted?
- What do we say to someone who asks to see or correct their details?
- Does attendance data go to any third party, such as a sponsor or accrediting body, and is that stated?
Steps to put it in place
- List every field on the current form and mark each as needed once, per session or not needed.
- Remove the unneeded fields and move per-session fields to the sessions that use them.
- Write a short notice that says what is collected, why, and how long it is kept; have your data protection lead review it.
- Set the recognition method for returning attendees and test it with a few members.
- Agree the retention date and who clears the list at the end of the season.
Worked example · Fictional example
A secretariat trimming a form used across ten sessions
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Perunding Pembiayaan asked members for job title, years in practice, address and dietary preference at every session. The secretariat reviewed the fields and found the series needed only name, organisation, membership number and email once.
It removed address and dietary preference, which were never used for a webinar, and kept an optional question box per session. Returning members confirmed their details from a pre-filled link. The secretariat's data protection lead reviewed the new notice before it went out.
Use this yourself
Repeat-attendee data map and question pack
Fill the first table for each field on your form. Then take the questions to your data protection lead.
- Who may see and edit the list:
- Method to recognise a returning attendee:
- Question: does the notice cover reuse across the series?
- Question: how long is data kept, and who deletes it?
- Question: is any data shared outside the secretariat?
- Question for the supplier: where is data stored and how is it exported?
| Field | Needed once | Needed per session | Not needed | Used for |
|---|---|---|---|---|
| Name | ||||
| Organisation | ||||
| Membership number | ||||
| Question for speaker |
Handle it in-house, or bring in help?
Your team can usually handle this when
- The series uses a simple form with a few fields.
- One person manages the list and the form.
- Your data protection lead is available and has agreed the notice.
Outside planning help earns its fee when
- Several teams or suppliers hold copies of the list.
- Registration data is shared with sponsors or accrediting bodies.
- The series has grown and the list needs cleaning and reconciling.
Want the registration data map and form reviewed?
A recurring programme manager can go through your form with you, sort each field, set up how returning attendees are recognised, and prepare the question pack for your data protection lead and platform supplier. The legal and privacy conclusions stay with the competent party in your organisation.
Questions organisers ask
Can we pre-fill the form for returning attendees?
Often yes, if your notice covers it and the platform supports it. Ask the person to confirm rather than retype, and ask your data protection lead and supplier to confirm the arrangement.
How much data is too much?
If you cannot say what a field is used for, it is probably too much. Remove it or make it optional with a stated reason.
What should we do with old lists?
Set a retention date and a named person to clear them. Ask your data protection lead what period is appropriate for your organisation.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.