It started with a Monday-morning meeting that had the vibe of a principal catching kids chewing gum. The executive—let’s call him Darren because that’s what everyone called him behind his back anyway—stood at the front of the conference room with a printout and a tight smile, talking about “discipline” and “professionalism” like he’d personally invented both.
Half the room had company keys in their pockets. The company ran a small fleet of branded SUVs and pickups that techs and supervisors used to bounce between client sites, the warehouse, and the office. Darren made it sound like those vehicles were sacred objects, and employees were barely trustworthy enough to touch the steering wheel.
Then came the new rule: no personal errands. Not a quick pharmacy stop. Not picking up lunch. Not swinging by daycare. “Company time is company time,” he said, and he said it like he was doing everyone a favor by reminding them.
The productivity sermon and the new crackdown
Darren didn’t just send an email; he performed the policy. He stood there talking about how the company had “leakage,” how the fleet was “not a perk,” and how anyone who couldn’t make it from Point A to Point B without “detouring” needed to reconsider their priorities.
He had examples ready, too—vague ones that couldn’t be argued with. Somebody had allegedly taken a truck to a hardware store on the weekend. Somebody else had “stopped at a coffee shop” on the way to a job and “racked up thirty minutes.” No names, just enough detail to make everyone sit straighter and wonder if they were about to get singled out later.
He rolled out a form employees had to sign acknowledging the policy and added a little extra sting: any violations could lead to losing vehicle privileges or “further action.” People watched him like you watch someone who’s clearly enjoying the power trip. A couple managers nodded along, the kind of nodding that wasn’t agreement so much as survival.
And because Darren could never just be strict quietly, he tied it all to productivity. He said clients were complaining. He said billable hours were slipping. He said the company needed “a culture shift.” The people who actually did the work exchanged looks that said, What culture? We’re barely keeping this place running.
Everyone tries to comply, and the resentment starts to simmer
For the next few weeks, the fleet turned into a mobile anxiety machine. People started timing their routes like they were training for a race, skipping bathroom breaks, eating in parking lots so they wouldn’t get accused of “loafing.” One supervisor stopped taking his truck home and started commuting in his own car just so he wouldn’t have to explain a gas station stop.
It wasn’t even the rule by itself that got under their skin—it was Darren’s smug certainty that he was the only adult in the room. Someone joked that they should all start wearing body cams, like cops, just to prove they weren’t grabbing a sandwich. Nobody laughed very hard.
The awkward moments stacked up fast. A tech got stuck in traffic and arrived at a site late; Darren asked him if he’d “made any unapproved stops.” A coordinator had to take a detour because of a road closure; Darren wanted her to “document it in writing.” People began forwarding each other the policy email like it was a curse chain.
And then Darren added the flourish that made it feel personal: he announced they were “enhancing accountability” with more active fleet tracking. It was already installed, apparently, but now it would be “reviewed.” He said it with that calm voice executives use when they want you to know they can see everything you do.
The tracking data starts telling a story nobody expected
Here’s the part that always happens in stories like this: the tracking system didn’t just watch the employees. It watched Darren, too. His company-issued SUV was on the same platform as everyone else’s, right there with a little icon and a trail of breadcrumbs.
At first, nobody was looking for dirt on him. The fleet administrator—one of those quietly competent back-office people who actually understands how systems work—started pulling weekly reports because Darren wanted them. Which meant she was staring at routes, idle time, stop durations, and timestamps, comparing them against job schedules.
And Darren’s vehicle didn’t fit the pattern. It wasn’t doing a clean office-to-client-to-office loop. It was doing long daytime runs to places that weren’t on any client list, lingering there for hours, then drifting back like nothing happened.
Once you notice something like that, you can’t unsee it. A stop labeled by the system as a “country club” because the GPS pin fell right on the clubhouse. Another that mapped directly to a casino. Multiple visits to a residential building in a part of town Darren never mentioned having business in.
“Can you pull Darren’s last month?” becomes the office’s quiet obsession
The fleet admin didn’t gossip, but she did have a boss, and her boss had a boss, and Darren had made the mistake of demanding “full transparency.” When she flagged a discrepancy—politely, in a neutral email—she got told to “dig deeper” and produce a complete report for leadership.
That was the moment it stopped being a weird blip and became a timeline. They pulled weeks. Then months. They matched it to Darren’s calendar, which was full of mysterious “external meetings” and “offsite strategy sessions.” The routes told a different story: midday drives that ended in parking lots next to golf fairways, not conference rooms.
The residential address came up again and again, usually in the late morning or early afternoon, with the SUV parked there for stretches long enough that nobody could pretend it was “dropping off documents.” Someone in HR quietly checked and realized it wasn’t Darren’s home address, and it wasn’t a client. It was a girlfriend’s apartment—an open secret once you knew what to look for.
When the total got calculated, it was almost funny in the worst way: 47 workdays’ worth of time where Darren’s company vehicle was logged going to golf courses, casinos, and that apartment. Not 47 trips. Forty-seven days. The number looked like a typo until you watched the data line up like a confession.
The meeting nobody wanted to attend
Leadership tried to handle it the way companies handle embarrassing things: quietly, behind closed doors, with very careful language. Darren got called into a meeting with the COO and HR, and the fleet admin was asked to be “available for clarification.” She spent that morning feeling like she’d swallowed a rock.
Darren walked in confident. He’d been the one pushing “accountability,” after all. He apparently thought this was about catching employees taking the long way to a job site, and he was about to be proven right.
Then the report got slid across the table. Pages of dates, locations, stop durations, route maps, and fuel card activity. Darren’s face did the thing people’s faces do when they realize the rules they wrote have become a trap they built for themselves.
He tried the first defense: “Those were client development meetings.” The COO asked why client development happened at a casino on a Tuesday at 1:14 p.m. He tried another: “That address is a family matter.” HR asked why a family matter required a three-hour stop twice a week for months.
The worst part, according to someone who later described it, was how fast Darren switched from righteous to offended. He wasn’t embarrassed; he was angry that anyone had the audacity to question him. He acted like the tracking system was an invasion of his privacy, as if he hadn’t just used it to scare everyone else into skipping lunch.
Fallout: the policy stays, but the trust doesn’t
Darren didn’t come to the next all-hands. There was a vague email about “leadership changes” and “interim oversight of fleet operations.” Nobody used his name, but everyone knew. The same managers who’d nodded along in the productivity lecture suddenly became very interested in “rebuilding morale.”
The policy about personal errands didn’t get rescinded, which was the detail that made people grind their teeth. Employees were still expected to act like robots in branded vehicles, documenting detours like they were writing police reports. The difference was that now everybody understood the rules weren’t about efficiency; they were about control.
People started doing the math in their heads. Forty-seven workdays isn’t a couple bad decisions; it’s a lifestyle. It’s a whole parallel job where the job is “being absent,” and the perk is that everyone else covers for you without knowing they’re doing it.
There were small rebellions—subtle, quiet ones. Less volunteer overtime. More “per policy, I can’t” responses. A few employees updated their resumes and stopped pretending they hadn’t been thinking about leaving for months.
The strangest part was what didn’t happen. No public apology. No acknowledgment that Darren’s lecture had been a performance built on hypocrisy. Just a company trying to move forward while everyone who’d sat through that meeting kept replaying his voice saying “company time is company time,” and wondering how many afternoons they’d rushed through traffic, skipping errands and swallowing stress, while his SUV idled outside a clubhouse or a high-rise apartment like it belonged there.