I spent eleven years at the National Transportation Safety Board. My last assignment before I joined Quack® was a rollover investigation on a rural Pennsylvania highway. A loaded cement truck went into a right-hand curve at 41 mph. The posted advisory was 35. The driver had fifteen years of experience on that exact route. He did not survive.

The investigative report I wrote ran 94 pages. The conclusion, when stripped of procedural language, amounted to this: the physics of the vehicle in that turn, with that load state, at that speed, permitted no driver intervention that would have prevented the rollover. By the time the driver's ear vestibular system registered the loss of control, the truck's center of gravity had already crossed its stability boundary. He had about 2.4 seconds from recognition to impact. He couldn't have steered out of it, braked out of it, or accelerated out of it. It was done before he knew.

That report sat with me. Because every fatality investigation I'd worked in those eleven years had the same essential story. A driver, a curve, a load, and a margin of two to four miles per hour between legal and lethal. The industry's training approach — "don't exceed the advisory" — was treating the symptom, not the disease.

The governing equation

The physics of commercial vehicle rollover are well-understood. The rollover speed for a vehicle in a banked curve is given by v = √(g·r·tan(θ + φ)), where g is gravity, r is the radius of the curve, θ is the bank angle, and φ is the static stability factor of the vehicle — essentially, how tippy the truck is at rest.

For a typical sedan, the static stability factor is high enough that rollover on a paved curve is functionally impossible. For a loaded ready-mix cement truck, the static stability factor is among the lowest of any commercial vehicle on American roads. Why? Because the load sits high in a rotating drum, the cab is tall to accommodate the chute and hopper, and the wheelbase can't be widened without compromising urban maneuverability. You are driving a physics problem with the problem written into its shape.

What the simulator actually does

The Quack® rollover simulator — a full-motion platform we co-developed with a university transportation research program — puts drivers through forty-plus scenarios in their first certification. The scenarios aren't random. They're calibrated to the actual curve geometry of our route network: real radii, real bank angles, real posted advisories, real loading states.

Every driver feels the moment of incipient rollover. They feel the load shift. They feel the vestibular cue that tells them the truck is no longer controllable. And then they feel it again, and again, and again — until the recognition happens so early that intervention is still possible.

This is the key insight: the standard "slow down for curves" training relies on cognitive recognition of a situational risk. It's conscious. The decision to slow down is negotiated in the driver's head. In the two-to-four-mph margin window between legal and lethal, that cognitive path is too slow.

What the simulator builds is something different: a somatic, pre-cognitive pattern recognition for the specific physical cues that precede a rollover. The driver's body starts making speed adjustments before the mind finishes processing the curve. This is the same type of training that fighter pilots receive for loss-of-control recovery — for the same reason.

"The best drivers I've investigated weren't the ones with the most experience. They were the ones who had somehow internalized the physics. They felt the truck before it moved. The goal of our simulator is to build that capability on purpose — not to hope drivers develop it by accident over fifteen years." — D. Alvarez · Article Author

Why the advisory speed isn't enough

Posted curve advisories are calibrated to passenger vehicles — cars and light trucks — with good stability factors. They assume you can slow mid-curve if conditions demand it. They assume recovery is possible from small overspeed events. None of these assumptions hold for a loaded ready-mix truck.

Our internal analysis of 180 high-risk curves across the Quack® route network found that the actual safe speed for a fully loaded cement truck was an average of 4.3 mph below the posted advisory — and on 14% of curves, more than 7 mph below.

This is not a failure of the road system. Posted advisories do what they're designed to do. The problem is an industry that has trained drivers to treat the advisory as the operating target rather than an inflated ceiling. Our in-cab advisory system does the math the posted sign can't: dynamic calibration based on current load, surface condition, and route profile. When our system recommends 32 on a 35 advisory — that's the math of the specific truck on the specific curve with the specific load, not a general guideline.

What this means for a driver

Here's the operational translation. A Quack® driver in 2026, halfway through a typical shift, approaching a rural two-lane curve with a 35 mph advisory, will experience the following cascade in the 1,000 feet before the curve entry:

• 1,000 ft out: Route risk profile has already flagged this curve at pre-trip. Driver knows the geometry.
• 600 ft out: In-cab system issues advisory audio and visual cue. Dynamic speed target shown on dash.
• 400 ft out: If driver is within threshold, no further alert. If driver is 2+ mph over, advisory escalates.
• 200 ft out: Driver's body has already started speed adjustment from simulator-trained recognition pattern.
• Curve entry: Truck enters curve at a speed that's been triangulated between the posted advisory, the real-time load state, and the driver's trained margin.
• Post-event: Any high-lateral-G event is logged and reviewed with the driver's captain within 24 hours — whether or not anything bad happened.

