The Trip You Quoted Isn’t the Trip You Ran. Who Catches the Difference?

By Christian Riddell

Motorcoach operators are pretty good at pricing trips.

Actually, I would argue most are very good at it.

We know deadhead. We understand minimums. We know what driver time costs, what wait time costs, what an extra day costs, and what happens when somebody wants to leave at 4:30 in the morning because apparently airports only work before the sun comes up.

We have spent decades refining the math.

So when people talk about revenue leakage in charter operations, the natural instinct is to look at the quote.

Did we price enough hours?

Did we account for deadhead?

Did we include parking?

Did we charge the right minimum?

Those are all good questions.

I just don’t think they are where a lot of the money is disappearing.

Because the trip you quoted and the trip you actually ran are very often two different things.

And somewhere between those two is a remarkably expensive little gap.

The itinerary was perfect right up until people got involved.

Here is a completely hypothetical trip that has probably happened at your company sometime in the last seven days.

The charter order says:

Pick the group up at the convention center.

Take them to dinner.

Take them back to the hotel.

Simple.

Beautiful.

Almost suspiciously easy.

Then the trip actually happens.

The group leader gets on the bus and says, “Before dinner, could we make one quick stop?”

Every driver in America knows that the words “one quick stop” rarely have anything to do with either “one” or “quick.”

But the driver takes them.

Because that is what good drivers do.

Then dinner runs late.

On the way back, somebody realizes they need something from a shopping center.

Twenty minutes turns into forty.

An accident closes the interstate, so the driver reroutes.

The four-hour trip you sold becomes five and a half or six hours of actual service.

Nothing went wrong.

In fact, from the customer’s perspective, everything may have gone exactly right.

The driver was accommodating.

The group got where they needed to go.

Dispatch handled whatever came up.

Everyone got home safely.

Five stars.

The question is not whether your team served the customer well.

The question is:

Who caught the difference between what you sold and what you delivered?

That is a very different question.

Follow the trip through your company.

Think about your process for a minute.

Not the process written in the handbook.

The real one.

A customer asks for a trip.

Sales quotes it.

The customer books it.

Operations builds it.

Dispatch sends it.

The driver runs it.

Then eventually somebody invoices it.

There are probably several people involved, multiple systems, some emails, a text message or two, maybe a handwritten note, and depending on the company, at least one piece of paper whose continued survival in 2026 is nothing short of inspirational.

Now imagine that extra restaurant stop happens.

Where does that information go?

The driver knows.

That much we can establish.

Does dispatch know?

Maybe.

Did the driver call?

Did they text?

Was it entered somewhere?

Was somebody in dispatch dealing with six other things when the call came in and simply make a mental note to deal with it later?

If it did get documented, what happens next?

Does sales see it?

Does accounting?

Does whoever creates the invoice know the trip ran an hour and a half longer than planned?

And, perhaps most importantly, does that person know before the invoice goes out?

This is where operators need to get curious.

Because revenue leakage is rarely caused by one person making one big, ridiculous mistake.

It usually happens through perfectly reasonable people doing their jobs inside a process with a weak handoff.

The driver handles the change.

Dispatch keeps the trip moving.

Accounting invoices what is in front of them.

Everyone does exactly what they are supposed to do.

And $125, $250, $400 or more of service quietly walks out the door.

No alarms.

No flashing lights.

No accounting scandal.

Just a slightly less profitable trip.

Multiply that across hundreds or thousands of trips and suddenly “slightly” becomes a very interesting word.

The money wasn’t lost when you quoted it.

This distinction matters.

If you quoted the trip correctly based on the itinerary the customer gave you, your pricing system did its job.

The leak happened later.

It happened when reality changed and your business failed to change with it.

That is fundamentally an operational problem, not a pricing problem.

We spend a tremendous amount of time in this industry asking whether our rates are high enough.

That conversation absolutely matters.

But you can raise your rates 5%, develop the world’s greatest pricing model, create beautiful rate tables, perfectly calculate demand, and still give away service every single day if nobody reconciles what was planned with what actually happened.

That is like owning a restaurant, carefully costing every ingredient in a steak dinner, then letting customers order an extra appetizer, another drink and dessert without putting them on the check.

The steak pricing isn’t the problem.

The check is.

Now comes the uncomfortable part: can you prove it?

Catching a variance is only half the job.

Let’s say accounting discovers two weeks later that the trip ran 90 minutes long.

Great.

Now what?

Someone calls the customer.

“Hi, we need to add an hour and a half of additional time to your invoice.”

The customer says:

“Why?”

And suddenly everyone begins an archaeological expedition.

Someone searches through dispatch notes.

Someone calls the driver.

Someone finds a text message.

Someone vaguely remembers the group stopping somewhere.

The driver says, “Oh yeah, they asked me to take them to a shopping center after dinner.”

Perfect.

Which shopping center?

“I don’t remember.”

How long were they there?

“Maybe 30 minutes?”

Who requested it?

“The group leader.”

Which group leader?

