A renovation schedule holds up when it is built around dependencies and float, not just a list of target dates. Sequence tasks by what physically has to be true before the next one can start, build in buffer around anything you do not control — permits, inspections, material lead times — and cascade the schedule the moment something slips instead of waiting for the whole job to catch up. Most schedules do not fail because the work took longer than expected; they fail because no room was left for the parts of the job that always do.
Most renovation schedules do not fail because the work took longer than the schedule said it would. They fail because the schedule never accounted for the parts of the job that reliably slip — a permit stuck at the city, a vanity on backorder, an inspector who cannot make it until Thursday. A schedule built as a list of target dates falls apart at the first one of those. A schedule built as a map of dependencies, with buffer placed where you do not have control, bends instead of breaking.
Start with dependencies, not dates
Before you write a single date on the schedule, write down what has to be true before each task can start. Drywall cannot start until rough inspection passes. Cabinets cannot hang until drywall and paint are done. Trim cannot go in until cabinets and countertops are set. Once the dependency chain is on paper, the dates are just the chain laid over a calendar — and when one link moves, you already know exactly what moves with it, because you built the schedule around the relationships between tasks instead of a wish for how the calendar should go.
Build in float where you do not control the clock
Float is buffer placed on purpose around the parts of the job you cannot compress by working harder: permitting, inspections, and material lead times. According to the 2023 U.S. Houzz & Home Study, kitchen renovations averaged 9.6 months of planning before construction even began, followed by 5.1 months of actual build time — real jobs, not worst-case ones. If your internal schedule does not leave room for that kind of runway on the front end and a multi-month build on the back end, you are scheduling the job you wish you had, not the one you are actually going to run.
A realistic phase-by-phase framework
- Demo and site prep (2–4 days) — clear the space, confirm disposal, protect adjacent rooms before a single trade shows up.
- Rough-in — plumbing, electrical, HVAC (1–2 weeks) — sequenced trade by trade, each one waiting on the last to actually finish, not just say they're close.
- Rough inspection (buffer 3–7 days) — scheduled the day rough-in finishes, not the day you hope the inspector is free.
- Insulation and drywall (1–2 weeks) — cannot start until rough inspection passes; this is where an unplanned re-inspection costs the most.
- Paint, cabinets, trim, fixtures (2–3 weeks) — the visible "finish" stretch, where delays get expensive and clients get anxious because the room finally looks close to done.
- Final inspection and punch list (buffer 1 week) — always budget a callback; almost every job has one.
The moment something slips, cascade it — do not wait
When a dependency moves, everything downstream of it moves too, and the sooner you push that change through the schedule, the smaller the damage. Waiting to see if you can "make it up" almost never works and it delays the one thing that actually protects the relationship: telling the client before they have to ask. A schedule that is wired around dependencies makes this easy — you already know what's downstream of the thing that slipped, so re-sequencing takes minutes, not a re-plan of the whole job. Software that drafts a plan from your walkthrough, like Lilli, can cascade that kind of change automatically, but the discipline behind it works just as well on a whiteboard and a Sharpie.
Where these schedules actually break
In practice it is almost never the trade work itself. It's a permit or inspection that took longer than assumed, a fixture or material lead time nobody confirmed before the schedule was built, or a client decision — a selection, a change order — that sat unanswered longer than the schedule allowed for. None of those are framing problems or plumbing problems. They are schedule-design problems, and they're exactly why the float belongs around them, not around the crews doing the work.
Questions, answered.
How much buffer should I build into a renovation schedule?
Build float around anything you do not directly control, not around the work itself. A good rule: 3–7 days around any inspection, and a week added to the tail end of the job for the punch-list callback that almost always happens. Do not pad the trade work — pad the handoffs between trades and the outside dependencies (permits, inspectors, vendors).
What is the difference between float and a delay?
Float is buffer you planned for on purpose — time built into the schedule around a step you cannot fully control, like a city inspection. A delay is float you did not plan for, showing up as a surprise. A schedule with real float absorbs the normal slippage of a job; a schedule without it turns every normal slippage into a client phone call.
How long does a typical kitchen remodel actually take?
Real jobs run longer than most people assume before a hammer is even picked up. The 2023 U.S. Houzz & Home Study found kitchen renovations averaged 9.6 months of planning before construction started, followed by 5.1 months of actual build time. If your working schedule does not leave room for a planning runway and a multi-month build, it is describing the job you wish you had.
Should I schedule around trades or around inspections?
Both, but inspections come first. Trade order is something you control; inspection timing is not. Build the trade sequence, then lay the inspection windows on top of it as fixed points you schedule buffer around — never as an afterthought squeezed between two trades who are ready to move.
What causes most renovation schedules to slip?
Three repeat offenders: permits and inspections taking longer than assumed, material and fixture lead times not confirmed before the schedule was built, and a decision (a selection, a change order) sitting with the client or designer longer than planned. None of these are trade problems — they are schedule-design problems, and they are the reason float has to live around them, not around the framing crew.