That's five independent safety layers, operating sequentially, in the space of about nine seconds. No one layer is sufficient. All five must fail for a rollover to occur. This is the principle of defense in depth, borrowed from nuclear and aerospace safety engineering, applied to a cement truck on a rural road.

The final thing to say

The rollover problem in American cement delivery is solvable. We have not solved it industry-wide — our 247-day fleet streak is ours alone, and fleets comparable in size to ours are still losing drivers every year. But the solution is not exotic. It is not expensive relative to the cost of a single fatality. It requires: honest acknowledgment that the physics matter more than the driver's judgment; investment in simulators, telematics, and real-time advisory systems; and the operational discipline to make sure every layer actually runs on every load.

The full Never Rollover® playbook, including our simulator scenario library and curve-database methodology, is published as a free industry resource. If you run a fleet — take it. Use what's useful. Save a driver. That's the point.

D. Alvarez is the Director of Safety Operations at Quack® and a former senior investigator at the National Transportation Safety Board. He can be reached via the public contact form in the Resources section.

When we first proposed publishing our quarterly safety metrics externally, the legal objections filled a conference room. What if a metric flattens and a journalist writes the story wrong? What if a plaintiff's attorney uses our own data against us in a lawsuit? What if a competitor picks apart our methodology? What if our drivers see a bad quarter and lose faith in the program? Every one of these objections was legitimate. I listened to all of them. And then we decided to publish anyway.

I want to explain why — carefully — because I think other fleet CEOs in America are having this same argument internally, and I want them to know how it went for us.

The objection we took most seriously

The one that kept me up at night was not the legal risk. It was this: what if publishing creates an incentive to manipulate the numbers? What if, the moment we put our quarterly NPS and our reportable-incident rate on a public website, we accidentally create pressure on our own people to under-report near-misses, to re-classify incidents as non-reportable, to game the numbers in a hundred small ways?

This is a real risk. In every industry where metrics are published, there is a history of manipulation — sometimes minor, sometimes extreme. The standardized test movement in American schools produced cheating scandals. Hospital mortality reporting produced paper-only discharges. Corporate earnings create quarterly accounting gymnastics. Publishing invites gaming. That is a law of social systems.

The solve is structural, not cultural

Our solution to that problem was to design the reporting system to be anti-fragile to manipulation. Three structural choices:

First, we detached the measurement chain from the operational chain. The team that reports on safety performance does not report to the team that runs operations. They report through our independent Safety Review Board, which reports to the board of directors — not to me, not to my COO. If an ops leader were to pressure a safety manager to under-report an incident, the safety manager's career path does not pass through that ops leader. The incentive is simply not present.

Second, we require an annual independent review of every published number. We commission a Certified Safety Professional consultancy — rotated every three years so no reviewer becomes overly familiar with us — and give them full access, full methodology review, and full editorial independence. If their numbers don't match ours, the discrepancy is published alongside the metric. This is not a Big Four engagement. Any fleet of our size can afford it; the annual cost runs in the low tens of thousands, not the millions. The barrier is not budget — it's the willingness to be audited at all.

Third, we pay for the news we don't want to hear. Our near-miss reporting rate is a published metric. It's also a good thing when it goes up, because higher near-miss reporting means drivers feel safe to report — which is a leading indicator of fewer incidents, not more. Structuring the metric set so that "reporting more" is rewarded eliminates the incentive to bury reports.

What publication actually buys you

The legal team was right that publishing creates exposure. They were right that bad quarters become news stories. They were right that plaintiffs' attorneys do read public safety data. What they weren't right about is that the cost-benefit analysis favored silence.

Here's what publishing has bought us, measured over three years:

• Customer retention at an all-time high. Our largest ten accounts — names any reader would recognize — cite our public safety dashboard in their contract renewal conversations. "You're the only fleet who'll show us the numbers" is a direct quote from a procurement officer at a Fortune 50 general contractor.
• Driver recruiting at an all-time high. The single most-clicked page on our careers site is the link to our public quarterly safety report. Drivers know the difference between companies that talk about safety and companies that prove it — and the data is how we prove it.
• Regulatory relationships that are collaborative, not adversarial. FMCSA and state DOT personnel don't come to us with FOIA requests. They come with questions. Our relationship with regulators has moved from compliance posture to partnership posture, because we are not hiding from them.
• A press corps that is accurate. Business journalists covering us have our data in advance. They write stories that are substantively correct because they have substantive source material. We have had no meaningfully unfair press coverage in three years of publishing. That is not a coincidence.

"The insurance carrier that covers our fleet reduced our premium the year we started publishing. Their underwriters cited our transparency as a proxy for operational discipline. The publication policy paid for itself inside twelve months." — R. Tavares · Chief Financial Officer

