EstateDeck Unit Management is the canonical master database for every flat in your society — owner, current tenant, parking slot, occupancy state, family members, vehicles. One source of truth that every other EstateDeck module reads from and writes back to.
Aligned with state Apartment Ownership Acts · Multi-phase societies · Ownership history forever · IT Act §65B-admissible.
EstateDeck Unit Management is the canonical master database for an Indian housing society or apartment owners' association. It holds, for every flat, the structural location (Phase → Tower → Floor), the unit attributes (carpet area, type, share certificate number per state AOA), the current legal owner and the complete ownership history, the tenant overlay where applicable, the parking slot deeded to the unit, the registered vehicles, and the family roster. The unit master is the single source of truth that every other EstateDeck module reads from — billing, accounting, documents, move-in/out, ANPR, smart meters. Database records are admissible as electronic evidence under IT Act 2000 §65B.
Mr. Pradeep Banerjee runs a 3-phase, 720-flat AOA in Kolkata's Rajarhat. Here's the canonical master record for Flat B-704 (Phase 2) — every field linked to every other module that touches it.
Members_2023.xlsx · Members_2024_final.xlsx · Members_2024_final_v2_REAL.xlsx · Members_Phase2.xlsx. Three towers, eleven sheets, last reliably updated by a Hon. Secretary who left in 2022.
Flat 1204 has a tenant in the gate register, a different name in the billing list, and a third name on the AGM voting list. All three are wrong. The actual owner moved to Singapore in 2021.
Slot B1-204 belongs to Flat 402, per the sale deed. The current resident parks there, but they moved into Flat 904 — and 402's owner is in Dubai. The dispute lands on the AGM agenda every year.
The previous tenant's car drove out of the gate three years ago and never came back. The RFID tag still works because nobody updated the registered-vehicle list. The new tenant's car is parked outside the gate.
EstateDeck is built as a set of focused modules. Unit Management holds the canonical master data — but it deliberately does not generate invoices, store PDFs, or run physical move events. Each of those lives in its own neighbouring module so the boundaries stay clean.
Model your society exactly as it exists — not a simplified version.
Carpet area, built-up area, share certificate — the data that downstream modules need.
Every legal owner. Every previous owner. Every sale date. Forever.
When the unit is rented, the tenant sits on top — the owner record stays.
The slot is deeded to the unit. Not to the person. End-of-story.
The master list of cars and bikes — read by ANPR for the gate allow-list.
Move from eleven Excel sheets to one database in one afternoon.
Less committee work. More accuracy. Full audit trail.
EstateDeck Unit Management is in production with three distinct society structures. Pick the closest to yours.
One tower, simple hierarchy, single registered bye-law. Owners are members of one cooperative; tenants come and go. Used by the Hon. Secretary as the central source of truth that the rest of the committee references daily.
Phase 1 built in 2017, Phase 2 in 2019, Phase 3 in 2022 — each phase has its own registered AOA, its own bye-laws, its own share certificate series. Unit Management holds the spine; phase-level configurations layer on top.
Property Manager runs 8–15 different societies under one EstateDeck account. Each society has its own unit master with its own statutory framework; PM gets a portfolio-level dashboard showing occupancy, owner-change trends, and tenant churn.
The Maharashtra Apartment Ownership Act 1970 defines the "deed of apartment" framework. The earlier Maharashtra Ownership of Flats Act 1963 (MOFA) still governs builder-to-buyer sale obligations. EstateDeck's unit schema captures both the apartment-deed structure and the share certificate per MCS Act 1960.
The West Bengal Apartment Ownership Act 1972 governs unit ownership in Kolkata and across the state, alongside the WB Co-operative Societies Act 2006 for CHS-registered societies. Share certificate format follows the WB registration requirements.
The Karnataka Apartment Ownership Act 1972 — for KAOA-registered Bengaluru apartment complexes (also registrable under Section 8 of the Companies Act 2013 for non-profit AOAs). EstateDeck supports both registration paths.
The Tamil Nadu Apartment Ownership Act 1994, applicable across Chennai, Coimbatore, Madurai, and the rest of the state. Defines unit boundaries and common-area share — both captured in the EstateDeck unit master.
North India's three primary AOAs — covering Delhi NCR, Gurugram, Faridabad, Noida, Greater Noida, and Lucknow. Each defines apartment unit + undivided share in common area + AOA-level governance. EstateDeck applies the configured framework per society.
Sections 54-58 of the Transfer of Property Act define sale and sale deed requirements. The Indian Stamp Act 1899 (state-specific rates) governs stamp duty on the deed. Both are referenced when EstateDeck runs the Ownership Transfer workflow.
"Before EstateDeck, I had a Google Drive folder with eleven Excel sheets — one per tower, plus a master that nobody trusted. When the Phase 2 AGM came up in 2024, three different members produced three different voter lists. We had to postpone by a week. After we migrated to Unit Management, the AGM voter list comes off the same database that the billing list comes off, that the parking allocation comes off, that the gate allow-list comes off. Owner moved? One edit. Tenant changed? One overlay. Sale completed? One transfer workflow, full history preserved. Sixteen months in, I haven't opened a single Excel sheet for a member record."
| What you need | Excel sheets | Basic ERP "members" table | EstateDeck Unit Database |
|---|---|---|---|
| Single source of truth | 11 versions exist | Only owner record | Owner + tenant + parking + vehicles |
| Ownership history | Overwritten on sale | Lost on transfer | Preserved forever |
| Parking ownership | Separate sheet, unlinked | Not modelled | Deeded to unit, follows ownership |
| Tenant overlay | Overwrites owner | Overwrites or no tenant model | Overlay — owner record preserved |
| Multi-phase support | Separate folders | Usually flat | 5-level hierarchy native |
| Other modules read it | Manual copy-paste | Limited integration | Every module reads live |
| Edit audit trail | None | Basic | §65B-admissible full log |
| State AOA-aligned schema | Ad-hoc | Generic | Per state AOA framework |
The questions every Hon. Secretary, Hon. Vice-President, and Property Manager asks before consolidating eleven Excel sheets into a real database.
We'll walk you through the unit master schema, the bulk import flow, and the cross-module references — in a 20-minute demo built for your society's structure, phase count, and statutory framework.
Book the Unit DB Demo →