How to stop double booking your engineers

Last updated: September 2026

The cause is almost always two lists

A clash is rarely a mistake of attention. It is a structural problem: the owner books from memory in the van, the office books from a diary, and an engineer agrees a follow-up directly with a customer on site. Three lists, one week.

Everything else follows from that. The apology, the rebooked visit, the customer who now doubts you, the day that quietly loses two hours.

So the fix is not a stricter system. It is making sure there is one place a booking can exist, and that everyone can see it at the moment they promise something.

Why a warning beats a hard block

Software that refuses to let you book two things at once sounds sensible and is wrong for the trades.

Real weeks contain deliberate overlaps: two engineers on one job, a quick call squeezed into a gap, a nominal all-day booking that is really two hours. A system that blocks those teaches people to book around it, usually by not booking at all, and then the calendar stops being true.

A warning does the useful half. You are told at the moment you do it, and you decide. The clashes that get through are the ones you chose, which is exactly the right outcome.

Three habits that prevent most clashes

1. One calendar, and promises only from it. If a booking is not on the shared week, it does not exist. That includes the one the owner agreed in a van.
2. Engineers do not agree return dates alone. They say “the office will confirm a slot today” and mean it. This single rule removes most third-party clashes.
3. Book with a duration, not just a day. All-day bookings hide clashes by definition, and a week of them looks full when it is half empty.

Where Dispatch fits

The week calendar is one grid for the team, showing bookings against people. Drag to move a job to another day or another person, book timed or all-day, and add a note the engineer will see.

Double bookings warn rather than block, which is the deliberate choice described above. You see the clash at the moment you create it and can go ahead if that is what you meant.

Because a booking belongs to a job rather than being a standalone diary entry, moving it never separates it from the work, the customer or the invoice. And when a visit moves to a different day, the customer can be emailed automatically, which removes the second half of the problem: the clash that was resolved but never communicated.

On a phone the whole week stays available behind a horizontal scroll rather than being cut down, so the person in the van is looking at the same week as the office.

What about the emergency that breaks the day?

A callout will always displace something. The damage is not the displacement, it is the person at the other end who finds out by waiting in.

The routine worth having: when you move a booked visit for an emergency, the customer whose job moved is told before the engineer arrives at the emergency. That is one message, sent immediately, and it converts a complaint into a minor inconvenience.

Keeping one or two unbooked hours a day makes this far less frequent, which is covered in dispatching engineers efficiently and in handling scheduling emergencies.

When a clash still happens

Decide in advance who loses. Usually it is the job that can move with the least harm to the customer, which is not always the least urgent one: a tenant who booked time off work is more expensive to move than a landlord who is not attending.

Then tell them yourself, early, with a new date rather than an apology and a promise to ring back. A customer who is told on Monday that Tuesday has moved to Thursday is mildly annoyed. A customer who waits in on Tuesday is looking for a new trades business by Wednesday.