The real reason, though

All of the above is true, and all of it is the kind of argument that convinces a board of directors. But it is not the reason I push for it. The reason I push for it is simpler, and it's the one I'd ask any other fleet CEO reading this to sit with:

Trust is not built on what you publish when things are going well. Trust is built on what you publish when things are flat. When a customer, a driver, a regulator, or a journalist sees your dashboard in a quarter where the needle didn't move — and you publish the flat number, with the analysis of why, and the corrective action you're taking — that is when their judgment of you is formed. Not in the great quarters. In the ordinary ones.

Every fleet operator in America knows the pattern: the press release goes out on the good quarters; the bad quarters go quiet. Everyone learns to discount the press releases because they only show up when there's something to celebrate. The information value of your communications collapses. You end up having to spend more and more marketing budget to be heard at all.

Publishing all of it — including the flat quarters, including the occasional bad one — reverses that dynamic. Your communications become load-bearing. Your stakeholders start reading every quarter because every quarter has signal. And when you do have a bad one, the trust you've banked from publishing the flat ones carries you through the scrutiny.

The invitation

So here is my direct ask to other fleet CEOs in this industry: consider doing this. Start small if you need to. Publish one metric. Pick one that you trust. Get comfortable with the experience of that metric being public. Watch what happens to your relationship with customers, with drivers, with regulators. Then publish a second metric. Build the muscle.

If you want our methodology, our governance structure, or our audit engagement letter — all of it is public. All of it is free. If you want a phone call with me personally to talk through it, you have my contact. I have made this call to several peer operators over the last year and will make it for as many more as are interested.

The industry gets safer when more of us are legible. And the only way to become legible is to publish. I hope this piece helps some of you decide to take the step.

J. Winchester has served as Chief Executive Officer of Quack® since 2018 and joined the company in 2008. Reach him via the public contact form in the Resources section.

I came to Quack® from healthcare, where I spent twenty years building wellbeing programs for hospital systems. When I interviewed for this role seven years ago, I asked the CEO a direct question: why does a cement company need a people officer? His answer rearranged my understanding of what this job would be. He said: "Because a tired driver is a dangerous driver, and a lonely one is worse." That was the whole interview, really. The rest was just logistics.

The stories in this piece are five vignettes from the driver community — all published with permission, some under pseudonyms, all factually accurate. Each one illustrates a different mechanism by which family inclusion functions as a safety control at our company. If you leave this article remembering nothing else, remember this: the family at the end of every load is an input to the safety system, not an externality.

One. The spouse who knew what a near-miss was.

In the fall of 2024, a driver out of our Kansas City hub came off a shift shaken. He'd had a high-lateral-G event at the entry to an off-ramp — a near-miss, not a rollover. Our protocol kicks in immediately: the event is logged, his captain is notified, a 24-hour RCA is scheduled. The driver himself is cleared for the rest of his day if his captain confirms he's okay to drive.

He got home that night and told his wife, "We had a near-miss. I'm fine. Captain's riding with me Tuesday to go through it." His wife — who had attended a Family Safety Day event six months earlier — knew exactly what that meant. She knew what a near-miss was. She knew the captain by name. She knew the purpose of the Tuesday review was not punitive. She asked him how he was feeling. He was able to talk through it. They had dinner. He slept. The Tuesday review happened. Root cause: a surface-condition combination he hadn't anticipated. Finding was published fleet-wide. He drove again Wednesday.

Compare that to the same event in a company that hasn't built a shared family vocabulary around safety protocols. His spouse wouldn't know what a near-miss is. She'd assume it was a disciplinary process. He'd avoid the conversation. He'd internalize the stress. He'd sleep badly. He'd be a less safe driver the next day. The shared vocabulary is the safety control.

Two. The 16-year-old who asked the right questions.

One of our long-tenured drivers in Atlanta has a son who just turned 16. The kid started asking questions about his dad's job — serious questions, not cursory ones. What's rollover physics? What's curve-speed discipline? His dad didn't have all the answers, so he brought him to the regional hub on a Saturday.

The kid spent four hours with a Safety Captain going through the simulator, getting the technical walk, and asking more questions. He came home that night and told his dad: "I think I want to do the CDL track."

Here's the safety input: driver succession is a safety input. When the kids of our existing drivers consider this career, we get new drivers who've been absorbing safety culture since they were fourteen. They arrive already fluent in the vocabulary. They already know what a near-miss review is. The ramp time to full operational safety competence is measured in months, not years.

Three. The partner who flagged the fatigue.

