How can we help? 👋

Data coverage methodology

A detailed explanation of how data coverage is calculated in Scaler, including both GRESB-aligned data coverage and Scaler’s meter-level data coverage used for data quality and gap detection.

Purpose

This article explains how data coverage is defined, calculated, and used in Scaler. It covers both GRESB-aligned Data coverage for reporting and analytics, and Scaler Data coverage for meter-level data quality assurance and gap detection.

Because data coverage is used differently depending on context, this article is structured with:

  • A quick guide for high-level understanding, and
  • A full technical guide for detailed methodology reference.

Two data coverage metrics in Scaler

Scaler provides two complementary data coverage metrics, each designed for a different purpose:

  • GRESB-aligned Data coverage
    • Used across analytics, dashboards, exports, and any reporting format aligned with the GRESB methodology or frameworks that do not specify their own data coverage rules.

  • Scaler Data coverage
    • A more granular meter-level metric used exclusively in the Data Collection Portal to support detailed QA, validation, and gap detection. Always clearly labeled as “Scaler” wherever it appears.

Both metrics are calculated using the same underlying meter data, but apply different aggregation rules and assumptions.


Quick guide

This short guide highlights the key differences between GRESB Data Coverage and Scaler Data Coverage and when to use each. Refer to the Full Guide for more detail.
GRESB Data coverage

Analytics & Reporting (where relevant)

What it measures

GRESB Data coverage measures reporting completeness at asset level, using an aggregated approach aligned with the GRESB Real Estate methodology.

How it works (high level)

  • Calculated at asset level
  • Based on:
    • the highest area coverage across energy categories, and
    • the widest time range available across all energy meters
  • Uses one coverage value per asset per year

What it is good for

  • Portfolio and asset analytics
  • GRESB-aligned KPIs and scores
  • External reporting (where relevant) and benchmarking

What it does not show

  • Missing or partial data on individual meters
  • Differences in completeness between meters
  • Gaps hidden by aggregation

 
Scaler Data coverage

For data quality and completeness

What it answers

“How complete is our underlying meter data?”

What it measures

Scaler data coverage measures data completeness at meter level, taking into account:

  • how much of the asset each meter represents, and
  • how much of the reporting period each meter has consumption data for.

How it works (high level)

  • Calculated from individual meters
  • Each meter’s time availability is:
    • weighted by its covered area, and
    • adjusted where the full asset area or reporting period is not covered by meters
  • Larger meters have a proportionally larger impact than smaller meters

What it is good for

  • Identifying missing or partial meter data
  • Data quality assurance and validation
  • Prioritising data collection efforts
  • Understanding why coverage is less than expected

Where it appears

  • Data Collection Portal only
    • (asset list, meters & consumption views)


One important thing to know

An asset can show 100% GRESB Data coverage while still having:

  • missing months on individual meters, or
  • meters that do not cover the full floor area.

This is expected behavior.

Scaler data coverage exists specifically to make these gaps visible.


When each metric is used

Use case
Metric to use
Submitting GRESB
GRESB data coverage
Analytics dashboards
GRESB data coverage
Checking data completeness
Scaler data coverage
QA and validation
Scaler data coverage
Improving meter coverage
Scaler data coverage

Summary

Aspect
GRESB data coverage
Scaler data coverage
Primary purpose
External reporting and benchmarking
Data quality and completeness
Used in
Analytics, reports, GRESB submissions
Data Collection Portal only
Level of analysis
Asset level
Meter level
Area perspective
Highest area coverage across energy categories
Weighted by meter-covered area and evaluated against total floor area per area type
Time perspective
Widest date range per asset
Meter-level time availability, weighted by meter size and adjusted for incomplete periods
Treatment of partial data
Aggregated — gaps may be hidden
Explicit — gaps are visible
On-site renewables
Excluded
Included
Reporting frequency
Annual
Daily (meter inputs)
What a high score means
Reporting requirements are met
Underlying meter data is complete
Typical use case
GRESB submission, portfolio analytics
QA, data validation, prioritisation

In one sentence

  • GRESB data coverage measures high-level, annual, resource-type coverage for reporting.
  • Scaler data coverage measures detailed, meter-level completeness for data quality assurance.

Full guide

The sections below provide the complete technical methodology for both data coverage metrics.

