Agree what goes in the calendar, who books what, and how travel and provisional work are shown. The software matters far less than the conventions everybody follows.

Why shared calendars fail

Rarely because the software is inadequate. Almost always because two people are using it differently.

One books only confirmed jobs. The other books everything including maybes. One includes travel time; the other does not. One puts the customer's name in the title; the other writes the job type.

Both are being reasonable. The calendar is now unreadable, because a block of time means different things depending on who created it.

Nobody discovers this until a double booking, and then it looks like carelessness rather than a missing agreement.

The conventions worth agreeing

The first two cause most double bookings. A job that runs from nine to eleven, with forty minutes of driving either side, occupies more of the day than the entry suggests.

Titles that work

A small convention with a large effect on readability.

Customer name, then the job type, then the address or town. In that order, because the calendar truncates and the first words are what shows.

"Henderson, boiler service, Coquitlam" tells you everything at a glance. "Service call" tells you nothing and requires opening it.

Phone number in the entry itself, not only in a separate system, because the moment you need it is the moment you are running late and driving.

A worked example

A two-van plumbing business double booking roughly twice a month.

The cause turned out to be travel. The office booked jobs back to back based on the stated duration, and the engineers were driving between them.

A job ending at eleven in one town and another starting at eleven in the next was, on the calendar, perfectly fine.

They changed one thing: every booking includes travel at the start, so an eleven o'clock job with thirty minutes of driving is entered from half ten.

Double bookings stopped almost entirely. The visible capacity per day fell, which was uncomfortable and accurate.

They had been running a schedule that only worked if nobody had to travel, which had never been true.

Provisional work

The second most common source of confusion.

A customer who might confirm occupies a slot in somebody's head and either does or does not appear in the calendar.

If it does not, the slot gets booked twice. If it does, the diary looks full when it is not.

The answer is showing provisional work differently: a different colour, a prefix in the title, or a separate calendar layered on top. Then it is visible without being treated as committed.

And a rule about how long provisional holds last, because a maybe from three weeks ago is not a maybe any more.

The counter-case

Where a shared calendar is more trouble than it solves.

A one-person business with no office. Sharing a calendar with nobody adds a synchronisation step and gains nothing.

Businesses where scheduling is genuinely centralised, with one person booking everybody, where a shared editable calendar creates the possibility of conflicting edits that a single scheduler does not.

And situations where the work is not time-slotted at all, such as a workshop taking jobs in order, where a list is more honest than a calendar.

The test is whether more than one person needs to know what a third is doing next Tuesday. If not, the simplest thing that works is right.

On the phone as well as the desk

A practical requirement rather than a preference.

A calendar that only exists on an office computer is a calendar that cannot be checked from a van, which means bookings get taken on paper and entered later.

That gap is where double bookings live. Two people entering from paper at the end of the day discover the conflict after both customers were promised.

Whatever you use has to be readable and editable from a phone, immediately, or the convention will be broken by circumstances rather than by carelessness.

Who books what

Worth settling explicitly in a business with more than one person.

The common arrangement that works: anybody can add to their own day, only one person adds to somebody else's, and anything affecting more than one person is checked first.

What causes trouble is everybody booking everybody with no rule, which produces conflicting entries and an argument about who was there first.

For a two-person business the rule can be informal, and it still needs saying aloud once rather than being assumed.

Keeping the customer informed from it

The step that turns a calendar into something the customer benefits from.

A confirmation when the booking is made, and a reminder the day before, both generated from the same entry.

That halves no-shows and it also catches errors: a customer who receives a confirmation for the wrong day says so immediately, which is considerably better than discovering it on the day.

Most calendar tools do this or connect to something that does, and it is worth setting up once.

What not to put in it

A calendar becomes unusable when it holds everything.

Reminders, tasks, notes to self and speculative ideas all compete with the entries that represent committed time, and after a fortnight nobody can tell at a glance whether a day is busy.

The rule that keeps it readable: the calendar holds time that is spoken for. Everything else belongs on a list.

The exception worth making is deliberate blocks for work that is not a customer job: a morning for quoting, an afternoon for maintenance. Those are genuinely spoken-for time and belong there.

What does not belong is a reminder to call somebody, which is a task with a deadline rather than a period of time.

Reviewing it weekly

Ten minutes that prevents most of the remaining problems.

Look at the week ahead together, or alone if there is only one of you. Check the provisional entries are still live, the travel is realistic, and nothing has been booked into a day that is already full.

That is the moment to catch a problem, rather than at half seven on the morning it happens.

How to record what happens on those jobs is a related habit, and it has the same requirement of being readable by somebody else.

Frequently asked questions

Why do shared calendars fail?

Because two people use them differently. One books only confirmed work, the other everything; one includes travel, the other does not. Both are reasonable.

What conventions need agreeing?

What counts as bookable, whether travel is included, what goes in the title, who books whom, assumed job duration, and how cancellations are handled.

What causes most double bookings?

Travel. A job ending at eleven in one town and another starting at eleven in the next looks fine on a calendar and is impossible in practice.

How should entries be titled?

Customer name, job type, then town, in that order because calendars truncate. Include the phone number in the entry itself.

How should provisional work be shown?

Differently: a colour, a prefix, or a layered calendar. Visible without being treated as committed, with a rule for how long a hold lasts.

Does it need to work on a phone?

Yes. A calendar only on an office computer means bookings are taken on paper and entered later, and that gap is where double bookings happen.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Double booking every few weeks?

It is usually travel time rather than carelessness, and the fix is one convention everybody follows.

Start a Conversation