Event & Group

Keep every movement wave tied to one current plan.

Passenger transportation operations software for event and group teams carrying coordinated movements from reservation to payment.

TOOSAEvent movement workflow
Movement waveVenue release plan
Conflict review

Route sequence: Staging, 16:10; South gate, 16:35; Hotel loop, 17:20.

Movement control brief

Shared capacity turns one delay into several decisions.

A movement plan must connect passenger groups, release windows, staging, vehicles, crews, providers, acknowledgements, and actuals.

Plan

Version every wave

Keep group, window, location, staging, and service assumptions together.

Share

Expose dependencies

Show when later waves rely on the same vehicle, crew, or provider.

Confirm

Read back the field plan

Make changed briefs and provider acknowledgements visible before movement.

Operating workflow

A venue release moves while two waves share capacity.

The event lead needs one revised movement plan, not separate fixes that create a later conflict.

Trigger

The first group is held while its assigned coach is needed for the next departure.

  1. 01
    Trace dependencies

    Identify affected groups, windows, staging, vehicles, crews, and providers.

  2. 02
    Compare revisions

    Build feasible sequences without assuming unconfirmed capacity or acknowledgement.

  3. 03
    Authorize one version

    The event lead selects the named movement and update set.

  4. 04
    Read back the plan

    Expose missing briefs, provider responses, actuals, and exceptions.

Validate before launchConfirm provider acknowledgements, operating scale, field communication, and result measures before launch.

What to evaluateCheck that teams can see dependencies and reconcile one authorized movement version.

Product path

Six products follow the same operating job.

The six products share one operating record. Confirm event scale, availability, connections, and write permissions for the selected workflow.

01

TOOSA Dispatch + TOOSA Fleet

Build. Connect waves, shared vehicles, staging, and conflicts.

02

TOOSA Crew + TOOSA Network

Coordinate. Carry briefs, provider options, and acknowledgement.

03

TOOSA Billing + TOOSA Automate

Reconcile. Prepare actuals, exceptions, and approved follow-up.

Readiness path

Move from exploration to launch validation.

Ready to explore

Explore planning and duty tools.

Review event context, routes, imports, duty templates, scheduled duties, driver work, tracking, history, and administration.

Configured for your operation

Configure the movement plan.

Define groups, waves, locations, capacity rules, roles, status language, acknowledgements, and the system of record.

Validated before launch

Validate production coordination.

Confirm provider connections, automated messages, operating scale, reliability, security, billing availability, and event reporting.