Event data deletion handover
The event is over, the team is moving on, and attendee files are still in inboxes, supplier systems and a shared drive.
The short answer
A deletion handover turns a vague intention into a list: each copy of event data, the person who deletes it, the date and the proof. It is signed off by one named owner and filed.
The dates come from your retention schedule and your reviewer. This page covers the handover, not the periods.
Find every copy
Use your personal data inventory, your sharing log and your supplier question log. Typical copies sit in the registration platform, email attachments, shared drives, downloaded extracts, printed lists, photographer and badge-printer files and volunteers' devices.
What each handover row records
- The copy and where it sits.
- The holder: your team or a named supplier contact.
- The action: delete, return, anonymise or keep with a stated reason and review date.
- The date the action is due.
- The proof: a screenshot, a written confirmation from the supplier or a signed note.
- Who checked the proof.
Things that are easy to miss
- Backups and automatic email archives.
- Supplier sub-contractors.
- Files on personal phones and laptops.
- Printed lists left in a venue or office.
- Anything kept 'for next year' with no reason recorded. Take it to your reviewer.
Closing the handover
- Send each holder a written request with the due date.
- Chase unanswered requests once, then escalate to the owner.
- Record proof as it arrives.
- Have the owner sign off and file the sheet with the event records.
- Pass anything that cannot be deleted to your reviewer with the reason.
Worked example · Fictional example
A fictional secretariat closes out a 260-delegate event
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Perunding Alam Sekitar lists nine copies across six holders: the registration platform, two spreadsheets, a volunteer's laptop, the badge printer, the photographer, the caterer, a printed desk list and the committee chair's email.
Eight are deleted or returned by the due date with written confirmation. The ninth, a speaker's travel record, is held for a funder reporting request; the owner records the reason and sends it to the reviewer.
Use this yourself
Data deletion handover sheet
Copy one row per copy of data. File the completed sheet with the event records.
| Copy and location | Holder | Action | Due date | Proof received (what, date) | Checked by |
|---|---|---|---|---|---|
| Registration platform export | Secretariat | Delete | |||
| Badge print file | Printer (named contact) | Delete | |||
| Photographer's raw files | Photographer | Delete | |||
| Printed desk list | Desk lead | Shred | |||
| Volunteer's downloaded extract | Volunteer | Delete |
Handle it in-house, or bring in help?
Your team can usually handle this when
- Few copies, one team and cooperative suppliers.
- A retention schedule already exists.
- Someone has time to chase confirmations.
Outside planning help earns its fee when
- Many suppliers and volunteers hold copies.
- The team has dispersed after the event and no one owns closure.
- You want deletion built into supplier contracts and the event handover.
Need the close-out run after the event ends?
A project lead can run the deletion handover as part of event close-out, chasing confirmations and filing proof, while an Event Blueprint can write deletion dates into supplier requirements from the start. Decisions on what must be kept stay with you and your reviewer.
Questions organisers ask
Is deleting a file enough?
Ask your IT or privacy reviewer about recycle bins, backups and synced devices, and record what you were told.
What if a supplier does not reply?
Chase once in writing, then tell the owner. Record every attempt.
Can we keep the list for the next event?
That is a decision for your owner and reviewer, based on the purpose you stated. Record the reason and a review date.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.