Structure

The project's physical stock: its towers (or wings), their floors and the units on each floor. Use it to set up a new project in bulk with the generator, to fix a single unit, to earmark units for rehab or amenities, and to see at a glance which units are free, held, allotted or booked.

Where to find it

Open a project and choose the Structure tab. The tab shows when you hold any permission on Towers, Floors & Units, on every kind of project. The Structure link on the project overview's Inventory card also brings you here, and the setup wizard's Towers & units step shows the same workspace.

You need the View permission on Towers, Floors & Units to see the towers and units. Without it the page shows "No access" and "You do not have permission to view the project structure. Ask your administrator."

In the default roles:

• Administrator and Project Manager can do everything here.
• Site Engineer can add and edit towers, floors and units, but not delete them.
• Most other roles, including Sales Executive, Front Desk and Legal & Documentation, can only view.

Before you start

• The project must exist. Its Property type decides which unit types you can pick: a unit type must suit the project (see Edit project).
• Unit types, unit configurations and amenities are lists your organization keeps under Settings > Lookups. Picking an amenity for a Common unit needs the View permission on Lookups.

What you see

Towers

The left-hand list Towers shows every tower of the project in alphabetical order, and the first one is selected when you open the tab. Each card shows the tower name and "N floors · N units · N planned" (the planned count only when set), then the amenities the tower provides, separated by " · " (for example "Gym · Refuge Area"): its rows on the Amenities tab plus the project-wide amenities one of its Common units houses. With no towers you see "No towers yet" and "A tower (or wing) holds floors and units. Add the first one to start."

With no tower selected the right side says "Select a tower" and "Pick a tower on the left to generate floors, browse units or view the inventory."

The selected tower

The tower name is the heading. Next to it are a view switch and a gear icon (hover Unit configurations):

View	What it shows
Generate	The guided generator for floors and units. Shown only with the Create permission.
Units	The tower's floors as a grid of coloured unit cells.
Floors	The floor list, for adding, renaming and removing floors.
List	A searchable table of every unit in the project.

A tower without floors opens on Generate when you can create; otherwise the tower opens on Units.

Units view

Headed "Inventory overview" and "<tower>, floor by floor."

• Counts: Available, Reserved (units reserved for tenants), Allotted, On hold (units held by a sent estimate), Booked and Sold, plus Blocked when any unit is blocked, and Common use when the tower has Common units. Common units (a gym, a refuge area) are not inventory: they are never in the status counts, only in Common use, so a tower of 35 flats and 2 common units reads "35 Available · 2 Common use", not "37 Available".
• Legend: Available, "Reserved for tenants (not yet allotted)", "Allotted to an allottee", "On hold (sent estimate)", Booked, then Sold and Blocked when present, and "PAP reserved" and "Common use".
• Floors run top-down, tagged G for ground, B1 for the first basement, 3F for the third floor, or the floor's own name.
• Each cell shows the unit number and its configuration (or unit type). An Available PAP or Common unit is coloured by its designation rather than green, because it is not for sale.
• Hover a cell to see the unit number, configuration or type, its carpet area (Mofa), facing, who holds it ("Allotted to…", "Booked by…", "On hold for…") or its status, and its designation.
• Click any unit to open it.

Floors view

The line "N floors · N units", then every floor, top floor first. Floors are labelled "Ground (0)", "Basement -1", "Floor 5", or "5 · Podium" when the floor has a name. Click a floor to expand it and see its units as small chips coloured by status. PAP units carry a PAP tag; Common units carry a C tag and a dashed border. Up to 200 units show per floor, then "+N more in Inventory".

With no floors: "No floors yet" and "Generate floors and units in one go, or add floors one at a time."

List view

A table of every unit in the project, starting on the selected tower.

