Skip to main content
GullySystem
A practical guide

Double booking a plot or unit: how it happens and how to stop it

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Clashes are recording gaps. Two people promise one unit without seeing each other’s promise, through verbal holds, token receipts written in a cash book, or brokers quoting from last week’s PDF. Close the gap with one live inventory that every desk and broker reads, holds that expire on their own, and every token receipt recorded against a unit number.

Where the second offer comes from

Walk back through your last clash. Almost every one began when an executive told a visitor “the east-facing corner plot is yours” while the master sheet at head office still showed it available. Nothing was recorded. Nothing blocked the next caller.

The same unit then reaches a second buyer through a broker, a walk-in or a phone enquiry, and each quotes from a list correct last Thursday. Nobody lies, yet both are wrong.

Worse, the corner premium, floor rise charge and covered parking slot differ per unit, so the second offer also carries a price that the first buyer was never given.

  • Verbal reservations that never reach the inventory sheet
  • Token cheques logged in an accounts ledger, not against the unit
  • Channel partners working from a PDF price list sent last week
  • Site office and head office keeping separate stacking plans
  • Cancelled bookings never released back to available

Why tokens and holds are the weak point

A token is a promise with a cheque attached, and when the receipt carries only a name and an amount, the unit number lives in one executive’s memory. Add a mandatory unit field.

When that executive takes leave, the unit looks free, and the title deed work later starts from the wrong plot, which nobody notices until registration day. Holds fail in another way. A hold with no end date becomes permanent by neglect, and sales teams stop trusting a sheet where half the held units are dead.

Salespeople then keep private notebooks of who really holds what, and the clash is built into the system until some busy Saturday exposes it in front of two buyers. Trust drains away first.

What a live inventory changes

A live inventory is one list of plots or flats, each carrying a status: available, on hold, token received, allotment letter issued, sale agreement signed, registered or cancelled. Every desk reads the same list. Nobody quotes before checking.

Moving a unit to on hold records who did it, for which buyer and until when, and nobody changes a status without typing a reason and signing the entry. No silent overwrite is possible.

A second executive trying the same unit sees the first hold, its owner and the minutes left, which ends the argument over who rang first.

  • One status per unit, with an audit trail of every change
  • Hold owner, buyer name and expiry on every hold
  • Token receipt that must name the unit before it saves
  • Agent view that shows availability but hides other buyers
  • Release to available when a booking is cancelled

Set hold expiry that people can live with

Pick hold lengths by stage. A walk-in hold might last a few hours, a hold pending a bank wire two days, and one waiting on a lender’s sanction letter a week. Short holds feel strict. They keep the stacking plan honest.

Expiry should warn before it acts, so alert the owner an hour or a day ahead and then release the unit without anyone pressing a button.

Allow one extension with a typed reason and let a manager approve the second, so favoured investors cannot freeze a corner plot or a penthouse quietly for weeks.

Test your process this week

Pull ten held units. Ask who reserved each, for which buyer and until when, then tally the answers found in the register against the ones recalled from memory. That ratio is your clash risk.

Fix the loudest gap first. For most developers that is the booking receipt, which should refuse to save without a unit number and a timestamp, so no token can float free.

Add auto-expiring reservations next, then retire the PDF price list your brokers forward and give them a live availability link that shows survey number, facing and carpet area.

Unit hold and token register

The register is one ruled page. Columns cover unit number, status, hold owner, buyer name, hold start, hold expiry, token receipt number, payment mode, broker name and release reason. Under the table sits a Monday checklist of three items: expired holds, receipts with no unit, and cancelled bookings not yet released.

Open a blank worksheet to print

Questions owners ask

Can a spreadsheet stop double booking?

Only for a small team in one office, and clashes return once the site office, head office and brokers each edit a separate copy. Choose a shared inventory.

How long should a hold last?

Match it to the stage, with hours for a walk-in and a few days while a token cheque clears at the bank. Longer holds need the sales head’s approval. Each extension also needs a typed reason stored in the hold record, so the reason survives staff changes and later disputes with the buyer.

What should happen when a buyer cancels?

The unit returns to available at once, with the cancellation reason on record, so no executive keeps telling visitors that a free unit is sold. Refunds run as a separate accounts task.

Do channel partners need access to the inventory?

They need availability and a button to request a reservation, but never other buyers’ phone numbers, payment status or the token amounts others have paid. Live access replaces the stale price PDF. Stale PDFs cause many clashes.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements