> For the complete documentation index, see [llms.txt](https://www.information-architecture.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.information-architecture.world/wiad-organizer-guide/things-to-do-after-the-event.md). # Things to do after the event Thank your team for making the event happen. Then complete the closeout tasks while details remain fresh. ### Close out your event Complete any remaining operational work: * Thank speakers, volunteers, sponsors, partners, and attendees. * Reconcile invoices, reimbursements, and local sponsorship commitments. * Record what worked, what changed, and what to improve next year. ### Share approved event content Publish slides, recordings, and photos only with the relevant permission. Respect speaker preferences and attendee photo consent. Share content through: * Your local microsite and social channels. * Accessible video and image formats with clear captions and descriptions. * The content collection process provided by the global team that year. Keep a single record of published links, speaker permissions, and asset locations. It makes future updates and handovers much easier. ### Complete the post-event survey The global team may send a post-event survey after World IA Day. Complete it promptly and include honest feedback. Your responses help improve future organizer support and global planning. ### Prepare for next year or hand over If you will organize again, save your notes, contacts, and reusable assets. Keep them in a shared location your team can access. If another organizer takes over, transfer account ownership using each platform’s access credentials. Update recovery contacts and two-factor authentication. Never share passwords. Remove access for people who no longer need it. Review how you retain or delete attendee information. Follow the privacy notice shared with attendees. Review [Collecting attendee data](/wiad-organizer-guide/audience-and-the-day-of-experience/collecting-attendee-data.md) before transferring any data. Contact if you need support with a transition.