• Filters: tower, configuration, status, designation, unit type (only when the project allows more than one), "Floor ≥" and "Floor ≤", and a search box "Search unit number".
• Columns: Tower, Floor, Unit, Configuration, Type (with facing), Carpet (Mofa) (with the super built-up area under it), Status and Designation.
• The pencil (or eye, if you can only view) on each row opens the unit. With nothing to show: "No units match".

The tower panel

Add tower or Edit <name>:

Field	Required	What to enter
Tower name	Yes	Up to 50 characters, for example "A", "Wing B", "Tower 1". "Wings are modelled as towers too." Must be unique in the project.
Planned floors	No	0 to 300. "Optional; for reference only. Floors are created on the Generate tab."
Description	No	Free text.
Occupation certificate no.	No	"Optional. This tower's own OC; blank = the project's OC covers it."
OC date	No	"Possession can be offered on this tower's units from this date."

The floor panel

Add floor or Edit floor <n>:

Field	Required	What to enter
Floor number	Yes	A whole number from -10 to 300. "0 is the ground floor; negative numbers are basements." A new floor suggests the number above the current top floor.
Name	No	For example "Podium" or "Terrace".

The unit panel

Add unit · <tower · floor> for a new unit, or Unit <number> for an existing one:

Field	Required	What to enter
Unit number	Yes	Up to 50 characters, unique on its floor. "Unit number is required" if blank.
Configuration	No	None or one of the organization's active typologies (an inactive one already on the unit shows "(inactive)"). The typology sets the unit type; the areas stay the unit's own.
Unit type	Yes	The kinds of unit the project's property type allows. Greyed out with "From the configuration" when a configuration is picked. "Choose a unit type" if blank.
Status	Yes	Available, Blocked or Reserved For Tenant. Other statuses are set by estimates, offers and bookings, and lock the field.
Designation	Yes	Saleable, PAP (reserved for PAP tenants) or Common (amenity space).
Amenity	No	Only for a Common unit: the amenity it houses (gym, society office, refuge area…). Amenities already on the project come first, labelled "Gym · on Tower A" or "Clubhouse · project-wide"; the rest of the lookup follows. The hint says where the chosen one stands: "Listed on Tower A on the Amenities tab", "Listed project-wide on the Amenities tab", or "Not yet listed on Tower A; it will be added to the Amenities tab when you save". With nothing chosen: "Gym, society office, refuge area … (Settings › Lookups › Amenities)". Shows "Needs the Lookups permission" without access to lookups.
Carpet area (Mofa)	Yes	In sq ft. "Enter a number" if blank.
RERA Carpet Area	No	In sq ft.
Super Built-up Area	No	In sq ft.
Facing	No	For example "East".
Description	No	Free text.

An existing unit also has a History button at the foot of the form (see below).

The hint under Designation explains each choice: Saleable is "Sales stock, or the rehab unit of a member / landowner"; PAP is "Only a PAP tenant can be allotted this unit; it is never sold"; Common is "Never allotted or sold; pick the amenity it houses".

Saving a Common unit with an amenity lists that amenity under the unit's tower on the Amenities tab (badge From units) unless it is already listed project-wide; the tower card on the left shows it too. Re-designating the unit, clearing its amenity, or deleting the unit or its floor takes the automatic row away again when no other unit of the tower houses it.

Unit configurations

The gear opens Unit configurations: "Typologies shared by every tower of this project". The card inside adds: "The typologies a unit can be, shared by every project (Settings > Lookups)." Only typologies whose unit type suits the project's property type are listed. Each typology shows as a chip with its unit type, a "N units" badge when units use it, and an Inactive badge when switched off. With none: "None yet. Without configurations, generate and unit forms take a plain unit type and areas."

The configuration panel (Add configuration or Edit <name>):

Field	Required	What to enter
Name	Yes	For example "2 BHK". "Shared by every project of the organization (Settings > Lookups)"
Unit type	Yes	One the project's property type allows.
Bedrooms	No	Apartments only, 0 to 20; "2.5 allowed".
Description	No	Free text.
Active	—	When editing only. "Inactive typologies stay on existing units but cannot be picked for new ones."

