Property
Applications, leases, renewals, and maintenance on a single tenant record per unit — the property lane, on the roadmap and opening by request.
2026-07-09 · By MCV.TECH Editorial Team · Property
Strip the industry to its frame and a property manager holds three things: the relationship with the tenant, the obligations to the owner, and the money moving between them. In most operations those three live in three systems, and the seams are where the month goes.
The property lane of the shared platform puts the whole tenant lifecycle on one record per unit: applications, the lease, renewals, communications, and every maintenance ticket in between. Rent drafts run automatically with ledgered receipts, so arrears surface as signal rather than as a spreadsheet review. Work orders classify and route to pre-approved vendors by trade and coverage — designed for zero manual coordination per ticket — with status flowing back to the same tenant record. Agent and brokerage commission splits calculate from the same ledger. The rollout posture is documented at tenant record & rollout posture.
Owners and managers usually read different reports about the same building. On one ledger, they read the same record at different distances: the manager works the open tickets and the arrears queue; the owner reads occupancy, balances, and work-order history across the portfolio. There is no reconciliation meeting about whose number is right, because there is only one number.
Honesty about availability matters more than enthusiasm about direction. The property lane is on the roadmap: scope is set, and it opens by request in a staged rollout rather than a general launch. The platform foundations it runs on — sign-on, per-brand isolation, the shared ledger, approval gates — are the same ones the live verticals operate today. What is staged is the property-specific workflow layer, and it will say so on this page until it is not.
We will not quote vacancy reductions or days-to-lease figures, and we will not describe a staged lane as if it were generally available. The claim is directional and structural: the tenant relationship belongs on one record, and the rollout sequence exists to prove that before it is promised broadly.
How multi-unit operators actually adopt a Business OS: one bounded workflow, explicit proof criteria, then expansion on evidence. · Source · CMS snapshot (seed).
A measured Business OS rollout starts with decisions, owners, evidence, and review gates — not a portfolio-wide switch-flip.
Useful agents act inside explicit scope, policy, approvals, and evidence trails while human operators retain the gates.