Communities, Projects, Buildings, Units
A Community is what the public sees. A Project is what the system builds to. A Building and Unit together are what the post office delivers to.
At a glance
- Hierarchy: Community → Project → Building → Unit. A Lot is a
(ProjectID, BuildingID, UnitID)triple. - A Community can hold many Projects (phases, product lines). Costs / plans / trades are anchored at the Project level.
- For single-family homes, BuildingID is
001and UnitID is0001— Lot ≈ Building. For attached/townhomes, one Building has many Units. - A Project’s
ProjectStatusID(aActive,pPending,cClosed,hHistorical,nNever Started,sDept/System) drives whether it shows up in dropdowns.
How they relate
Section titled “How they relate”Community ─┬─ Project A ─┬─ Building 001 ─┬─ Unit 0001 (a single-family lot) │ │ └─ Unit 0002 │ └─ Building 002 ─── Unit 0001 └─ Project B ─── Building 010 ─── Unit 0001- A Community can hold many Projects (phases, product lines, attached vs. detached, etc.).
- A Project holds many Lots. Costs, plans, and trades are attached at the Project level.
- A Lot is keyed by
ProjectID + BuildingID + UnitID. - For single‑family homes, BuildingID is usually
001and UnitID is0001— the Lot is effectively the Building. - For attached/town homes, one Building has multiple Units (one per address).
Active vs. closed
Section titled “Active vs. closed”A Project has a ProjectStatus that drives whether it appears in dropdowns and runs nightly. The two values you’ll actually see day-to-day are a Active and c Closed.
All 6 ProjectStatus codes
| ID | Name | What it means |
|---|---|---|
a | Active | Selling and/or building right now. |
p | Pending | Setup is being completed; not yet selling. |
c | Closed | All lots have closed; archived. |
h | Historical | Old project kept for reporting only. |
n | Never Started | Created but never went live. |
s | Dept/System Use | Internal shell project (e.g. for templates). |
What lives at each level
Section titled “What lives at each level”| Level | What is configured here |
|---|---|
| Community | Marketing info, sales agents, agent commissions, traffic sources |
| Project | Standard Plans available, Cost Book, Price Book, Schedule template (StdPlan), QB Company linkage, financial template |
| Building | Address(es), HOA fees, lot premiums, city/zip |
| Lot (Unit) | Plan/options chosen, schedule, contract, costs, statuses |
Where in the apps
Section titled “Where in the apps”| App | Screen |
|---|---|
| SMART | Administration → Community / Project / Building |
| SMART 2.0 | project-management/ |
| Builder Portal | DefaultProject.aspx (Admin → change default project); Schedule.aspx uses it |
| Trade Portal | communities.aspx, default.aspx |
| Home Owner Portal | implicit — the buyer sees only their Lot |
Common SQL
Section titled “Common SQL”All active projects in a division
SELECT p.ProjectID, p.ProjectName, c.CommunityNameFROM dbo.Project pJOIN dbo.Community c ON c.CommunityID = p.CommunityIDWHERE p.ProjectStatusID = 'a' AND p.DivisionID = 'ATL';