The organisation needed one event management and ticketing platform for attendees, organisers, vendors, and venue teams. The existing journey divided event setup, programmes, ticket types, registration, payments, vendor coordination, check-in, venue capacity, and reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete event management and ticketing platform shaped around attendees, organisers, vendors, and venue teams
The organisation needed one event management and ticketing platform for attendees, organisers, vendors, and venue teams. The existing journey divided event setup, programmes, ticket types, registration, payments, vendor coordination, check-in, venue capacity, and reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between ticketing, venue operations, and event reporting, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole event management and ticketing platform.
- Separate firm event management rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined ticketing, venue operations, and event reporting without blurring roles
Use one event model from public listing through ticket validation and on-site operations, with role-specific views for each team.
In the event management and ticketing platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Next.js, Node.js, PostgreSQL formed one supportable event management and ticketing platform
The architecture follows business ownership rather than the navigation menu. Next.js, Node.js, PostgreSQL share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind venue operations.
In the event management and ticketing platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Next.js supports the primary product surface.
- Node.js owns a bounded part of the product journey.
- PostgreSQL keeps operational data and handoffs reviewable.
The release had to prove the whole event management and ticketing platform, not one polished screen
Organisers can manage the whole event without reconciling separate ticketing, programme, and venue records. The release plan therefore followed representative work across every audience and the complete path through ticketing, venue operations, and event reporting.
Acceptance for the event management and ticketing platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Organisers can manage the whole event without reconciling separate ticketing, programme, and venue records.
- 01
The event management and ticketing platform now gives attendees, organisers, vendors, and venue teams one shared operating record.
- 02
Ticketing, venue operations, and event reporting follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.