GRESB-aligned data coverage

What GRESB data coverage measures

GRESB Data coverage measures whether an asset meets the minimum data availability requirements for external reporting and benchmarking aligned the GRESB Real Estate methodology.

It is designed to:

  • assess reporting completeness at asset level, and
  • support standardised comparison across portfolios and participants.

GRESB data coverage is not intended to assess meter-level data completeness.


Where GRESB Data coverage is used in Scaler

Analytics Portal

  • Portfolio Overview, Portfolio Analytics, Asset Overview, Asset Analytics
  • Applies to Energy, GHG Emissions, Water, and Waste
  • Drives data coverage graphs and related KPIs
  • Scores → GRESB
    • Visualizations and calculations follow GRESB’s coverage methodology.

Data Collection Portal

  • Within PortfolioAsset List→ edit > Meters & Consumption wherever data coverage is shown and labeled Data coverage (GRESB)

Reports & Exports

  • GRESB Real Estate Asset Spreadsheet
  • Data Exports with calculated metrics prefixed gresb_data_coverage

Methodology

Data coverage is calculated at asset level using an aggregated approach.

(GRESB) data coverage = Area coverage × Time coverage

Expand

Area coverage (GRESB)

Area coverage represents the highest percentage of floor area covered across the three GRESB energy categories:

  • Electricity
  • District heating & cooling (DHC)
  • Fuels

Example:

If electricity meters cover 100% of the asset’s floor area and fuel meters cover 10%, area coverage is 100%.

This reflects GRESB’s requirement to report coverage by energy category, not by individual meter.


Time coverage (GRESB)

Time coverage represents the widest date range available across all energy meters, expressed as a percentage of the reporting period.

GRESB requires:

  • one date range per asset, and
  • a single value applied across all energy categories.
Important GRESB constraint: Time coverage is reported at asset level, even when individual meters have different or partial data periods.

Example

In the GRESB Asset Spreadsheet, Scaler reports the widest available date range across all energy meters.

  • Natural gas: Jan–Jun
  • Electricity: Jul–Dec
    • → Scaler reports Jan–Dec as time coverage.

Important note:

This may make the time coverage appear more complete than expected. If you need to adjust coverage boundaries, contact Account Operations for assistance in updating the meter area coverage to balance this.


Methodological constraints of GRESB data coverage

GRESB data coverage has several intentional constraints:

  • Only one date range may be reported per asset
  • Coverage is reported annually, not at meter level
  • Aggregation is done per energy category, not per meter
  • On-site renewable electricity is excluded from coverage calculations

These constraints support standardised benchmarking but limit visibility into partial or missing meter data.


Relationship to Scaler data coverage

GRESB data coverage and Scaler data coverage serve different purposes and are calculated using different levels of granularity.

  • GRESB data coverage provides a high-level reporting indicator
  • Scaler data coverage provides a meter-level data completeness indicator

As a result:

  • An asset may show 100% GRESB data coverage
  • While still having incomplete or missing data on individual meters

This difference is expected and reflects the distinct objectives of each metric.


Scaler Data coverage (meter level)

What Scaler Data coverage measures

Scaler data coverage measures how complete consumption data is across all meters in an asset, taking into account:

  • how much of the asset each meter represents, and
  • how much of the reporting period each meter has data for.

This metric is designed for data quality assurance, not external reporting. It provides visibility into gaps that aggregated methodologies (such as GRESB) cannot detect.


Where Scaler Data coverage is used in Scaler

In the Data Collection Portal, Scaler Data coverage appears in:

  1. Asset ListData coverage (Scaler) columns
  1. Meters & Consumption tables
  1. Meter ListTime coverage column (per meter)

Methodology

Expand

Key variables used in this calculation

Input fields

  • Area type
  • Covered area
  • Meter version start date
  • Meter version end date
  • Include in calculations
  • Subcategory
  • Status

Calculated metrics

  • Scaler data coverage
  • Time coverage
  • Scaler time coverage
  • Scaler area coverage

Role of total floor area

Scaler evaluates data coverage within each Area type, relative to that area type’s total floor area as defined in Reporting Data.

For each Area type:

  • The total floor area represents the maximum area that can be covered by meters
  • Meter Covered area values are evaluated against this maximum
  • Coverage is capped at the total floor area to prevent overstatement

