Scheduling That Survives Contact With Reality
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
A lot of owners build a schedule that would work perfectly if every job took exactly as long as planned and nothing went wrong. Then the first job runs an hour over, and the whole day — sometimes the whole week — collapses like dominoes behind it. The problem isn't that things went wrong; things always go wrong. The problem is a schedule packed so tight it has no room to absorb the overruns that are guaranteed to happen — a schedule that only works if reality cooperates, which it won't.
PACKED SCHEDULE RESILIENT SCHEDULE
Job A │Job B│Job C│Job D Job A │ buf │Job B│ buf │Job C
one overrun ─► everything one overrun ─► absorbed,
behind it collapses rest stays on track
─────────────────────────────────────────────────────────────
No slack = one delay wrecks the day. Slack = the day survives.Owner symptoms
One job running long throws off your whole day or week.
Your schedule assumes everything goes exactly to plan.
You're constantly apologizing for running behind.
Why this happens
A back-to-back schedule feels efficient and productive — no wasted time, maximum jobs. But it's efficient only in the fantasy where every job runs to plan. In reality, jobs overrun, parts are late, customers aren't ready, and traffic happens. With no buffer between jobs, the first delay cascades into every job after it, and you spend the day chasing a schedule you can never catch up to. Packing the schedule tight doesn't create capacity; it just removes the slack that would have kept the day intact.
Common mistakes
Booking jobs back-to-back with no buffer.
Scheduling for the best case, so any delay cascades.
Confusing a full schedule with a productive one.
How experienced operators think about it
They build slack into the schedule on purpose, because they know overruns are certain and a rigid plan guarantees a bad day. Their aim isn't to cram in the most jobs; it's to run a schedule that stays intact when reality intrudes — which means buffers between jobs and not booking every minute. They'd rather do slightly fewer jobs reliably than more jobs in a cascade of delays and apologies.
Practical actions
Build buffers between jobs, sized to how much your jobs typically run over.
Don't book every minute — leave room to absorb the normal delays.
Protect one flex slot for the overrun or emergency that will come.
Schedule from realistic durations, not best-case ones.
Questions every owner should ask
Does my schedule assume everything goes perfectly?
What happens to my day when one job runs an hour over?
Have I built in any slack to absorb the delays I know will come?
Frequently asked questions
How do I keep one late job from wrecking my whole day?
Build buffers between jobs and don't book every minute. Slack in the schedule absorbs an overrun so it doesn't cascade into everything after it. A resilient schedule beats a maximally packed one.
Isn't leaving buffer time just wasted capacity?
It feels like it, but it's insurance. Without buffers, one delay costs you the whole day in a cascade of knock-on delays. A little planned slack keeps the day — and your reliability — intact.
Related articles
Jobs Take Longer Than I Quoted — the pillar.
Building in Buffers Without Padding Every Quote — buffering the quote, not just the schedule.
We're Always Behind Schedule — the operations view.
Try a free Weekly Focus assessment
If one late job keeps wrecking your whole schedule, building in slack is the fix. Throne of Profit's free Weekly Focus assessment is a no-cost way to see where your schedule breaks.