Mapping the real estate data stack from parcels to portfolios

For 100 Market Street, the parcel layer tells us: it sits on a 0.8 acre lot, is zoned for high-density commercial use, and last changed ownership three years ago. That is our anchor. Every other data source will link back to this parcel.

Why the parcel matters as a key

In database terms, the APN is your primary key: the stable identifier that lets you join messy sources together. Addresses are unreliable (100 Market St, 100 Market Street, Suite 400) but a parcel number is precise. Good real estate data teams normalize everything back to the APN.

Layer 2: Market comps (commercial data providers)

Public records tell you what the government thinks. Comps (comparable properties) tell you what the market thinks.

This is where paid providers dominate. CoStar is the largest commercial real estate data provider in the US, offering lease comps, sale comps, and tenant information. Competitors include Reonomy, CompStak, and Moody's CRE (formerly Real Capital Analytics). These are subscription products, often expensive, and their coverage varies by market.

Comps give us:

• Asking rents per square foot for similar office space nearby.
• Recent sale prices of comparable buildings.
• Vacancy rates in the submarket.
• Tenant rosters in competing towers.

For 100 Market Street, comps might show that similar Class A office space in the submarket asks a certain rent per square foot, and that the building last traded at a specific cap rate. Cap rate (capitalization rate) is annual net operating income divided by property value, the standard yield metric in commercial real estate.

A caution: comps are estimates assembled from broker reports, public filings, and proprietary research. Two providers can disagree on the same building's rent. Treat comps as a range, not a fact.

Layer 3: The rent roll (owner's internal data)

Now we go inside the building. The rent roll is the owner's master list of every lease: tenant name, suite, square footage, rent, lease start and end dates, and escalation clauses.

This is the most valuable and most private layer. It lives in property management and accounting systems like Yardi, MRI, or RealPage. Unlike public records, you only get it if you own or operate the asset (or are underwriting a purchase).

The rent roll answers the questions that actually drive value:

• In-place rent: what tenants pay today, which may differ sharply from market asking rent.
• WALT (Weighted Average Lease Term): the average remaining lease length, weighted by rent. A short WALT means more near-term risk.
• Rollover schedule: when leases expire, so you can forecast vacancy.

For 100 Market Street, the rent roll might reveal that a major tenant occupying 30 percent of the building has a lease expiring next year, at a rent well below current market. That single fact reframes the whole investment: is that upside (you can re-lease higher) or risk (the tenant might leave)?

Layer 4: Operational data (IoT sensor feeds)

The newest layer is the building itself, instrumented. IoT (Internet of Things) sensors now track occupancy, temperature, energy use, elevator traffic, and air quality in real time.

This matters for three reasons:

• Operating cost: HVAC (heating, ventilation, and air conditioning) is often the largest controllable expense. Sensor data lets operators run systems only when floors are occupied.
• Sustainability reporting: energy data feeds ESG (Environmental, Social, and Governance) disclosures, increasingly required by investors and, in some jurisdictions, by law.
• Tenant experience: occupancy sensors reveal whether tenants actually use the space they lease, which predicts renewal.

For 100 Market Street, sensor data might show that occupancy peaks midweek at a fraction of leased capacity, a pattern common in post-2020 office markets. That insight shapes both energy strategy and re-leasing assumptions.

🎬 [VIDEO: "How Smart Buildings Use IoT and Data" — youtube.com — a clear overview of building sensor systems and what the data enables for operators]

Assembling the property data model

Here is the core challenge: four sources, four formats, four update frequencies. Public records change rarely. Comps update monthly. Rent rolls update as leases sign. Sensors stream continuously.

A coherent property data model joins them on the parcel key and layers time on top. Conceptually:

The value is not in any single layer. It emerges from the joins. Market rent alone is a number. Market rent compared to in-place rent from the rent roll, adjusted for a lease expiry you found in the rollover schedule, weighted against actual occupancy from sensors: that is an investment thesis.

From building to portfolio

Everything above describes one asset. Owners hold portfolios: dozens or hundreds of buildings. The stack scales, but new problems appear.

Standardization becomes critical. If each building's rent roll uses different suite-naming conventions, you cannot roll them up. Portfolio teams enforce a common data dictionary (agreed definitions for every field) so that "occupied square feet" means the same thing across all assets.

Aggregation unlocks portfolio metrics: total NOI (Net Operating Income), blended WALT, geographic concentration, tenant concentration (how much rent comes from a single tenant across all buildings). A retailer that is a small tenant in ten buildings can become a hidden concentration risk.

Benchmarking lets you compare assets against each other and against the market. Which buildings underperform their submarket comps? Which have the highest energy cost per square foot? Data at portfolio scale turns individual quirks into patterns you can act on.

The direction of travel in 2026 is clear: firms are investing in centralized data platforms that pull all four layers into a single warehouse, so an analyst can ask one question and query across every building at once.

Key takeaways

• The parcel number is the anchor. Normalize every data source back to the APN, because addresses are unreliable join keys.
• Four layers, four owners, four update speeds. Public records (yearly), comps (monthly), rent rolls (on signing), and IoT (continuous) each behave differently and must be reconciled.
• Value lives in the joins, not the layers. In-place rent means little until you compare it to market comps, lease expiries, and actual occupancy.
• Comps are estimates, not facts. Providers disagree; treat market data as a range and cross-check when the stakes are high.
• Standardization is the price of scale. A shared data dictionary is what turns a pile of building records into a queryable portfolio.