The panel reminds you: "A configuration is the typology only. Carpet (Mofa), RERA carpet and super built-up areas are recorded on each unit…"

What you can do

Add tower

Add at the top of the tower list, or Add tower when there are none, opens the tower panel. Click Add tower to save; you see “Tower "<name>" added.” and the new tower is selected.

• Who: the Create permission on Towers, Floors & Units. Otherwise the buttons aren't shown.
• If it's refused: "A tower with this name already exists in this project." shows under Tower name. Names are compared without regard to capitals, so "a" and "A" clash.

Edit tower

The pencil on a tower card (hover "Edit <name>"), or Edit tower on step 1 of the generator. Click Save changes; you see “Tower "<name>" updated.”

• Who: the Edit permission on Towers, Floors & Units.
• The same duplicate-name rule applies.

Delete tower

The bin on a tower card (hover "Delete <name>") asks "Delete tower?": "<name> with its N floors and N units will be removed. Towers holding units that are not Available cannot be deleted." Click Delete; you see “Tower "<name>" deleted.”

• Who: the Delete permission on Towers, Floors & Units.
• If it's refused: "Tower has N unit(s) that are not Available". Every unit must be Available first: release the holds, allotments and bookings, and unblock blocked units.

Generate

The Generate view builds floors and units for the selected tower in one run, one floor range at a time. The panel on the right, This run so far, previews the floors and the first unit numbers each range will create.

1. Tower. Shows Planned floors, Floors created so far and Units created so far, with Edit tower and Add another tower. "Floors and units are generated into this tower. Existing floors are reused and existing unit numbers are skipped, so a run can be repeated safely." Click Define the first floor range (or Add another range).
2. Floor range.
   • From floor and To floor (both required, -10 to 300). On a tower with no floors yet, the first range starts at 0. When Planned floors is set, To floor starts one below it (for 20 planned floors, 0 to 19). Each further range starts on the floor after the last one.
   • Skip floors ("Optional, comma separated"), for example 13.
   • Range label, optional, for example "Shops".
   • Floor name pattern, which starts as "Floor {floor}". "{floor} becomes the floor number, {floor_code} G / B1 / 1 …"
   • Click Continue to units. "Must be greater than or equal to the first floor" means To floor is below From floor.
