Create a Unit
Creating a unit defines a single sellable item — a plot, flat, villa, or shop — inside a subproject. You give it a number, a type, an area drawn from the subproject's saleable pool, a price, its owners, and its boundaries.
Before you start: the subproject must exist and have saleable area allocated to it (a unit's area comes from that pool). The partners who own the unit should already be in the system.
Opening the form
- Open the subproject and go to its Units section.
- Click Add Unit (requires the create unit permission).
- The unit form opens, organized into sections.
Section A — Basic details
| Field | Notes |
|---|---|
| Unit Number | Required. Unique within the subproject — two units in the same subproject can't share a number. 1–50 characters. |
| Unit Type | The type of unit (Plot, Flat, Villa, Shop…). Selecting it loads any type-specific custom fields. |
| Facing | The direction the unit faces (for example, East, North-East). |
| Status | The unit's starting status. New units typically start at Draft while being configured. |
Unit number uniqueness
The unit number must be unique inside its subproject. If you reuse a number, the save is blocked. (Different subprojects can reuse the same number — uniqueness is scoped to the subproject.)
Area — drawn from the subproject's saleable allocation
A unit's area isn't typed in freely — it's allocated from the subproject's saleable area. The form shows the saleable area available (total saleable, already allocated, and what's left). You allocate this unit's share from that remaining pool.
- You can record length and width, from which the area is derived, or enter the area directly.
- The unit's area is the sum of its allocations against the available saleable area, validated so you can't allocate more than the subproject has left.
When editing an existing unit, the available-area figures exclude that unit's own current allocation, so the maths stays correct while you adjust it.
Pricing
Record the commercial terms for the unit:
- Square-foot rate — the price per square foot.
- Total rate — the total price for the unit.
These feed quotations and sales orders downstream.
Section B — Shareholders
The shareholders table records which partners own this unit and in what proportion. The standard ownership rule applies:
Holdings must sum to exactly 100%, and at least one managing partner is required.
- One row per partner, each with a percentage.
- No partner appears twice.
- The total must be exactly 100.00%, or the save is blocked.
See Validation rules for the precise arithmetic.
Section C — Boundaries
Record the unit's physical boundaries on each side. All four are optional and can be filled partially:
| Side | Example |
|---|---|
| North | "Plot 24" |
| South | "30-ft road" |
| East | "Plot 22" |
| West | "Open space" |
Boundary descriptions matter for the legal sale document, so capture them as accurately as you can.
Custom fields
If the unit type or your organization defines custom fields, fill in any that apply. Mandatory fields must be completed before saving.
Saving
When you click Save:
- Validation runs on submit — errors show inline and the form jumps to the first problem (duplicate unit number, shareholders not summing to 100%, area over the saleable limit, etc.).
- The unit saves with its shareholders, boundaries, and an initial status timeline entry, all atomically.
- The unit is now part of the subproject and can be placed on the site map (for Layout subprojects) and moved through its lifecycle.
Creating units in bulk
For large layouts, units can be created in bulk from a template rather than one at a time. Use the bulk-upload option in the subproject's Units section, fill the downloaded template, and upload it — each row becomes a unit, validated the same way as a single create.
What's next
- Map the unit onto the site map — see Layouts and SVG.
- Move it through the sales journey — see Unit lifecycle.