Ticketing, scheduling, attendee management, vendor coordination -- what to build when you're creating software for events management.

Most events don't need a custom app. Eventbrite, Humanitix, and Tito handle ticketing and registration for the vast majority of public events, and they do it well. If you're running a conference, a community fundraiser, or a recurring local event, starting on one of these platforms is almost always the right call.

Custom event management software makes sense in a smaller set of situations: recurring events with complex workflows that the standard platforms don't support; multi-day conferences where the event itself needs a dedicated attendee app with agenda, speakers, and networking; events that are part of a larger platform or membership system and need deep integration; or organisations running multiple events at scale where the per-ticket fees on standard platforms become a significant cost.

When custom does make sense, the build is typically split into two parts: an ops-facing management system for the organiser, and an attendee-facing app or website. Both have distinct requirements, and scoping them separately helps clarify what's actually needed.

Here's what an events app typically needs to handle well.

Event creation and scheduling

The management side starts with creating events: name, description, dates, venue, capacity, session structure, and any multi-day or multi-stream configuration. For conference organisers running parallel sessions across multiple rooms, a schedule builder that manages room capacity and avoids speaker clashes is a core admin function.

Content management lets non-technical event staff update event details, speaker bios, sponsor information, and agenda items without needing developer involvement. A schedule that changes constantly up until the event -- as speaker confirmations come in and sessions get shuffled -- needs to be editable by the organiser without a deployment every time.

Calendar sync lets attendees add sessions they want to attend directly to their phone's calendar, which is one of the most-used features in any conference app.

Ticketing and registration

A ticketing module needs to handle ticket types (general admission, VIP, early bird, group rates, complimentary), capacity limits per ticket type, and discount codes. One-off payments via Stripe handles the transaction, with automatic confirmation emails and ticket delivery.

For events with complex registration -- multi-day conferences where attendees select which days to attend, workshops with limited places that require separate booking, or gala dinners alongside a conference -- the registration flow needs careful design. The simpler the flow, the higher the completion rate.

GST calculations need to handle the different treatment of ticket types. Conference registrations are generally taxable; charitable fundraiser tickets may have a partial deductibility component that needs to be disclosed on the receipt.

Attendee check-in

On the day, check-in needs to be fast. A QR code on the confirmation email, scanned by staff with a tablet or phone, is the standard approach. Offline mode is important here: event venues often have poor wifi, and a check-in system that stops working when the venue network is overloaded is a problem at exactly the wrong moment.

For large events with multiple entry points, the check-in system needs to sync across devices so the same attendee can't check in twice at different gates.

Self-service check-in kiosks -- where attendees scan their own QR code -- reduce queues at registration desks for high-volume events.

Attendee-facing agenda and navigation

A dedicated attendee app or mobile-optimised web app serves as the event companion: full schedule, speaker profiles, exhibitor listings, venue maps, and personalised agenda where attendees save the sessions they want to attend.

Maps and geolocation helps attendees navigate multi-venue or multi-room events. For conferences at large hotels or convention centres in Sydney and other major cities, a floor plan integrated with the session schedule is a genuine convenience.

Push notifications handle real-time updates: session starting in 10 minutes, room change for a session, keynote running late, networking lunch is now open. Keeping attendees informed without requiring them to check the app constantly improves the event experience.

Speaker and exhibitor management

Speakers need to confirm their session details, upload presentation materials, and communicate with the organising team. An exhibitor portal lets vendors submit their booth information, logos, and descriptions for the event guide without back-and-forth email.

Document management for speaker assets -- presentation files, bio photos, headshots -- keeps everything in one place and avoids the organisers managing a flood of email attachments.

Role-based permissions ensure speakers can edit their own profiles and upload their own materials, but can't see other speakers' information or the event's financial data.

Vendor and supplier coordination

Large events involve significant vendor coordination: catering, AV, security, decorators, and transport. A vendor management module tracks each supplier's deliverables, contract status, and on-the-day schedule.

For events with food vendors or market-style components -- outdoor festivals, markets, and trade fairs across NSW and beyond -- vendor onboarding (application, selection, payment, briefing) can be handled through the platform rather than via spreadsheets and email.

E-signatures for vendor agreements means contracts can be sent, signed, and returned digitally without printing or scanning.

Notifications and attendee communication

Pre-event communications -- registration confirmation, event reminders, schedule updates -- and post-event follow-up are important parts of the attendee experience.

Transactional email handles the automated communications: immediate registration confirmation, a reminder two days before the event, and a post-event survey invitation the day after.

SMS notifications are more effective than email for time-sensitive updates on the day itself -- a session cancellation or a venue change that attendees need to see immediately.

Post-event surveys and reporting

Capturing attendee feedback while the event is fresh produces more useful data than a survey sent a week later. An in-app survey triggered at the end of the final session, or an SMS link sent immediately after close, maximises response rates.

Analytics dashboard for event organisers shows registration numbers over time, ticket type breakdown, session attendance by room, check-in rates, and revenue. For an organisation running multiple events per year, this data informs planning for the next event.

CSV and Excel export of attendee lists, check-in records, and financial summaries is important for post-event reporting to boards, sponsors, and funding bodies.

What does it cost?

A custom events platform varies significantly by scope. A registration and ticketing system with attendee check-in and basic management tools typically runs $30,000--$60,000 AUD. A full platform with attendee app, speaker and exhibitor portals, vendor management, and reporting would be $60,000--$120,000+ depending on the complexity of the event format and integrations required.

The app cost calculator can help you estimate your specific build.

Questions to ask before you build

Have you genuinely outgrown Eventbrite, Humanitix, or Tito? These platforms are well-built and handle most events well. The strongest case for custom is when your event format has complexity they can't support, when per-ticket fees at your volume are significant, or when you need deep integration with a larger platform. If it's mainly that you want your own branding, there are cheaper ways to achieve that.

Are you building for a single event or an ongoing platform? A custom build makes more sense amortised across many events over several years than for a single event where the platform won't be used again.

Do you need a native mobile app, or would a mobile-optimised web app work? A native iOS and Android app requires more budget, App Store submissions, and ongoing maintenance. For most events, a well-built responsive web app -- bookmarked to the home screen -- is a better fit. Native apps make more sense for recurring annual events with a persistent attendee community.

What does your venue's connectivity look like? If check-in, agenda access, and live updates all depend on a reliable internet connection, test the venue network before committing to an online-only approach.

What happens with attendee data after the event? Privacy Act obligations apply to personal information collected at registration. Define your data retention and deletion approach before the platform is built.

Code Workshop

What does an events app need?