How do you schedule emergency work alongside planned work?

The default arrangement in most trade and service businesses is that emergency work displaces planned work. Something urgent arrives, a booked job is pushed, and the customer who booked three weeks ago absorbs the disruption. That is efficient in the narrow sense and it transfers the cost to the party with the least involvement in it, which is why the resulting complaints are the ones businesses find hardest to answer.

The alternative depends on an observation that is easy to verify in your own records: emergencies are unpredictable individually and reasonably stable in aggregate. The specific call is a surprise; the number of such calls in a typical week is not. Once that is measured — and a quarter of records is enough — capacity can be reserved against the average rather than found by displacing something.

A reserved block works better than a general intention because it is visible in the schedule and therefore defended. An intention to keep some slack is consumed by the first busy week and never returns. A block that exists on the calendar can be released as it approaches if nothing has arrived, which converts unused reserve into planned work at short notice rather than into idle time.

The release rule is what makes the arithmetic work and it needs to be explicit. If the reserved capacity is unclaimed by a stated point — the previous afternoon, the morning of — it goes to the waiting list or to a planned job that can be brought forward. That requires a list of customers who would accept short notice, which is worth maintaining for exactly this reason and is usually easy to assemble because flexibility is common among people who have already booked.

What planned customers are told matters as much as the mechanism. A business that explains it holds capacity for emergencies is describing something reassuring — the same protection would apply to them — and it sets an expectation that occasional movement is possible. A business that says nothing and then moves a booking has surprised someone, and the surprise is what produces the complaint rather than the delay itself.

Where displacement genuinely cannot be avoided, the customer being moved should be contacted immediately rather than discovering it, offered a specific replacement rather than a vague reschedule, and given something for the inconvenience where the disruption is material. That sequence costs little and it separates a business that handles a difficult constraint well from one that appears disorganised, which is the distinction customers actually make.