Back to blog

    The Anatomy of a Double-Booking (And How It Actually Happens)

    A small group of tourists waiting at a Gothic Quarter meeting point in Barcelona looking around for a guide who hasn't arrived
    March 19, 20266 min readOperations

    Nobody sets out to book two tours for one guide. It's never a decision. It's an accident with six or seven small, reasonable steps in front of it. Here's one of those accidents, reconstructed…

    The short answer

    • A double-booking is almost never carelessness. It's two people editing an out-of-sync shared spreadsheet, where one save silently overwrites the other.

    • "Just be more careful" can't fix a structural problem; only a system that makes the conflicting entry impossible to save can.

    • The fix is a single source of truth that checks availability at the moment a guide is assigned.

    The point isn't to find the person who screwed up. The point is that no single person did. Two contradictory tabs did.

    The setup

    Small DMC in Barcelona. Three ops people, call them Núria, Pau, and you. One master Google Sheet, one tab per week. Around forty active freelance guides. A normal, healthy operation. This is a Wednesday.

    Step by step: how one guide ends up in two places

    1. 09:12: A repeat client emails Núria: private Gaudí walking tour, Saturday 10:00, English. She checks the sheet, sees Elena is free Saturday, and pencils her in.
    2. 11:40: Pau is on the phone with a different client closing a Saturday food tour in El Born, also 10:00. He opens the sheet. But it's slow to sync on his laptop and still showing the version from before 09:12. Elena looks free. He books her.
    3. 11:41: Two saves collide. Google Sheets keeps the last write. Núria's Gaudí note in Elena's row is quietly overwritten by Pau's food-tour note. No warning. No conflict flag. One of the two bookings has just silently vanished from the record. But not from the client's inbox.
    4. 14:00: Núria emails her client to confirm Gaudí, Saturday 10:00, Elena. From her memory, that booking is real. From the sheet, it never happened.
    5. Thursday: Elena gets a WhatsApp from Pau: 'Saturday 10:00, El Born food tour, yes?' She says yes. She never heard about Gaudí. Why would she, it's not in the sheet anymore.
    6. Saturday, 09:58: Two groups. Two meeting points. One Elena. She's in El Born. The Gaudí group is outside Casa Batlló wondering where their guide is.

    No one made a bad decision. Everyone made a reasonable decision against a version of reality that was already out of date.

    Where it actually went wrong

    Notice the failure isn't at 09:58 on Saturday. That's just where you felt it. The failure was at 11:40, when Pau made a real commitment based on a stale screen. Everything after that was baked in.

    Three things made it possible, and none of them is 'someone was careless':

    • The record could be silently overwritten. Last-write-wins is fine for a shopping list. It's a landmine for bookings.
    • The record and the commitment lived in different places. The sheet said one thing; the client email and the WhatsApp said another. Nothing reconciled them.
    • Nothing checked for physical impossibility. One human, two meeting points, same minute. The system had no concept that this was even a problem.

    Why 'just be more careful' doesn't fix it

    The instinct after a double-booking is to add a rule: always refresh before booking, always check with Núria, always colour the cell. Rules like that hold until it's the fourth Saturday in July and everyone's slammed. Process discipline degrades exactly when volume is highest. Which is exactly when double-bookings happen.

    You can't out-discipline a system that permits the mistake. You have to make the mistake impossible to enter.

    What 'impossible to enter' looks like

    The fix isn't a smarter human. It's a shared state that only allows one truth. When a tour and a guide are matched, that slot is taken: not pencilled, not probably, taken. And the same guide can't be committed to an overlapping slot, by anyone, from any laptop. Elena claiming the El Born food tour would leave the Gaudí slot showing as unfilled, sending it back to the pool where another qualified English-speaking guide can pick it up.

    That's the quiet value of one calendar with real assignment logic underneath it: not that it's prettier than the sheet, but that Pau physically cannot do at 11:40 what he did. There's also a record. Who was assigned, when, and by whom. So Thursday's 'wait, who's on Gaudí?' takes five seconds, not a forensic investigation.

    What it still won't fix

    No tool saves you from a guide who says yes and then forgets, or a client who books the wrong date. Those are real, and they'll still happen. What it removes is this specific, maddening, entirely preventable class of failure: two contradictory versions of the truth, both confidently acted on. If you've felt the 09:58 feeling, you already know it's worth removing.

    If reading that made your stomach drop a little, it's because you've lived some version of it. It's one of the reasons EasyPlanning exists. One calendar for every tour, guides who only see open slots that don't clash with their other tours, assignments you confirm, and a full history when someone asks 'who was on that?' If a stale spreadsheet has cost you a Saturday, start a free trial and re-run last week, or book a demo and we'll walk through your own worst near-miss. For the wider warning signs, see 5 Signs Your Tour Company Has Outgrown Spreadsheets.

    For how assignment requests, applications, and departure history work in EasyPlanning, see the staffing and assignments guide.

    Frequently asked questions

    How do double-bookings actually happen if we're careful?

    They're rarely carelessness. Usually two people edit a shared spreadsheet against slightly out-of-date views, and one save silently overwrites the other. The conflict is baked in the moment a commitment is made, not when it's discovered.

    How do you prevent double-booking tour guides?

    Use shared state that locks a slot when a guide is assigned, so the same guide can't be committed to an overlapping tour from any device. Plus a record of who assigned what and when. 'Be more careful' fails under peak-season volume.

    Stop running Saturday from a spreadsheet

    EasyPlanning gives tour operators one shared calendar and guides who apply for open slots themselves. No credit card to start.