Promises of Performance™
From the First Mile to the Last
Article 5 of 8
Estimated Reading Time: 11 minutes
Target Audience: Motor carrier owners and executives, safety and compliance leaders, human resources professionals, driver managers, dispatchers, operations leaders, orientation and training personnel, professionals involved in driver onboarding, and professional drivers
Written by Brad Redden, Founder and Chief Compliance Advisor, CPO Consulting™ | Ask the Chief™
Published by: CPO Consulting™, LLC
Last Reviewed: September 28, 2026
Orientation Ends. Onboarding Doesn’t.
The videos have been watched.
The policies have been discussed.
The paperwork has been completed.
Questions have been asked and, hopefully, answered.
The driver understands the company’s expectations, knows who to contact when something goes wrong, and has been told what to do when the plan stops working.
Orientation is complete. Onboarding is not.
Now the driver moves to Operations. That may sound like a routine transition. It isn’t. It is another handoff.
And every handoff is a point where expectations can be preserved, clarified, or lost.
I came to believe that handoff was important enough that it should not happen accidentally.
In one operation where I oversaw driver orientation, I required Operations to take the new driver to lunch on the second day. The purpose was simple: get acquainted. Talk.
Operations could begin discussing its intentions for the driver after the handoff. The driver could begin developing a relationship with the people who would soon influence much of the daily work experience.
Then, when orientation was completed, the physical handoff was normally made by either me or the recruiter who had participated in the hiring and onboarding process.
That wasn’t ceremony for the sake of ceremony. There was continuity.
The driver did not simply disappear from one department and appear in another. Someone who understood how the relationship began helped transfer it to the people responsible for what came next.
Because the driver was about to discover whether the company described during hiring and explained during orientation was the same company encountered in daily operations.
This is where onboarding gets real.
Service the Product That I Installed
Throughout this series, I have used an analogy adapted from something I learned from my father.
He was a successful banking software salesman who later became an entrepreneur and keynote speaker. He understood that making the sale was only the beginning of a larger transaction. The relationship passed through three hands:
- The salesperson made the promise.
- The installer had to deliver it.
- The account manager had to live with and service it afterward.
A weakness at any one of those handoffs could affect the entire customer relationship.
The promise did not stop belonging to the company simply because the salesperson had moved on.
The same principle applies to driver onboarding.
Recruiting is the entry point. It can create expectations that follow the prospective driver into hiring. CPO Consulting™ is not a driver recruiting firm, and this series is not intended to teach carriers how to recruit drivers. Our concern begins when communication with a prospective driver creates expectations someone else in the organization will eventually have to fulfill.
Hiring and onboarding translate those expectations into an actual employment decision and prepare the driver for the job.
Orientation explains how the organization expects that job to be performed.
Then Operations inherits the relationship.
When I finished orientation and handed a driver to supervisors and Operations, my expectation was simple:
Service the product that I installed.
The driver is obviously not a product. The analogy describes the responsibility that transfers with the handoff.
To me, servicing what had been installed meant upholding the company’s policies and procedures, never knowingly risking a violation of law, respecting applicable industry best practices, and not asking someone to do something unsafe.
It also meant supporting the expectations that had already been established.
That did not always happen.
Sometimes Operations failed to hold true to the agreement.
Sometimes the driver changed an expectation midstream.
Sometimes circumstances changed and neither side could continue exactly as originally anticipated.
That distinction matters.
The objective isn’t to find a villain every time something changes.
The objective is to recognize the change, communicate about it, and keep the organization aligned around the standards and values that are not supposed to change with it.
The Driver Should Not Have to Decide Which Department Is Telling the Truth
Imagine what happens when the driver leaves orientation and begins hearing different versions of the company.
Safety says one thing. Dispatch says another. Human Resources explains a policy. A supervisor responds: “That’s not how we do it here.”
Orientation teaches a reporting procedure. Someone in Operations says: “Don’t worry about that.”
The driver was told to report equipment defects. The response is: “Just run it.”
The driver was told to call when something did not seem right. The first time the driver calls, someone treats the question like an interruption. I wish I could say drivers never came back to me and said: “That’s not what I was told in orientation.” However, they did. More times than I care to admit.
It does not take many experiences like that before a new employee begins asking a question management should never have created: Which version of this company is real?
That does not mean every additional instruction from Operations represents a contradiction. Operations may have information the orientation instructor did not have.
- Circumstances change.
- Customers change.
- Equipment fails.
- Plans change.
Clarification is normal. Contradiction is different.
The problem begins when different parts of the organization establish incompatible expectations and leave the driver to decide which one to follow.
Operations Is Where the Promise Meets Pressure
It is relatively easy to talk about safety in a classroom. The harder test comes when freight needs to move. A customer is waiting. A delivery window is getting tight. The driver’s available hours are disappearing. A tractor develops a defect. Weather deteriorates. A load is already late.
Someone has promised something to a customer.
In my experience, one of the most common choke points between Safety and Operations could be summarized simply: Take care of the customer and get the load delivered.
That objective is understandable. Customers matter. Freight matters. Revenue matters.
A motor carrier cannot remain in business very long without them.
The problem comes when the only perceived solution to an operational problem begins conflicting with the safety or compliance standards the organization has already established.
This is where the organization demonstrates what it actually values. Operational pressure is real. Good safety management should acknowledge that rather than pretending it does not exist. And Safety should not respond to every difficult operational problem with nothing more than: “No.”
A better response is: Let’s work through the challenge.
The load may ultimately be delivered late. That is unfortunate.
But a late load is generally preferable to a load that is not delivered at all because of a preventable incident, or a decision that jeopardizes someone else’s safety or adversely affects the carrier’s safety performance.
The question is not whether Operations will face pressure. The question is: What does management do with that pressure?
Does the organization work together to solve the problem within the standards it taught? Or do the standards begin changing because following them has become inconvenient?
That distinction goes directly to one of the principles underlying this series: Culture is communicated through management’s response when compliance, safety, or established standards become inconvenient.
The unexpected is normal in trucking. And when the unexpected happens, values are tested.
The truth can become apparent very quickly. “Stop. Call. Ask.” Only Works if Someone Answers Correctly
In Article 4, I explained one of the messages I gave drivers during orientation: Trucking is a dangerous job, but it should never be an unsafe job. Do not do things that are not safe. If you’re unsure: Stop. Call. Ask. Let’s make it safe. Then proceed.
But that instruction creates an obligation on the other end of the telephone. I have seen both extremes. I have seen Operations support a driver’s decision. And I have personally witnessed situations where, when supporting the decision became inconvenient, the driver was ridiculed or subsequently affected through load assignments.
Think about the lesson that teaches. We told the driver to call. The driver called. We told the driver to make the safe decision. The driver made it. Then the driver’s experience suggested there might be an operational price for doing exactly what we taught.
The next time that driver faces uncertainty, what have we taught the driver to do?
A company cannot tell drivers to speak up and then create a culture that teaches them not to.
This issue was not merely theoretical for me.
There were times when a driver called me after orientation because something did not seem right and helping that driver was unquestionably what I believed I was supposed to do.
But doing so could place me under adverse scrutiny or result in my decision being overridden, sometimes at the expense of the safety or compliance standard I was attempting to uphold.
That creates a problem much larger than a disagreement between Safety and Operations.
If Safety has upheld the organization’s expected standard and Operations conflicts with that standard, senior management ultimately becomes responsible for alignment.
Someone has to determine what the organization actually stands for.
There is also an important regulatory distinction here.
Poor management communication, disagreement, ridicule, or an unfavorable operational decision is not automatically regulatory coercion. Federal regulations establish specific requirements governing coercion under 49 CFR 390.6. That is an important regulatory boundary. But a strong safety culture should aim considerably higher than merely avoiding conduct that crosses the legal definition of coercion.
The better question is whether daily management behavior encourages safe and compliant decisions before a situation ever reaches that point.
The Informal Instructor May Be More Powerful Than the Orientation Instructor
Some of the most influential training a new driver receives will never appear on an orientation agenda.
It happens in parking lots. It happens over the telephone. It happens at the dispatch window. It happens in the shop. It happens when another driver says: “Forget what they told you in orientation. Here’s how we really do it.”
That sentence should concern management.
New employees watch experienced employees. They watch supervisors. They watch dispatchers. They watch Maintenance.
They notice which policies matter and which ones appear optional. They notice whose calls get answered. They notice which shortcuts are tolerated. They notice whether the person who raises a legitimate concern receives support or frustration.
Formal orientation tells the driver what the organization says it expects.
Informal instruction begins teaching the driver what the organization actually tolerates.
If those lessons conflict, the informal lesson often has one significant advantage: The driver sees it happening in the real world.
That makes organizational consistency essential.
Operations Needs Enough Information to Continue the Onboarding
A good handoff requires information. That was one reason I involved Operations before orientation was finished.
The Day 2 lunch gave Operations and the driver an opportunity to begin getting acquainted before the formal handoff. Operations could discuss its intentions. The driver could ask questions. Each could begin understanding the other before someone handed over a set of keys and a load assignment.
After orientation, either I or the recruiter who had participated in hiring and onboarding normally completed the physical handoff.
The process does not have to look exactly like that in every company. But the principle matters.
Operations needs to understand the driver it is receiving.
That may include the position the driver was hired to perform, relevant operational expectations established during hiring, work type, assigned equipment, schedule or home-time arrangements relevant to Operations, training already completed, additional training still needed, experience with particular equipment or work, identified coaching needs, and the appropriate contacts when questions arise.
But continuity does not mean unrestricted information sharing. Sensitive employment information, medical information, protected records, regulatory records, and other confidential information should remain subject to appropriate access controls and applicable requirements. The principle is simpler: The information necessary for the next person to perform their responsibility should survive the transition.
If Operations needs information to successfully integrate the driver into the operation, the organization should have a process for getting that information there.
Communication is the key. In my experience, that was also one of the clearest differences between good dispatchers or supervisors and everyone else. They communicated.
Don’t Make the Driver Carry the Handoff
A weak organizational handoff can turn the new driver into the communication system between departments.
- “Tell Dispatch what Recruiting told you.”
- “Explain to your supervisor what Safety said.”
- “Tell Operations what HR told you.”
- “Go back and ask them.”
The driver should absolutely participate in communication. Drivers have responsibilities too. They should ask questions, identify inconsistencies, provide accurate information, and speak up when something does not match what they understood.
And sometimes the driver is the party who changes the expectation. That matters too.
The promises in Promises of Performance™ have always been reciprocal.
A carrier cannot reasonably be expected to honor an agreement that the driver has materially changed without discussion any more than the driver should be expected to silently accept a materially different job than the carrier represented.
But management owns the organizational handoff.
The driver should participate in the handoff. The driver should not have to become the handoff.
When departments disagree, management should resolve the disagreement. The new driver should not have to negotiate between Safety, Human Resources, Dispatch, Maintenance, and Operations to determine which instruction controls. That is an organizational responsibility.
When Something Doesn’t Match, Resolve It Early
Not every inconsistency is evidence of dishonesty or poor intent.
- People misunderstand.
- Information gets lost.
- Freight changes.
- Customers change.
- Equipment fails.
- Schedules change.
- Sometimes circumstances outside anyone’s control affect continued operations and revenue generation.
That is trucking. An expectation that was reasonable when discussed may become impossible later. What matters is how the organization responds when the difference becomes apparent.
- Stop.
- Clarify.
- Identify what was communicated.
- Determine what is actually possible.
- Resolve the difference.
- Then communicate the answer consistently.
Sometimes the correct answer may be: “What we told you has changed.”
Say so. Explain why. Determine what needs to happen next. Credibility does not require perfection.
It requires candor when reality changes.
Trying to convince the driver that an earlier conversation never happened rarely fixes the underlying problem.
It usually creates another one.
Management Alignment Is Part of the Safety System
It would be easy to treat all of this as an employee-relations issue. It is more than that.
Conflicting organizational instructions can influence decisions involving Hours of Service, vehicle condition, accident and incident reporting, cargo handling, documentation, customer interaction, and escalation.
That makes alignment more than good communication. From a management perspective, it is part of an effective safety and compliance system.
Safety cannot operate as an island. Neither can Operations.
Operations understands freight, customers, schedules, equipment utilization, and the realities of moving the business.
Safety and Compliance understand regulatory obligations, risk, company standards, and the consequences when something goes wrong.
Maintenance has its responsibilities. Human Resources has its responsibilities.
Each function sees part of the operation. The objective should not be for one department to “win.” The objective should be for the organization to solve operational problems without abandoning the standards it established.
Sometimes Safety needs to understand the operational problem better. Sometimes Operations needs to understand why a proposed solution creates unacceptable safety or compliance risk. Sometimes the driver needs to understand that circumstances have legitimately changed.
The strongest organizations create enough communication between those functions to find another solution.
But when Safety has upheld an established standard and another part of the organization attempts to override it, senior management cannot remain outside the disagreement.
Leadership owns alignment. That does not mean senior management should automatically side with one department. It means senior management must ensure that the company is operating according to the laws, policies, procedures, safety expectations, and organizational values it claims to follow.
The Promise → The Process → The Practice
Article 5 is where the framework underlying Promises of Performance™ becomes particularly visible.
The Promise: What the carrier and prospective driver communicated and reasonably understood before and during the employment decision.
The Process: How the organization translated those representations into hiring, qualification, preparation, documented expectations, orientation, and operational readiness.
The Practice: What actually happens when the driver begins working.
Do Dispatch, Safety, Human Resources, Maintenance, supervisors, and management substantially reinforce what the driver was told?
Does the driver continue honoring the commitments made during the hiring and onboarding process?
Or does daily experience begin rewriting the Promise and the Process?
Perfect consistency is unrealistic. People make mistakes. Circumstances change. Operations are complicated.
And when there is a risk of a negative outcome, people naturally want to avoid it. That is where judgment gets difficult.
Sometimes the desire to avoid conflict, protect a customer relationship, preserve revenue, keep a driver happy, or simply make today’s problem go away can lead otherwise reasonable people toward poor decisions.
There is no perfect formula that eliminates those moments. That is precisely why alignment matters. The goal is not perfection. The goal is for everyone involved to be on the same page, adhering to the same fundamental values when judgment becomes necessary.
Realistic promises. Processes capable of supporting them. And everyday practice that reasonably reflects what both sides agreed to.
The Chief’s Closing Thought
After nearly two decades of watching drivers move from hiring through orientation and into Operations, I wish I could tell you there is a perfect system for making the handoff work.
There isn’t.
I tried to create continuity. Operations spent time with the driver before orientation ended. Either I or the recruiter who had participated in the hiring and onboarding process physically completed the handoff.
I taught the standards.
I told drivers to stop, call, and ask.
I expected Operations to service the product that had been installed.
Sometimes it worked exactly as intended. Sometimes Operations failed to hold true to an expectation. Sometimes the driver changed the expectation midstream. Sometimes a customer, equipment failure, freight problem, or other circumstance changed the situation for everyone. And sometimes the greatest challenge was simply human nature.
When people see the possibility of a negative outcome, they often try to avoid it.
- Nobody wants the customer upset.
- Nobody wants the load late.
- Nobody wants the truck sitting.
- Nobody wants the driver unhappy.
- Nobody wants the difficult conversation.
But avoiding today’s conflict at all costs can create tomorrow’s safety, compliance, operational, or personnel problem. That is what the handoff ultimately taught me.
There is no perfect answer.
It requires people to communicate. It requires departments to be aligned. It requires the driver and the carrier to continue honoring their respective commitments. And it requires everyone involved to adhere to the same fundamental values when the easy answer disappears.
Because the unexpected is normal in trucking. When it happens, values get tested. And the truth about an organization’s culture can become apparent very quickly.
Every handoff is a point where expectations can be preserved, clarified, or lost.
The handoff from Orientation to Operations may be where everyone involved first discovers which one it is going to be.
Looking Ahead
In Article 6 of Promises of Performance™, The First 30–60 Days: When Safety Culture Becomes Real, we will follow the driver beyond the initial handoff.
A new driver is watching.
The organization is teaching its culture whether management intends to or not.
Article 6 will examine the period when the expectations established through hiring, onboarding, orientation, and the operational handoff begin becoming habits or disappearing altogether.
Leave a Reply