shared calendar
A shared calendar is a calendar app used as a business's entire booking system, which works until an event gets deleted and takes the job with it.
A shared calendar, Google Calendar is the one I see most often, is a simple, flexible tool for booking a job onto a schedule that a whole team can see. It costs nothing extra, everyone already knows how to use it, and it is genuinely a good way to glance at what is happening today or this week. That is exactly why so many small businesses end up running their entire booking process through one.
The trouble starts when the calendar stops being a view of the schedule and becomes the only place a job’s details are actually stored. I saw this directly in one moving and rubbish removal business: every booking lived on a shared Google Calendar, full stop. Not a summary of a booking recorded elsewhere. The booking itself.
That arrangement is fragile in a specific, predictable way. A calendar event can be deleted by anyone with edit access, in one click, by accident. When that happens, the job does not just disappear from the schedule. Every detail attached to it, the customer, the price, the notes, goes with it, because there was never a second copy anywhere.
Why it matters to you
The risk grows with the size of the team, not shrinks. A one-person calendar is easy to keep track of. A calendar shared across an office and a field crew, with everyone able to edit, is a calendar where a single wrong click can erase a real, paid job with no trace of it left.
It is also a system of record problem in disguise. If the calendar is the only place a job exists, the calendar has quietly become the business’s most important piece of infrastructure, without anyone ever deciding that on purpose or building any protection around it.
What I do about it
I do not usually take the calendar away. It is a genuinely good way to see a day’s schedule at a glance, and there is no reason to throw that out. What I change is what stands behind it: lead capture and booking flow into a proper system that stores a job’s real details durably, with the calendar reading from that system rather than being the sole copy of it.
Whatever replaces the pure-calendar approach has to actually work for the people using it day to day, which is the exact step where a tool like Jobber usually fails. A system nobody trusts gets worked around, and the business ends up back on the calendar regardless of what was rolled out.
What it looks like in practice
Before: a booking exists as a calendar event and nothing else. Delete the event and the job is gone, with no other record anywhere to reconstruct it from.
After: the calendar still shows the schedule, because that view is useful, but the job’s actual details live in a system built to hold them. A deleted calendar entry is a scheduling mistake to correct, not a lost job.
Questions I get about this
- What is wrong with using Google Calendar to run bookings?
- Nothing, as a way to see a schedule. The problem is when the calendar becomes the only place a booking's details are stored. Delete the event, and the job, the customer, the price, all of it, is gone, because nothing else was keeping a copy.
- Isn't a shared calendar simple and cheap, though?
- It is, and that is exactly why so many small businesses start there. It works fine at a small scale with careful people. The risk grows as the team grows, because more people have edit access, and one accidental deletion can wipe out a real, paid job.
- What replaces it?
- The calendar itself usually stays, because it is a genuinely useful way to see the schedule at a glance. What changes is that it stops being the only record. A proper system holds the actual job details, and the calendar becomes a view into that system instead of the sole copy.
Want this set up properly for your business?
This is the kind of thing I build every week. Grab a time and we will talk through what fits.