Create a Subproject
Creating a subproject adds a buildable block to a project — a layout, a tower, a villa cluster. You define its type and location, split its area into saleable and non-saleable, set its ownership, and attach amenities.
Before you start: the parent project must exist, the subproject type you need must be configured in Masters, and the partners who own this block should already be in the system. The land comes from stock allocated to the parent project.
Opening the form
- Open the parent project, or go to Subprojects in the navigation.
- Click Add Subproject (requires the create subproject permission).
- The multi-section form opens.
Basic details
| Field | Notes |
|---|---|
| Subproject Code | Auto-generated and read-only (default prefix SP-), running in sequence per organization. |
| Subproject Name | Required. 2–255 characters. |
| Parent Project | The project this block belongs to. |
| Subproject Type | Required. Layout, Apartment, Villa, etc. The type determines the available unit types and any type-specific custom fields. |
Type-driven custom fields
Choosing a subproject type loads any custom fields configured for it. Mandatory ones must be filled before you can save. If you change the type, the type-specific custom fields reset (they belonged to the previous type's template).
Location
Record the location hierarchy — Country → State → District → Taluk → Village — each level filtering the next. Subprojects typically share the parent project's broad location but can be more specific.
Partner holdings
The holdings table sets ownership of this subproject. The standard rule applies:
Holdings must sum to exactly 100%, and at least one managing partner is required.
- One row per partner, each with a percentage (two decimals).
- At least one managing partner.
- No duplicate partners.
- Total must be exactly 100.00%, or the save is blocked.
See Validation rules for the precise arithmetic.
Area details
A subproject's land is split into two pools. Add area rows and tag each with its type:
| Area type | Use it for |
|---|---|
| Saleable | The land that becomes units (plots, flats, villas). Units draw their area from here. |
| Non-saleable | Common areas, amenities, roads, setbacks — land that supports the development but isn't sold. |
Record each area's value (and a description, such as "Main block saleable area"). The saleable total is what's available to allocate to units later, so getting this right keeps your unit area accounting accurate.
Amenities
Attach the amenities this subproject offers — a clubhouse, a park, a lift, water supply, and so on. Amenities are defined in Masters with a type (Internal, External, Common Area, Unit Feature, Utility) and can carry their own custom fields. Add each amenity once — duplicates aren't allowed per subproject — and fill any amenity custom fields that apply.
For Layout subprojects, you can later place each amenity as a marker on the site map — see Layouts and SVG.
Stock mappings
A subproject's land comes from the stock allocated to its parent project. Map the relevant project stock into the subproject so the area chain is complete: stock → project allocation → subproject mapping → unit allocation. The available allocations to map from are shown for you to choose.
Saving
When you click Save:
- Validation runs on submit — errors appear inline and the form jumps to the first problem.
- The subproject, its holdings, areas, amenities, and custom fields save atomically.
- The subproject is created under its parent project, ready for units to be added.
What's next
- For a Layout, upload the site map — see Layouts and SVG.
- Add the sellable items — see Create a unit.
- Assign subproject roles to users — see Manage a subproject.