Total floor area is therefore used to:

  • determine whether meters fully cover the asset for a given area type, and
  • apply area-based corrective factors when coverage is incomplete.

Total floor area values

Total floor area is derived from Reporting Data → Floor Areas, mapped to meter area types:

Reporting Data → Floor Areas
Meter Area Type
Gross floor area (GFA)
Whole Building, Shared Services
GFA - Common area
Common Area
GFA - Tenant area
Tenant Space

High-level calculation logic

Scaler data coverage is calculated using a meter-weighted approach.

At a high level:

  1. The Time coverage of each meter is calculated individually
  1. Each meter’s time coverage is weighted by its proportion of the total covered area
  1. Corrective factors are applied where the full asset area or reporting period is not covered by meters

This approach avoids double penalisation when meters are missing both time and area coverage.


Meter-level time coverage

Definition

Time coverage represents the proportion of the reporting period for which a meter has consumption data.

It is calculated per meter as:

Time coverage= Days with consumption ÷ Total daysin reporting period

Important characteristics

  • Time coverage is calculated per meter
  • Meter start and end dates (Meter version start date, Meter version end date) define the period during which coverage is expected
  • Time coverage is later aggregated to asset level using meter weighting
  • Asset Status (e.g. Major Renovation, New Construction) is not used to adjust time coverage

Meter weighting by covered area

Each meter contributes to Scaler data coverage in proportion to the floor area it represents.

Covered area assumptions

Scaler assumes that:

  • Meters of the same resource (energy, water, waste) do not overlap in the floor area they cover within the same Area type
  • Covered areas are summed across all Subcategories (e.g. Natural gas, Off-site electricity, District heating & cooling)
  • The total is capped at the floor area defined for the relevant Area type

Meters that are:

  • inactive for the period, or
  • excluded via Include in calculations

do not contribute to coverage.


Weighted aggregation of time coverage

Each meter’s time coverage is weighted by its share of the total covered area:

Meter weight= Covered area of meter ÷ Total covered area of all meters

Scaler data coverage is then calculated as the weighted average of meter-level time coverage:

Scaler data coverage = Σ (Meter weight × Meter time coverage)

This ensures that:

  • Larger meters have a proportionally larger impact
  • Missing data on a large meter affects coverage more than missing data on a small meter

Corrective factors

After meter-level aggregation, Scaler applies corrective factors to account for incomplete coverage at asset level.

Time corrective factor

The time corrective factor adjusts for periods in the reporting year where:

  • the asset is active, but
  • no meters exist to cover that period.

This prevents overstating coverage when meters are created mid-year.


Area corrective factor

The area corrective factor adjusts for cases where:

  • meters do not cover the full floor area of the asset for the relevant Area type.

This ensures that coverage reflects actual meter completeness, not just the presence of some meters.


Relationship to Scaler time and area coverage

Because Scaler data coverage is calculated using meter-weighted time availability:

  • It cannot be derived from
    • Scaler time coverage × Scaler area coverage

  • Each metric serves a different diagnostic purpose:
    • Scaler time coverage highlights temporal completeness
    • Scaler area coverage highlights spatial completeness
    • Scaler data coverage reflects their combined effect at meter level

Key assumptions

  • Non-overlap is assumed across different Area types
  • On-site renewable electricity meters are included
  • Asset construction status does not modify time correction logic
  • Coverage reflects data completeness, not data accuracy

Why this methodology is used

This approach:

  • Prevents double penalisation of missing meters
  • Reflects the true impact of missing data on large meters
  • Makes partial data gaps visible
  • Supports targeted data completion efforts

An asset may show 100% GRESB data coverage while still having materially incomplete meter data — Scaler data coverage is designed to reveal those gaps.


Example calculation

This example shows how Scaler data coverage is calculated when meters do not cover the full floor area of an asset.

Expand

Scenario

An asset has a gross floor area (GFA) of 700 m² and three energy meters covering the same Area type (Whole-building).

Meter
Covered area
Meter Time coverage
Meter A
100 m²
100%
Meter B
200 m²
100%
Meter C
300 m²
0%
  • Total covered area by meters = 600 m²
  • Total asset floor area (GFA) = 700 m²
  • All meters are:
    • active for the reporting period
    • included in calculations

