For chauffeur operators

How to Manage Affiliate Chauffeur Jobs: Handoffs, Changes & Billing

By Adam Benbader, Founder, LuxDispatch

Practical guidance for chauffeur operators. Example is fictional.

A farm-out is a ride you arrange for another chauffeur company to operate. For the receiving company, it is a farm-in. The handoff needs to cover more than the initial booking: later pickup changes, chauffeur instructions and affiliate billing still need clear ownership.

When is an affiliate handoff complete?

Check four things separately:

Sent → Accepted → Operationally synchronized → Financially reviewed

  • Sent: the offer has reached the intended company.
  • Accepted: that company has confirmed it will operate the ride.
  • Operationally synchronized: both offices and the chauffeur have the current instructions. Recheck this after a change.
  • Financially reviewed: customer charges and the affiliate amount have each been checked against their agreement; any unresolved differences and each payment status are recorded separately.

An unresolved charge still needs a decision. Reviewed does not mean approved or paid.

Confirm acceptance and the operating booking

An offer is a request, not confirmation that another company has taken responsibility for the ride. Agree who accepts it and how your office will know.

Then check that the receiving team can find the job in its working schedule. Compare the pickup date, local time and time zone, addresses, vehicle requirement and service notes. Keep both companies' references linked so nobody has to guess which booking a message concerns.

If the job is missing, check acceptance and where it should appear before sending it again. A second offer can create a second problem: duplicate bookings.

Keep later changes synchronized

Suppose the pickup moves from 10:00 to 11:00. Recording that in the arranging office is only part of the work. Who updates the operating booking? Who confirms the chauffeur has the new time?

Keep the change, requester, time and acknowledgement with the job. If it affects the price, record the approval or leave the question visibly open. A message being delivered is not the same as someone confirming the update.

Share the passenger details needed to operate the ride, with appropriate access. The affiliate does not need your customer price, margin or unrelated account information simply because it is doing the driving.

One ride, two financial records

From the arranging operator's perspective:

RecordWhat it tracks
Customer receivableWhat your client owes you
Affiliate payableWhat you owe the company operating the ride

These amounts can follow different rates and agreements. A customer payment does not establish that the affiliate has been paid. A completed ride does not automatically settle either record.

Review waiting time, extra stops, tolls and other reported charges against each agreement. A note from a driver is information to check, not automatic permission to bill the client. Keep disputed or unapproved extras separate from approved charges.

For the customer side, see how ride changes and extra charges reach the final invoice.

A handoff checklist: where could the record be unclear?

  • Was the job sent without a clear acceptance?
  • Did the booking change after acceptance without acknowledgement?
  • Does the chauffeur still have an older itinerary?
  • Do the two offices have different versions of the ride?
  • Are driver notes being treated as approved charges?
  • Was the customer total changed without reviewing the affiliate amount?
  • Is the ride marked complete while an amount or payment status remains unresolved?

These are checks to run, not assumptions that your operation has a problem.

A fictional corporate airport ride

  1. An assistant books for a passenger on a corporate account. Operator A farms out the ride; Operator B accepts.
  2. The assistant adds a stop. A records the request and any required price approval; B acknowledges it and updates the chauffeur.
  3. After completion, B reports tolls and waiting. A separately reviews the customer charge and affiliate payable.

The same job reference connects the history without requiring both companies to see the same commercial information. Passenger, booker and billed-to account remain distinct roles.

Try it on one job

Take one recent affiliate ride through these checks. Which answers are already clear? Where, if anywhere, does someone have to chase a confirmation or reconstruct a charge? If your current process handles it well, that is useful to know too.

Want to compare this workflow with your current process? LuxDispatch is booking, dispatch and billing software for chauffeur companies. You can request a private walkthrough using sample data.