Keep Registration Records Useful and Privacy-Conscious

A useful registration record tells the organizer what they need to run the event without collecting unrelated personal information. Start with the decisions the record supports: identifying a booking, allocating a design, communicating practical updates and arranging agreed support. Do not begin with every field a form builder happens to offer.

Give each field a job

For every question, write why you need the answer and who will use it. A design choice may help prepare canvases; a home address may be unnecessary for an event with venue collection. Keep support requests separate from a public attendance sheet and use the organization's appropriate private process.

This is a practical record-design exercise. Your organization remains responsible for its privacy obligations and approved notices. The event checklist helps connect registration decisions to the real plan.

Map fields and copies

Add required or optional status, sharing destination, retention rationale and review owner in your private working record. Avoid placing sensitive details into a worksheet shared with all volunteers.

Test one unnecessary field

Imagine a library painting session where everyone collects supplies at the venue. The organizer considers collecting postal addresses “in case they are useful.” No current task needs them. The practical response is to remove that field, while keeping a contact method needed for event updates under the library's approved process.

The same review applies to copied spreadsheets, printed check-in lists and emailed attachments. A clean main record is not enough if older versions remain scattered among helpers.

Assign a record owner

1. Identify the authoritative registration record.
2. Give helpers only the information their tasks need.
3. Record approved corrections in one place and communicate necessary updates.
4. Collect or appropriately dispose of temporary working copies through the organization's process.
5. Review records after the event according to the applicable retention requirements.

Do not adopt an arbitrary universal deletion period. Some information may have a continuing purpose or required retention; the responsible organization must decide that.

Registration questions

Can the supply team work from quantities alone? Often it can. Use design counts and references in the group supply plan rather than a full attendee list.

Does registering mean joining a mailing list? Treat marketing preferences through the organization's separate approved process. For future sessions, use aggregate lessons in repeat hosting notes where individual identities are unnecessary.