The handoff problem nobody talks about

I've watched a lot of good projects go sideways not because the people were bad at their jobs, but because nobody knew what the person before them had decided.

What happened

No major industry news this week worth your time — so instead, a field note on something I've seen inside nearly every shop I've worked with over the past 12 years: the handoff problem.

A handoff is any moment where information, a decision, or a responsibility moves from one person to another. Estimator to project manager. PM to superintendent. Super to foreman. Office to owner. Most companies have dozens of these every week. Almost none of them have a system for it.

What they have instead is a phone call, a sticky note, a forwarded email chain, or — most commonly — an assumption that the other person already knows.

Why it matters for your shop

When handoffs fail, the cost doesn't show up on a line item. It shows up as a foreman waiting on a material decision, a sub who missed scope because the PM didn't brief him, a change order that didn't get issued because nobody owned the follow-through. It shows up as your phone ringing at 6:45 on a Tuesday morning with a question that should have been answered three days ago.

For a company doing $5M to $90M in work, these aren't small leaks. They compound. One unclear handoff at the start of a project can create four problems by the time you're in the middle of it.

Here's what I see owners get wrong: they try to fix handoff failures with more meetings. A standing Monday call, a weekly job walk, a Friday check-in. The meetings multiply, and the handoffs still don't work — because the problem was never about face time. It was about what information moves, to whom, and in what form.

The shops that handle this well aren't doing anything exotic. They've decided what a handoff looks like for each transition in their business, written it down simply, and made it someone's job to do it. A project turnover template in Notion. A pre-construction checklist the PM runs through before handing a job to the super. A standing agenda item that forces the question: what does the next person need to know that only I currently know?

When I started layering tools like Claude and Granola into this work, the biggest win wasn't automation — it was that transcribed meetings and summarized notes finally made handoff information searchable and durable instead of living in someone's head or a buried email thread. But the tools only help if the habit of capturing is already there. The system comes first.

If you're honest with yourself, you probably already know where your handoffs break. There's usually one transition in every construction company that causes 60% of the friction. Estimating to operations is the most common one. But I've seen it just as bad between field and billing, or between you as the owner and anyone you're trying to delegate to.

One thing to try this week

Pick the one handoff in your company that causes the most repeated questions or dropped balls. Write down — in under 10 minutes, in plain language — what information needs to move at that transition, who sends it, who receives it, and what format it takes. Don't build a system yet. Just name the thing. Most owners have never written it down, and the act of doing so usually makes the gap obvious.

That's the starting point. Everything else comes after.

— Austin