Scaler data coverage methodology

Scaler data coverage measures actual data completeness at the meter level, revealing gaps that aggregated methodologies like GRESB data coverage cannot detect.

Use this metric for: data quality assurance, identifying missing or incomplete meters, and prioritising data collection.

Applies to: Energy, water, and waste.

→ Learn about GRESB data coverage methodology

Scaler data coverage evaluates two things for each meter: how much of the asset's floor area it represents (area coverage), and how much of the reporting period it has data for (time coverage). These are combined into a single weighted figure at asset level.

An asset can show 100% GRESB data coverage while still having significant meter-level gaps — hidden by Scaler's widest-range time coverage approach and GRESB's asset-level aggregation. Scaler data coverage exists specifically to surface those gaps. It answers the question: "How complete is our underlying meter data actually?"

Use Scaler data coverage for: QA before GRESB submission, identifying which meters need data, tracking data collection progress.

Use GRESB data coverage for: GRESB submissions, portfolio analytics, external benchmarking.

Scaler data coverage appears in the Data Collection Portal only:

It is labelled "Scaler" or "Critical" to distinguish it from GRESB data coverage.

Scaler data coverage uses a meter-weighted approach. The steps are:

SCALER_DATA_COVERAGE = Σ(METER_WEIGHT × METER_TIME_COVERAGE) × CORRECTIVE_FACTORS

Meter weight = covered area of meter ÷ total covered area of all active meters

The corrective factors and meter weighting are applied independently, so each type of gap is counted exactly once. A meter with 50% time coverage within a 6-month metering window contributes 50% of that 6-month window — not 25% of the full year.

Key inputs from meter configuration: Area type, Covered area, Meter version start date, Meter version end date, Include in calculations, Subcategory.

Note: asset Status (New Construction, Major Renovation) does not modify Scaler time coverage logic.

Time coverage per meter is the proportion of the reporting period for which that meter has consumption data:

TIME_COVERAGE = DAYS_WITH_CONSUMPTION ÷ TOTAL_DAYS_IN_REPORTING_PERIOD

Meter version start date and Meter version end date define the window during which coverage is expected. A meter is only evaluated against the days it is active — not the full reporting year.

Meters that are excluded entirely: inactive meters, and meters where Include in calculations = no/false. These contribute nothing to coverage.

Applies when the asset is active but no meters exist for part of the reporting year — for example, when meters are created mid-year. It represents the fraction of the year that meters were actually present.

TIME_CORRECTIVE_FACTOR = MONTHS_WITH_METERS ÷ TOTAL_MONTHS_IN_REPORTING_PERIOD

Example: meters created on 1 July mean only 6 of 12 months have any meters at all. Time corrective factor = 6 ÷ 12 = 0.50. This is applied after the meter-weighted calculation to account for the unmeasured period before metering started, which would otherwise be invisible.

Applies when meters collectively don't cover the full floor area for the relevant area type. It represents the fraction of the floor area that has been attempted to be metered at all.

AREA_CORRECTIVE_FACTOR = TOTAL_COVERED_AREA ÷ FLOOR_AREA_FOR_AREA_TYPE

Example: asset GFA = 1,000 m², meters cover 600 m² in total. Area corrective factor = 600 ÷ 1,000 = 0.60. This applies even if all 600 m² of existing meters have perfect time coverage — the remaining 400 m² has no meters and is unaccounted for.

Critical insight: even if all existing meters have 100% time coverage, Scaler data coverage will remain below 100% until meters collectively cover the full floor area.

Scaler evaluates coverage relative to the total floor area defined in Reporting Data → Floor Areas, per area type:

You cannot derive Scaler data coverage by multiplying Scaler time coverage × Scaler area coverage. The weighting happens at meter level before aggregation — these are three separate diagnostic metrics serving different purposes:

Covered area values are summed across subcategories and taken at face value. Scaler has no way to detect physical overlap between meters — if two meters cover the same floor space, their areas will be summed as if they are distinct. The total is capped at the floor area for that area type to prevent the sum from exceeding the building maximum, but within that cap Scaler cannot detect misconfiguration.

Two scenarios illustrate how this works:

On-site renewable electricity is included, unlike GRESB data coverage which excludes it. Scaler data coverage is for internal QA and should reflect your full metering infrastructure.

Asset construction status does not modify time correction logic. No special treatment is applied for Major Renovation or New Construction.

Coverage reflects completeness, not accuracy. Scaler data coverage measures whether data exists, not whether it is correct.

All relevant area types have meters covering 100% of floor area, and all meters have consumption data for every day of the reporting period. No gaps exist in the underlying meter data.

Typically indicates one or more of: missing meters for certain area types or energy categories, meters with partial time coverage, or large meters with incomplete data (which have disproportionate impact due to weighting).

To improve coverage: navigate to the Meter List and sort by Time coverage to identify gaps. Focus on meters with large Covered area values first — these have the highest impact on the overall figure.