3. Units. Choose what is on these floors:
   • Same units on every floor: Units per floor (1 to 100, starts at 4), Unit type, Carpet area (Mofa) (required), and optionally RERA Carpet Area and Super Built-up Area. Then Designation ("Saleable (default)") with Amenity for Common units, the Unit number pattern (starts as {floor}{seq:02d}) and a Facing cycle such as "East, West, North, South", applied to the units in order, repeating.
   • Different units per floor: list every position on one floor, and the same list repeats on every floor of the range. Add a position with a button per active configuration, Custom position or New configuration…. Each row has Configuration ("Custom (no configuration)"), Unit type, Carpet (Mofa), RERA carpet, Super built-up, Facing and its own Designation (blank means the range's), with Duplicate and remove icons. A row that ends up Common shows Amenity in place of Designation. This kind has its own Unit number pattern, where {seq} is the row number.
   • No units: floors only, for parking, amenity, refuge or service levels. Parking slots themselves are set up on the Parking tab.
   • How patterns work explains the tokens: {floor} (the floor number), {seq} (the unit's position on its floor, from 1), {tower} (the tower's name) and padding such as {seq:02d}. The field hints also offer {floor_code}, which gives G for the ground floor and B1, B2 for basements, so {floor_code}{seq:02d} numbers the ground floor G01, G02.
   • Click Review.
4. Review & generate. Lists the ranges in this run, each with edit and remove icons. Click Add another range for the next set of floors, or Generate N units (Generate N floors when the run has no units).

When the run succeeds you see "N units on N new floors created in <tower>." The view switches to Units with a summary: "Generated N floors and N units in <tower> · N floors already existed · N unit numbers skipped as duplicates. Running the generator again with the same pattern only adds numbers that do not exist yet." New units are Available.

• Who: the Create permission on Towers, Floors & Units. Without it the Generate view isn't shown.
• Greyed out: Generate is greyed out, with no reason on hover, while the run has no range, or while the review shows a red note: "Two ranges cover the same floor; edit the from / to numbers.", "More than 5,000 units in one run; split it into several runs." or "Range N: <pattern problem>".
• Mixed-use projects: on a Mixed project, step 1 offers Start from a mixed-use template (shops, parking, offices, apartments) while no range has been added. It fills four ranges and jumps to the review: two shops on the ground floor (numbered S01, S02), parking floors 1 to 3 with no units, two offices per floor on 4 and 5, and four apartments per floor from 6 up to the planned floors (or up to 12 when fewer than 7 are planned). The template leaves the areas blank: edit each range and fill in the carpet area (Mofa) before you generate.
• If it's refused: the reason names the range, for example "Range 2 · designation: …". Common ones: "Enter the carpet area (Mofa)", "Choose a unit type", "Pick a configuration or enter the carpet area (Mofa)", "Floor N is already covered by range M", "At most 5000 units per run (this plan makes N)".
• The preview warns "no {seq} token: every unit on a floor would get the same number" when a pattern has no {seq} and more than one unit per floor.

Add floor

Add floor in the Floors view (or Add a floor when the tower has none) opens the floor panel. Click Add floor; you see "Floor N added."

• Who: the Create permission on Towers, Floors & Units.
• If it's refused: "This floor number already exists in the tower." shows under Floor number.

Edit floor

The pencil on a floor row (hover "Edit floor"). Change the number or name and click Save changes; you see "Floor N updated."

• Who: the Edit permission on Towers, Floors & Units.

Delete floor

The bin on a floor row (hover "Delete floor") asks "Delete floor?": "Floor N and its N units will be removed. Floors holding units that are not Available cannot be deleted." Click Delete; you see "Floor N deleted."

• Who: the Delete permission on Towers, Floors & Units.
• If it's refused: "Floor has N unit(s) that are not Available".

Add unit

The + on a floor row in the Floors view (hover "Add unit") opens the unit panel for that floor. Click Add unit; you see "Unit <number> added."

• Who: the Create permission on Towers, Floors & Units.
• If it's refused: "This unit number already exists on the floor." shows under Unit number (capitals are ignored). "Configuration <name> is for <type> units, not <type>" means the greyed-out Unit type still holds a different type from the configuration you picked.

Save changes (unit)

Click a unit in any view to open Unit <number>. Change what you need and click Save changes; you see "Unit <number> updated."

• Who: the Edit permission on Towers, Floors & Units. With view access only, the pencil in List becomes an eye. You can still open a unit, but saving is refused with "You do not have permission to do that."
• Greyed out: Save changes stays greyed out, with no reason on hover, until you change something.
• Status: you can move a unit between Available, Blocked and Reserved For Tenant. A unit that is Reserved For Buyer, Allotted, Booked or Sold shows "This unit is <status>; its status is controlled by the booking and cannot be changed here." and the field is locked. For a held unit the hint reads "On hold: a sent estimate holds this unit for its buyer. It is released when that estimate is cancelled or expires, or becomes Booked."
• Designation: locked on any unit that isn't Available or Blocked, with the hint "Locked while the unit is <status>; release it first".
• If it's refused:
  • "This unit number already exists on the floor."
  • "That configuration is inactive; reactivate it or pick another."
  • "Configuration <name> is for <type> units, not <type>"

Delete (unit)

Delete at the bottom of the unit panel asks "Delete unit?": "Unit <number> will be removed. Only Available units can be deleted." Click Delete; you see "Unit <number> deleted."

• Who: the Delete permission on Towers, Floors & Units. Otherwise the button isn't shown.
• If it's refused: "Only Available units can be deleted (this one is <status>)". A unit that appears on an estimate or booking can't be deleted either: "That conflicts with existing data."

History (unit)

History at the foot of an existing unit's panel (hover "Who changed this record, what and when") opens the panel History · Unit <number>: who changed the unit, what they changed and when, newest first.

• Who: anyone with the View permission on Towers, Floors & Units, or the View permission on Audit Trail. A new unit has no history, so the button shows only once it is saved.
• Each entry has a badge (Create, Update or Delete) and a summary ("Created", "Changed <fields>" or "Deleted"), then who made the change (a person, "<name> via AI connector", Workflow or System), the date and time, and the IP address when one was recorded. An update lists each Field with its Before and After values, using the screen's area names (Carpet area (Mofa), RERA Carpet Area, Super Built-up Area); a create or a delete has a Show N values link.
• It loads 25 changes at a time; Load older changes brings the next ones. With nothing recorded you see "No history yet" and "Changes are recorded from 28 Sep 2026; nothing has changed on this record since."

Add configuration

Add configuration in the Unit configurations panel, or New configuration… in the unit panel and in the generator's Different units per floor step. Click Add configuration; you see “Configuration "<name>" added.” From the unit panel or the generator, the new typology is picked for you straight away.

• Who: the Create permission on Towers, Floors & Units.
• If it's refused: "A configuration with this name already exists in this project." shows under Name. Despite the wording, names are unique across the whole organization, not just this project.

Edit or delete a configuration

Click a chip in Unit configurations to open Edit <name>.

• Save changes saves it; you see “Configuration "<name>" updated.” Untick Active to stop the typology being picked for new units. The Edit permission on Towers, Floors & Units is needed to open a chip.
• Delete asks "Delete configuration?": "<name> will be removed. Configurations in use by units cannot be deleted; deactivate them instead." You see “Configuration "<name>" deleted.” It needs the Delete permission on Towers, Floors & Units.
• If delete is refused: "N unit(s) use this configuration; deactivate it instead".

Export

Export above the tower list (hover "Download this list as an Excel sheet") downloads every unit of the project as an Excel workbook. Use it to edit units in bulk and bring them back with Import.

• Who: the View permission on Towers, Floors & Units and on Projects.

Import

Opens Import units: "A row names its tower and floor; a tower or floor that is not there yet is created. Status is not in the sheet — it follows estimates, offers and bookings."

1. Download template (or use an exported file) and fill it in. The closed columns are dropdowns. What each column takes explains every column.
2. Choose Excel file (.xlsx or .csv). The file is checked first, and nothing is written yet: "Checked, nothing written yet. Use Import to apply it." The counts show how many rows are to add, to update, skipped and with errors. A row that creates a tower or floor says so.
3. Click Import N rows. You see "N added, N updated." and "Imported into <project>."

Import N rows is greyed out, with the reason on hover, when:

• no file is chosen: "Choose a filled-in sheet first";
• some rows fail: "Fix the N rows listed below, then choose the file again" (the dialog also says "Nothing has been written. Fix the rows below in your sheet and choose the file again.");
• nothing would change: "This sheet has no rows to add or update".

Row errors you may see include "tower: required", "unit_number: required", "unit_number: the same unit appears on row N", "unit_type: required for a new unit (or name a configuration that says it)", "carpet_area_sqft: required for a new unit" and "designation: unit <number> is <status>; release it before changing what it is for".

• Who: both the Create and Edit permissions on Towers, Floors & Units. Otherwise the button isn't shown.

Statuses

A unit's status says whether it can be sold or given. Only Available, Blocked and Reserved For Tenant are set by hand; the others follow the sales and rehab flows.

Status	Meaning	How it changes
Available	Free stock. Every new unit starts here.	Set by hand. A sent estimate moves it to Reserved For Buyer; allotting it on an offer moves it to Allotted.
Blocked	Kept off the market, for example for a dispute or the developer's own use.	Set by hand; set it back to Available to release it.
Reserved For Tenant	Earmarked for the rehab side but not yet promised to anyone.	Set by hand. Allotting it on an offer moves it to Allotted.
Reserved For Buyer	Shown as "On hold": a sent estimate holds it for its buyer.	Back to Available when the estimate is cancelled, superseded or expires, or the opportunity is lost; Booked when it is booked.
Allotted	Promised to a named allottee (member, landowner or PAP tenant) on an offer.	When the offer gives the unit up or is cancelled, it returns to the status it had before.
Booked	A buyer's booking holds it. An allottee's unit stays Allotted when booked.	Back to Available when the booking is cancelled.
Sold	Appears in the filters, legend and counts.	Can't be set by hand, and no step in the app sets it: a booked unit stays Booked.

Things to know

• Designation is separate from status. A Saleable unit is sales stock, or the rehab unit of a member or landowner. A PAP unit can only be allotted to a PAP tenant and is never sold. A Common unit houses an amenity and is never allotted or sold. Only Saleable units can go on a buyer's estimate or booking. Once an estimate, offer or booking relies on a unit, its designation is locked, so a promised unit can't quietly change what it is for.
• Three areas. Every unit needs a Carpet area (Mofa); RERA Carpet Area and Super Built-up Area are optional. Which of the three a Per Sqft price multiplies is the project's chargeable area (Carpet area (Mofa) unless your organization or the project says otherwise). If a unit lacks that area it can't be priced, so record it before you price the unit. See Unit Pricing.
• The units sheet names its area columns differently. The column for RERA Carpet Area is headed built_up_area_sqft, and the column for Super Built-up Area is headed rera_carpet_area_sqft. Check you are filling the right column.
• Unit types follow the project's property type. A residential project offers residential unit types only, and so on. If a type is missing, either change the project's property type or mark the unit type as suiting it under Settings > Lookups.
• Configurations are shared by the whole organization. Adding, renaming or deactivating one here changes it for every project. A configuration sets only the unit type (and bedrooms), never the areas, even though some hints show sizes in examples such as "2 BHK 650 sqft".
• The generator is safe to repeat. Existing floors are reused and unit numbers that already exist on a floor are skipped (capitals ignored), so running the same ranges again only adds what is missing. At most 5,000 units and 50 floor ranges go in one run.
• The tower's OC gates possession and revenue. While the promoter's books' revenue policy requires an occupation certificate, possession can't be offered on a unit before the OC date of its tower, or of the project (on its Settings tab) when the tower has none; a tower's own OC always wins for its units. The revenue run recognises a booking's revenue only once the OC covers the trigger date, and notes "No occupation certificate on or before the trigger date" until then. The OC isn't shown on the tower card; open Edit <name> to see it.
• Deleting is for mistakes only. A tower, floor or unit can only be deleted while every unit in it is Available, and deleting a tower removes all its floors and units with it. Units on an estimate or booking can't be deleted at all.
• The locked-status note always mentions the booking. "…its status is controlled by the booking and cannot be changed here" also shows for units held by an estimate or allotted on an offer. Release those from the estimate or the offer.
• Sheet import rules:
  • Status is not in the sheet.
  • A row updates an existing unit when it carries that unit's id (from an export), or names the same tower, floor and unit number. Otherwise it adds a new unit and creates any missing tower or floor.
  • A unit can't be moved to another tower or floor by sheet.
  • Nothing is written unless every row passes.

Related

• Project overview
• Project setup wizard
• Edit project
• Project settings
• Parking
• Unit Pricing
• Construction Stages
• Society & Tenants
• Revenue policy
• Revenue run