VTS Asset Intelligence vs. AISB — Why Lease Verification Is Not Building Verification

VTS Got Something Right

VTS launched Asset Intelligence on April 1, 2026. The feature applies expert-in-the-loop verification to lease abstraction across more than 600,000 leases — trained AI extracts terms, human reviewers confirm ambiguous clauses before they enter the lease database. The design is clean: AI handles the volume, experts handle the edge cases, and verified output enters the system of record.

This is the right model for its domain. Lease abstraction has exactly the error profile where expert-in-the-loop verification adds contractual protection: ambiguous renewal options, non-standard CAM definitions, jurisdiction-specific carve-outs that differ between a New York office lease and a Singapore retail agreement. VTS's 600,000-lease dataset gives it a training corpus that a building-by-building AI tool could not replicate.

What VTS built for leases is genuinely valuable. The question is what it does not cover — and why that gap matters for building owners and FM directors who need intelligence across both layers.

Ask the Agent: Query your building's compliance gap across lease, operations, and carbon layers →

What Lease Verification Tells You — and What It Doesn't

Lease intelligence tells you what you are contractually obligated to pay. Building operations intelligence tells you what you are actually consuming. These are different data streams from different systems, and neither is a substitute for the other.

Consider a concrete scenario: a portfolio manager with a Class A office building in NYC. VTS Asset Intelligence correctly extracts the CAM reconciliation terms from the lease — the landlord can pass through HVAC capital improvement costs up to a defined cap, escalating at 5% annually. This is exactly the kind of clause where AI abstraction errors cause real financial exposure, and expert verification eliminates it.

But the building is facing a 2025 LL97 compliance threshold. LL97 — New York's Local Law 97 — calculates carbon intensity penalties based on measured energy consumption, not lease terms. The lease document has nothing to say about whether the HVAC system's actual kWh consumption will push the building above its carbon intensity limit. That determination requires building sensor data, utility interval meter data, and an emissions factor calculation — none of which live in the lease database.

When the LL97 fine arrives, it arrives because the two data streams were never connected. The landlord knew the lease terms precisely. The FM team knew the energy consumption approximately. Nobody had modeled the interaction between the CAM-capped retrofit budget, the HVAC efficiency gap, and the LL97 penalty curve — simultaneously, from a single analytical layer.

The Structural Difference

When You Need Both Layers

The integration question matters most for three categories of building owners and FM professionals:

Portfolios with green lease obligations: When a lease contains a green lease clause requiring the landlord to share energy performance data with tenants, or requiring both parties to work toward a carbon reduction target, the lease verification layer (VTS) and the building operations layer (AISB) need to speak to each other. The lease clause defines the commitment; the building operations data determines whether the commitment is being met.

Assets approaching compliance thresholds: LL97, UK MEES, EU CSRD, and Singapore's BCA Green Mark requirements are all measurement-based compliance frameworks. The compliance question is not "what does the lease say?" — it is "what does the meter say, and how does that translate into a carbon intensity figure under the applicable methodology?" This is exclusively a building operations data question. But whether a compliance penalty can be passed through to tenants via CAM or must be absorbed by the landlord is a lease terms question. You need both to model the financial exposure correctly.

Operators evaluating AI building investments under PACE or green bond structures: PACE lenders require M&V documentation aligned to IPMVP. Green bond allocation frameworks require independent verification of energy savings claims. Neither requirement can be satisfied with lease document intelligence. And the IPMVP M&V report cannot be produced without verified building operations data. The two verification layers serve different parts of the same capital transaction.

The Foundry Principle

AISB operates on a foundry model: we never compete with the operators, brokers, or tools we serve. VTS's lease intelligence capability is a specialist tool for a specific problem. AISB does not replace it. For portfolios that need both lease-level and operations-level intelligence, the two tools are complements rather than competitors — one verifies what you pay, the other verifies what you consume and emit.

What AISB provides that no current lease intelligence platform provides: the cross-layer query. When a building owner asks "what is my total financial exposure from this asset's LL97 penalty trajectory, including the CAM pass-through limit from the lease and the carbon intensity gap from the building sensor data?" — that question can only be answered by a system that holds all three data layers simultaneously. Lease terms. Building performance data. Compliance framework calculations.

This is the intelligence gap that matters in the 2026 procurement cycle. Not which platform has better AI, but which platform can answer the questions that cross the layers.

Query your compliance gap:
Ask the AISB agent about your building's cross-layer exposure: lease terms, LL97 trajectory, and IPMVP savings verification →

Related reading: Why AISB will never compete with you: the Morris Chang commitment for PropTech · No platform connects lease CAM terms, LL97 compliance, and building sensor data