"Do you want my resignation or should I just go?" He'd been there two weeks.

A shop I work with pays their techs full warranty hours on comebacks.

Even workmanship comebacks.

On purpose.

Most shop owners hear that and think it's insane. It's actually one of the smartest moves in their entire operation. And it starts with a story about a bent hood.

A junior tech. Second week on the job.

He goes to close the hood on a brand-new van. Doesn't realize it's a prop rod, not hydraulic.

Bends the hood.

He walks from the shop into the front office and says something along the lines of — "Do you want my resignation or should I just go?"

The owner looked at him and said: that's the kind of employee we want. He told us immediately. He didn't hide it. He didn't make an excuse. He showed us exactly who he is.

That tech just hit his two-year anniversary with the shop.

Now — most of us hear that and think, "Good for them." But the real question is: what did that shop build that made a second-week tech walk in and confess instead of covering it up?

Because that doesn't happen by accident.

A different shop owner told me that a fleet customer pulled him aside one day and said something that made his stomach drop.

"We could tell the difference between a vehicle that one tech worked on versus the other guy. We weren't sure we were going to keep bringing our stuff to you."

The owner had no idea.

The tech had been making sloppy mistakes. Not catastrophic ones. The kind that erode trust slowly. And the tech never said a word about it.

The customer knew before the owner did.

That's the real cost of a shop where techs are afraid to admit when they screw up. It's not the comeback. It's the comebacks you never hear about — until a customer walks.

Your name goes out the door. Not the technician's name.

So how did that first shop — the one with the junior tech — build an environment where mistakes get reported instead of buried?

Two things.

The first is a monthly meeting with one specific question.

The owner brings in lunch for the team. Nothing fancy. Pizza, subs, whatever. They talk about what's going well, what tools need replacing, what's bugging people.

Then he asks every tech in the room:

"In the last 30 to 60 days — is there any car you wish you could get a do-over on? And why?"

One question. Each tech takes a turn.

They talk about the job that didn't go the way they wanted. What they missed. What they'd do differently.

Every other tech in the room is listening. They're absorbing somebody else's hard lesson without having to make the same mistake themselves.

One tech's do-over becomes the whole team's training. For free.

But this only works if the environment is safe enough for honesty. And that's where the second piece comes in.

The shop's philosophy: if your techs aren't making mistakes, they're either covering something up or they're not learning.

Both of those are bigger problems than the comeback itself.

The only things that get someone fired? Lying about a mistake. Or making the exact same one over and over. Everything else is a learning opportunity.

That's why they pay warranty hours on comebacks — even workmanship ones. If the tech eats the hours, what's the incentive? Hide the problem. Cut corners on the redo. Never mention it happened.

Remove the financial punishment and you remove the reason to hide.

The tech fixes it right. Learns the lesson. And the shop's quality goes up — not down.

There's a guardrail. If it's the fifth time a rear main seal comes back from the same tech, that job's going to somebody else. This isn't a reward for screwing up. It's an investment in getting better, with a clear boundary.

You don't need a perfect system to start this.

You need lunch. One question. And the guts to let your team be honest without getting punished for it.

"Any car in the last 30 to 60 days you wish you could get a do-over on?"

Buy some pizza. Ask it at your next team meeting.

The tech who bends the hood and tells you is worth ten times more than the tech who hides it and lets your customer find out.

1 comment