Building Slack Into a Fully Booked Week

Why this matters

A schedule booked to one hundred percent capacity looks efficient on paper and is actually the most fragile plan a dispatcher can build. The first job that runs long, the first tech who calls in sick, the first same-day emergency, and the whole week starts collapsing into apologies and reschedules. Slack is not wasted capacity, it is the shock absorber that keeps one bad hour from becoming a bad week. Building it in deliberately, rather than hoping the week goes perfectly, is what separates a schedule that survives contact with reality from one that does not.

Step 1: Accept that a fully booked week is a promise you cannot keep

Every job estimate is a guess with a margin of error, and every week has a nonzero chance of a sick call, a traffic jam, or an emergency walking in the door. A week planned at full capacity assumes every one of those guesses lands exactly right and nothing unplanned happens. That almost never occurs. Start from the assumption that some slack is not optional if you want to hit your commitments, and the rest of this process is about deciding where to put it.

Step 2: Build buffer time between jobs, not just at the end of the day

The instinct is to stack jobs back to back and let overflow spill into the evening. This protects the wrong thing. Put small buffers, even ten to fifteen minutes, between individual jobs across the day instead of concentrating all slack at the end.

• A buffer between job two and job three absorbs a fifteen-minute overrun on job two without touching jobs four through eight.
• A buffer only at the end of the day absorbs nothing until the very last slot, meaning every job in between is running on a schedule with zero margin, and the compounding effect of several small overruns lands entirely on the last customer of the day.

Step 3: Reserve a real slot for same-day work, every day

Same-day emergencies are not a surprise, they are a predictable weekly volume with an unpredictable daily timing. Treat that volume as a line item on the schedule, not an interruption to it.

• Look at your own history: how many genuinely urgent same-day calls does a typical day actually bring in. Reserve at least that much open capacity, spread across two or three techs rather than concentrated on one, so a same-day call does not automatically fall to whoever happens to be free.
• If a day passes with no same-day emergency, that reserved slot becomes a chance to catch up on a job running behind, pull forward a job from later in the week, or give a tech a genuine breather. It is never truly wasted.

Step 4: Protect one tech's afternoon as float capacity

Rather than spreading thin slack evenly across every tech, consider designating one person per day whose afternoon stays lighter than everyone else's. This float tech becomes your answer to "who backs up the job that's about to slip" without having to pull someone off their own full day and cause a second problem to solve the first one. Rotate who carries the float role so it does not become an unofficial demotion for one person.

Step 5: Size the slack to the week's known risk, not a fixed formula

A slow, predictable week (routine maintenance, low weather risk, no known problem customers) needs less slack than a week during a heat wave, a cold snap, or right after a run of callbacks on a specific job type. Look at what you actually know about the week ahead, per the daily risk-scan habit, and size the buffer up or down instead of applying the same fixed cushion every week regardless of conditions. See related: Reading the Board for Tomorrow's Risk, Not Just Today's Jobs.

Step 6: Say no to the last slot before it becomes a problem

The hardest discipline in this whole process is refusing to fill the very last open slot on a day that is already tight, even when a customer is asking for it. A dispatcher under pressure to keep the board full will squeeze one more job in "since there's technically an opening." That opening is the shock absorber for everything already committed. Filling it converts your slack back into risk. Hold the line, and if the customer's need is genuine and urgent, use the reserved same-day capacity from Step 3 instead of cannibalizing the buffer meant for everyone else.

Step 7: Track whether the slack actually gets used, and adjust

Slack that never gets touched for a month straight is probably oversized; slack that evaporates by 10 a.m. every day is undersized. Review this monthly, not daily; day-to-day variance is normal and does not mean the plan is wrong. Look for the pattern over several weeks before deciding to add or remove buffer, and adjust the amount rather than the principle. The goal is never a perfectly full board, it is a board that can absorb a bad morning without every customer that day paying for it.

References

• See related: Reading the Board for Tomorrow's Risk, Not Just Today's Jobs
• See related: A Cancellation Opens a Same-Day Gap: Decision Tree
• Trade-standard practice for field-service capacity planning