Subprojects Overview
A Subproject is a distinct buildable block inside a project. Where the project is the whole development venture, a subproject is one specific thing you build and sell within it — a plotted layout, an apartment tower, a cluster of villas. Subprojects are where the development gets concrete: they hold the units people buy, the area breakdown, the amenities, and (for layouts) the SVG site map.
Relation to the parent project
Every subproject belongs to exactly one parent project and inherits its context (location, ownership chain). A project can have many subprojects. The subproject:
- Has its own partner holdings (which must total 100%).
- Draws its developable land from the stock allocated to the parent project, via stock mappings.
- Is carved into units that are actually sold.
Subproject types
The type you choose shapes what the subproject is and which unit types and custom fields apply to it. The common types are:
| Type | What it is | Typical units |
|---|---|---|
| Layout | A plotted-development site map — land divided into plots. | Plots |
| Apartment | A multi-storey building of flats. | Flats |
| Villa | A development of independent or row houses. | Villas |
A Layout subproject is special: it supports an interactive SVG site map onto which you map each plot's boundary and each amenity's position. See Layouts and SVG.
Saleable vs non-saleable area
Not all the land in a subproject can be sold. Vruksha splits a subproject's area into two kinds:
| Area type | What it covers | Can it be sold? |
|---|---|---|
| Saleable | The portion that becomes sellable units (plots, flats, villas). | Yes — allocated to units. |
| Non-saleable | Common areas, amenities, roads, setbacks, utility space. | No — it supports the development but isn't sold. |
Keeping these separate matters: units can only draw their area from the saleable pool, so the area accounting stays honest. You record the area breakdown when you create the subproject.
What a subproject holds
- Type, name, and location.
- Partner holdings (must total 100%, with a managing partner).
- Area details — saleable and non-saleable.
- Amenities — internal, external, common-area, or utility features.
- Stock mappings — the project stock that supplies this subproject's land.
- SVG layouts (for Layout subprojects) — site maps with unit polygons and amenity markers.
- Units — the sellable items.
- User-role mappings — which users have which subproject-scoped roles here.
What you can do with a subproject
| Action | Page |
|---|---|
| Create a buildable block | Create a subproject |
| Upload a site map and map plots/amenities | Layouts and SVG |
| Edit, manage holdings, assign roles | Manage a subproject |
| Add the sellable items | Create a unit |