Set retention and deletion checks for event attendee records

Inventory every operational copy

Event information can remain in the original form, Airtable, shared CSV files, reception printouts, notification emails and attachments. Begin with a list of information type, location, owner and purpose. Deleting a source row does not remove a previously exported CSV. This guide describes an operational inventory and cleanup process; it does not prescribe a universal legal retention period. The responsible organisation must determine requirements for the actual information and activity. That decision comes before configuring a deletion timer, because a convenient product setting is not itself a retention policy.

Make purpose-specific retention decisions

Contact details used for arrival, a refund case, aggregate event statistics and a request for future announcements serve different purposes. Do not delete everything on one arbitrary day simply because the event ended. Separate purposes that have finished from justified continuing uses. Future-event messages are not the same activity as necessary communication about the booked event. For aggregate reporting, examine whether identifying columns are needed at all. When a particular case requires a hold on deletion, record the reason, owner and review date so a temporary exception does not become indefinite storage by default.

Record the decision and owner

The register should identify location, information category, retention decision, deadline, owner, deletion method, checked-at time and exceptions. A clear separation between the person confirming the decision and the person recording execution is easier to audit than unrestricted edits to every field. A due-date view is a queue for the agreed action, not necessarily authority for immediate automatic deletion. An unresolved attendee enquiry may need a separate decision. State whether a rule uses event date, submission date or another reference, because those choices can select very different records.

Distinguish a retention rule from permanent deletion

Tally documents submission retention controls as a Business feature. Expired submissions move to Trash, which is different from immediate permanent deletion. Review the current Trash and deletion behaviour against the action your organisation actually requires, and record the correct state. Deleting a form also affects its submissions, so distinguish closing a public intake URL from cleaning up selected answers. Connected tables and previously exported files need their own checks. Do not describe a form-level retention timer as a mechanism that erases all copies held across every integration and recipient.

Include exports, printouts and attachments

Assign custody and disposal responsibility for reception printouts. Include shared-drive CSVs, local downloads and emailed versions in the inventory. Check attachment-sharing settings separately rather than assuming removal of a form response revokes every link as expected. Avoid creating a fresh complete copy of personal information merely as proof that another copy was deleted; keep an appropriate minimal execution record. Address backups according to the actual service and organisational process. Cleanup is a coordinated action across known locations, not a claim that an organiser can silently control every recipient’s device.

Choose native controls or a manual checklist

A one-off event can begin with a location inventory and scheduled manual reviews. Before buying automatic retention, verify that the decision is settled, exceptions can be handled and connected copies are covered. Assess plan requirements, register access, attachment storage and staff effort together. Make might notify an owner about due records, but permission to notify is separate from authority to delete. Start with a reviewable queue and an escalation route for mistakes. Automation becomes useful once the rule is reliable; it should not turn an unresolved retention question into an irreversible action.

Verify what the completion record means

Use fictional submissions to test a future deadline, a due item, an unresolved case, movement to Trash, permanent removal, a remaining integration row and a remaining CSV. Do not compress every outcome into a single cleaned-up checkbox; identify which location and action were checked. Confirm that a routine roster export does not immediately recreate information that was meant to be retired. Completion means the required actions and remaining exceptions can be explained. Link retention back to intake, attendance and file-submission design so cleanup is considered before copies are distributed.

• Track event attendance in Airtable
• Collect workshop applications with Tally
• Build a Tally file submission form: size, file types and link access