> 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/audience-and-the-day-of-experience/preparing-for-event-registration.md).

# Preparing for event registration

Registration is often an attendee’s first interaction with your event. Make it clear, accessible, and easy to complete.

Choose the platform that works best for your local community. Link to it clearly from your microsite and every promotional channel.

### Choose a registration platform

Confirm that your platform supports:

* Keyboard and assistive-technology access on desktop and mobile devices.
* Clear form fields, confirmation emails, reporting, and attendee check-in.
* Your local language, currency, privacy, and payment requirements.

Test the platform before opening registration. Complete a sample registration on a phone and with a keyboard.

### Platforms used by WIAD locations

These platforms have been used by WIAD locations in past years. Verify current availability, pricing, accessibility, and local payment requirements before choosing one.

* [Eventbrite](https://www.eventbrite.com/d/world-ia-day/world-ia-day/?crt=regular\&sort=best) has been used globally.
* [Peatix](http://peatix.com/) was used by [WIAD Tokyo](http://wiad2016tokyo.peatix.com/).
* [Timepad](https://welcome.timepad.ru/) was used by [WIAD Saint Petersburg](https://uxspb.timepad.ru/event/285200/).
* [Ti.to](https://ti.to/home) was used by [Tampa Bay](https://ti.to/wiadtampa/world-ia-day-2016), Zürich, and [Los Angeles](https://ti.to/wiadla) in 2018.

### Create a clear registration experience

Give prospective attendees enough information to decide whether to register:

* Event date, time zone, format, venue or online access details.
* Program highlights, presenters, and accessibility information.
* Registration cost, capacity, cancellation terms, and contact details.

Keep the form focused. Request only data that supports registration, event delivery, or a specific planning decision.

Review [Collecting attendee data](/wiad-organizer-guide/audience-and-the-day-of-experience/collecting-attendee-data.md) before finalizing form fields.

### Plan for access and support

Make the form usable for everyone:

* Label every field clearly and describe errors in text.
* Use sufficient color contrast and do not rely on color alone.
* Provide a contact method for people who need registration support.

Ask attendees how you can support their participation. Do not ask for medical diagnoses. Plan privately for accommodation requests that need advance coordination.

Review [Keep accessibility in mind](/wiad-organizer-guide/branding-marketing-+-promotion/updating-the-wiad-website/keep-accessibility-in-mind.md) before publishing.

### Prepare for registration operations

Set up:

* A confirmation email with essential event details.
* A waitlist process if capacity is limited.
* A check-in process that records actual attendance.

If you charge admission, confirm fees, refunds, and applicable local financial requirements before opening registration.

### Launch and promote registration

Publish the registration link on your local microsite. Include it in social posts, emails, partner outreach, and event materials.

Keep the event details consistent everywhere. Share updates when the program, venue, access information, or registration status changes.

Use [Local marketing strategy](/wiad-organizer-guide/branding-marketing-+-promotion/local-marketing-strategy.md) and [Social media channels](/wiad-organizer-guide/branding-marketing-+-promotion/social-media-channels.md) to coordinate promotion.