How to handle a day that goes sideways

A trades week that only works when nothing goes wrong is not a plan. It is a hope with appointments in it.

Last updated: September 2026

Plan for the interruption you know is coming

Every reactive trade has a predictable rate of emergencies. You may not know which Tuesday, but you know roughly how many per week, because last year had them too.

Which means a diary booked solid is not optimistic, it is wrong. Every callout then breaks a promise made to somebody else, and the cost lands on the customer who waited in.

The businesses that handle this well do something very simple: they leave room, and they decide in advance who loses when room runs out.

Leave the gap on purpose

One to two unbooked hours a day, protected, is the single most effective scheduling decision a small trades business can make. It absorbs the callout, the job that overruns and the second visit for a part.

The instinct is to fill it, especially in a quiet week. Resist that: an unfilled gap in a quiet week costs you nothing, and a missing gap in a busy one costs you a customer.

Where the gap goes matters too. Late morning tends to be more useful than first thing, because it catches both the overnight emergency and the job that started badly at eight.

Decide who moves before you have to

When the day breaks, the decision has to be made in ninety seconds, so make the rule in advance. The job that moves should be the one where moving does the least harm, which is not the same as the least urgent.

A tenant who booked a day off work is expensive to move. A landlord who is not attending is not. A commercial customer with a contract may be contractually first. A vulnerable customer without heating is not moveable at all.

Write the order down once. In the moment, the person answering the phone should not be inventing a policy while somebody is shouting at them.

Where Dispatch fits

Practically, rearranging a day means three things: seeing the week, moving a job, and telling people.

The week calendar shows the team on one grid, and a booking is dragged to another day or another person. Double bookings warn rather than block, so you can deliberately squeeze a callout into an occupied slot when that is the right call, which in an emergency it often is. Priority is a field on the job, so the urgent work is visible rather than remembered.

When a visit moves to a different day the customer can be emailed automatically, and when a job is cancelled a written reason is required and recorded, which matters when somebody asks a fortnight later why that job never happened.

The engineer sees the change on their own phone with the job detail attached, so a reassigned callout arrives with the fault, the address and the history rather than as a text saying “go to Kempston”.

What to say to the customer who loses their slot

Tell them yourself, immediately, with a new date. Not an apology and a promise to ring back later: a specific alternative.

“I have had an emergency this morning and I am going to have to move you to Thursday morning, is that workable?” respects their time. Silence until they ring at four o clock does not, and that is the version that produces the review.

If you can, offer something concrete: a firm slot rather than a window, or first call on the new day. It costs nothing and it converts a broken promise into a managed one.

After the week from hell

Look at what actually happened rather than resolving to be better. Count the emergencies, count the jobs moved, and see whether the gap you left was in the right place or the wrong size.

Two or three weeks of that tells you your real emergency rate, and you can build the week around it rather than around the week you wish you had.

The related habit is keeping the waiting work visible so an unexpected gap can be filled rather than lost, which is covered in managing multiple jobs, and preventing double bookings covers the clashes you did not choose.

Questions

Scheduling emergencies: FAQ

How much slack should I leave in the week?

One to two unbooked hours a day for most reactive trades, protected even in a quiet week. An unfilled gap costs nothing; a missing one costs a customer.

Which job should I move when an emergency lands?

The one where moving does least harm, which is not always the least urgent. Decide the order in advance so nobody is inventing a policy on the phone.

Can I reassign a job to a different engineer quickly?

Yes. Drag it to another person or day on the week calendar, and they see the job on their own phone with the fault, address and history attached.

Will the customer be told automatically?

If you ticked to email them, they are emailed when the visit moves to a different day or is cancelled. Anything more personal is still worth a call.

Build a week that bends

One grid for the team, drag to move a job, a warning when things collide, and an email to the customer whose visit moved.