Skip to main content
GullySystem
Automotive

Fuel and Driver Records for Airport taxi services

Keep vehicle fuel entries and driver records available for operating review.

Assets and Fleet

Does this function belong in your operation?

Use when your business operates vehicles and is responsible for fuel or driver administration.

A vehicle is refuelled or a driver's operating details change.

Identify equipment or vehicles used to support “Airport pickup with flight tracking”. Vehicle and driver functions require a fleet operation; an equipment register does not by itself justify trip management.

Bring the records the workflow depends on.

  • Vehicle and driver identifiers
  • Fuel receipts and meter readings
  • Required driver documents

Outputs to check

  • Vehicle fuel and meter register
  • Driver document and assignment record
  • Consumption and advance exception list

Follow the fuel and driver records workflow.

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

  1. 1. Register operating identities

    Maintain the vehicle and driver references used by entries.

  2. 2. Capture fuel

    Record the receipt, amount, quantity and meter reading.

  3. 3. Check consistency

    Review duplicates and impossible reading sequences.

  4. 4. Reconcile activity

    Compare fuel with relevant trips and settle authorised advances.

  5. 5. Maintain driver records

    Review document dates and send any operating restriction decision to the fleet owner.

Who uses the module, and who approves?

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

Driver

Photographs the slip at the pump and enters the meter reading.

Dispatch lead

Watches consumption against the trips they allotted.

Accounts assistant

Settles the fuel station bill, recovers advances and keeps the driver ledger clean.

Owner

Reviews vehicle costs and unexplained consumption differences using the recorded trips and readings.

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.

Meter replaced

Record the change and use a reviewed distance basis rather than comparing incompatible readings.

Fuel slip duplicated

Hold the claim and reconcile date, vehicle and receipt reference.

Driver document expires

Flag the record and send the operating decision to the authorised fleet manager.

Can this work independently?

These records can be maintained independently with vehicle and driver identifiers. Trips provide operating context, expenses provide settlement and HR may hold employment details. Fuel calculations need valid distance readings; they do not by themselves prove theft, efficiency or driver performance.

Systems and records it connects with

  • Vehicle and trip management: Vehicle assignments, trip activity and completion records.
  • Fixed asset register: Asset identifiers, custody and acquisition records.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.
  • Expense tracking: Approved cost entries, evidence and payment references.

Configure, test and introduce the workflow.

  • Send the vehicle list, driver details and licence dates. We write back what is missing.
  • Tell us which pumps and cards you use. A fill screen arrives set up for those sources. Start small. Drivers on a handful of vehicles enter fills for a while, and a mileage view comes back to compare with what you expected.
  • Remaining drivers see the phone screen. Dispatch and accounts join them, and the group leaves trained.

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.

  • Fuel entries link to a vehicle.
  • Invalid meter sequences are flagged.
  • Driver document dates remain visible for review.
Airport taxi services

How the business operates.

An airport taxi operator takes advance bookings, counter requests or travel-desk orders and allocates suitable cars and drivers to pickup times. The passenger, the person booking and the paying organisation can be different people. Flight changes, terminal instructions and waiting charges affect dispatch and billing. This illustrative operating model fits an operator managing bookings and trips; a marketplace matching independent drivers requires a different commercial and technical scope.

Booking desk and account service

Record passenger and booker contacts separately, alongside flight, terminal, destination, vehicle class and fare agreement. A hotel or corporate account needs its billing reference and the person authorised to change a booking.

Dispatch and holding-lot coordination

Allocate a driver and car against pickup time and availability. Where the operator runs a holding-lot queue, keep entry and release decisions visible. A revised arrival time needs acknowledgement rather than an assumed change.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Booking number, booker, passenger and payer contacts
  • Flight, terminal, pickup point, destination and vehicle class
  • Fare rule, waiting allowance and approved extra charges
  • Driver allocation, vehicle assignment and acknowledgement

Operational bottlenecks to check

The flight changes but dispatch does not

A new arrival time is useful only if the dispatcher and assigned driver receive and acknowledge it. Define how the desk responds when a feed or message is unavailable.

Booker and passenger receive different information

A family member or travel desk can hold the booking while the traveller's phone is offline. Specify which details reach each contact and who is authorised to request a change.

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 and confirm the booking

    Record who is travelling, who booked and who pays. Confirm the pickup instructions and fare basis before treating the car request as accepted.

  2. 2. Review arrival changes

    Update the expected arrival through the agreed manual process or supported feed. Record who acknowledged the changed pickup time and whether the original car and driver remain available.

  3. 3. Allocate the car and driver

    Check availability and the operator's readiness criteria before dispatch. A reassignment needs a recorded reason and updated information for the people relying on the earlier confirmation.

  4. 4. Perform and record the trip

    Capture pickup, destination and completion against the same trip number. Waiting, tolls and other extras need the agreed evidence and approval treatment rather than an unlabelled amount added at settlement.

  5. 5. Reconcile the shift

    Compare trip records with coupons, collected fares and approved expenses. Keep an unexplained difference visible with an owner instead of changing the fare retrospectively to make the cash total fit.

  6. 6. Bill accounts and resolve exceptions

    Prepare corporate or hotel statements from the agreed trip records. Follow disputed charges, cancellation adjustments and missing trip evidence before marking the account period complete.

Industry reports to connect with

  • Bookings and completed trips by pickup period, destination and vehicle class
  • Unassigned, reassigned, cancelled and missed-pickup bookings
  • Driver and vehicle availability against committed trips
  • Shift settlement differences and unapproved extra charges

Questions before implementation.

When should airport taxi services consider fuel and driver records?

Use when your business operates vehicles and is responsible for fuel or driver administration. A vehicle is refuelled or a driver's operating details change.

What should we bring to the requirements discussion?

Bring anonymised examples of Vehicle and driver identifiers; Fuel receipts and meter readings; Required driver documents. 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. Keep vehicle fuel entries and driver records available for operating review. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The records do not independently verify licence validity, fitness to drive or fuel misuse.

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. Fuel entries link to a vehicle. Use this check when reviewing the first working version.

Talk to us

Discuss fuel and driver records 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