Programme and delivery tools
Event registration form field minimiser
The registration form is growing, and someone should ask why each field is on it before the form goes live.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
…
The short answer
The minimiser takes each proposed registration field with its purpose, how necessary it is, whether it is required, who owns it and how long you will keep it. It suggests keeping the field, making it optional, considering removing it or removing it, and lists privacy-review questions for the form.
A sensitive field is never recommended for marketing, scoring or profiling. The tool makes no statement about whether the form meets the PDPA or any other law: it sorts fields by the necessity you state and gives you questions to take to whoever is responsible for data protection.
What to enter
- Each field on the proposed form, one per row, with the purpose in your own words.
- How necessary it is: needed to run the event or deliver what you promised, useful but the event runs without it, or nice to have.
- Whether it is required or optional on the form.
- The retention owner as a role, and how long you will keep the data under your own rule. Tick Sensitive if you think the field is sensitive.
How each field is judged
A field with no purpose is held until one is written. A field that is needed and has a purpose is kept, required or optional as you set it. A field that is only useful but required is better optional, and a nice-to-have field is either removed or, if optional, worth considering for removal.
A field is treated as sensitive when you tick it or when its name looks sensitive, for example religion, race, health or an identity number. That is your own flag, not a legal category.
Sensitive fields and lead scoring
A sensitive field with a marketing, scoring or profiling purpose is marked for removal. The same goes for a sensitive field that is not needed to run the event. A sensitive field that is genuinely needed goes to privacy review first, with a question about why it is needed, who may see it and how it is protected.
Collecting more in the hope that it improves sponsor targeting or lead scoring is not a purpose the tool will accept for a sensitive field. See the registration form design and sponsor data-sharing review for the surrounding decisions.
Retention and ownership
A field with no retention owner or no retention period is flagged. An unknown period is not the same as a short one. Write the rule you will apply, for example until the event report is signed off, and name the role who deletes the data.
For the list of fields and their meanings, use the registration data dictionary.
Limits
The worksheet depends on the purposes and necessity you enter. It does not know the law that applies to your organisation or the notice you must give. Use the questions it produces, and the privacy notice drafting questions, with the person responsible for data protection.
Worked example · Fictional example
A fictional one-day forum
Fictional fields and purposes, to show the suggestions.
A fictional forum proposes six fields. Name and email are needed and required. Job title is useful but required, so it should be optional. Dietary requirement is needed for catering and optional. Religion is proposed to improve lead scoring for sponsors, and home address has no purpose written.
Religion is marked for removal. Home address needs a purpose before it can be judged. Two fields have no retention owner and three have no retention period.
| Field | Purpose | Suggestion |
|---|---|---|
| Full name | Name badge and attendance list | Keep, required |
| Job title | Group attendees for roundtable seating | Make optional |
| Religion | Improve lead scoring for sponsors | REMOVE |
| Dietary requirement | Plan catering | Keep, optional |
| Home address | (none written) | Needs purpose or necessity |
Use this yourself
Registration field worksheet
Complete one row per field before the form is built. Take the review questions to whoever is responsible for data protection.
| Field | Purpose | Needed, useful or nice to have | Required or optional | Sensitive (yes or no) | Retention owner and period |
|---|---|---|---|---|---|
| Review question: does the form say what is collected, why, who sees it and how long it is kept? | |||||
| Review question: which fields are shared with a supplier or sponsor, and on what basis? |
Handle it in-house, or bring in help?
Your team can usually handle this when
- A short form, a clear purpose for every field and someone responsible for data protection who reviews it.
- No data is shared with sponsors or suppliers beyond what delivery needs.
Outside planning help earns its fee when
- Several teams want fields added and no one owns the decision on what the form collects.
- A registration vendor, a venue and sponsors each ask for attendee data.
- The form, notice, retention and sharing decisions must be settled against the event timeline.
Need the registration decisions coordinated?
An outsourced conference project lead can run the field review with your committee, collect the purposes and owners, take the privacy questions to your data-protection contact and keep the final form aligned with the registration vendor brief. What the form collects and what is lawful remain your decisions.
Questions organisers ask
Does the tool say my form complies with the PDPA?
No. It makes no statement about whether a form meets any law. It sorts fields by the necessity you state and gives questions for whoever is responsible for data protection.
Can I add a sensitive field to improve lead scoring?
The tool marks a sensitive field with a marketing, scoring or profiling purpose for removal.
What if I do not know the retention period yet?
It is flagged as unknown. Unknown is not the same as short, so write the rule you will apply.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.