Skip to main content
GullySystem
Automotive

Business solutions for Employee transport operators

Explore software for work such as “Employer shift rosters and accepted passenger changes”. Review each business function below, including when it fits and what to check before implementation.

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.

Trip desk and exception handling

Record reported departure, passenger outcomes and completion evidence with the person providing it. Keep a missed pickup separate from a passenger cancellation. Refer unresolved arrival or incident reports through the employer’s established operating process instead of closing them with the trip.

Contract accounts

Match the charge basis to the contract version and supporting trip sheet. Fixed vehicle deployment, passenger use and extra trips require different billing evidence. Supplier charges and the amount recoverable from the employer are separate reviews, even when they concern the same journey.

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
  • Reported boarding, cancellation, no-show and completion events with source and time
  • Interruption or complaint file with responsible contact, action and outstanding decision
  • Operative rate basis, accepted trip statement and billing adjustments
  • Role access list covering current employer, site and assigned trip scope

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.

Partner and customer bills disagree

A partner claims a deployed vehicle while the employer disputes a cancelled trip. Retain both commercial bases and the operating evidence; neither invoice proves the other amount is payable.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  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.

Roles and responsibility boundaries.

Employer transport contact

Supplies or accepts the roster and resolves requests affecting work sites, shift eligibility and employee instructions. This role represents the employer; the operator does not change employment attendance or transport entitlement from a trip record.

Dispatch coordinator

Confirms available vehicles, accepted partner capacity and crew assignment. Carries approved roster changes into the dispatch copy and records which version reached the responsible crew.

Driver and assigned trip crew

Provide the actual journey and passenger-event evidence through the agreed reporting method. The operating team owns driving, passenger assistance and incident action; entering a status is not a substitute for those duties.

Trip desk reviewer

Investigates conflicting no-show or completion reports and retains their source. Connects the employer’s decision, dispatcher action and passenger communication without exposing another employer’s roster.

Billing reviewer

Checks the contract basis, accepted trip evidence, adjustments and supplier claim separately. Passes disputed lines for resolution rather than treating every scheduled journey as billable.

Reports your managers need.

  • 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
  • Accepted trip statements with disputed billing lines
  • Employer and partner balances linked to separate supporting records

Connections to scope

  • Employer roster exports: stable passenger and site identifiers, permitted fields and a checked change history. An HR connection is optional and requires authorised access.
  • Partner or existing transport systems: accepted vehicle assignments and trip references through a supported exchange; an emailed request alone is not acceptance.
  • Tracking or communication providers: source time and delivery status where a supported connection exists. A position feed or message acknowledgement does not prove passenger completion.
  • Accounting: accepted billing statements, issued invoices and verified receipts, with customer and supplier sides kept separate.

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Reconcile one employer’s operating records

Compare its signed scope, latest roster, dispatch sheets and accepted bill. Agree the service-date convention for overnight shifts and the people who control changes.

Exercise conflicting records

Test a roster amendment after dispatch, partner substitution and disputed no-show. Include a journey with incomplete evidence so the desk sees what must remain open.

Compare a trial statement

Trace billed trips back to their accepted evidence and check who can see passenger details. Resolve rejected records and permissions before adding further employer sites.

Limitations to settle before implementation

  • Employer eligibility, security requirements and local transport obligations remain with the responsible employer, operator and advisers. No universal escort or operating rule is prescribed.
  • Transport boarding and trip records do not establish payroll attendance, employee discipline or workplace entry.
  • Live location, automated routes, mobile check-in and emergency response are separate capabilities to verify; this proposal does not assert that they are installed.
  • Passenger addresses and contact details require restricted operational use. External files and partner copies need their own access and retention controls.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Employer shift rosters and accepted passenger changes
  • Vehicle, driver and partner assignment records
  • Passenger-event and trip-completion reconciliation
  • Contract-based trip statements and employer billing
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

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