Skip to main content
GullySystem
Automotive

Vehicle and Trip Management for Employee transport operators

Connect an employer’s current passenger roster to the actual vehicle journey and its evidence.

Assets and Fleet

Does this function belong in your operation?

Use for operators directly managing employee cabs, vans or staff buses, including accepted partner vehicles.

An employer roster or accepted additional request needs an actual transport assignment.

The employer sends a revised outbound roster after dispatch has allotted the vehicles. The trip record needs to show which version actually reached the crew and what happened to the changed passengers. Retain the employer site, service date and direction as well as the vehicle; a shift name alone cannot distinguish an overnight return from the next day’s inbound run.

Bring the records the workflow depends on.

  • Employer site, service date, direction and roster version
  • Passenger requirements and accepted changes from the authorised source
  • Actual vehicle, driver, required crew and partner acceptance
  • Reported departure, passenger events, completion and costs

Outputs to check

  • Roster-linked assignment and substitution history
  • Passenger-event exceptions with source and review owner
  • Accepted trip statement with separate operating and billing decisions

Follow the vehicle and trip management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Identify the demand

    Link the employer site, direction, service date and current roster.

  2. 2. Confirm capacity

    Retain actual vehicle and driver assignment, required crew and partner acceptance.

  3. 3. Hand over the list

    Record which passenger-list version reached the assigned crew.

  4. 4. Record actual events

    Keep departure, boarding or no-show reports and interruptions with their source.

  5. 5. Review completion

    Separate vehicle return from unresolved passenger evidence and employer decisions.

  6. 6. Prepare the operating statement

    Link accepted trip evidence and costs for the separate billing review.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Roster coordinator

Records employer instructions and checks that the dispatch list reflects accepted changes.

Dispatcher

Confirms capacity and the actual crew, retaining partner acceptance and substitution evidence.

Trip desk reviewer

Reconciles reported passenger events and sends unresolved differences to the responsible employer contact.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Roster changes after assignment

Preserve the dispatched version and the accepted amendment, including who received it.

Partner changes the vehicle

Record the replacement and operational approval without deleting the original acceptance.

No-show challenged by a passenger

Retain the original report and new evidence; refer the correction decision to the responsible reviewer.

Can this work independently?

Trip records can start with checked manual rosters and operating sheets. The employer controls eligibility and shift changes; dispatch controls the actual assignment. Recorded location or scheduled arrival does not establish passenger completion. Automated routing, tracking, mobile check-in and emergency response require separate verified arrangements.

Systems and records it connects with

  • Employer roster: authorised passenger and site references.
  • Contracts and invoices: applicable charge basis and accepted trip statement.
  • Partner or location tools: actual source records only where supported access exists.

Configure, test and introduce the workflow.

  • Reconcile an employer’s roster, dispatch sheets and service-date convention.
  • Test a late amendment, vehicle substitution and contested no-show using sample records.
  • Compare actual passenger outcomes and trial trip statements before relying on the register.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • An overnight outbound run keeps its correct service date and direction.
  • A changed roster identifies the version used for actual dispatch.
  • Trip completion cannot silently close an unresolved passenger event.
Employee transport operators

How the business operates.

An employee transport operator turns an employer’s shift demand into actual passenger journeys. The planning unit is an employer site, shift date and direction, with a roster version behind each trip. The operator assigns owned or accepted subcontracted vehicles and crews, records changes and reconciles what ran before billing. A worker’s transport request, vehicle assignment, boarding record and office attendance are different facts. The software scope proposed here is an operating record shared by dispatch, the employer contact and accounts; route automation and live vehicle feeds need separate confirmation.

Employer roster desk

Receive the employer’s current passenger list, site and shift requirements. Keep changed departure dates and pickup instructions tied to their source. A return journey after midnight needs its own service date; the previous shift label alone is not enough to identify it.

Dispatch and partner capacity

Match the current roster to available vehicles and responsible drivers. Retain escort or other staffing requirements supplied by the employer and the responsible operator. A request sent to a partner is not accepted capacity, and a replacement needs an actual assignment record.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Employer site, cost-centre reference and named transport authority
  • Versioned passenger roster with service date, direction and approved pickup instruction
  • Trip sheet linking roster version, vehicle, driver and required crew
  • Partner request, acceptance, substitution and actual vehicle references

Operational bottlenecks to check

Roster changes after dispatch

A changed shift reaches the employer desk but not the assigned driver. Keep version and acknowledgement records so reviewers can distinguish an uncommunicated change from a passenger who did not travel.

Trip completion hides missing evidence

A vehicle return does not show that every planned passenger boarded or completed the journey. Retain passenger outcomes independently and assign unresolved records for review.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Establish the service arrangement

    Identify who supplies roster changes and who accepts billable work. Record the signed scope, operating contacts and authorised staffing requirements before entering a repeating schedule.

  2. 2. Prepare the shift roster

    Separate inbound and outbound travel and retain cancellations or additional requests. Resolve inconsistent employee, site or service-date references with the employer before dispatch uses the list.

  3. 3. Confirm the actual trip

    Record vehicle and driver identity, partner acceptance and the current passenger list. A revised route or substitution needs the employer’s required decision and a traceable crew handoff.

  4. 4. Record the journey evidence

    Keep planned times beside actual reported events. Preserve a passenger’s disputed no-show and the source used for completion review instead of replacing the original event.

  5. 5. Resolve service exceptions

    Link missed pickups, interruptions and unconfirmed completion to a named desk owner. Urgent operating action follows the established response process; the case record supports follow-up rather than replacing it.

  6. 6. Reconcile and bill

    Compare actual trip evidence with the relevant contract. Review extra duties, cancelled deployment and supplier claims separately, then retain the accepted statement and unresolved commercial differences.

Industry reports to connect with

  • Roster revisions not yet reflected in dispatch assignments
  • Assigned trips without confirmed vehicle or partner acceptance
  • Passenger no-show disputes and unconfirmed completion events
  • Planned versus actual departures by employer site and direction

Questions before implementation.

When should employee transport operators consider vehicle and trip management?

Use for operators directly managing employee cabs, vans or staff buses, including accepted partner vehicles. An employer roster or accepted additional request needs an actual transport assignment.

What should we bring to the requirements discussion?

Bring anonymised examples of Employer site, service date, direction and roster version; Passenger requirements and accepted changes from the authorised source; Actual vehicle, driver, required crew and partner acceptance; Reported departure, passenger events, completion and costs. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Connect an employer’s current passenger roster to the actual vehicle journey and its evidence. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The module does not set driving procedures, certify vehicle readiness, decide employment attendance or prescribe escort requirements.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. An overnight outbound run keeps its correct service date and direction. Use this check when reviewing the first working version.

Related functions for employee transport operators.

    Talk to us

    Discuss vehicle and trip management for your business.

    Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

    What happens after you share your requirements

    1. We review your brief and the systems you already use.
    2. We clarify the workflow, missing information and the work to consider first.
    3. The proposed scope sets out the deliverables, responsibilities and dependencies.
    4. Review the scope and commercial terms before deciding whether to proceed.

    Start with your requirements

    Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

    Share your requirements