A driver gets a LINE message twenty minutes before pickup: "Airport run, 2pm, one passenger." It looks complete enough to act on. It isn't. No flight number, so no way to check if the flight's delayed. No terminal. No passenger name, so no way to find the right person among a hundred other people holding signs. No note that the guest has two large suitcases and asked for a bigger vehicle.
None of that missing information stops the driver from leaving the office. It stops them from doing the pickup smoothly, and it's usually the reason they end up calling back to ask something that should have been answered before they left. Every one of those calls costs the office's time, the driver's attention on the road, and—often—a few minutes of the guest standing at arrivals wondering where their ride is. Call that combined cost the handoff tax: what a business pays every time information exists somewhere in the system but doesn't make it into the driver's hands.
If a driver has to call the office to find something out, the job order was incomplete before the trip ever started.
This piece breaks down where the handoff tax actually gets paid, what a complete job order needs to include, and why it matters more for partner bookings than direct ones.
The gap between "assigned" and "ready"
A trip showing up correctly on a dispatcher's schedule is a different thing from a driver having everything they need to execute it. The schedule confirms *that* a trip is happening. A job order needs to confirm *how*—and that's where a quick message tends to fall short, because it's written fast, from memory, by someone juggling three other things.
The fields that matter aren't exotic. They're the ones that are easy to assume "the driver probably knows" or "I'll tell them if it comes up": exact pickup time and location, passenger name, contact number, flight or reference number for airport jobs, number of passengers and bags, vehicle type required, and any special notes—a returning VIP guest, a child seat request, a language preference.
Why this matters more for repeat and B2B bookings
A one-off customer booking directly usually gives you everything up front because they're motivated to be found. Bookings that come through an agent, a hotel concierge, or a corporate account are different—the details often get relayed secondhand, shortened along the way, and by the time they reach the driver they've lost the specifics that were in the original request. This is exactly the relay a B2B portal is built to shorten, since a partner booking directly against your live schedule skips the secondhand retelling entirely.
This is also where returning guests get missed. A regular corporate client who always wants the same pickup point instead of the default one, or a VIP guest with a standing preference—if that context lives in someone's memory rather than the job order, it disappears the moment that person is off shift.
Picture a hypothetical transfer company called Tawee Transport, running mostly B2B airport transfers for three hotel partners. Before they standardized their job order format, roughly one in six driver call-backs traced to a detail the hotel concierge had mentioned in their original booking message but that never made it past the office relay. After switching to a fixed job-order template—same fields, every booking, no exceptions—those call-backs dropped to close to zero within a month, not because the drivers got better, but because the information stopped getting lost in the handoff.
What a complete job order actually prevents
It's not about paperwork for its own sake. Each missing field maps to a specific failure: no flight number means no way to know a flight landed early or late. No passenger name means standing at arrivals scanning faces. No bag count means showing up with a sedan for a group with golf bags—the same vehicle-type mismatch that shows up when own-fleet and supplier-network vehicles aren't tracked with the same data. No special note means a returning guest's usual request gets treated as new every time.
A driver working from a complete job order spends their attention on the road and the passenger, not on reconstructing details that should have been handed to them.
The Handoff Tax Playbook
- Fixed Field Template — every job order uses the same fields every time, regardless of how the booking arrived, so nothing depends on whoever happened to relay it.
- Zero-Assumption Rule — never assume a driver "probably knows" a detail from a previous trip; repeat it explicitly on every job order, every time.
- Returning-Guest Notes Travel With the Record — a standing preference or VIP note lives with the customer record, not with whichever staff member remembers it, so it survives shift changes.
- Call-Back Tracking — log what a driver had to call the office to ask, weekly; a rising pattern points directly at which field keeps getting dropped.
A restaurant with a delivery fleet pays the same handoff tax when a rider shows up without the gate code or gets the wrong floor—the fix is identical: a fixed template that doesn't rely on whoever typed the order remembering everything.
Completeness: what this all comes down to
If there's one word for what prevents a driver from being the last person to find out about a change, it's Completeness—not speed, not a friendlier message, just making sure nothing that was known when the booking was made gets lost between there and the driver's hands.
So here's the question worth asking after your next trip: if you asked your driver right now what they knew about that pickup before they left the office, would their answer match everything you actually knew? If there's a gap, that gap is the handoff tax you're still paying.
FAQ
What's the minimum information a driver job order needs?
Pickup time and location, passenger name and contact number, flight or reference number for airport jobs, passenger and bag count, required vehicle type, and any special notes—treat these as the non-negotiable baseline regardless of booking source.
Why do B2B and partner bookings lose more detail than direct ones?
Because the information passes through an extra relay—an agent or concierge takes the original request, then someone on your side re-types it into a job order—and each relay is a chance for a detail to be shortened, forgotten, or assumed unnecessary.
Does a standardized job order template slow down fast bookings?
No—once the fields are fixed, filling them in takes about the same time as writing a free-form message; the difference is that nothing gets skipped just because it wasn't top of mind that day.
How do you know if the handoff tax is a real problem for your business?
Track how often a driver calls the office mid-trip to ask something that should already be on the job order. If that number isn't close to zero, the tax is being paid regularly, even if nobody's been counting it.
What this looks like with NAWA Travel
NAWA Travel turns every confirmed booking—whether it came from the website, a B2B partner, or a direct call—into a driver job order with the details already attached: pickup time, location, passenger information, flight or reference numbers, and any special notes tied to the booking. Drivers see one complete record instead of a summary that leaves out what they'll actually need on the ground.
If your drivers are still calling the office mid-trip to fill in gaps a message left out, talk to us about your current dispatch workflow.