Recommended launch checklist

Complete this before announcing events publicly. Every check is done while signed out, on a phone as well as a desktop.

1. Platform

• [ ] The POM theme, or a child of it, is active.
• [ ] POM Events is active on this site.
• [ ] The License section reports a valid state for this domain.
• [ ] On multisite, POM Events is active on the main site and the network license is configured there.
• [ ] The site timezone under Settings → General is correct.
• [ ] Event URLs resolve; permalinks were re-saved after activation if needed.

2. The registration decision

• [ ] Totally disable event attendees functionality is set deliberately, not left at its default by accident.
• [ ] If registration is enabled, the team knows POM Events sends no confirmation emails.
• [ ] If access is sold, WooCommerce is active and the purchase path has been tested end to end.

3. Site-wide settings

Archive

• [ ] Posts per page matches how long the lists should be.
• [ ] Events thumbnail placeholder is set, so events without an image do not render as gaps.
• [ ] Error message is written in the site's voice.
• [ ] Events list loader is set, or deliberately left empty.
• [ ] Hide events date is set deliberately.

Single event

• [ ] Subheader, title and Add to calendar are on or off deliberately.
• [ ] The Go back button, its label and its URL are correct if enabled.
• [ ] The header image source — featured image or custom — is chosen.
• [ ] The privacy policy URL is set if registration collects personal data.
• [ ] The form clause text is written and legally reviewed.
• [ ] Related-content options match how the site links events to articles.

4. Content

• [ ] Every published event has a start and an end date.
• [ ] Dates and times are correct in the site timezone.
• [ ] Every event has a place, or deliberately has none.
• [ ] Every event has a featured image, or the placeholder is acceptable.
• [ ] Event types and categories exist and are assigned — empty taxonomies mean empty filters.
• [ ] No test or draft event is reachable.
• [ ] Past events behave as intended: they leave the upcoming list and their button shows the finished label.

5. Registration behavior

• [ ] The form opens and validates.
• [ ] A registration reaches the Confirmed list.
• [ ] The duplicate-email rule was tested.
• [ ] The capacity rule was tested and the waiting list works.
• [ ] Button labels are correct in all three states: available, waiting list, finished.
• [ ] Display remaining space shows what you expect, including the full state.
• [ ] The optional form fields are the ones you actually need.
• [ ] The team knows registrations create WordPress user accounts.

6. Finding events

• [ ] The search form is placed on the page visitors will use.
• [ ] Type and category filters return sensible results.
• [ ] The date picker filters correctly.
• [ ] Load more events works past the first page.
• [ ] The empty-result message reads well.
• [ ] The calendar, if used, shows the right events and each entry opens its page.
• [ ] Both work on a phone.

7. The public event page

Open a representative event signed out:

• [ ] Subheader, title and categories are correct.
• [ ] Start and end dates read correctly.
• [ ] The details sidebar shows only fields that have content.
• [ ] Add to my calendar produces the right date and title.
• [ ] Additional link buttons open what they promise.
• [ ] Previous and next navigation moves between events chronologically.
• [ ] The related-content block is correct, or absent.
• [ ] The page reads well on a phone.

8. Privacy and data

• [ ] The privacy policy covers the personal data the form collects.
• [ ] The consent checkbox appears on the form.
• [ ] The team knows attendee exports contain personal data.
• [ ] Someone owns the attendee lists and their retention.

9. The team

• [ ] Someone owns event content.
• [ ] Someone owns attendee lists and the door list.
• [ ] The team knows how to move a registration between Confirmed, Waiting list and Cancelled.
• [ ] The team knows that deleting a cancelled registration is permanent.
• [ ] The team knows that a change is only live once checked signed out.

The site is ready when a visitor can find an event, understand it, register, and appear on the list the organizer will actually use at the door.