Your Job Handoff Is a Verbal Agreement — That's the Problem

March 2020. Mike's in the hospital, phone going to voicemail, and I'm at a card table in the garage trying to figure out which of our open jobs are actually open.

Not "open" like on a board somewhere. Open like — somewhere in the world, there is a customer who has been told something by my dad, and I don't know what, and there may or may not be a part on order, and I have no idea when anyone promised we'd be back.

That's when I understood what a handoff is. Not because I was doing them right. Because I wasn't doing them at all. Every job that was mid-stream and living in Mike's head was now a mystery I was solving backwards, one phone call at a time, with Hank climbing on me.

The shop almost didn't make it. Not from lack of work. From lack of information transfer. We had jobs. We had customers who wanted us. We were losing them because nobody knew what the guy before them had said.

---

The "Just Go Finish It" Conversation Is Costing You More Than You Think

Every small shop does this. I did it last Thursday.

Your first guy starts a job. Something pulls him — an emergency, a second truck going down, a slab leak across town. You call your second guy. You say: "Go finish what Dom started on Edgewater. Water heater swap. He's got the unit on the truck. Should be two hours."

In the small-shop world, that's just called dispatch. Nobody thinks of it as a problem.

What it actually is: a transfer of liability with no documentation. And I didn't learn that until I was picking up the pieces in a garage with a card table and a two-year-old.

I worked at Crestwood Plumbing from 2012 to 2018. Thirty trucks, commercial and residential. Every single job had a paper jacket. Physical folder. What was found on the first visit, what was done, what parts were ordered, what the customer was told and by whom, what was outstanding. It was not complicated. It was maybe ten lines of writing. But every tech who touched that job after the first one picked up the folder before he got in the truck.

I came home in 2019 and watched Mike run a three-truck shop entirely on memory and personality. His relationships were real. His memory is genuinely impressive. When Mike was on every job, Mike was the system. I watched that and thought: this is how a small shop runs. Personal. Fast.

That was the wrong lesson.

When Mike ended up in the hospital, everything he knew went with him. The guys were capable. The system just didn't exist without him in it.

---

What Actually Goes Wrong When You Don't Have a Handoff Process

Let me give you a real one.

Dom's on West 117th, sweet lady, maybe 70, slow tub drain. Snakes it forty feet, nothing changes. Calls me from the driveway. We do a sewer scope — camera through the cleanout, sixty feet out, collapsed clay under the side yard. 1925 house, Edgewater neighborhood, iron and clay pipe, exactly what you'd expect under that street.

That call from the driveway worked out because Dom called me.

Now imagine I'd sent a second tech instead. No handoff, just "go check on the slow drain on 117th, Dom had to leave." Second tech walks in, sees the snake in the bucket, figures Dom ran it and it didn't clear. Runs it again. Charges the $89. Leaves.

Customer calls back in a week. Drain's still slow. We're starting from zero with a customer who's been waiting and has started to wonder about us. Whatever the callback costs — and in my shop that's a real number with a truck and a tech on the clock — we own it. And if the second tech damaged the already-compromised clay trying to clear it, we own that too.

But the money isn't the worst part.

I've sat across from someone — older lady, fixed income, been in the house forty years — and she looks at me and says: "Your guy told me it was just the drain. Now you're telling me it's the sewer?" There is no good answer to that. She's not wrong. She was told something. Now she's being told something different. And she doesn't know which one of us to believe.

That's a handoff failure. The first tech gave her information he hadn't written down anywhere, and the second tech walked in without knowing what she'd been told.

A customer complaint about being told two different things is almost never about the technical work. It's about the handoff. And you can't respond to it publicly without looking like you're blaming your own guy.

---

What a Real Handoff Actually Contains

Six fields. That's it.

What was found. One or two sentences. "Collapsed clay at approximately sixty feet, confirmed by camera."

What was done. "Snake run, forty feet, no clearance. Scope performed."

What's on the truck or on order. If Dom pulled a part, the second tech needs to know it's already there. Otherwise you get guys stopping at Ferguson for something that's sitting on Dom's truck.

What the customer was told and by whom. This one matters most. "Dom told Mrs. Kowalski it was likely a drain issue before we scoped. Joe called after the scope and updated her on the sewer situation. She knows the estimate is coming."

What's left to do. The actual scope of what the second tech is walking into.

Landmines. The oak tree she won't let you touch. The husband who's home at 3 and has opinions. The check that needs to go to Becca, not to Dom. The dog that bites. Whatever the first tech knows about this job that isn't in any other field — it goes here.

Becca runs our office two days a week. She cannot dispatch a second tech if she doesn't know what the first tech left behind. And if the handoff doesn't exist, she's calling Dom while Dom's in a crawlspace on his next job — which means Dom's half-present on two jobs, and the information Becca gets is incomplete anyway because Dom's telling her what he remembers from two hours ago while staring at a corroded shutoff.

A good CSR is worth two trucks. I mean that literally. But she can't run dispatch on information that lives in a truck cab.

---

Stop Blaming the Helper

