Post-event closeout

After the event, reconcile outstanding organizer tasks, sponsor follow-ups, prizes, and analytics. Preserve event records; do not delete records merely to make a dashboard look complete.

1. Export or share reports only through approved data-handling procedures.
2. Assign sponsor and attendee follow-ups to named owners.
3. Resolve prize claims through the admin workflow and document exceptions.
4. Capture outages, content decisions, and process improvements for the next event.
5. Mark the event closeout complete only after owners confirm their work.

Purpose and checklist

Closeout transfers active operations into owned follow-up without deleting useful records. Event Operations, Sponsor Success, Programming, and Communications assign a named owner/backup for each stream.

1. Use /post-event, /admin/analytics, /admin/followups, and /admin/prizes only as role-appropriate; list each open workstream.
2. Reconcile check-in, sponsor follow-ups, prizes, moderated content, and incidents. Dashboard counts are signals, not financial/delivery proof without source evidence.
3. Do not send reports/exports/email without separate authorization including recipient and scope.
4. Record lessons as a dated decision/issue with source links; do not silently overwrite a current runbook.
5. Handoff remaining work and close only after owners acknowledge it.

Escalate missing records, data access concerns, or analytics inconsistencies. A production fix follows deploy and release.