Run the whole event from one place.

OAO, Operational Administration Overview, is the live operations layer for events.

It connects organisers, staff, security and vendors while the day is happening. Each person sees what is relevant to their role. The organiser sees the full picture.

  • No sprawling WhatsApp groups
  • No chasing updates across radios, spreadsheets and paper
  • No guessing who is where
  • One event. One operational view.
OAO organiser command centre — live venue map, staff, security, vendors, tasks and activity in one operational view
The organiser command centre. One live picture of the event.

One live operational hub for the whole event.

Staff & workforceSecurityVendorsShiftsTasksIncidentsZones & mapsCommunicationsLive activityOSO

Every user gets a role-based workspace through Passport, while the organiser sees the whole event.

Built for the chaos behind the curtain.

Vendor power

A stall loses power mid-setup. The vendor needs staff, not another group chat.

Missing check-in

A steward has not arrived. The roster still says they are on the door.

Security incident

An incident is logged at an entrance. It needs an owner, a place, and a record.

Overdue task

A setup job slips. Nobody can see it unless they already know to look.

Zone coverage

A floor is short. You only notice when the queue appears.

Wrong entrance

A guest is sent to the wrong door. Staff on the ground cannot see the same instruction.

Those problems usually live in different places. OAO pulls them into one operational picture.

The organiser sees the whole event.

Organiser command centre with venue map, live counts and activity feed

Who is working

Presence, role, team and zone — not a static roster from last week.

What needs attention

Open tasks, incidents, overdue jobs and help requests in one place.

Where it is happening

A live map and zone picture, not a separate floorplan on someone’s phone.

Who owns it

Every item has a team or a person. The organiser can see the gap if it does not.

Live activity feed

Examples from a simulated event day — not live figures.

  1. Incident

    Security incident logged at the north entrance

    Example from a simulated event day — assigned to the door team.

  2. Vendor

    Power issue reported at a stall

    Example from a simulated event day — floor staff can see the job.

  3. Staff

    Steward still not checked in

    Example from a simulated event day — the zone stays short until someone covers.

  4. Task

    Setup task overdue in Zone 2

    Example from a simulated event day — visible to the organiser and the assigned team.

One system. Different views.

Event staff mobile app with five tabs: home, tasks, venue map, communications and more

Role workspace

Event Staff

Shift, zone, assigned jobs and team messages. The work in front of them — not the whole operation.

Role workspace

Security

Posts, coverage, incidents and the jobs that belong on the security desk.

Role workspace

Vendors

Their stall, setup status, and a way to ask for help without ringing the organiser.

Full picture

Organiser

Everything. People, places, tasks, incidents and communication — the whole event.

Simple access through Passport.

  1. 01

    Email

    A person is invited or signs in with the address the organiser holds.

  2. 02

    Event membership

    They are attached to this event — not given a generic app login.

  3. 03

    Role

    The organiser assigns the role: staff, security, vendor or organiser.

  4. 04

    Correct workspace

    They open the workspace that matches that role. Nothing else.

The organiser assigns role, team, zone, shift and permissions. Staff do not choose their own permissions.

Geographic operations, not a poster on the wall.

Filter the map to the work you need. Open a map item and you open the record — the person, the stall, the incident or the task.

  • Staff on the floor
  • Security posts
  • Open incidents
  • Active tasks
  • Vendor stalls

OSO watches the operation with you.

It looks for exceptions and patterns: a zone going short, a task slipping, a cluster of incidents, a vendor waiting too long. It brings them to the organiser. It does not run the event on its own.

Not another chatbot. An operational second pair of eyes.

The attendee digital layer

Hosted Events is what visitors hold: map, timetable, vendors, stamps and the day in their pocket.

The operations backend

OAO is what the operation holds: people, places, tasks, incidents and communication. Both sit inside Wheelside. They are not the same product.

Anyone running a live site with more than one team.

Festivals

Crew, traders, security and a site that will not sit still.

Conventions & shows

Halls, guests, vendors and a day that moves by the minute.

Live performances

Doors, stages, back of house and the people holding each one.

Venue programmes

Repeated events in a known building — still a live operation every time.

People + Places + Tasks + Incidents + Communication

Most event software helps plan the event. OAO helps run it.

  • What is happening?
  • Where is it happening?
  • Who owns it?
  • What needs attention next?

That is OAO.

See it on a simulated event day.

The demo is a read-only walkthrough of a simulated operation. It is not live event control, and it is not a claim of official partnership.

Operate the event. See the whole picture.

People. Places. Operations. All together.