LeadOne AIby One Construction
Operations6 min readUpdated

Stacking plans: how to manage unit inventory, holds and bookings without double-selling

How developers can use a live stacking plan to manage unit status, time-limited holds, channel partner access and launch-day bookings without double-selling.

On this page
  1. What a stacking plan is
  2. Define statuses and who can change them
  3. Rules for holds
  4. Booking needs proof of payment
  5. Channel partners and inventory
  6. Pricing on the stacking plan
  7. Launch day
  8. Reading the stacking plan for decisions
  9. Blocked units and landowner shares
  10. What to report every week
  11. Sources

Every developer has a story about a unit sold twice. Two sales managers each promised the same corner flat on the 14th floor. A channel partner took a cheque for a unit that had been booked that morning. The buyer who loses out rarely comes back, and often tells others.

Double-selling is almost always an inventory problem. Status lives in a printed sheet, a WhatsApp group or an Excel file that three people edit. A stacking plan that is live and shared solves most of it. This article explains how to set one up and the rules that make it work.

01What a stacking plan is

A stacking plan shows a tower as a grid. Floors run top to bottom and unit positions run left to right. Each cell is a unit, coloured by status. A sales manager can see at a glance which flats are available on which floors, and a promoter can see which stacks and configurations are selling.

A simplified stacking plan for four floors of one tower.
Floor01 (3 BHK, park)02 (2 BHK)03 (2 BHK)04 (3 BHK, corner)
12BookedAvailableOn hold (till 6 pm)Booked
11AvailableAvailableBookedSold
10BookedBlocked (landowner)AvailableBooked
9SoldAvailableAvailableOn hold (till Fri)

02Define statuses and who can change them

StatusMeaningWho can set itExit
AvailableOpen for saleSystem, on releaseHold or booking
On holdReserved for a named buyer until a set timeSales executive or managerBooking, or automatic release on expiry
BookedBooking amount receivedCRM team on payment proofAgreement registered, or cancellation
SoldAgreement for sale registeredCRM teamCancellation only, with approval
BlockedNot for sale for now (landowner share, management reserve, later release)Sales head or promoterRelease by the same role

The rule that prevents most double-selling: a unit can move from available to on hold or booked only through the system, and only one buyer can hold it at a time. If two people try at once, the second sees that it is taken.

03Rules for holds

Holds are where inventory discipline breaks down. Reps hold good units 'for a client' and forget. Popular units sit idle for weeks while other buyers are told they are unavailable.

  • Time limit. For example, 24 hours without a token and 72 hours with one.
  • Named buyer. A hold must link to a lead with a phone number. No anonymous holds.
  • Automatic expiry. When the time runs out, the unit returns to available and the rep and manager are notified.
  • Extensions need approval. A manager can extend once. Beyond that, the sales head decides.
  • Limits per rep. Cap active holds per person during a launch.
TipReview expired holds weekly by rep. A rep with many expired holds and few bookings is blocking inventory from colleagues, deliberately or not.

04Booking needs proof of payment

A unit should become booked only when the booking amount is received or a cheque is recorded with its details. Verbal confirmations should stay as holds. This keeps the booked count honest, which also matters for your quarterly RERA update on units booked.

05Channel partners and inventory

Brokers need to know what is available, and they need it fast. Sending them a PDF stacking plan each morning creates stale information by noon. Options that work better:

  • Give partners view-only access to live availability, without prices if you prefer to share those separately.
  • Let partners request a hold through the system, approved by your sales manager.
  • Tie each hold to the partner's registered lead, so ownership and brokerage are clear.

06Pricing on the stacking plan

Each unit's price depends on base rate, floor rise, PLC and parking. If these are applied by hand, mistakes follow. Attach price rules to the tower and units so the stacking plan shows the computed price for each available unit.

This also makes price changes easier. When you raise the base rate by ₹200 per sq ft after the first 30% of a tower is sold, the change applies to every available unit at once, and booked units keep their agreed price.

07Launch day

Launches put the most pressure on inventory. Many buyers want the same units, often within minutes.

  1. Freeze the price list and the blocked units the evening before.
  2. Decide the allotment method: first-come, draw of lots among EOIs, or slots. Publish it.
  3. Give every sales manager the same live view on a tablet or phone.
  4. Allow holds only through the system, with short expiry (for example 30 minutes on launch day).
  5. Collect booking amounts on the spot and mark units booked immediately.
  6. Keep a person whose only job is to resolve conflicts.

LeadOne AI's stacking plan runs on every rep's phone and the web, with time-limited holds and an audit log of status changes.

08Reading the stacking plan for decisions

  • Absorption by stack. If one stack sells much slower, look at its view, layout or price.
  • Floor bands. If lower floors sell out first, floor rise may be too steep, or buyers are price-sensitive.
  • Configuration mix. If 3 BHKs lag, consider a payment plan or a targeted campaign before cutting price.
  • Holds that never convert. Patterns by rep or by unit tell you where the problem is.

09Blocked units and landowner shares

In joint development arrangements, a share of units belongs to the landowner. Management may also reserve units for later release or for pricing reasons. These units should appear on the stacking plan as blocked, with the reason recorded, so nobody quotes them by mistake.

  • Only the sales head or promoter can block or release a unit.
  • Record why each unit is blocked: landowner share, management reserve, legal hold, or pricing.
  • If the landowner sells their units through your team, track them separately so brokerage and collections go to the right party.
  • Review blocked units every month. Units blocked 'for now' can stay blocked for years.

10What to report every week

ReportWhy it matters
Available units by configuration and floor bandShows what you actually have to sell
Active holds and holds expired this weekShows hold discipline by rep
Bookings and cancellations this weekShows net absorption
Realised price vs list price by unit typeShows where discounts concentrate
What is a stacking plan in real estate?
A grid view of a building showing every unit by floor and position, coloured by status such as available, on hold, booked and sold. It helps sales teams see availability and avoid selling the same unit twice.
How long should a unit hold last?
Many developers use 24 to 72 hours, shorter on launch days. The key is a written limit, automatic release on expiry and approval for extensions.
Should channel partners see live inventory?
Giving partners view-only live availability, with holds requested through the system, reduces conflicts. Share prices according to your own policy.
How do developers prevent double booking of flats?
Keep one live inventory that every rep and partner uses, allow holds and bookings only through it, let only one buyer hold a unit at a time, release expired holds promptly, and mark a unit booked only on proof of payment.
Should landowner units appear on the stacking plan?
Yes, as blocked units with the reason recorded. That way nobody quotes them by mistake, and you can track them separately if your team also sells them for the landowner.

Put your next launch on LeadOne AI.

Write to us for a demo on your own project's units and price list.
hello@leadoneai.com
Your reps can download the app today.
Download on the App StoreDownload on the App StoreAndroid: coming soon to Google Play