What a double booking actually costs a turf in Dhaka

Ask a turf owner about double bookings and you will usually get a shrug and a story. It happened twice last season, it was sorted out, one team played at eight instead of seven. No harm done.

The shrug is understandable and the arithmetic disagrees with it. A double booking on a Friday evening is one of the most expensive events in a facility’s week, and almost none of the cost shows up in the day’s cash count.

The arithmetic

Take a ground charging ৳2,500 an hour, with a Friday evening that sells out from 5 PM to 11 PM. Two teams arrive for the same 7 PM slot. What does the next hour cost?

• The slot itself, if you refund or comp one team: ৳2,500.
• The manager’s next forty minutes, spent apologising instead of selling: unbilled but not free.
• The eight to twenty-two players watching an argument at your gate. Every one of them has a phone and a group chat.
• The team you turned away, who booked with you every second Friday: about ৳65,000 a year, if they do not come back.
• The review. One angry post in a local football group reaches more prospective customers than a month of your boosted posts.

The ৳2,500 is the only number that reaches your books. The other four are the real bill, and they arrive quietly over the following months as a slightly emptier calendar.

Where they actually come from

In our experience of how grounds here operate, double bookings have three sources, and only one of them is carelessness.

1. Two channels, one calendar in someone’s head

A booking arrives by phone while another arrives on WhatsApp. Both are written down — one in the register, one in a message thread that gets scrolled past. There is no single place that knows both. This is the most common cause by a distance, and it is a structural problem rather than a human one.

2. The advance that was never confirmed

Someone sends a bKash advance and a screenshot. Your staff member marks the slot as taken. A second staff member, who never saw the screenshot, sells the same slot at the counter an hour later. Neither did anything wrong.

3. The verbal hold that outlived the conversation

"I will confirm by evening." Nobody wrote it down, or somebody wrote it down and nobody removed it. Holds without expiry are slow leaks: they either cause clashes or they quietly block sellable slots.

Why "we will be more careful" does not fix it

Because none of the three causes above is carelessness. They are all the same underlying problem: more than one person can commit the same hour, and nothing in the process makes that impossible. Adding vigilance to a system that permits the error only reduces the frequency. It does not remove the possibility, and busy Fridays are exactly when vigilance is thinnest.

A rule that depends on someone remembering is a rule that fails on your busiest evening.

What actually removes it

One calendar that every channel writes to — the counter, the phone, the customer’s app, the WhatsApp enquiry your staff enters — and a system that refuses to record two overlapping bookings on the same unit. Not a system that checks and warns. One that refuses.

That distinction matters more than it sounds. Software that "checks before saving" still has a gap between the check and the save, and two people clicking at the same moment can both pass the check. The only reliable place to enforce it is in the database itself, as a constraint on the data rather than a step in the code. That is how Sportify does it: the storage layer will not accept an overlapping booking, so the second one fails no matter how the timing falls.

Add holds that expire on their own, and the third cause disappears too — an unconfirmed slot releases itself instead of waiting for someone to remember.

The test to run on your own ground

Look at last month. Count the slots you refunded, comped or moved. Count the regulars who stopped coming. You will not get an exact figure, and you do not need one — if the number is more than zero on a ground that sells out on Fridays, it is already larger than the cost of fixing it.