Can a tenant occupy multiple units with different move-in dates?
Yes. A single tenant can be assigned to multiple building locals (units), and each assignment has its own independent dates and occupancy status.
How multi-local assignments work
When you assign a tenant to locals, each assignment is a separate record in the tenant_locals table with its own:
- move_in_date — when the tenant starts occupying this specific unit
- move_out_date — when they leave this specific unit
- occupancy_status — tracked independently (scheduled, active, moved_out)
Example scenario
Company A rents:
- Office 301 (150 m²) — move_in: Jan 1 (status: active)
- Storage B2 (25 m²) — move_in: Mar 1 (status: scheduled until March, then active)
- Office 302 (150 m²) — move_in: Jan 1, move_out: Jun 30 (status: active until July, then moved_out)
Each local transitions independently. In February, Company A is active in Office 301 only. In March, they're active in Office 301 + Storage B2. In July, they've left Office 302 but still occupy the other two.
How this affects cost allocation
The tenant's effective area is the sum of all their active locals. As locals transition in or out, the effective area changes, which affects their allocation factor.
- January–February: 150 m² (Office 301 only)
- March–June: 325 m² (Office 301 + Storage B2 + Office 302)
- July onward: 175 m² (Office 301 + Storage B2)
How this affects the tenant's overall move-out
The tenant-level move_out_date (on the tenant record itself) controls portal access and subscription counting. It should be set to the date the tenant fully vacates all units, not the date they leave one unit.
If Company A leaves Office 302 in July but still occupies Office 301 and Storage B2, do NOT set the tenant-level move_out_date — only set it on the Office 302 local assignment. The tenant-level move_out_date should only be set when they leave entirely.
Where to manage: Tenant Hub → select tenant → their Locals section shows all assignments with individual dates and statuses.