What IWMS can't do: the lease-level work gap

IWMS platforms are underappreciated for what they do well. Storing a structured record of a real estate portfolio across hundreds of properties, maintaining space allocations, running a maintenance work order queue, producing ASC 842 payment schedules, these are hard problems at enterprise scale, and a well-implemented IWMS solves them.

They are also consistently oversold as a complete solution to the problem of managing a large lease portfolio. They are not that. There is a category of work, call it the lease-level layer, that sits outside what an IWMS is designed to handle. That work is document-intensive, unstructured, and recurring. It is also the work where errors cost occupiers the most money.

What IWMS was built for#

The IWMS category, defined by Gartner in 2004, was built around a specific architecture: a single platform with one database, connecting space management, maintenance management, lease administration, capital project tracking, and sustainability data. The integration was the value proposition. Before IWMS, those functions lived in separate tools and separate spreadsheets.

That integration architecture requires structured data. Lease payments go in as a schedule. Space allocations go in as square footage figures. Maintenance requests go in as structured tickets. The system operates on what you put into it, in the form it expects.

That constraint is not a design flaw. Databases require structure; that is what makes them searchable, reportable, and reliable as systems of record. The constraint does mean, however, that anything not yet structured, a new lease document, an incoming CAM reconciliation statement, a landlord letter about a renewal option, has to be processed into structured form before the IWMS can do anything useful with it. That processing step is not something the IWMS does. It is something the human team does.

The lease-level work the IWMS does not do#

Reading source documents#

When a new lease is signed, the legal document has to be read, and the material terms, rent schedule, renewal options, CAM definitions, exclusions, notice periods, personal guarantees, have to be extracted and entered into the IWMS. This is lease abstraction. It is time-intensive, accuracy-sensitive work. Errors made in abstraction persist in the system indefinitely unless someone goes back to the source document and corrects them.

IWMS platforms do not read documents. They hold the output of document reading: the abstract. The reading itself is manual, typically done by a lease administrator or an outsourced abstraction service. At scale, the backlog of unabstracted amendments and modifications is where portfolio risk accumulates invisibly.

Validating abstracts against source documents#

A lease gets amended. The amendment changes a CAM exclusion, or extends the renewal notice period, or modifies the rent escalation structure. The abstract in the IWMS should be updated to reflect the change. In practice, it often is not, because the abstraction process requires time, and the team has the next twelve things to get to.

The IWMS cannot detect that its own data is stale. It does not know the source document changed. It will report the incorrect notice period, the incorrect exclusion, and the incorrect escalation schedule with the same confidence it would report correct data. Closing that gap is exactly what lease administration is built to do.

Processing incoming CAM statements#

CAM reconciliation statements arrive annually from every landlord across the portfolio. Each one is a separate document that needs to be compared against the lease terms for that property: the CAM pool definition, the excluded categories, the pro-rata share structure, the gross-up provisions, and the controllable expense caps.

The IWMS holds the abstract of those terms. It does not hold the statement, and it cannot perform the comparison. That comparison requires reading the statement, finding the relevant lease clauses, and identifying where the two diverge. It is document work, done manually, across every property in the portfolio during the first quarter each year. The recurring errors to look for are in our CAM reconciliation errors checklist.

For a team of four managing two hundred fifty locations, completing a thorough review on every statement in a ninety-day window requires roughly five hundred to one thousand hours of work. That exceeds the available capacity, which means some statements are paid without review and errors compound forward. If the underlying process is unfamiliar, what CAM reconciliation is covers it in detail.

Drafting landlord correspondence#

When a lease administrator needs to dispute a CAM charge, request a renewal extension, or respond to a landlord notice, the IWMS holds the lease data that informs the response. It does not draft the response. That is writing work: pulling the relevant clause, framing the factual dispute, drafting a letter that is accurate and commercially appropriate.

At one or two locations, writing these letters is a manageable task for an experienced lease administrator. Across dozens of active disputes in a large portfolio, it is volume work that compounds with the review work and the abstraction backlog.

Critical date validation#

IWMS platforms have date-tracking modules. They are useful. They are also dependent on accurate data entry. A renewal option with a one hundred eighty day advance notice requirement is a critical date. If that date was entered incorrectly at abstraction, wrong by a month, or populated from an outdated draft rather than the executed lease, the system will generate an alert one hundred eighty days before the wrong date. The option window closes without action, and the lease renews at market rather than at negotiated terms.

The IWMS cannot verify its own dates against the source document. It can only report what it holds. For portfolios where the source documents have not been re-reviewed since the original abstraction, the dates the system holds should be treated as unverified.

The cost of the gap#

The lease-level work gap has a direct financial consequence. Errors in lease abstracts lead to missed options and incorrect payment calculations. CAM statements paid without review fund persistent billing errors that compound over the remaining lease term. Critical dates missed mean renewal leverage lost.

The cost is largely invisible in the IWMS itself. The system does not record what it did not catch. It records what was entered. A portfolio that looks healthy in the IWMS dashboard, current abstracts, all critical dates populated, reconciliations processed, may be running a material undetected overcharge across a meaningful share of its locations.

The gap also compounds with portfolio size. For twenty leases, a small team can manage the document-level work manually. For two hundred leases with five amendments each, the unabstracted document backlog alone is a significant liability.

What closes the gap#

The gap is not closed by hiring more lease administrators, though that helps at the margins. It is closed by a tool that can do the document processing work, reading, extracting, comparing, drafting, at the volume a large portfolio generates.

That tool is not an IWMS. It is an agent: software designed to operate on unstructured documents and surface the structured data or exceptions that require human attention. The agent reads the new lease and validates or updates the abstract. It processes the CAM statement and identifies discrepancies against the lease terms. It monitors critical dates and verifies them against the source document, not just the entered record. It drafts the dispute letter when one is needed. The broader division of labor is covered in AI agents vs IWMS.

The IWMS remains the system of record. The agent is the processing layer that keeps the system of record accurate and current, and handles the incoming document volume the team cannot process alone.