“The lady in the red jacket.”

Excellent.

Please tell accounting to add “Lady in Red Jacket — approximately 30 minutes” to the supporting documentation.

I am sure the customer will immediately cut the check.

This is where operational sloppiness becomes a customer-service problem.

Because even if you are completely entitled to the additional charge, asking a customer to reconstruct a trip three weeks later creates friction.

From their side, it feels like a surprise charge.

And nobody likes surprise charges.

Timing changes the entire conversation.

Now run the same scenario differently.

The group leader asks the driver for the extra stop.

The driver records the change when it happens.

Dispatch can see the trip varying from the plan while the trip is still active.

The additional time or stop is documented against the original itinerary.

The customer is notified quickly if appropriate.

Suddenly the conversation sounds completely different.

“Just a heads-up — the additional stop requested this afternoon added 45 minutes to today’s service and will be reflected on the final invoice.”

That is not a confrontation.

That is normal business.

The group leader remembers asking for it because they asked for it three hours ago.

Everybody understands what happened.

There is documentation.

There is context.

And the customer has not spent three weeks mentally closing out the trip only to have someone reopen it with another charge.

Same service.

Same customer.

Same money.

Entirely different customer experience.

This is why getting actual trip information back into the business quickly is not simply an accounting issue.

It is part of good customer service.

So where does the information disappear in your company?

Here is the exercise I would encourage every operator to do.

Pick ten recently completed trips.

Not the easy airport transfers.

Pick the ugly ones.

The multi-day trip.

The convention movement.

The athletic team.

The wedding.

The tour where somebody inevitably decided that the itinerary was more of a suggestion than a plan.

Pull up what you quoted.

Then find out what actually happened.

Compare:

• Actual start time versus scheduled start time.
• Actual finish time versus scheduled finish time.
• Stops added or removed.
• Wait time.
• Route changes.
• Additional mileage.
• Changes requested by the customer.
• Any operational adjustment that could affect what the trip should ultimately cost.

Then trace those changes through your company.

Where were they recorded?

When did dispatch know?

When did billing know?

What documentation exists?

Was the invoice adjusted?

If it wasn’t, why not?

That last question is the important one.

Not because somebody needs to get in trouble.

Quite the opposite.

This is not about catching employees doing something wrong.

It is about catching processes that make it unnecessarily difficult for good employees to do things right.

You may discover your drivers are documenting everything beautifully, but nobody in billing ever sees it.

You may discover dispatch knows exactly what happened, but the information lives in a text thread.

You may discover accounting sees trip sheets three days after the invoice has already been created.

You may discover drivers are expected to remember every deviation at the end of a 14-hour day and write it on a piece of paper.

If that is the process, I would suggest the problem is not your drivers’ memory.

The problem is the process.

Actual versus planned should not be a detective story.

This is one of the areas we have spent a lot of time thinking about at TBN.

The idea is remarkably simple.

You already know what was supposed to happen.

Your system has the itinerary.

What you need next is a clear picture of what actually happened.

That means giving the driver a practical way to capture actuals against the plan from the road, making meaningful variances visible to dispatch while the trip is still happening, and carrying those differences forward into billing with the supporting documentation attached.

Not because every five-minute deviation should become a charge.

It shouldn’t.

Good operators use judgment.

Sometimes taking care of the customer means absorbing something small. Sometimes traffic is traffic. Sometimes the right business decision is to simply take care of somebody.

That discretion should remain yours.

But there is a huge difference between choosing not to charge for something and never knowing it happened.

One is customer service.

The other is leakage.

And you cannot manage what you cannot see.

This may be one of the most profitable reports you never run.

We talk constantly about utilization.

We talk about revenue per coach.

We talk about driver costs, fuel costs, insurance, maintenance, pricing and margins.

We should.

Those numbers matter.

But I would add another question to that list:

How much service did we provide last month that never made it onto an invoice?

Most operators cannot answer that today.

That does not mean the number is enormous.

It may not be.

But I suspect almost every company has a number.

And until you measure it, you simply do not know.

Maybe you find $500.

Maybe you find $5,000.

Maybe you discover the bigger problem is not the dollars at all, but that customers are receiving unexpected adjustments weeks after trips because information is moving too slowly through the company.

Any of those findings are useful.

Because once you can see the leak, you can decide what to do about it.

That is the point.

Technology should not make every decision for an operator.

It should put better information in front of operators while there is still time to make the decision themselves.

That is especially true here.

Your driver knows what happened.

Your dispatch team knows how the day unfolded.

Your billing department knows what should be invoiced.

The opportunity is simply connecting those three realities before the information gets old, fragmented or forgotten.

We spend a lot of energy making sure the trip we quote is profitable.

Maybe it is time we spend just as much making sure the trip we ran was profitable too.

Pull ten trips.

Compare the plan to the actual.

Follow every variance all the way to the invoice.

I have a feeling you will find the weak handoff pretty quickly.

And once you see it, it becomes remarkably difficult to unsee.

#TBNDrives #TheFutureIsHere