Appointment capacity planner

Why the buffer is the input people get wrong

Planning a calendar to its theoretical maximum is the same mistake as running a highway at full occupancy: it works until the first disturbance, and then every following slot is late. Appointments cancel, homeowners reschedule to the one evening the rep is already booked, adjusters move an inspection, and a hail event drops a week of work into three days. The buffer is what absorbs that. Plan to fill every slot and the reschedules have nowhere to go but next week, which is how a roster ends up permanently a week behind while still reporting a full calendar.

Set it deliberately rather than by feel. A shop whose work is scheduled weeks out and rarely moves can hold back very little; a storm-restoration crew whose calendar is rebuilt after every event needs real slack, and the buffer is the honest place to put it rather than pretending the reps will absorb it. The planner keeps the raw ceiling visible next to the planned figure precisely so you can see what the buffer is costing you and decide whether it is worth it.

Which side binds, and why it is worth naming

Two capacities have to meet: the calendar the reps can absorb, and the appointments the phones can produce. Whichever is smaller is the one that decides your month, and every dollar spent on the other side is spent on the wrong thing. If setting is short, another rep sits idle and the hire that would have paid for itself was on the phones. If setting is ahead, the surplus does not become revenue -- it becomes double-booked slots, longer gaps between booking and visit, and appointments that go cold before anyone knocks on the door.

The planner names the binding side and prints the size of the gap in appointments per month, which is the unit both hiring decisions are actually denominated in. Read the shortfall as a target rather than a verdict: a gap smaller than one setter's monthly output is a scheduling or list-quality problem, not a headcount one, and hiring against it buys you the surplus case instead.

The headcount figure rounds up to a whole person on purpose. Rounding down produces a plan that cannot meet its own target and reads as though it can, which is the failure mode a capacity model is supposed to prevent.

Get your own two rates before you trust the output

The output is only as good as the appointments-per-rep and appointments-per-setter figures you feed it, so measure them rather than estimating. For the rep side, count completed appointments over a normal month and divide by rep-days worked, not by calendar days -- counting a rep who was on a roof for half the month as a full rep is what makes a capacity plan look achievable and behave otherwise. Include drive time and write-up in your judgement of what a day holds; a shop spread across a metro does not get the same number as one working a single suburb.

For the setting side, count confirmed appointments that were actually kept in the diary, divided by setter-days on the phones. Booked-and-cancelled is not capacity, and a setter whose bookings evaporate before the visit is producing a number that flatters the plan and starves the reps. If the two figures differ sharply between your best and worst performer, plan on something nearer the median than the best -- the ceiling you can staff to is the one an ordinary week produces.

Then re-run the month by season if your work is weather-driven. One blended annual average hides both the quiet month, where the binding side is demand rather than either capacity, and the storm month, where the answer changes overnight and the plan that mattered was the one you had written down in advance.

Worked example, using the numbers the page loads with

The planner opens with six reps running four appointments a day over twenty-two working days, a fifteen percent buffer, and three setters booking three appointments a day each. Reps times appointments times days is a raw ceiling of five hundred twenty-eight appointments a month. Take fifteen percent off for the buffer and the planned calendar is about four hundred forty-nine, with roughly seventy-nine held back as slack.

The setting side does not come close. Three setters at three bookings a day for twenty-two days produce a hundred ninety-eight appointments a month, against a calendar that can hold four hundred forty-nine -- a gap of about two hundred fifty-one appointments. The phones bind, not the calendar, and filling that gap takes seven setters in total, not three. Hiring a seventh rep here would do nothing: the reps already have more room than the phones can fill.

Where this fits

• Storm restoration appointment setting -- the setting side of this plan, if the answer came back that the phones are what binds.
• Storm damage appointments -- what happens to every input on this page in the week after an event.
• Call center cost estimator -- prices the setting headcount this planner says you need, three ways, so the plan carries a budget.
• B2B appointment setting explained -- the longer argument about what a setting function does and where its output actually comes from.