Ask most commercial and retail property teams what runs their operations and the answer is almost always a platform like Yardi or MRI. That answer is correct, and it is also incomplete. Those platforms are a system of record — the single source of truth for leases, rent rolls, unit status, and financials. What they are not, by design, is a system of action — something that actually chases the tenant, collects the document, or resolves the exception. Confusing the two is where a lot of commercial real estate operations quietly go wrong.
That distinction is not a knock on Yardi, MRI, or any other property management system. They do what a system of record is supposed to do, and they do it well. The problem shows up when property teams expect the record to also be the doer — when the assumption is that because a lease expiration date lives in the PMS, someone or something is automatically acting on it. It usually is not. That gap between what is recorded and what is actually executed is the subject of this article.
What a system of record does well
A property management system earns its place at the center of the operation because it is authoritative. It holds the lease terms, the rent schedule, the unit and tenant roster, the accounting ledger, and the historical record of what happened and when. When a broker asks what the current rent roll looks like, or an auditor asks for the lease abstract on a given suite, the PMS is where that answer comes from — and it should be. Centralizing that data is what makes a portfolio auditable and financially sound in the first place.
Systems of record are also built for structure and permanence. They enforce a schema, they retain history, and they give every stakeholder — ownership, asset management, accounting, leasing — a shared source of truth to work from. None of that is in question. The issue is what happens next: a system of record can tell you that a certificate of insurance expired last Tuesday. It cannot, on its own, pick up the phone, send the follow-up, or make sure a replacement certificate is in hand before an incident turns that gap into a liability.
What it leaves undone
Most property management systems were architected to store and report, not to initiate and follow through. That is not a flaw so much as a scope boundary — but it is a boundary that a lot of operators run past without noticing. The PMS will flag that a lease renewal option lapses in 60 days. It will not draft the renewal notice, track whether the tenant responded, or escalate if they went silent. It will show a delinquent balance. It will not run the collections conversation, negotiate a payment plan, or know when a friendly reminder should become something firmer.
In practice, this is the work that ends up bolted onto whatever staff member has the most slack in their week — a property manager sending compliance-collection emails between showings, an admin manually re-keying a tenant request from an inbox into the PMS because the two systems don't talk to each other, someone reconstructing "who said what" from memory because the record has the outcome but not the conversation that got there. The system of record is accurate. The operational follow-through around it is improvised.
The system-of-action gap
The system-of-action gap is the space between "the data says this needs to happen" and "this actually happened." It is where tenant communication stalls, where compliance documents go uncollected past their deadline, and where lease events get noticed too late to act on cleanly. It exists in every portfolio that treats its PMS as the entire operation rather than the record layer underneath it — and it grows in direct proportion to portfolio size, because the volume of things that need doing scales faster than any one person's capacity to remember and execute them manually.
Closing that gap is exactly the kind of managed operation we built Premise to run. We sit on top of the system of record and act on what it surfaces: reaching out to tenants before an SLA slips, chasing and verifying compliance documents against the lease terms they're supposed to satisfy, and flagging lease events with enough lead time to act rather than react. The record stays authoritative — we do not replace it — we close the distance between what it says and what actually gets done. You can see the specifics of what we handle across communication, compliance, and lease operations.
Record and action, working together
The right way to think about this is not record versus action, it is record and action, each doing the job it is built for. The system of record stays the ledger of truth: what the lease says, what the balance is, what the history shows. The system of action is what turns that ledger into follow-through — the outreach that happens, the document that gets collected and verified, the exception that gets escalated to a person instead of sitting unresolved. Property teams that only have the first are flying with excellent instruments and no autopilot; every course correction depends on someone noticing and acting manually.
This is also why AI-plus-human execution matters more than automation alone: volume needs an engine, but judgment calls — a tenant relationship that needs a real conversation, an exception that does not fit the standard playbook — still need a person who owns the outcome. We wrote about how that division of labor actually works in practice in AI plus human operators: how commercial property operations actually get run, which is worth reading alongside this piece if you are evaluating where the action layer should live.
Your PMS was never going to do the work — it was never built to. Owning the decisions instead of the paperwork starts with putting a real system of action underneath the system of record you already trust.