One Job Slips. What Happens to the Rest of Your Week?

It's Tuesday afternoon. The inspector doesn't pass the rough-in — he wants a second vent before he'll sign it off. Re-inspection is Thursday at the earliest.

That's a two-day delay on one job. The problem is that it isn't only on one job. Your tiler is booked at that house tomorrow. Your lead is supposed to be across town Thursday starting a rough-in on a new build. The customer at the third job was told Friday, and Friday is now doing a lot of work.

The delay itself is normal — everyone in the trades loses days to inspections, deliveries and weather. What separates a bad week from a bad month is how quickly you can see what the delay touched, and how fast you can move the rest of the work around it.

The real problem is that you can't see what it touched

Most crews keep the week in one of three places: a whiteboard, a spreadsheet, or somebody's head. All three have the same weakness. They record when work happens, but not why it happens then.

So when Tuesday moves, you're left reconstructing the reasoning from memory. Does the tile still work Wednesday? Only if the rough-in passed — which it didn't. Can the lead start the new build Wednesday instead of Thursday? Only if nothing else needs him. Who else was going to be at the first house?

Every one of those answers exists. They're just not written down anywhere, which means the only way to get them is to work through it in your head at five o'clock, usually while driving.

The fix is to record the reasoning alongside the dates — which job depends on which, and who's booked where. Once that's on the schedule, a slip stops being a puzzle and becomes a question the schedule can answer. (If your schedule doesn't hold that reasoning yet, building a construction Gantt chart is the place to start.)

Three kinds of slip, and they behave differently

The slip inside one job. The rough-in fails, so the tile can't start, so the fixtures can't be set. It travels along the chain of work in that job. This is a straightforward dependency problem: whatever was waiting on the failed work moves by the same amount.

The slip that jumps to another job. Your lead was going to finish here Wednesday and start there Thursday. Now he's here until Thursday. Nothing about job two changed — it just lost the only person who was going to do it. This is the one people miss, because on paper the two jobs have nothing to do with each other. They share a person, and that's enough.

The slip that costs a date you promised. Somewhere at the end of the chain is a date a customer is holding: a move-in, a rental turnaround, a kitchen that has to work before a family comes to stay. Some slips consume slack nobody was using. Some slips eat a promise. You need to know which one this is before you decide how hard to fight it.

Step 1. Find the things that can't move

Before you rearrange anything, mark the fixed points. In most weeks there are only a handful:

• Inspections and re-inspections — the inspector's calendar, not yours
• Material deliveries and long-lead items
• Subs who are booked elsewhere and can't come back until the following week
• Customer-side constraints — an occupied house, a business that can't close, a move-in date
• Weather windows for exterior work

Everything else is negotiable, even if it doesn't feel like it. Sorting the fixed from the movable takes about two minutes and it tells you where the real constraint is. Usually the delay you're panicking about isn't the constraint — the re-inspection date is.

Step 2. Follow the chain inside the job

Start at the work that slipped and walk forward. What was waiting on it? What was waiting on that?

You're looking for the point where the chain stops mattering — where the work that follows has enough float that a two-day shift disappears into it. On a small job that's often two or three links along. On a tight job it runs all the way to the end date, which means the whole job just moved.

The chain that runs from the delay to the finish date is the critical path for the rest of that job. Anything on it moves the end date. Anything off it has room.

Step 3. Look at who was booked, not just what

Now do the same walk for people. Pull up the week and ask, for each person and each sub: where were they going to be, and does that still make sense?

This is where the second kind of slip surfaces. Your lead is now stuck at the first house through Thursday, so Thursday's start on the new build has no one on it. That's not a delay you caused by rescheduling — it already happened the moment the inspection failed. You're just finding out about it now instead of Thursday morning.

Step 4. Resequence — pull work forward, don't just push everything back

The instinct is to slide everything right by two days. That's the worst available option: it wastes the two days completely, and it moves work that didn't need to move.

Better: find work later in the week that doesn't depend on what slipped, and pull it forward into the hole.

Here's the week from the top of this article, before and after.

Before

After

Nobody has an idle day. The re-inspection sits on Thursday where the inspector put it. Henderson's tile moved to Friday, which is the one thing you now have to tell a customer about — and that's a much shorter phone call than four vague ones.

The reason this works is that Lot 17's rough-in never depended on Henderson at all. It was on Thursday because that's where it landed when you built the week, not because anything held it there. Most weeks have two or three of those, and they're your recovery room.

Step 5. Decide who hears about it today

Not everyone needs a call. Work out who's actually affected:

• The customer whose date moved. Same day, before they find out from an empty driveway. Say what happened, what you've done about it, and the new date. If you rearranged the week so their date didn't move, that's worth a sentence too.
• The sub whose day you changed. Immediately, because they're building their own week around you.
• The customer whose date didn't move. Nothing. Don't create noise.

The tone matters less than the timing. "The inspector wants a second vent, we're doing it tomorrow, re-inspection Thursday, tile shifts to Friday" is a fact and a plan. The same news on Friday morning is an excuse. Our guide on communicating estimates and changes to customers goes deeper on framing the conversation, and the process for handling a scope change — as opposed to a delay — is covered in handling change requests.

Preventing about half of these

You can't stop an inspector failing a rough-in. You can stop it from taking the whole week with it.

Leave float where the risk is. Not spread evenly across the job — concentrated right after the parts that historically slip. Inspections, deliveries, anything behind a wall in an old house. A single buffer day after the rough-in absorbs the most common failure in this trade.

Don't book a person to the last hour. A crew booked at 100% has no capacity to recover. Around 80% is where a week can absorb a bad day without a phone call.

Stagger the fixed points. If two jobs both have inspections on Thursday and one lead, you've built the collision yourself.

Update the same day. A schedule that's three days behind reality is worse than no schedule — people trust it and act on it. Five minutes at the end of the day is the whole discipline.

When there's no way to absorb it

Sometimes there isn't a resequence that works. The promised date is gone, and no amount of rearranging brings it back.

At that point stop optimizing and start triaging: what's the actual new end date, what does it cost, and what's the one change that would move it most — a second crew, overtime, splitting the scope so the customer gets the working kitchen now and the tile later. Our guide on what to analyze first when a project is in trouble works through that in order.

The thing not to do is promise a date you can't see a path to. You only get to be wrong about a date once with most customers.

The five-minute version

When something slips: mark what can't move, follow the chain from the delay forward, check who was booked and is now free, pull independent work into the gap, and call the one customer whose date actually changed.

The whole exercise takes about five minutes when your schedule holds the dependencies and the assignments. It takes an evening when it doesn't — and it's the evening, not the delay, that makes the week feel out of control.