You are double-booked, or out of area, or the booking needs a vehicle you do not run. The choice is to lose the job, hand it to a marketplace that will keep the customer, or pass it to another operator.
Passing it is right almost every time. The reason operators hesitate is a specific fear: the driver who covers the job goes back to that client directly, and an account that took three years to win is gone in one transfer.
Farming out is normal, and refusing it is expensive
Call it farming out, subbing out, passing on, affiliating — the practice is identical worldwide and older than any app. Corporate accounts, hotel contracts and airport work all produce demand that no single operator can match to their own fleet on any given day.
Operators who refuse to pass work end up declining bookings. Declining bookings is how you lose an account: a corporate client who hears “sorry, we cannot cover that” twice will find someone who always can, and they will move everything, not just the job you declined.
The risk of farming out is losing one client to a bad actor. The risk of not farming out is losing accounts to your own unreliability. The second is bigger and much more common.
Set the terms before the job, not after
Nearly every dispute comes from something that was never said out loud. Before a job moves, four things should be explicit:
- The client stays with the originating operator. Permanently, not for the duration of this booking. Say it plainly; do not imply it.
- The fare, agreed up front. A number, in a currency, before acceptance — not a conversation after the client is home.
- The standard required. Vehicle class, dress, meet-and-greet or kerbside, signage, whether the covering driver identifies themselves as your operation or their own.
- Who the client contacts. Usually you. If the covering driver's number goes to the client, you have made the introduction yourself.
In a chat message these get typed once, if at all, and are unreadable a week later. As structured fields on a job they are attached to every booking automatically, which is most of why structured job posts matter at all.
Who you pass to matters more than any agreement
No agreement survives a bad actor. What actually protects the account is the fact that the covering driver is a member of a community they do not want to be removed from.
That is the quiet mechanism behind every functioning chauffeur network: taking a client gets you removed, being removed cuts you off from a stream of work worth far more than one account, and everybody knows it. Reputation is enforceable in a community where members will see each other at the same terminal next week — and unenforceable with a stranger from an open Facebook group.
What to tell the client
Corporate and chauffeur clients handle this well when they are told, and badly when they discover it. A short, confident line before the job — that a partner vehicle from your network is covering this movement and you remain the point of contact — almost always lands fine. It reads as capacity rather than a gap.
Discovering it at the kerb, from a driver in a different car with a different company name, reads as a subcontractor you did not mention. Same fact, entirely different account outcome.
Keep a record, especially for corporate work
For corporate contracts this is not optional. When a client asks who drove their finance director on the 14th, “one of our partner drivers, I think” is the answer that loses the contract.
Minimum useful record per farmed-out job: which member covered it, when they accepted, the agreed fare, whether it completed, and any incident. That is exactly the record a group chat cannot produce and a job-based system produces automatically.
Warning signs a job should not be passed to someone
- They ask for the client's direct contact details when there is no operational reason.
- They want to invoice the client instead of you.
- They are vague about vehicle, licensing or insurance.
- They accepted instantly without asking a single question about a complex job.
- They are not really in your community — they are someone's cousin who was added last week.
Passing work is one of the highest-leverage things an operator does. Done inside a community with standards, verified membership and records, it is how a small operation covers demand far beyond its own fleet without ever risking an account.
DriversClan is built to make that safe by default. Join the founding communities.