This means 100 m² of the asset has no meter coverage.


Step 1: Calculate meter weights

Meter weights are based on each meter’s share of the total covered area:

Meter
Weight
Meter A
100 ÷ 600 = 16.7%
Meter B
200 ÷ 600 = 33.3%
Meter C
300 ÷ 600 = 50.0%

Step 2: Apply meter-level time coverage

Each meter’s Time coverage is multiplied by its weight:

Meter
Calculation
Meter A
16.7% × 100% = 16.7%
Meter B
33.3% × 100% = 33.3%
Meter C
50.0% × 0% = 0.0%

Aggregated meter-level result:

Weightedtime coverage = 50.0%

Step 3: Apply the area corrective factor

Because meters cover 600 m² out of 700 m², Scaler applies an area corrective factor:

Area correctivefactor =600 ÷700 =85.7%

Step 4: Calculate Scaler data coverage

Scalerdatacoverage=50.0% ×85.7% =42.9%

Interpretation

  • Two meters have full data, but they do not cover the full building
  • The largest meter (300 m²) has no data
  • An additional 100 m² of the asset has no meter at all

As a result:

  • Only part of the asset is fully represented by consumption data
  • Scaler data coverage reflects both missing meter data and missing area coverage

This behavior is intentional and helps surface:

  • where meters are missing, and
  • which gaps have the largest impact.

Why total floor area matters

Total floor area (e.g. GFA) is used to:

  • detect whether meters collectively cover the full asset, and
  • prevent overestimating data completeness when only part of the building is metered.

Even if all existing meters have perfect time coverage, Scaler data coverage will remain below 100% until the full floor area is covered by meters.


Comparison to GRESB data coverage

In this same scenario, GRESB data coverage could still appear high if:

  • the widest time range spans the full year, and
  • at least one energy category covers most of the area.

Scaler data coverage intentionally provides a stricter, meter-level view.


How to achieve 100% Scaler Data coverage

Achieving 100% Scaler data coverage means that all relevant meters collectively:

  • cover the full floor area of the asset (per Area type), and
  • have complete consumption data for the entire reporting period.

Because Scaler evaluates data coverage at meter level, both dimensions must be addressed.

Expand

Two dimensions of Scaler data coverage

Scaler data coverage depends on two independent dimensions:

  1. Spatial completeness
    1. Do meters collectively cover the full floor area of the asset?

  1. Temporal completeness
    1. Do meters have consumption data for the full reporting period?

Both must reach 100% for Scaler data coverage to reach 100%.


Spatial completeness: full floor area coverage

To achieve full spatial completeness:

  • Meters must collectively cover 100% of the relevant floor area for each Area type
  • Covered areas are evaluated against the total floor area defined in Reporting Data
  • Covered areas are capped at the total floor area to prevent overstatement

If part of the asset’s floor area is not represented by any meter:

  • Scaler data coverage will remain below 100%, even if all existing meters have full data

Temporal completeness: full reporting-period coverage

To achieve full temporal completeness:

  • Each meter must have consumption data for every day in the reporting period
  • Meters created mid-year reduce coverage unless earlier periods are backfilled
  • Missing periods on large meters have a proportionally larger impact

Time completeness is evaluated at meter level and then aggregated using meter weighting.


Why large meters matter more

Because Scaler data coverage is calculated using a meter-weighted approach:

  • Meters with larger Covered area have a greater impact
  • Missing data on a large meter reduces coverage more than missing data on a small meter

As a result, prioritising data completeness on high-coverage meters has the biggest effect on improving overall coverage.


Common reasons coverage is below 100%

Coverage may remain below 100% when:

  • One or more meters have missing consumption periods
  • Meters do not collectively cover the full floor area
  • Meters are inactive for part of the reporting year
  • Meters are excluded via the Include in calculations setting

This does not necessarily indicate incorrect data — it highlights where completeness can be improved.


How this section is intended to be used

This section explains what conditions must be met to achieve full Scaler data coverage.

For step-by-step guidance on:

  • creating or adjusting meters,
  • addressing missing periods,
  • using ghost meters, or
  • prioritising data completion efforts,

see the dedicated article:

How to achieve 100% Scaler data coverage
 

Did this answer your question?
😞
😐
🤩