Controllable vs Uncontrollable Expense Coding in Lease Abstracts
CAM caps are one of the most valuable tenant protections in a commercial lease, but they only protect against the expenses that fall on the controllable side of the line. The controllable-versus-uncontrollable distinction determines which costs the cap restrains and which costs can escalate without limit. When an abstract records the cap rate but not the category framework, the cap becomes effectively unverifiable.
This article covers the practical logic of controllable and uncontrollable expense classification, how to design abstract fields that capture category coding rather than just the cap figure, what happens when lease versions shift categories, and how non-standard lease definitions require custom field design rather than a generic template.
The Structural Problem with Cap-Only Abstracts
A typical cap field in a lease abstract contains a single value: "5% per year" or "CPI, not to exceed 4%." That value answers one question: how much can covered expenses increase annually? It does not answer the question that determines whether the cap was violated: which expenses does it cover?
A retail lease might cap controllable expenses at 5% compounded annually but exclude real estate taxes, insurance premiums, utility costs, snow removal, and security from the cap. In a year with a mild winter and stable taxes, the tenant benefits from the cap. In a year with sharp insurance increases and a significant snowfall, the uncapped categories can produce a total CAM increase well above 5% even though the cap was technically honored on controllable items.
The reviewer who sees only "cap = 5%, compounded" in the abstract cannot determine whether the cap was violated without reconstructing the category framework from the lease itself. That reconstruction should have happened at abstraction, not at review.
Standard Classification Patterns
Most commercial leases in the US office and retail sectors follow a reasonably consistent pattern for what is controllable versus uncontrollable, though the specific list varies by lease and market.
Typically Uncontrollable
Real estate taxes and special assessments are almost universally uncontrollable because they are set by government authorities. Insurance premiums are typically uncontrollable because landlords cannot control underwriting decisions or market-driven rate changes, though some leases limit recovery to commercially reasonable coverage amounts. Utilities are often uncontrollable for shared services like common area lighting and HVAC, though the treatment of pooled versus separately metered utilities varies significantly across leases.
Snow removal and winter maintenance appear in some leases as uncontrollable because weather drives costs. Other leases treat snow removal as controllable through vendor management. The categorization should reflect what the lease says, not a default assumption.
Typically Controllable
Janitorial and cleaning services, landscaping and groundskeeping, general maintenance and repairs, property management fees, and security services are the most common controllable categories. These costs can be influenced through vendor selection and contract terms, which is the rationale for capping them.
Management fees present a categorization tension. Some landlords argue that management fees are uncontrollable because they are set by the management agreement, not the landlord's discretionary decisions. Tenants typically treat them as controllable because the landlord selects the management company and sets the fee structure. When the lease is silent on whether management fees are controllable or uncontrollable, the abstract should flag the ambiguity.
Non-Standard Definitions
Non-standard definitions are common in negotiated leases, particularly for large tenants with negotiating leverage or for specialized property types. A lease might define uncontrollable expenses to include only taxes, insurance, and utilities, leaving snow removal, security, and emergency repairs subject to the cap. Another might define controllable expenses as only janitorial and landscaping, removing property management from the capped pool.
When the lease uses a non-standard definition, the abstract field cannot rely on a template list. It must record the specific categories the lease assigns to each side of the controllable-uncontrollable line.
Abstract Field Design for Category Coding
The minimum useful field set for controllable-versus-uncontrollable coding includes:
A cap rate field with the numeric cap value (percentage or CPI linkage).
A compounding rule field with values: compounding, non-compounding, or not specified.
A base year or base amount field for the starting point of cap calculations, because some caps apply against a stated base rather than prior-year actuals.
A controllable categories field that lists which expense types are subject to the cap, either by selecting from a standard taxonomy or by recording lease-specific language.
An uncontrollable categories field that lists which expense types are explicitly excluded from the cap.
An exceptions field for unusual carve-backs or qualifications that do not fit either the controllable or uncontrollable list cleanly.
The failure mode for this field set is collapsing the two category fields into a single "cap carve-outs" field that lists only the uncontrollable exceptions without documenting the affirmative controllable set. That design works when the uncontrollable list is short and the controllable list is implied. It fails when a subsequent amendment modifies the controllable set or when a non-standard definition requires explicit documentation of what is capped.
Handling Category Shifts in Amendments
Amendments that change which expenses are controllable or uncontrollable are more common than lease teams expect. A tenant who renews and negotiates a broader controllable definition may shift administrative fees from uncontrollable to controllable as part of the deal. An amendment following a major capital project might temporarily reclassify certain capital-adjacent costs.
The abstract must reflect the current state of category assignments, not the original lease's version. When an amendment changes a category assignment, the standard correction is to update the category fields directly and record in the amendment notes field the original classification and the date of change. Retaining the original classification with an amendment note that contradicts it creates a data conflict that downstream review teams cannot resolve without returning to the source documents.
For portfolio-wide abstraction work, amendments that affect cap or category logic should be flagged as priority review items during QA, because they have direct financial consequences for every reconciliation period covered by the amended term.
What Breaks Without Category Coding
When a reconciliation arrives and the abstract contains only a cap rate, the reviewer must answer two questions: is the specific line item subject to the cap, and was the cap ceiling calculated correctly? Without category coding in the abstract, both questions require manual lease review. That is the work the abstraction should have already done.
The downstream consequences are concrete. A management fee that the reviewer incorrectly assumes is uncontrollable because the abstract did not code it will not be included in the controllable total when testing the cap. If the management fee was actually controllable and should have been capped, the miss becomes a false-clean result: the reviewer concludes the cap was honored when it was not. This is exactly the kind of silent error that produces repeated overcharges across multiple reconciliation cycles without triggering a dispute.
For lease abstraction firms offering CAM audit support or white-label review services, category coding quality determines whether the downstream review is meaningful. An abstract that codes controllable and uncontrollable categories explicitly converts what would be a manual reconstruction task into a direct comparison against the reconciliation statement. The review is faster, more reliable, and more defensible because it is grounded in structured abstract data rather than re-reading the lease at review time.
Firms applying this guidance can run a free audit through CAMAudit to verify how the detection engine handles these clauses on a real reconciliation statement.