ova
An event coordinator speaking into a two-way radio.

Large public events

One platform for every volunteer and crew member

Recruitment, shifts, check-in and compensation in one place, with a live view of who is where.

All use cases

The problem

The people who make events happen are managed across separate tools, spreadsheets and mailing lists. Volunteers get requests from many different addresses, and an opt-out in one place isn't respected in the next.

Groups sign up more people than actually turn up, while compensation is often paid per registered person. Afterwards, working out payments takes days per event. On the day itself, nobody has one view of who is standing where.

The journey

  1. The right people are invited

    Nova

    Volunteers and groups get one consistent request, based on their preferences and earlier events.

  2. Sign-up and shifts

    Your team

    Volunteers choose or confirm a shift. Group coordinators manage their own members.

  3. Check-in on the day

    Your team

    Volunteers and staff check in on site, so attendance is known for everyone.

  4. One live overview

    Your systems

    Event managers see who is at which position along the site or course, and where gaps appear.

  5. Proposals for the manager

    Nova

    The assistant suggests replacements and next steps. The manager approves each one.

  6. Compensation from attendance

    Your team

    Payment is based on who was actually there. Finance reviews it and exports the payment file.

Nova's solution direction

  • One platform, one view

    Volunteers, groups and paid crew share one foundation and one live overview, with clear separation of roles and data.

  • An assistant, under control

    It supports the event manager from start to finish, and nothing goes out without approval.

  • Payments from real attendance

    Days of end-of-event administration become a review of a prepared overview.

  • Data and code you own

    Volunteer data and the software stay with the organisation, rather than in another licence.

Anonymised use case, based on a real brief in our studio. Names and identifying details have been left out. It describes a solution direction, not a measured result.

More use cases

What's the use case you would start with?