Conferences & summits
Multi-day programmes with tracks, parallel sessions and delegate categories.
Event Registration & Ticketing
Sell the seats, take the payment, and know exactly who is walking in.
Registrations arrive through a form, payment arrives by bank transfer, and someone matches the two by hand. A ticketing system does that on its own, keeps a live count of what is left, and turns the door list into a scan.
Live seat
capacity
capacity
Online
payment
payment
e-Tickets and
QR check-in
QR check-in
Attendance
reporting
reporting
Seats remainingCounted down as they sell
Payment receivede-Ticket issued at once
Checked inAttendance recorded on the door
The problem
The event runs fine. The admin around it does not
Organisers rarely struggle with the programme. They struggle with the fortnight before it, when the registration list, the payment list and the name badges all have to agree.
- Registrations come through a form and payments through a bank transfer, and someone reconciles the two by hand.
- Nobody knows how many seats are left until a person counts the spreadsheet again.
- Early-bird, member and group rates are applied manually, so mistakes turn into refunds.
- On the day, check-in is a printed list and a highlighter, and the queue builds.
- Afterwards, attendance records and certificates take a week to sort out.
Built for organisers
Anyone selling a seat against a fixed capacity
Whether it is a two-day conference, a Saturday workshop or a run with four thousand entries, the mechanics are the same: a fixed number of places, tiered pricing, and a door that has to move quickly.
Training providers
Workshops and courses with intakes, prerequisites and certificates on completion.
Associations & CPD
Member and non-member pricing, with points posted to the member record afterwards.
Attractions & activities
Sessions running several times a day, each with its own slot and capacity.
Sports events & runs
Categories by distance and age, with waves, kit collection and bib numbers.
Corporate & community
Invite-only sessions, RSVP lists and events that are free but still capacity-bound.
A custom platform is worth building when you run events repeatedly, sell several ticket types, need registration data in a particular shape, or want the attendance record to land somewhere afterwards.
For a single event with one ticket type, a hosted ticketing service will get you selling this afternoon and take a cut. That is often the right answer, and we will say so.
From publish to follow-up
How a registration moves through the system
Six steps. The one that saves the most time is the fifth — the door stops being a bottleneck once the list is a scan rather than a search.
Publish
Event, sessions, capacity and ticket categories go live on your own site.
Register
Attendee picks the session and ticket type, and capacity is checked as they do.
Pay
FPX or card for individuals, an invoice for corporate group bookings.
Confirm
e-Ticket with a QR code issued automatically, resendable and transferable.
Check in
QR scanned at the door and attendance recorded as people arrive.
Follow up
Certificates, feedback forms and the attendance report, from the same data.
Walk-ins and cash payments still happen, and the system has to handle them without breaking the count. Registration at the door is part of the build, not an exception to it.
Core modules
Main modules and functions
Most organisers start with events, ticket types, registration and payment. Check-in and certificates are added once the first event has actually sold.
Events & sessions
Multi-day programmes, parallel tracks, repeat sessions, venue capacity per room.
Ticket types & pricing
Early bird, member, student and group rates, promo codes, and cut-off dates per tier.
Registration forms
Questions per ticket type, dietary and accessibility needs, consents captured and dated.
Payments & invoicing
FPX and card, corporate invoices for group bookings, refunds and cancellation handling.
e-Tickets & QR
Issue, resend, and transfer a ticket to a colleague when the named attendee changes.
Check-in
Scanning on a phone or tablet, walk-in registration, and attendance per session.
Communications
Confirmations, reminders, joining instructions the day before, and post-event follow-up.
Certificates & CPD
Issued automatically once attendance is marked, with points posted where they belong.
Reports
Sold against capacity, revenue by ticket type, attendance and no-show rate, exports.
From a live build
Screens from a ticketing platform we built
From Kiddypedia, where parents browse programmes, pick a date and a slot, choose a ticket category and check out. The full story is in the e-ticketing case study.
Implementation
Typical implementation
Six stages, planned backwards from the event date rather than forwards from today.
Scoping workshop
Sessions with the organising team. We write down the ticket types, the pricing cut-offs, and what has to be asked of an attendee at registration.
Output: ticket matrix and registration fieldsProgramme & capacity audit
Every session, room capacity, speaker slot and clash gets listed before anything is built — this is where double-booked rooms surface.
Output: session grid with capacitiesDesign & sign-off
Screen-by-screen design of the registration flow and the organiser back office, reviewed with whoever will run the door on the day.
Output: signed-off screens, build scheduleBuild in stages
Events, ticket types, registration and payment first, so you can open sales while check-in and certificates are still being finished.
Output: test system, updated fortnightlyRehearsal & UAT
A dry run of the awkward cases: a sold-out session, a group booking on invoice, a transferred ticket, a walk-in, and a scan with no signal at the door.
Output: signed UAT and a door-day planOpen registration
Sales open, with us on hand through the first days and again on the event day itself.
Output: live platform, SOP, event-day support
Timeline
About three months — and the date does not move
Registration should open well before the event, so the build has to finish earlier than people expect. Work back from the day, not forward from the kick-off.
Month 1Month 2Month 3Month 4
Scoping workshop
Programme & capacity audit
Design & sign-off
Core build
Payments, e-tickets, check-in
Rehearsal & UAT
Registration opens
Event day & follow-up
The gap between the last two bars is deliberate. Registration wants to be open at least a month before the doors, which means the software has to be finished before that — the event date is the one thing in this project that cannot slip.
Client feedback
From a client who needed a deadline met
We were extremely impressed with the team at UNO. Their friendly and professional approach, coupled with their ability to not only meet timelines but also provide invaluable advice, exceeded our expectations. They demonstrated a deep understanding of our requirements and consistently delivered results that at times went beyond scope, which was appreciated. It was a pleasure working with UNO and we highly recommend their services.