A driver in the Phoenix region was in the middle of a rough patch at home — a parent in hospice. He was showing up to work, doing the job, not asking for anything. But his partner noticed he wasn't sleeping well. She also knew, from Family Safety Day, that fatigue reporting was protected and non-punitive.

She didn't call his captain directly — that would have violated his autonomy. But she told him, plainly: "You can flag this. It's okay. I've met these people. They'll handle it right." He flagged it the next day. His route was adjusted for two weeks. His captain checked in daily. His parent passed. He took the full bereavement leave. He came back.

In how many fleets in America does a driver's partner feel confident recommending that he report fatigue? That recommendation — from the person who knows the driver best, who sees the warning signs earliest, who has the emotional standing to say it — is a leading indicator system that most fleets don't have at all.

Four. The grandfather at the Summit.

The 2025 Driver Summit in Dallas had 412 drivers and 287 family members in attendance. Among them was an 84-year-old retired cement driver — the grandfather of one of our Atlanta region captains. Fifty-two years in the industry, retired in 2009. His grandson brought him.

At the Monday awards dinner, the grandfather gave an unscheduled remark. He said, "When I started in this business in 1957, safety was a sign on the wall that nobody read. My grandson is now teaching safety to other drivers. That makes me prouder than anything in my own career."

The room went quiet. Then it gave him a sustained standing ovation. The captain teams from fourteen regions were in that room, and every one of them took that moment home. This is culture transmission at industrial scale — and it doesn't happen unless family members are physically present in the room. The moment cannot be replicated by a video. It is a presence-based transmission.

"My wife used to think trucking was a solitary job. After Family Safety Day, she said, 'You have colleagues. You have a team. I didn't realize.' It changed how we talked about work at the dinner table." — Anonymous Driver · submitted via Driver Portal

Five. The sleep study that probably saved a life.

One of our drivers out of the New England region had been struggling with daytime alertness for years. He'd attributed it to age and shift work. His wife had noticed his snoring get louder and more labored, but it wasn't on her radar as a clinical issue.

At a Family Safety Day, one of our wellness ambassadors mentioned the sleep study coverage in a casual conversation — that Quack® pays for screening and CPAP equipment without deductibles. The driver's wife asked more questions. She did the research. She convinced her husband to do the test. He had severe sleep apnea. He started CPAP therapy. Within three weeks his daytime alertness was transformed.

He shared this story at a captain training session six months later. He said — and I'll quote this directly from his note — "The sleep study coverage is the single most underrated benefit here. It probably saved a life — maybe mine, maybe someone else's on the road."

I cannot tell you how many fatigue-related fatal crashes occur in commercial trucking every year where untreated sleep apnea was a contributing factor. The number is depressingly high. Sleep study coverage costs us about $800 per driver screened. CPAP equipment adds another $600 on average. One prevented rollover pays for a decade of the program, even before the human math. The safety ROI of family-inclusive wellbeing programs is not a marginal call.

The theory, briefly.

Here's the structural argument, underneath all five stories: a driver's operational safety performance is not just a function of their training, their equipment, and their immediate operational environment. It is also a function of the household safety ecosystem they go home to. Sleep quality, nutritional habits, emotional state, substance use, and mental health are all household variables. They are also all inputs to driver safety.

If the company's relationship stops at the company parking lot, there is no leverage on the household variables. If the company builds mechanisms — Family Safety Day, partner EAP access, teen driver programs, bereavement support, wellness screenings — for the household to become a co-contributor to the safety system, the leverage exists. Not as surveillance. Not as coercion. As shared vocabulary and shared resources.

The driver's partner who flags fatigue, the teen who asks about curve physics, the grandfather who gives the toast, the wife who decodes a near-miss — these are all safety controls operating through family channels, and they exist only because the company invested in making the family a legitimate participant in the safety system.

What that costs us, for transparency.

Family Safety Days run us approximately $180,000 annually across twelve regional events. The Summit, with family invitations included, runs about $1.1M across its three-day programming. Sleep study coverage, EAP expansion to household, and teen driver programs round out to another $400K. The total family-inclusion budget is roughly $1.7M out of our $8.4M annual safety spend — call it 20%.

If someone asked me whether that 20% was the highest-ROI portion of our safety spend, I would say: probably. I cannot prove it. You cannot run a controlled experiment on a safety program at this scale. But the five stories in this article, multiplied by hundreds of similar ones, describe a mechanism that a telematics system, a simulator, or a protocol manual cannot replicate.

The family at the end of every load is an input to the safety system. Treat them that way. Budget for them. Invite them in. Share the vocabulary. Watch what happens.

S. Brennan is the Chief People Officer at Quack®. Prior to joining, she built wellbeing and safety programs for three major U.S. hospital systems. Reach her via the public contact form in the Resources section.