Kaizen
Sound familiar? · Scheduling

How do I stop double-booking jobs?

Two customers were told 9am. One crew exists. Somebody is about to get a very apologetic phone call, and it is not the first time this month.

The short answer

Double-booking happens when more than one calendar exists: the office's, the owner's phone, the technician's memory, and the paper diary. Any booking made in one and not the others is a conflict waiting for the morning. The fix is one calendar that everyone books into and reads from, where a slot that is taken cannot be offered, crews and durations are set per job type, and the customer's confirmation comes from that same calendar. Conflicts stop being possible rather than merely rare.

You know this is you when

  • Bookings get made from the truck, the office, and the owner's phone, into different places.
  • The 7am scramble is reconciling who is actually going where.
  • A customer has been told two different times by two different people.
  • Reschedules are where most of the conflicts come from.
  • You have apologised for the same mistake more than twice this quarter.
67%
fewer no-shows is a typical result of layered SMS reminder sequences
KAIZEN CATEGORY RESEARCH · MORE DATA →
01

What it is costing you

A double-booking is two problems at once. One customer gets bumped, often on the morning of, and experiences the business as unreliable at the exact moment they were counting on it. The other gets a crew that arrived flustered. Then the day's route unravels to fit the rebook, and a third customer gets a later window than promised.

The reputational cost outlasts the day. Customers forgive a late arrival; they remember being forgotten. A bumped customer rarely complains to you. They tell the neighbour, and they do not rebook.

02

Why it keeps happening

Growth creates calendars. At one truck, one diary was enough. At three trucks and an office, bookings come from the field, the phone, the website, and the owner's text thread, and each person writes it down where they are. Nobody intends to keep four calendars; the business just never designated one.

Reschedules are the weak point. Moving a job means removing it from one place and adding it to another, and the removal is the step that gets skipped under pressure. The original slot stays booked in one calendar and open in another, and the next person fills it.

And durations are guessed. A job type with no set duration gets booked into whatever gap looks about right, which means a two-hour install can sit in a sixty-minute slot and collide with the next one on paper before it collides in the driveway.

03

How to fix it

  1. 01
    One calendar, and everyone books into it

    The office, the owner, the crew, and the customer's self-booking link all write to the same calendar and read from it. A booking made from the truck is visible in the office the same second. No diary, no second phone, no "I will add it when I am back."

  2. 02
    Make taken slots unofferable

    If a crew is booked, that crew's slot cannot be offered, by anyone, through any channel. The rule is enforced by the calendar, not by the person remembering to check it.

  3. 03
    Set durations and crews per job type

    An install is two hours and needs two people; a service call is forty-five minutes and one. Booking a job type reserves the right amount of the right crew automatically, so the conflict is caught at booking instead of on site.

  4. 04
    Attach the schedule to the customer record

    When the booking lives on the customer's record, the reschedule is one move that updates the calendar and texts the customer in the same action. Kaizen runs scheduling this way, so a change made anywhere is the change everywhere.

See the fix running, on your business.

A 30-minute walkthrough with Mel, built around scheduling chaos. No deck: the product, using scenarios from your trade.

Book a walkthrough
04

Common questions

Can a shared Google Calendar fix this?
It helps with visibility and it is far better than four diaries. What it does not do is enforce crew capacity and job durations, carry the customer history, or send confirmations and reschedule links itself. Most businesses outgrow it the first time two people book the same crew from two devices.
What about jobs booked from the truck?
They are the most important ones to capture, because they are the ones most likely to live only in a technician's head. Booking from the phone into the one calendar takes seconds and the office sees it instantly, so the truck becomes a booking point rather than a leak.
How do I handle emergencies that break the day?
Emergencies will always break the schedule; that is the job. The difference with one calendar is that the bumped customer is rebooked into a real slot and told by text automatically, instead of discovering the change when nobody arrives.
How does Kaizen prevent double-booking?
One calendar for every channel, crew capacity and job durations enforced at booking, confirmations and reschedules by text, and the schedule attached to the customer record so every change is one action. Conflicts are prevented, not reconciled.