Trust Is Given, Not Earned: The Operator Philosophy That Made a Multi-Station Operation Possible
Most of the contractors I meet operate from the same assumption: trust must be earned.
Drivers have to prove themselves before they get autonomy. Managers have to demonstrate judgment before they get authority. Vendors have to earn payment before they get paid quickly. Trust is the reward at the end of a long evaluation period, granted only when there is sufficient evidence to justify it.
This is the conventional posture. It feels safe. It also caps the operation at the size of one person’s ability to monitor everything.
The operators I respect run on the opposite assumption.
Trust is given, not earned. It is extended first, before the evidence exists. It is the precondition for any operation that scales beyond one human’s personal supervision — which, in a FedEx Ground contract, means any operation at all.
This article is about why that posture works, what it looks like in practice, and what to do when trust is broken.
The math forces the philosophy
A FedEx Ground contractor cannot personally deliver a contract’s worth of packages. The volume is too high. The geography is too spread out. The day is too long. The work is too physical.
You either trust drivers to do the work, or you don’t have a business.
This is more obvious than it sounds, but it is genuinely underweighted in how most new contractors think about their operation. They want to control every detail. They want to inspect every package. They want to verify every scan. They want to second-guess every routing decision.
They cannot. The math will not allow it.
One contractor + zero trust = one route’s worth of work. One contractor + thirty drivers trusted = thirty routes’ worth of work.
Trust is the scale mechanism. There is no other.
You cannot scale through better software, harder negotiation with FedEx, more clever route design, or any operational improvement on the margin. Those things help. But the central fact is that scale comes from being able to step out of the truck and trust someone else to drive it. Everything else is optimization around that one fact.
Trust is not naive
The contractors who hear “trust is given, not earned” sometimes interpret it as “trust everyone, hope for the best.” That is not what this is.
Extending trust is the default posture. Making trust safe is the operator’s job.
Trust without smart system design is just hope. Smart system design without trust is micromanagement that doesn’t scale. The two go together. The system is built so that when you extend trust, the outcomes are usually good. Specifically:
Daily pay rewards efficient drivers, not slow ones. A driver paid daily has every incentive to finish the route efficiently and safely. A driver paid hourly has the opposite incentive — slower is more pay. Daily pay aligns the driver’s incentive with yours, so extending trust to a daily-pay driver is safer than extending trust to an hourly driver.
Stop bonuses give a clean performance signal. When you pay a clear bonus at a stop threshold, you are telling the driver what you value and rewarding them when they deliver. The conversation is honest. The driver knows what they are working toward.
Fast pay (Friday, every Friday, on time) removes a recurring source of friction. A driver who depends on the Friday paycheck to fill the gas tank and feed the family is in a different mental state than a driver who worries about whether they will be paid this week. The first driver is yours to coach and develop. The second driver is looking for the next job.
Paying above market attracts the kind of people you want to trust. This sounds simple but most contractors don’t do it. They try to win on price. They lose on people. The contractors who pay above the local market rate attract better candidates, see lower turnover, and have less reason to second-guess the people they hired.
VEDR and telematics verify; they do not surveil. A camera in the truck is for safety coaching and accident reconstruction, not for catching drivers doing wrong. The distinction matters. Drivers know the difference between “the camera is here to help us all drive safely” and “the camera is here because we don’t trust you.” The first culture produces engaged drivers; the second produces drivers who find ways around the system.
BCs get authority and accountability. A Business Contact who has decision-making authority and is accountable for the outcomes runs the station the way it needs to be run. A BC who has to call you for every decision is not a manager — they are a phone tree.
Each of these design choices makes trust safe. None of them removes the need for trust. The system reduces risk; the trust is still extended.
The compounding effect
There is a feedback loop in how trust is extended.
People rise to the level of trust you extend to them. People also sink to the level of suspicion you extend to them.
A driver who knows you trust them treats the truck better. They scan more carefully. They handle the customer better. They drive more defensively. They take a small extra step on the loading dock to make sure the right package is on the right truck. They do these things because they have been treated as a capable adult and they are responding accordingly.
A driver who knows you watch them like a hawk does the minimum. They scan when they have to. They drive the route as fast as legally possible. They argue about coaching events. They are looking for the next job. They are not, in any real sense, on your team — they are renting their labor to you by the hour and they treat it that way.
This is not a hypothesis. It is the observable difference between operations where the contractor extends trust and operations where the contractor doesn’t. The first kind of operation has lower turnover, better customer feedback, fewer accidents, and better margins. The second kind of operation has constant turnover, escalating drama, and a contractor who is exhausted.
The compounding effect goes both ways. Trust produces trustworthiness. Suspicion produces resentment.
Trust is freely given, but it is not infinite
The thing that makes trust-as-default work is the corollary: when trust is broken, you act fast.
Trust is given freely. It is not, however, irrevocable. When someone breaks trust — a drug-test failure, a fraud event, repeated unsafe behavior, a no-call/no-show pattern, a fundamental dishonesty — you act fast.
This is why the introductory period in the employee handbook matters. The first 30 to 90 days are a working trust trial. Extend trust generously during this window. If the new hire turns out not to be a good fit, terminate within the window without overthinking it.
This is also why your BCs should have authority to terminate trainees in the first weeks. A BC who has seen hundreds of drivers come through the station has pattern recognition that even they cannot fully articulate. When their gut says “this driver is not going to work out,” it is usually right. Empowering BCs to act on that pattern recognition — before the new hire becomes a workers’ comp claim or a customer incident — saves real money and real drama.
The mistake most contractors make is the opposite. They extend trust slowly and reluctantly to new hires, then once the introductory period ends they keep marginal employees long past the point where it was clear the fit was wrong. Both halves of that posture are wrong. The right approach is the inverse: extend trust generously at the start, and remove that trust quickly when it is clearly broken.
What this looks like day to day
Trust as a default operating philosophy has practical implications. The ones that show up most often in my operation:
I do not call drivers when they are on a route. If a driver calls me mid-route, the BC handles it. I will not engage. The driver has been trusted to do the route; trying to micromanage them mid-shift signals the opposite. I call back when they are off route.
I do not second-guess BC decisions made in my absence. If the BC handled a problem on Tuesday while I was unreachable, I do not Monday-morning quarterback it on Wednesday. The decision was theirs to make. If they made the wrong call, we talk about it as a learning conversation, not a reversal.
I do not withhold pay until I am “sure” everything was right. Friday is Friday. Payroll runs. If a discrepancy surfaces, we deal with it as an adjustment — never as a reason to delay the paycheck. The Friday paycheck is sacred.
I do not install camera systems to “catch people doing wrong.” Cameras and telematics are for safety, coaching, and incident response. The framing matters. When drivers see the camera as their teammate (insurance against a false accusation, training tool to improve technique) rather than as their warden, the relationship works.
I do not change procedures every week to “tighten controls.” Constantly tweaking procedures sends the signal that the operator does not trust the people running the operation. Set the procedures, communicate them clearly, and then let the people run within them.
I do not personally inspect work that the BC or driver has already signed off on. If the BC verified that a truck was loaded correctly, I trust the BC. If the driver scanned the package as delivered, I trust the scan. Spot-checking is fine; routine re-inspection is a signal that nobody else’s judgment is trusted, and the rest of the operation responds accordingly.
The pattern across all of these is the same: extend the trust, then act consistently with having extended it.
Trust as the IC model’s foundation
There is a broader observation worth making here. The FedEx Ground network only works because trust flows down through several layers:
- FedEx trusts contractors to deliver the contract. (They have to. The independent contractor model literally requires it.)
- Contractors trust BCs to run the station. (Or the contractor is a daily on-site manager, not an owner.)
- BCs trust drivers to run the routes. (Or the routes don’t run.)
- Drivers trust each other to cover when one of them needs help. (Or coverage breaks down.)
It is trust all the way down. The contractors who fight this — who try to insert themselves at every layer, who try to control every detail, who do not extend trust — eventually wash out. The math will not allow them to scale, and they will be exhausted within a few years.
The contractors who lean into this — who extend trust deliberately at each layer, who build the incentives that make trust safe, who act fast when trust is broken — build sustainable operations. They sleep more. They make better decisions. They are still in the business in five years.
The reading list connection
If you have read the Time and Space article or the Contractor’s Real Job article, this article completes the trilogy. Time and Space is the operational framework. The Contractor’s Real Job is the role definition. Trust Is Given is the foundation underneath both.
The intellectual lineage I draw on, for what it is worth:
- Marcus Aurelius’s Meditations — the stoic recognition that what you cannot control is not your job to control. You cannot personally drive every route. Accept that and act from there.
- Michael Gerber’s The E-Myth Revisited — the explicit framing of working on the business instead of in it. You cannot work on the business if you do not trust the people running it.
- Phil Knight’s Shoe Dog — a memoir of a founder who trusted his team in genuinely extreme circumstances. The recurring theme: the people who built Nike were given enormous trust by Knight, often before they had any track record. They responded.
None of these is a how-to book on trust specifically. All of them point at the same insight: the operator’s job is to build a system that runs without them, which is impossible without extending trust to the people in the system.
What about the people who can’t be trusted?
The most common pushback to this philosophy is: “Sure, but what about the people who steal from me? What about the drug failures? What about the drivers who quit mid-route?”
Those people exist. They are real. Their existence does not change the philosophy.
The defense against bad actors is not to extend less trust to everyone. It is to:
- Design hiring to filter for the people likely to be trustworthy (background check, drug screen, motor vehicle record, pattern-recognition by experienced BCs)
- Design the system so that bad actors are caught quickly (telematics, scan compliance, fuel card monitoring, settlement reconciliation)
- Act fast when someone breaks trust (terminate, document, move on)
- Resist the temptation to over-correct by clamping down on everyone else
When you have a fraud event, the temptation is to install new controls, new monitoring, new procedures across the entire operation. Resist. The new controls don’t hurt the bad actor (they were already going to break the new rules too) — they hurt the 95 percent of your team who were trustworthy all along. The new controls signal “we no longer trust you,” and the compounding effect kicks in the wrong direction.
The correct response to a fraud event is: terminate the bad actor, document the event for the record, examine whether the existing system caught the problem (and how fast), and resist the urge to “tighten” everything. Most “tightening” damages the team’s trust without actually deterring future bad actors.
The single sentence to take with you
If you remember one sentence from this article, make it this one:
Trust is the precondition for scale. Extend it first, build the incentives that make it safe, and act fast when it is broken — but do not withhold it at the start, because withholding it caps your operation at one person’s ability to watch everything.
The contractors who get this right run operations that survive their absence. The contractors who don’t run operations that consume them entirely. The choice shows up in how many hours you work, how many routes you can run, and whether the business owns you or you own it.
Trust is given. Make it safe. Act when it is broken. That is the whole philosophy.