Orientation for a lane in staged rollout
The property lane is on the roadmap: scope is set, and it opens by request in a staged rollout rather than a general launch. This page describes the operating model being rolled out — and is explicit about what is and is not available.
The tenant record
Applications, leases, renewals, communications, and maintenance history live on one tenant record per unit. The whole relationship is readable in one place, inside the brand's boundary, with the same per-brand isolation every platform record carries. The field note the tenant relationship is one record describes the same lifecycle from the operator's chair.
The rent ledger
Monthly drafts run automatically with ledgered receipts. Charges, drafts, and balances share the property record, so arrears surface as signal in the manager's queue rather than as a month-end spreadsheet review. Owners read the same ledger the manager does, at portfolio distance.
Vendor dispatch
Work orders classify and route to pre-approved vendors by trade and coverage — designed for zero manual coordination per ticket. Vendor approval is a gate, not a contact list: coverage and trade are verified before dispatch is permitted, and status flows back to the tenant record as the work progresses.
Commission splits
Agent and brokerage splits calculate from the same ledger on configured scales, with onboarding tax documentation tracked alongside.
Availability boundary
The platform foundations described here — sign-on, isolation, the ledger, gates — are live today. The property-specific workflow layer is staged and opens by request. Live unit, tenant, and ledger state belongs to the authenticated console; this page is orientation, not an availability statement.