Privacy and information handling
Event data minimisation checklist
The registration form has grown to 28 fields over three events, and nobody can say what half of them are used for.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Data minimisation here means a simple discipline: for each field, name the task that fails without it, the person who uses it, and the date it will be deleted. A field with no answer to those three is a candidate for removal.
Your data protection contact decides what is acceptable. The checklist helps your team arrive with specific proposals and not a long form.
Ask three questions of every field
- What task fails or becomes harder if this field is missing?
- Who uses the answer, and when? If the answer is nobody, remove it.
- How long is it kept, and who deletes it after the event?
Common fields and the questions to ask
| Field | Questions to ask before keeping it |
|---|---|
| Phone number | Is it for on-day contact only? Could it be asked only of speakers and VIPs? |
| Job title | Is it printed on the badge or used for eligibility? Otherwise is it needed? |
| Date of birth, gender, nationality | What decision depends on it? If none, remove. If one does, ask your contact how to handle it. |
| Identity or passport number | Is it required by a third party such as a venue or visa process? Ask the contact how it should be requested and who sees it. |
| Dietary and access needs | Collect as a need, not as a reason. Who reads it, and is it deleted after the event? |
| Home address | Is anything posted? If not, remove. |
| Employer details | Needed for invoicing or group rates? Only then. |
| Marketing preferences | Keep separate from registration. See marketing permission separation. |
Minimise beyond the form
- Badge: print only what other delegates need to see.
- Exports to suppliers: send the columns they need, not the whole sheet.
- Sponsor and exhibitor lists: share only what has been reviewed. See sponsor data-sharing review.
- Feedback forms: ask for names only when you need to follow up.
- Old events: delete or archive in a defined place, with a named owner.
Order of work
- Pull the list of fields from your personal data inventory and the form.
- Run each through the three questions with the person who would use the answer.
- Mark each field keep, optional, move to a later stage, or remove.
- Test the shortened form with the field minimiser tool and the validation sheet.
- Send fields marked as uncertain to your data protection contact.
Worked example · Fictional example
Cutting a form from 28 fields to 17
Fictional organisation and figures, for illustration only.
A fictional trade association reviews its annual conference form with its caterer, badge printer and finance contact. Nine fields have no user, such as a home address and date of birth. Two are moved: the phone number is asked only of speakers, and dietary needs are asked after payment.
Nationality, kept for years by habit, goes to the data protection contact as a question. The form is now 17 fields, and each has a named user and deletion date in the sheet.
Use this yourself
Minimisation checklist table
Copy one row per field. A blank owner or blank reason means the field is a removal candidate.
| Field | Task that fails without it | Who uses it | Keep / optional / later / remove | Deletion date and owner | Question for contact |
|---|---|---|---|---|---|
| Phone | On-day contact for speakers | Programme lead | Optional, speakers only | 30 days after event, secretariat | |
| Date of birth | None identified | Nobody | Remove | ||
Handle it in-house, or bring in help?
Your team can usually handle this when
- Fewer than 15 fields and one person who knows what each is for.
- Your contact has already approved a standard field list.
- The event is the same as last year's.
Outside planning help earns its fee when
- Fields were added by several teams and nobody owns the form.
- A sponsor or committee member asks for extra fields without a stated reason.
- You need the review done quickly alongside other registration work.
Want the form and handovers trimmed to what is used?
An Event Blueprint can include a field-by-field review of the registration form and supplier files, with the questions for your data protection contact attached. The planner proposes; your contact decides.
Questions organisers ask
Is a shorter form always better?
Not always. A field that supports a real task, such as a dietary need, is worth keeping. The aim is a reason for every field.
A sponsor asks for extra delegate fields. What should we do?
Ask for the reason in writing and take it to your data protection contact. Do not add the field to the form until it is approved.
When should we delete event data?
Set the date before the event, name the owner and confirm deletion. The retention decision itself goes to your data protection contact.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.