Do Not Book What the Trucks Cannot Run: Capacity-Aware Scheduling

Capacity-aware scheduling means the calendar can only sell what the trucks can run: slots sized by job type, drive time counted as work, and a daily ceiling per crew. A full calendar is only a good problem if every booking on it actually happens. Overbooked jobs do not happen. They get apologized for.

01

Overbooking is a refund with extra steps

"A full calendar is a good problem to have." Owners say it with a tired grin, and the grin is hiding the math. A calendar can be full of two different things: work the crews will actually complete, or promises the afternoon will break. The second kind is not revenue. It is a refund with extra steps: the 4 PM call to push a customer to tomorrow, the goodwill spent, the review risked, the office hour burned on apologizing, and often the job itself quietly gone to whoever can actually show up.

The customer who got bumped does not remember being booked. She remembers being dropped. From her side of the phone, an overbooked shop and a flaky shop are the same shop. So the test of a schedule is not how full it looks on Monday. It is how much of Friday happened the way Monday promised.

02

Mapping calendar slots to real crew capacity

Overbooking starts with a calendar that lies about time. On a default calendar, every appointment is an identical block, and identical blocks are fiction in the trades. A thermostat swap is not a slab leak. When both book as "an appointment," the day fills with jobs whose real hours were never counted, and the afternoon inherits the difference.

The fix is unglamorous: give every job type an honest duration, measured from your own history rather than optimism. Look at what the last twenty of each actually took, door to door, and make that the slot length the calendar sells. Then set the ceiling: how many real hours a truck can run in a day, and stop the calendar at that number, not at the number that would be nice. Good intake feeds this directly, because a booking that captured what broke and how bad it is can be sized honestly at booking time. That sizing is half of what a proper job brief exists to carry.

An honest caveat about the templates: they are averages, and averages miss. The two-hour job will sometimes take four, and a rule-based calendar still needs a human override for the weird one, the hoarder house, the unit on the roof, the job the last shop abandoned halfway. Capacity rules shrink the surprises. Nothing deletes them, which is exactly why the schedule should also hold a little slack rather than being sold to the last minute.

03

Drive time is capacity too

Here is the leak hiding in most full calendars: the truck's day includes hours no invoice ever sees. A crew that runs six jobs scattered across the map spends a working shift's worth of the week behind the windshield, and a calendar that books jobs without asking where they are treats that time as free. It is not free. It is capacity, burned in traffic, invoiced to nobody.

Counting drive time changes booking decisions on the spot. Two jobs on the same side of town on the same day cost one drive. The same two jobs on opposite days cost four. A dispatcher who can see the map while booking will cluster work by neighborhood almost by reflex, and the calendar should make that easy: address captured at booking, jobs visible by area, and rules of thumb like holding certain days for certain zones. A shop that books geographically does not get more hours in the day. It gets more of its existing hours back from the windshield, which pencils out to the same thing.

04

The rules that let anyone, or anything, book safely

Now collect the pieces: slot lengths by job type, a ceiling per truck, drive-time sense, plus the reserved emergency hold and the release time if you run one. Together they form something more useful than a policy. They form a rulebook that makes booking safe no matter who is holding the pen.

That last part matters more every year, because the pen changes hands constantly. The owner books from the truck, the office books at the desk, and after hours, if the shop runs one, an automated booking system fills slots by the same rules. It checks the real calendar, offers real slots sized for the job, books only by the rules you set, and never double-books, because it reads the same calendar you do. Encode the limits once and the calendar itself becomes the bad guy, declining the un-runnable booking at the moment of booking, politely, instead of your dispatcher breaking a promise at 4 PM.

The score to watch is not how full the board looks. It is the completion rate: of everything booked, how much ran as promised. When that number holds through your busy weeks, the calendar has stopped selling fiction, and full finally means what the grin always hoped it meant.

QUESTIONS

Common questions

What is capacity-based scheduling?

Booking against what your crews can actually run: slot lengths set by job type, drive time counted as work, and a ceiling per truck per day. The calendar only offers what the trucks can deliver.

How do I stop overbooking my crews?

Encode the limits into the calendar itself: if the slot system only offers what fits, nobody has to be the bad guy at 4 PM. The rules say no at booking time, politely, instead of the dispatcher saying it at the deadline.