When a handed-off job goes sideways, the first instinct in a small shop is to blame the second tech. He should've called. He should've asked more questions. He should've known.

I've said the backwards version out loud. Which is how I know it's backwards.

If your handoff depends on the second tech being smart enough to figure out what he walked into, you don't have a handoff. You have a lottery.

Apprentices today aren't worse than they were in 2005. What I believe — and I've written about this before — is that they're being trained worse, by guys like me who are too busy to train them right. A helper walking into a job without a written handoff and making the wrong call isn't a failure of initiative. It's a failure of whatever system didn't give him the information he needed.

The whole point of a handoff process is that it works when the senior guy isn't there. That's the only time it needs to work.

---

How One Callback Turned Into a One-Star Review

Dom started a water heater swap on a Tuesday. Bradford White 40-gallon, natural gas, direct replacement out in Broadview Heights. Should've been three hours start to finish.

Midway through, slab leak call comes in. I pull Dom. I call Marcus — my other guy, two years in, reliable — and I tell him: "Dom started the water heater on Broadview, go finish it, unit's in, just make the connections and check it out."

Marcus goes. Marcus finishes. Good work.

What Marcus didn't know: Dom had flagged the expansion tank as undersized. The city had put a pressure-reducing valve on the street, which closed off the backflow path into the main, which meant the system was now closed-loop and building thermal expansion pressure against a tank that was too small for the new setup. Dom had a replacement tank on his truck. He was going to swap it same day. He hadn't told Marcus. I hadn't told Marcus. There was no handoff. There was a phone call.

Marcus hooks up the water heater, fires it, pressure checks fine right then, signs off, leaves.

Eight days later, the T&P valve starts weeping. Customer calls in. I send Dom because it's his original job. Dom goes out, looks at the tank, knows immediately. Tank goes in. Labor's on us — Dom's time, plus the tank we should've billed first trip. We eat it. The job wasn't done right, and it doesn't matter that Marcus didn't know, because Marcus didn't know.

That's not the worst part.

The customer wrote the Google review before Dom got back out there. One star. "Sent two different guys, first one didn't finish the job right, now I'm having problems a week later." Every piece of equipment we installed works. The water heater's fine. The expansion tank is correct. The work is right.

What she reviewed was the experience: two different guys, two different stories, a problem a week later. I cannot respond to that publicly without either confirming my guys made a mistake or throwing Marcus under a bus. So I don't. The review is still up.

That week, I wrote down the handoff checklist for the first time. Six fields on a whiteboard in the shop.

---

What You Can Actually Do This Week

Start with whatever Becca — or whoever's running your phones — doesn't have to fight every day. Whiteboard in the shop. A note in Jobber's job details. A shared Google Doc your whole team can pull up on their phones. The format doesn't matter. What matters is the information actually moving from the first tech to the second one.

Six fields. Written down before the first tech leaves the job.

Then one rule, non-negotiable:

No second tech goes to a handed-off job until he's read the handoff and confirmed it with whoever wrote it. Thirty seconds on the phone. Did you read it, do you have questions, okay go. That's it.

That step forces the handoff to be written in the first place, forces the second tech to actually read it, and creates one moment where gaps get caught before the truck leaves the yard — instead of after the customer calls back.

Guys who skip it to save ten minutes are the ones calling me from driveways trying to explain a one-star review.

---

Questions I Get About This

What if my jobs are simple enough that a verbal handoff works fine?

The slow tub drain on West 117th looked simple until Dom put a camera in it and found collapsed clay at sixty feet. The woman didn't know the difference between "simple" and "complicated." She just knew two different people told her two different things. Write it down. The easy jobs take forty-five seconds.

My guys resist any kind of paperwork. How do I get them to use this?

Put it in the dispatch notes in whatever software you're already on, or a physical half-sheet in the job folder. Six fields, not a report. Most resistance comes from guys who think you're auditing them — frame it as the second tech not walking in blind. If your first tech has ever gotten a callback call on a job he left two days ago, he already understands why this matters.

What if I'm a one-truck shop?

Your handoff problem is usually you-to-the-next-version-of-you. If you get sick, or want to eventually hire help, every open job living in your head right now is a liability. Document what you found and what you told the customer. Someone's going to need it — and that someone might be you, three weeks later, on a callback you can't remember clearly.

Should I use Jobber's job notes or something separate?

Whatever the person running your phones doesn't fight every day. Becca's on Jobber, she knows where the notes live, that's where we put it. If you're on Housecall Pro, use job details. If you're on nothing, whiteboard and job cards. The tool doesn't matter. Becca can't dispatch on information that doesn't exist.

How do I handle it when the first tech calls in instead of writing it down?

Take the call. Take notes while he's talking. Then type it somewhere the second tech can read before he leaves — if Becca's taking the call, she should be entering it live. The call gets the information moving. The note is what makes it real. Thirty extra seconds there saves an hour on the back end.

What's the most important of the six fields if I have to start with one?

What the customer was told and by whom. If the second tech doesn't know what the first tech told her, he's going to say something different. She's going to notice. That's the field that cost me the Google review on the Broadview Heights water heater. Start there.