Skip to content Skip to footer
Back to Portfolio
our work

Festival.org — The work behind a smooth arrival

SaaS Websites

Public site: events.festivalorg.net

A ticketing product has two audiences who rarely see the same screen. A guest wants to know what to buy and what happens next. An organiser has to manage tickets, participant information and orders while the event itself is taking shape. The quality of the interface shows up at a real moment: someone arrives with a ticket and the people at the door can get on with welcoming them.

Festival.org booking flow on a published event
Booking flow captured from the public product at events.festivalorg.net. Public website capture, stored locally for this case study.

Functionality

The confirmed product lives at events.festivalorg.net, not on the unrelated festival.org domain. Public pages cover event listing, ticket selection, checkout, accounts, rider information, bank-transfer and pay-on-site orders, and invoices generated from the order. Guests can review tickets before signing in; participant details sit on the ticket, while rider information can be completed later from the account.

Editorial concept of a Festival.org demo invoice or organiser view with sample data
Demo invoice or organiser view with sample data. Labelled as a concept until an approved demo environment capture is available. Editorial illustration (concept). Not a product screenshot.

From concept to implementation

  1. Map event roles
  2. Define ticket and participant rules
  3. Prototype booking
  4. Test order and invoice scenarios
  5. Implement
  6. Rehearse event-day use

Developer commentary

The event page keeps ticket selection in a recognisable place so a guest does not have to hunt for the next step. Interior frames show the booking path from a published event and a labelled demo of an organiser or invoice view using sample data — never a live personal order.