The booking mix-up that made me stop trusting Excel

A couple of years ago, before any of this existed, I ran bookings for a 40-unit project out of one Excel file on Google Drive. Two sales guys, one sheet, colour-coded rows - green for booked, yellow for token received, that sort of thing. It worked fine for the first fifteen units.

Then one Saturday, both of them were showing the same flat to two different families at the same time. Neither knew. One had opened the sheet on his phone that morning before it synced, marked the unit as "hold," and gone to meet his client. The other opened it twenty minutes later on his laptop, saw it as available, took a token of ₹51,000 in cash, and marked it booked. By evening we had two "booked" families for A-402, and only one flat.

It wasn't really an Excel problem

I spent a while being annoyed at Google Sheets for this, which in hindsight was pointless. The sheet did exactly what a shared file does - it showed whatever was last saved to whoever opened it. The actual problem was that nothing forced the two of them to be looking at the same version of the truth at the same moment. A phone with a weak signal in the site office was enough to break the whole system.

Sorting it out cost us one refund, one very awkward phone call, and about a week of one family not trusting us at all until we personally sat with them and worked out a better unit with some price flexibility. Not the end of the world, but not something I wanted to explain to an investor either.

What changed

The fix isn't complicated - a unit's status has to update the moment someone touches it, for everyone, not just for the person holding the phone. That's really the whole idea behind the Projects module in this CRM: the second a token is recorded against a unit, it's gone from "available" everywhere, on every device, immediately. No refresh, no "let me check with the office and call you back."

1. A unit can only be booked once - the system won't let a second booking through against the same unit
2. Every team member sees live status, not whatever was last saved locally
3. Token amount, date and who took it are recorded automatically, so there's no reconstructing it from memory later

I'm not going to pretend a spreadsheet can't work for a small project run by one person. It can. But the moment more than one person is touching bookings - which for most builders is by unit five or six - that's the moment a shared file stops being enough.