Skip to main content
GullySystem
Automotive

Vehicle and Trip Management for Taxi operators

Record actual taxi assignments and ride outcomes so dispatch, fares and shift collections share the same trip references.

Assets and Fleet

Does this function belong in your operation?

For operators directly managing taxi trips and driver assignments, with actual vehicle records.

An accepted ride is allocated, or a stand or direct-driver pickup is recorded under the operator’s process.

A taxi trip needs its actual booking source, accepted driver and vehicle, journey outcome and fare evidence. Include stand or direct-driver work through the operator’s agreed process so shift records are complete. Keep a cancelled or passenger-not-found job distinct from a completed ride. A change of driver retains both assignments. Trip closure sends evidence to billing and collection review; it does not itself confirm cash, bank settlement or driver payment.

Bring the records the workflow depends on.

  • Booking or direct-pickup source and accepted journey details
  • Driver shift, vehicle identity and actual dispatch acceptance
  • Agreed fare basis, payment mode and reported trip events

Outputs to check

  • Trip and assignment history by actual vehicle and driver
  • Completed, cancelled and unsuccessful pickup outcomes
  • Fare and collection evidence awaiting reconciliation

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. Create the operating trip

    Retain the original booking or stand-pickup reference. Identify the passenger and actual journey without exposing unrelated rider history to the driver.

  2. 2. Confirm assignment acceptance

    Check current driver and vehicle availability through the operator’s process. A dispatch message or offer is not evidence that the driver accepted.

  3. 3. Record actual progress and changes

    Preserve reported pickup and journey events, including a replacement driver or changed destination. Retain prior assignments and the basis for any added charge.

  4. 4. Record the true outcome

    Distinguish a completed ride, cancellation, passenger not found and interrupted journey. Do not invent a fare or passenger pickup merely to clear a dispatch status.

  5. 5. Reconcile trip evidence

    Pass actual charge and collection references to accounts. Retain customer disputes and driver-to-office handover questions after the vehicle becomes available.

Who uses the module, and who approves?

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

Dispatcher

Maintains accepted assignments and unresolved ride coverage.

Driver

Reports actual journey events and collection references through the agreed process.

Trip reviewer

Checks fare evidence and differences without changing the original reports.

Shift cashier

Uses trip references to reconcile collected money independently of dispatch closure.

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.

Driver rejects an assignment

Return the coverage question to dispatch and preserve the rejected offer; a new assignment needs actual acceptance.

Vehicle changes during the journey

Retain both units, the handoff and the reported passenger outcome for review.

Stand pickup lacks an office booking

Register the actual source and accepted fare evidence under the operator’s process rather than omitting it from the shift.

Destination change produces a dispute

Preserve the original journey, actual change and commercial decision separately.

Can this work independently?

Trips can use entered driver, vehicle and booking records. Suitability and operating permissions remain with the operator. Meter data, location, route estimates and platform feeds require supported connections. Billing and collection review use actual outcomes rather than inferred dispatch events.

Systems and records it connects with

  • Future reservation or direct ride request.
  • Driver-reported event and fare-supporting evidence.
  • Customer charge and linked driver-to-office collection record.

Configure, test and introduce the workflow.

  • Reconstruct office-booked, stand and direct-driver trips from actual records.
  • Test a rejected assignment, failed pickup and mid-trip vehicle change.
  • Reconcile an ended trip whose cash or disputed fare remains unresolved.

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.

  • Each actual ride identifies its source, driver and vehicle.
  • Dispatch closure cannot create a completed ride or confirmed payment.
  • Replacement assignments and disputed additions retain their earlier evidence.
Taxi operators

How the business operates.

The dispatcher takes a telephone booking while another driver reports a stand pickup. Both rides need a trip record, but only one passed through the reservation desk. A taxi operator must reconcile those operating records with what each driver collected and what reached the office. This scope covers directly managed taxi journeys from calls, a stand or permitted digital requests, including future reservations and accepted outstation work. It focuses on dispatch decisions, actual ride outcomes and shift collection records. App-origin work remains a separate source when the operator actually handles it. The workflow is a requirements proposal, not a claim that automated dispatch, live maps or payment processing are installed.

Booking and reservation desk

Record pickup details, intended passenger, fare basis and agreed payment method. Distinguish immediate requests from future reservations. A request is not a confirmed pickup until the operator has made and communicated its actual booking decision.

Dispatch and shift control

Keep driver availability, current assignment and vehicle identity aligned with reported events. Record an accepted dispatch separately from an offer or message. If a driver releases a future job or a ride runs beyond the planned end, review the next commitment instead of assuming capacity.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Booking source, passenger contact and pickup or destination details
  • Requested time, confirmation and later change history
  • Agreed fare basis, inclusions and payment method
  • Driver shift, vehicle identity and accepted dispatch

Operational bottlenecks to check

A future booking loses its driver

The assigned driver releases the job but no replacement accepts. Retain the unassigned state and customer communication decision instead of keeping a confirmed driver name from the earlier plan.

One ride produces two payment claims

A driver reports cash while the passenger says the office was paid. Compare the actual evidence and collector before changing either record or charging again.

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. Capture the ride request

    Record the pickup and destination with the agreed fare basis. A regular rider’s history is context; confirm the current journey instead of silently repeating an old destination.

  2. 2. Make the booking decision

    Check capacity for the requested work and communicate the actual decision. Future reservations remain subject to active allocation review; no message alone proves a driver has accepted.

  3. 3. Record the assigned trip

    Link driver, vehicle and source booking. Add direct-driver or stand pickups through the operator’s actual process so they do not disappear from shift reconciliation.

  4. 4. Preserve the actual outcome

    Record pickup, completion, cancellation or unsuccessful collection with the source evidence. Retain changed destinations and disputed additions separately from the original fare agreement.

  5. 5. Reconcile customer money

    Identify who collected the payment and how it was verified. Keep an account fare outstanding when nothing was collected, rather than requiring the driver to report cash that never changed hands.

  6. 6. Close the shift record

    Compare recorded trips, collections and actual office handover. Leave unexplained differences assigned for review; ending a shift does not settle driver pay, customer credit or a pending refund.

Industry reports to connect with

  • Requested rides awaiting a booking or dispatch decision
  • Future reservations with released or conflicting assignments
  • Completed, cancelled and passenger-not-found trip outcomes
  • Trip charges awaiting evidence or dispute review

Questions before implementation.

When should taxi operators consider vehicle and trip management?

For operators directly managing taxi trips and driver assignments, with actual vehicle records. An accepted ride is allocated, or a stand or direct-driver pickup is recorded under the operator’s process.

What should we bring to the requirements discussion?

Bring anonymised examples of Booking or direct-pickup source and accepted journey details; Driver shift, vehicle identity and actual dispatch acceptance; Agreed fare basis, payment mode and reported trip events. 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. Record actual taxi assignments and ride outcomes so dispatch, fares and shift collections share the same trip references. 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 provide driving directions, certify readiness, track live location by default or establish a driver’s arrival or earnings.

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. Each actual ride identifies its source, driver and vehicle. Use this check when reviewing the first working version.

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