When a project runs late, the first instinct is to look at the work. Was the crew slow? Was the task harder than expected? Did someone underestimate it?
Sometimes, sure. But after more than twenty years in construction and real estate development, I've found that most lost days don't disappear while people are working. They disappear in between: the morning nobody showed up because the last trade didn't say they were done, the week a submittal sat in someone's inbox, the decision that waited for a meeting that kept getting moved.
The work is usually visible. The handoffs usually aren't. That's why they're where schedules quietly go to die.
Every handoff is a small bet
A handoff is any moment where one person or team finishes and another has to start. Framing to rough-in. Design to permitting. Sales to operations. A question from the field to an answer from the office.
Each one is a small bet that three things are true at the same time: the first team is actually done, the next team knows it, and the next team has what it needs to start. Miss any one of those and the clock keeps running while nothing moves.
On a schedule, that gap often doesn't even show up as a task. It shows up later as "slippage," and everyone argues about whose work took too long.
"Done" has to mean the same thing to both sides
The most common handoff failure I've seen is two people with different definitions of done. One crew calls an area complete because their part is finished. The next crew walks in and finds cleanup left, a missing inspection, or materials staged where they need to work.
Nobody lied. They just never agreed on what "ready for the next trade" looks like.
The fix is boring and it works: write down what done means at each major handoff, in plain words, and walk it together the first few times. A short checklist that both sides helped write beats any amount of after-the-fact blame.
Make the handoff someone's job
Handoffs drift because they belong to everyone, which means they belong to no one. The finishing team assumes the next team is watching. The next team assumes they'll get a call.
Good operators name an owner for each critical handoff. Not to do all the work, just to confirm three things out loud: we're done, you know it, and you have what you need. That one phone call or message closes most of the gap.
Watch the waiting, not just the working
If you want to find your real schedule risk, stop staring at task durations for a minute and look at the waiting:
- How long do questions from the field wait for answers?
- How long do approvals sit before someone signs?
- How many days pass between one trade finishing and the next one starting?
- Which decisions are stuck waiting for a meeting instead of a person?
You'll usually find more recoverable time in those gaps than in pushing anyone to work faster. And unlike pushing people harder, tightening handoffs doesn't burn out your best crews.
The same rule outside the jobsite
None of this is unique to construction. A sales team hands a customer to operations. A developer hands a feature to testing. A founder hands a task to a new hire. Every growing business is really a chain of handoffs, and the business runs exactly as fast as its slowest one.
The tools can help, but only after you've decided what done means and who owns the moment it changes hands. Software will happily track a handoff nobody owns; it just won't make it happen. I wrote more about that in Software Won't Fix a Process Nobody Owns.
Where to go next
If you lead projects, pick one recurring handoff this week and ask both sides what done means. You'll probably hear two different answers, and that's the most useful thing you'll learn all week.
I write about construction, real estate development, operations, and the systems that make hard projects work. More about me is at /about, my books are at /books, and my podcast, Faith, Business & Politics, is at /podcast.
