Skip to main content
GullySystem
Logistics

Business solutions for Fleet operators

Explore software for work such as “Recurring passenger route and shift-duty coordination”. Review each business function below, including when it fits and what to check before implementation.

Fleet operators

How the business operates.

A passenger fleet operator sells recurring transport duties or whole-vehicle journeys using vehicles it operates or directly coordinates. A client account can cover employee shift routes, group travel or dedicated chauffeured duties, each with its own accepted scope. The operating record connects that commitment to actual vehicle and driver assignments, interruptions and supported charges. This requirements example follows the passenger-hire emphasis of this trade and overlaps corporate cab and bus-rental services. It does not describe a tracking-software supplier or assume the customer owns the fleet. School transport, self-drive hire and goods delivery need their own confirmed operating scope.

Client contracts and duty requests

Retain the accepted route or hire terms, customer approver and changes. A standing contract does not prove every duty was requested, performed or authorised for extra billing.

Fleet allocation

Match each duty to the actual vehicle, driver and reviewed readiness information. Keep maintenance blocks, conflicting jobs and proposed partner supply visible until the responsible operator confirms the assignment.

Duty execution and handover

Record actual start, completion and interruptions against the current instruction. A replacement vehicle or driver needs its own handover record; a passenger’s acknowledgement does not change the client’s purchasing authority.

Operating and client accounts

Reconcile fuel and supported operating expenditure separately from customer charges. The cost of a missed or changed duty does not automatically become a billable extra under the client agreement.

The records that hold the operation together.

  • Client agreement, route or duty reference and authorised requestor
  • Accepted vehicle class or named-unit commitment with actual assignment
  • Driver assignment history, operating-review references and maintenance blocks
  • Actual duty times, distance readings and interrupted or cancelled service evidence
  • Fuel receipts, reading corrections and approved operating-cost references
  • Customer billing decisions, verified receipts and separately reconciled driver advances

Operational bottlenecks to check

Standing routes hide changed instructions

A client adds a stop or shift through a passenger contact while accounts holds the old scope. Preserve the request and actual approver before changing the continuing commitment.

One vehicle appears available twice

A group journey, regular route and proposed partner duty can overlap. Record confirmed assignments and readiness blocks before offering capacity to another client.

Fuel differences become accusations

Missing readings, empty positioning runs and duplicated receipts distort comparisons. Keep the review factual and do not infer driver misconduct from a single consumption figure.

Substitution removes the original promise

An available replacement can differ from the accepted class or named vehicle. Retain the operational review and customer decision rather than overwriting the original booking.

Follow the work across teams.

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

  1. 1. Define the contracted service

    Record the client’s route, shift or group itinerary and the agreed vehicle commitment. Confirm whether a named unit is required or an accepted class can fulfil the duty.

  2. 2. Create the actual duty

    Link each requested occurrence to the applicable contract or accepted hire instruction. Retain customer approval for changes rather than treating an informal passenger request as a new commercial order.

  3. 3. Review and allocate resources

    Check current assignments and operational restrictions with the responsible owner. A document stored on file or a free calendar slot does not itself establish vehicle or driver readiness.

  4. 4. Capture execution and interruptions

    Retain actual duty evidence and changes of driver or vehicle. Keep the original commitment visible when a breakdown or altered shift requires a reviewed alternative.

  5. 5. Reconcile costs and client work

    Match fuel, readings and approved expenditure to the actual vehicle activity. Apply customer charges under accepted terms while preserving cancelled duties, disputed extras and unverified receipts.

  6. 6. Review the continuing account

    Use supported duty and cost records when the client reviews routes or hire terms. A renewal proposal stays separate from an accepted extension and from future resource commitments.

Roles and responsibility boundaries.

Client account coordinator

Maintains accepted route or hire terms and checks the authority behind changed duties before sending them to dispatch.

Fleet controller

Assigns actual vehicles and drivers while preserving conflicts, maintenance restrictions and unacknowledged partner requests.

Driver or duty supervisor

Records the actual duty and relevant handovers, referring changed passenger requests through the agreed operational and commercial process.

Vehicle and driver administrator

Keeps operating identity, document references and review dates current, passing readiness questions to the responsible qualified decision-maker.

Accounts reviewer

Checks evidenced costs and accepted billable work, retaining driver advances and customer receipts as separate financial records.

Reports your managers need.

  • Client duties by accepted, completed, interrupted and cancelled outcome
  • Vehicle and driver conflicts with unconfirmed partner requirements
  • Fuel and reading exceptions linked to actual operating activity
  • Supported duty charges awaiting client or accounts review
  • Contracts approaching their actual review dates with unresolved changes

Connections to scope

  • Assess imports from existing duty sheets, vehicle registers and accounts using stable client, vehicle and duty references.
  • Tracking, fuel-card, roster and messaging connections need confirmed support and access authority; a manually recorded duty does not establish any live connection.

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.

Separate client service models

Compare a recurring employee route with a whole-vehicle hire. Identify what the operator directly controls and what any partner must acknowledge.

Reconcile resources and obligations

Match current client commitments to actual vehicle and driver records. Keep unclear readiness and missing documents assigned for review without assuming an uploaded file grants permission.

Test a changed duty

Try a new shift, a passenger-requested stop and a substituted vehicle. Check customer approval, resource acceptance and actual outcome as distinct decisions.

Review operating and billing records

Trace fuel and duty evidence through cost review and customer billing. Preserve positioning activity, driver advances and disputed extras instead of netting them into a single trip balance.

Limitations to settle before implementation

  • This passenger-hire scope excludes school pupil custody, individual-seat ticketing, self-drive rental and freight operation. Those models need separately reviewed workflows.
  • The operator and qualified advisers decide vehicle suitability, driver eligibility and operating obligations. Record dates and assignments do not establish those decisions.
  • No replacement availability, arrival promise, route optimisation, live tracking, fuel-saving result or automatic payroll deduction is created by these records.
  • Passenger route, address and contact details require restricted operational use. Partner copies and retained duty evidence need their own access and retention decisions.

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.

  • Recurring passenger route and shift-duty coordination
  • Whole-vehicle hire and actual resource allocation
  • Vehicle fuel, driver references and duty-cost reconciliation
  • Client transport agreement review and supported service 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