Scaler Spreadsheet Tutorials

What the spreadsheet is

The Scaler Spreadsheet is an Excel-based bulk upload tool. Download data from Scaler, edit it in Excel, upload it back in. Three reasons you'd use it:

How to download

Go to Data Collection Portal → Asset List. Select the assets you want to work with, then click Download in the floating action bar at the bottom of the screen. You'll see three options:

After downloading, the platform immediately opens the Upload window. Close it for now — you'll come back to that once your edits are done.

What's inside

When you open the spreadsheet in Excel, the first three tabs are reference and guidance — not for data entry:

The remaining tabs are data sheets — Asset Details, Floor Areas, Certifications, Energy Meters, Energy Consumption, and many others. Which tabs appear depends on what you selected when downloading.

Critical rules

These apply every time you use the spreadsheet. Getting them wrong causes upload failures, data loss, or duplicate records.

Asset Details controls which assets are processed. Asset Details always exports, regardless of your custom selection. Scaler will only process data for assets that are present in Asset Details in the same upload. Every other sheet — Floor Areas, Certifications, Meters, Consumption — is only processed for assets that appear there.

The spreadsheet overwrites your data. For any asset present in Asset Details, all changes across every other sheet are applied on upload — Scaler doesn't merge, it overwrites. Edited cells are updated. Deleted rows are deleted. Only include what you intend to keep. Only edit what you intend to change.

Never edit system-generated IDs. SCALER ASSET ID, METER ID, METER VERSION ID, CONSUMPTION ID — never edit these for existing records. If you change them, Scaler loses the match and creates a duplicate instead of updating the original. Row 9 marks these columns Don't Change.

Three-field asset identification — exact match required. Every row in every sheet is linked to an asset via SCALER ASSET ID, CLIENT ASSET ID, and ASSET NAME. All three must match exactly — capitalisation, spacing, everything. Always copy-paste these from an existing row. Never type them manually.

Download fresh — edit — upload in one session. Don't download a file and leave it for later. If someone else changes the platform in the meantime, your upload overwrites their work.

Excel only — not Google Sheets. Dropdown validation only works in Microsoft Excel. Google Sheets silently breaks it. Desktop Excel or OneDrive only.

Don't touch the hidden sheets. The LISTS, METADATA-hidden, LISTS-hidden, and EXCLUDE tabs power the dropdown validation across the entire file. Don't edit, rename, or delete them.

The three reference tabs

These tabs aren't for data entry — they're there to be read. This video gives you a quick orientation to each one, but the content is designed to be read directly, not watched on screen.

Metadata & Info — Check cell B6 for the template version number. The version history table shows every update to the spreadsheet and whether older versions are still compatible. A No in the compatibility column means you need to download a fresh copy before uploading.

How to Use This Spreadsheet — Step-by-step workflow for adding, editing, and deleting data, plus a quick reference summary table at the bottom. If you're unsure whether to delete a row or just clear the cells, the answer is in that table. Read this before your first upload.

Descriptions & Guidance — Every field across every sheet documented with descriptions, additional guidance, and framework reporting requirements. The Additional Guidance column is where the non-obvious rules live — field dependencies, validation logic, connections between sheets. Scroll right to see framework columns (GRESB, GRI, SFDR, SECR, INREV SDDS, EU Taxonomy). Filter by framework to see exactly which fields are required for a specific report.

Rows 7, 8, and 9

Every data sheet has three rows near the top that tell you how to fill in each column. Check these before entering data in any column you haven't used before.

Row 7 — Type. What kind of value the field accepts: Text, Integer (whole numbers only, no decimals), Number (decimals allowed), or Dropdown (must exactly match one of the available options).

Row 8 — Unit. The unit your value should be entered in. Key ones: financial fields like GROSS ASSET VALUE are in millions (10 million = enter 10, not 10,000,000); percentages are 0–100 (3% = enter 3); floor areas are m² or ft² depending on the asset unit system; embodied carbon is always kgCO2/m² regardless of unit system. Getting the unit wrong doesn't always cause a failure — sometimes Scaler silently misinterprets the number. Always check Row 8 before entering any numeric value.

Row 9 — Requirement. Whether a field must be filled in:

Key rules for this sheet

The three identity fields — SCALER ASSET ID, CLIENT ASSET ID, ASSET NAME — must match exactly across every sheet in the upload. Always copy-paste them from an existing row; never type them manually. A single character difference will cause Scaler to treat the row as a different asset.

Never edit SCALER ASSET ID for an existing asset. It is system-generated and is how Scaler recognises the record. Editing it will create a duplicate instead of updating the original.

ASSET UNIT SYSTEM is descriptive, not instructional — Scaler does not convert data. If you set an asset to Metric but your floor area values are in square feet, Scaler will store those numbers as square metres. Set this correctly at asset creation and change it via Asset Details only, in a standalone upload.

COUNTRY is required and high-consequence. It drives location-based emission factors, CRREM pathways, framework report groupings, and benchmarks. Use the dropdown — do not type freehand.

MAIN PROPERTY TYPE and MAIN PROPERTY SUBTYPE are both required and affect benchmarking, CRREM pathways, and building performance standard tracking. Consult the property type mapping article in the knowledge base if you're unsure which type to use.

Sold assets still need ACTIVE IN ANALYTICS = True for the period they were held. Setting this to False excludes the asset from all reports — including periods before the sale. Keep it True until you have finished reporting for every period that includes that asset.

ACTIVE IN REPORTING OUTPUTS is the recommended way to customise a report run. Download Asset Details only, toggle this field across your portfolio as needed, upload, generate the report, then reset.

Tags and Entity Names must match exactly across portfolios — same capitalisation, same spacing — to be usable as company-level filters.

Key rules for this sheet

Each row links one asset to one asset group. The same asset can belong to multiple groups (one row per assignment).

ASSET GROUP NAME identifies the group as it appears in the Scaler Platform and in reports. It must match exactly across all rows that belong to the same group — same capitalisation, same spacing.

ASSET GROUP ID is a unique internal identifier for the group within your organisation. Conditionally required when the asset is assigned to a group.

ASSET GROUP GRESB ASSET ID is the unique ID automatically assigned to the asset group in the GRESB Portal. Required when reporting to GRESB as a grouped asset.

SCALER ASSET ID is system-generated — do not edit.

CLIENT ASSET ID and ASSET NAME are required and must match exactly with Asset Details.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when construction data is genuinely updated for a new phase or revision.

All fields except the identity columns and RELEVANT SINCE are optional. This is a specialist sheet — populate only the fields relevant to your reporting requirements.

Material fields: WEIGHT OF RAW BUILDING MATERIALS and TOTAL WEIGHT OF BUILDING MATERIALS are both in kg. The raw-to-total ratio is used to calculate the share of recovered, recycled, or biosourced materials.

Construction-phase environmental data: ENERGY CONSUMPTION DURING CONSTRUCTION PHASE (MWh), EMBODIED CARBON DURING CONSTRUCTION PHASE (kgCO2), and WASTE GENERATION DURING CONSTRUCTION PHASE (kg).

EU Taxonomy compliance fields cover technical screening criteria for Activity 7.2 (Renovation of existing buildings) under Climate Change Mitigation. These are boolean fields including: compliance with major renovation requirements, 30% reduction in Primary Energy Demand, fossil fuel exclusion, waste sorting facilities, heating/ventilation system efficiency, and circular design principles.

Water fixture flow rates (litres/min or litres): hand-wash taps, kitchen taps, showers, WC flush volumes, and urinal flush volumes. These support EU Taxonomy water-related Do No Significant Harm criteria.

Air quality and contamination fields cover emission limits, air quality testing, and environmental contamination assessment — all supporting EU Taxonomy pollution prevention criteria.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when embodied carbon values are genuinely updated.

All carbon values are entered in kgCO2/m². Row 8 confirms this for every stage field. This is a per-area intensity metric — not a total.

The lifecycle stages follow EN 15978:

All stage fields are optional. Populate what you have — you don't need every stage to make the data useful. Most organisations start with the upfront stages (A1–A5) and expand over time.

Maximum 4 decimal places on all values, consistent with other numeric fields in the spreadsheet.

This sheet stores the floor area values for each asset — the foundation that Scaler uses for energy intensity calculations, data coverage, certification scope, and meter area linkage. Every asset needs at least the three required GFA fields before meaningful analytics can run.

Key rules for this sheet

ASSET UNIT SYSTEM is pre-filled on export — do not edit it. All floor area values you enter must be in the unit shown for that asset: m² for Metric, ft² for Imperial. If the column is blank for an asset, that asset's unit system hasn't been set in Asset Details yet — fix that first.

GFA — COMMON AREA plus GFA — TENANT AREA must equal GROSS FLOOR AREA (GFA). This is a hard validation. If the three values don't add up, the upload fails. When you update any one of the three, you must update all three together in the same new row. There is no partial update.

Enter 0, not blank, when there is no common area or no tenant area. All three GFA fields are required. A blank field fails the required field check. Zero is the correct value for "none of this type."

Only add a new row when floor areas genuinely change. This sheet uses the Relevant Since pattern — if nothing has changed since your last entry, no new row is needed. Scaler looks back to the most recent Relevant Since date on or before the reporting period and uses that row. If you correct a value, update the existing row. Only add a new row when the actual area changed at a real point in time.

Maximum 4 decimal places on all area values. More than 4 decimal places will fail on upload. Check any values pasted from other systems — especially converted units — and round before uploading.

The same sum rule applies to GIA and GUA if you populate them. GIA — Common Area plus GIA — Tenant Area must equal Gross Internal Area. Same for GUA. If you enter any of the three in a group, all three must be consistent.

GFA — EXTERIOR AREA (column J) links to the Outdoor / Exterior / Parking area type on meters and certifications. Enter exterior and parking areas here if you want to track their energy use separately from the building envelope. ⚠️ Note: the current spreadsheet version (v2026.02.02) shows GFA - EXTERIOR AREA on both column J and column Q — this appears to be a labelling issue. Use column J. Check the Descriptions & Guidance sheet for definitions, and contact your account team if column Q is unclear.

Leaving COVERED AREA blank on a meter or certification auto-links it to the relevant GFA value from this sheet. Update GFA here and all linked meters and certifications update with it automatically. Only enter a specific Covered Area on a meter when it genuinely covers a sub-area.

Key rules for this sheet

This sheet uses the Relevant Since pattern — but most fields change every year. Unlike Floor Areas, where a single row may be valid for years, Reporting Details fields like GROSS ASSET VALUE, ANNUAL VACANCY RATE, GROSS RENTAL INCOME, and PERCENT OF OWNERSHIP typically need a new row every reporting year. Only populate columns that have a new value in that row — Scaler looks back independently for each field.

Two changes on different dates require two separate rows. If Gross Asset Value changes on 1 January and a contact changes on 1 June, you need one row per date. Each row represents one point in time when something became relevant. You cannot combine two different effective dates into a single row.

STATUS START DATE and STATUS END DATE are auto-populated — do not touch them. Row 9 marks both as DON'T CHANGE / auto-generated. When you add a new row with a new STATUS value, Scaler reads your RELEVANT SINCE date as the status start date and automatically closes the previous status's end date to the day before. Your only job is to set RELEVANT SINCE and STATUS correctly.

GROSS ASSET VALUE and GROSS RENTAL INCOME are entered in millions. EUR 13,000,000 = enter 13. EUR 2,500,000 = enter 2.5. Row 7 type field confirms: number (millions). Entering the full number will make assets appear to be worth thousands of times their actual value in reports.

ANNUAL VACANCY RATE and PERCENT OF OWNERSHIP are entered as 0–100. Row 8 confirms: 0-100, e.g. 3% = 3. So 2% vacancy = 2, 75% ownership = 75. Do not enter as decimals (0.02, 0.75).

Only add a STATUS value in a row when the status is genuinely changing. If Standing Investment continues unchanged, leave STATUS blank in the new row. Scaler finds the most recent prior STATUS automatically.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when installations or configurations genuinely change.

Solar panel fields:

Parking and EV fields:

Battery storage: BATTERY ENERGY STORAGE SYSTEM (boolean) and TOTAL BATTERY CAPACITY (kWh).

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when the offset status genuinely changes.

All offset fields are boolean (yes/no). There are six fields, covering two dimensions:

The six fields are: CARBON OFFSET — PURCHASED BY LANDLORD, OFF-SITE ELECTRICITY, CARBON OFFSET — PURCHASED BY TENANT, OFF-SITE ELECTRICITY, CARBON OFFSET — PURCHASED BY LANDLORD, FUELS, CARBON OFFSET — PURCHASED BY TENANT, FUELS, CARBON OFFSET — PURCHASED BY LANDLORD, DISTRICT HEATING AND COOLING, CARBON OFFSET — PURCHASED BY TENANT, DISTRICT HEATING AND COOLING.

Each field requires a valid certificate proving the carbon emissions have been offset.

Key rules for this sheet

This sheet does not use the Relevant Since pattern. Each row is a standalone certification record. One row per certification per asset. There is no date-based look-back logic — add a new row for each distinct certification.

GROUP → TYPE → LEVEL must be filled in that order — always use the dropdown. These three fields cascade: GROUP determines which TYPE options appear, and TYPE determines which LEVEL options appear. Never type directly into these cells and never paste values from another row or another source. Even if the value looks identical, pasted text may fail validation. Clear the cells and re-select from the dropdown each time.

LEVEL is always required, even for pass/fail certifications. If your certification type has only one level option (e.g. Obtained or Certified), you must still select it. Leaving LEVEL blank will cause the upload to fail.

DATE OBTAINED is required when the certification has been obtained. Row 9: conditionally required when OBTAINMENT STATUS equals Obtained or is blank. A blank OBTAINMENT STATUS is treated as Obtained, so if you don't explicitly set status, you must supply a date.

For in-progress certifications: set OBTAINMENT STATUS to Planning to obtain and leave DATE OBTAINED blank. Do not enter a registration date, application date, or target date in DATE OBTAINED. Entering any date in that field tells Scaler the certification has been issued. ⚠️ Note: some guidance documents suggest entering a registration date here for in-progress certifications — this is incorrect. Follow the rule above.

Leaving COVERED AREA blank auto-links the certification to the full GFA. Only enter a value if the certification covers a sub-area of the building. The unit is m² or ft² per the asset's unit system (shown in the pre-filled ASSET UNIT SYSTEM column — do not edit it).

The EU Taxonomy / SFDR fields (columns O–R) are specialist fields — leave blank if not applicable. These four fields — Primary Energy Demand, PED Meets NZEB Criteria, Percentage Lower Than NZEB, and Top Percentage of National Stock — are only relevant for EU Taxonomy alignment and SFDR reporting. NZEB thresholds are country-specific and must be sourced from national energy regulation authorities.

DATE EVIDENCE SUBMITTED FOR REVIEW — ignore this field. It's a legacy column from a one-off GRESB scoring change and is no longer relevant. Leave it blank.

Key rules for this sheet

This sheet does not use the Relevant Since pattern. Each row is a standalone contract record — one row per contract per asset. There is no date-based look-back logic.

NAME is any internal identifier for the renewable energy contract or certificate.

PROCUREMENT TYPE, MARKET-BASED CLAIM, PROXIMITY, and VINTAGE OF GENERATION are all required dropdown fields. Never type or paste into these cells — always use the Excel dropdown.

PROCUREMENT TYPE specifies how the renewable energy was acquired — for example, Power Purchase Agreement, Energy Attribute Certificate, or utility green tariff.

MARKET-BASED CLAIM indicates whether the procurement qualifies as bundled or unbundled for market-based emissions accounting. This distinction affects how Scaler applies the contract to scope 2 calculations.

PROXIMITY records the geographic distance between the renewable energy source and the point of consumption. Closer proximity generally strengthens the market-based claim.

VINTAGE OF GENERATION is the year or time period when the energy was actually generated.

START DATE and END DATE define the procurement or delivery period for the contract. START DATE is required; END DATE is optional.

PURCHASED AMOUNT is the quantity of renewable energy procured. When populated, UNIT becomes required — select the unit from the dropdown.

This sheet defines the structure of your energy meters — what type of energy each meter tracks, which area it covers, and how consumption data will be recorded against it. Every asset that has energy data in Scaler needs at least one meter set up here before any consumption can be entered.

Key rules for this sheet

Each row is one meter version. A single physical meter can have multiple rows if its configuration has changed over time. Scaler links versions together automatically via the Meter ID.

Before setting up meters in the spreadsheet, set one up in the platform first. The platform interface makes the required fields and their relationships much easier to understand before working in bulk.

METER TYPE, METER VERSION, AUTOMATED, and ASSET UNIT SYSTEM are all auto-generated or pre-filled. Do not populate these. Leave them blank on new rows; they will be assigned by Scaler on upload.

METER ID must be unique per asset. If two meters on the same asset share a Meter ID, the upload will fail. If you copy a row as a template for a new meter, update the Meter ID first.

SUBCATEGORY and SOURCE must always be selected from the dropdown — never typed or pasted. The exact values drive emission factor assignments. A free-typed value that looks correct will still fail on upload.

CONSUMPTION FORMAT must not be changed on an existing meter. Changing from Consumption recording to Meter reading (or vice versa) on a meter with historical consumption data will cause Scaler to misinterpret all existing records. If the format genuinely needs to change, close the meter with a version end date and create a new version.

AREA TYPE drives scope emissions allocation — landlord-controlled meters go into scope 1 (fuels) or scope 2 (electricity, DHC); tenant-controlled meters go into scope 3. Common Areas and Shared Services are always landlord-controlled by definition.

COVERED AREA cannot exceed the linked floor area. If your GFA is 1,000 m² and you enter 1,002 in Covered Area for a whole-building meter, the upload will fail. If Covered Area is left blank, it automatically stays in sync with the relevant floor area field.

PERCENTAGE GREEN is required when SUBCATEGORY is Off-site electricity or any DHC type and SOURCE is Mix of green/grey. If left blank in that case, the upload will fail. For DHC meters with other source types, it is optional — but if blank, consumption is treated as 100% grey.

SUPPLIER must match the Emission Factor Tool exactly. The subcategory and source on the meter must also match what that supplier is configured for in the platform. A mismatch means Scaler falls back to the default emission factor silently.

INCLUDE IN CALCULATIONS defaults to TRUE when blank. Set it explicitly to FALSE for source meters feeding a calculated meter, and for tenant meters you're not yet reporting on.

To create a new meter version: add a METER VERSION END DATE to the existing row, copy the row, clear the METER VERSION field on the new row, set METER VERSION START DATE to the day after the previous version's end date, and update the field that changed. The new version's start date must be exactly one day after the previous version's end date — a gap or overlap will cause an error.

Key rules for this sheet

When meter details change, never update Energy Consumption in the same session. Export only the Energy Meters sheet, make the change, upload it, then export a fresh Energy Consumption sheet. The updated meter details propagate into the export automatically. If you edit both sheets in parallel, consumption rows can end up carrying outdated meter details — which corrupts the import.

METER VERSION is auto-generated — leave it blank on new rows. Scaler assigns the correct version based on which meter version was active during the consumption period. Never populate this field manually, and never copy a Meter Version value from one row into a new row you're creating.

SUBCATEGORY and AREA TYPE are pre-filled on export — do not edit them. These come directly from the meter configuration. If they look wrong, fix them in the Energy Meters sheet and re-export.

CONSUMPTION FORMAT is set on the meter, not here — and it determines which fields are required. There are two formats. Consumption recording: enter a start date, end date, and consumption quantity for a period. Meter reading: enter a reading date and cumulative meter reading value; Scaler calculates consumption from consecutive readings. You cannot mix formats within a single meter.

For on-site renewable meters (solar/wind), use PRODUCTION instead of CONSUMPTION. Leave CONSUMPTION blank and enter the gross energy produced in PRODUCTION. Enter energy exported to the grid in REDELIVERY TO GRID (use 0 if none). Scaler calculates net on-site consumption as Production minus Redelivery.

ESTIMATE USING SOLAR PANEL DATA can be toggled per row. Setting it to True for a period tells Scaler to estimate solar production using the panel count and average watt-peak from Sustainable Characteristics — useful for periods before metering was installed. Setting it to False or leaving it blank uses actual data. You can mix both approaches across different periods on the same meter.

UNIT OF CONSUMPTION must be consistent across all rows for the same meter. If historical rows use kWh and you add a new row in MWh, Scaler cannot compare them and intensity calculations will be wrong. Check existing rows before adding new ones. If the unit genuinely changed (e.g. supplier changed reporting), that warrants a new meter version.

CURRENCY is required whenever COST is populated. Both are optional, but if you enter a cost figure you must select the currency from the dropdown — do not type it.

This sheet works the same way as Energy Meters. If you've already set up energy meters, most of the logic carries over directly — same versioning model, same area type rules, same covered area constraints. The differences are water-specific fields.

Key rules for this sheet

Each row is one meter version. A single physical meter can have multiple rows if its configuration has changed over time. Scaler links versions together automatically via the Meter ID.

METER TYPE, METER VERSION, AUTOMATED, and ASSET UNIT SYSTEM are all auto-generated or pre-filled. Do not populate these. Leave them blank on new rows; they will be assigned by Scaler on upload.

METER ID must be unique per asset. Prefix numeric-only IDs with an apostrophe so Excel saves them correctly as text.

SUBCATEGORY and SOURCE must always be selected from the dropdown — never typed or pasted. SUBCATEGORY indicates whether the water is Potable or Reclaimed. Don't edit either field when METER TYPE is a calculated meter.

CONSUMPTION FORMAT must not be changed on an existing meter. Changing between Consumption recording and Meter reading on a meter with historical data will cause Scaler to misinterpret all existing records. If the format genuinely needs to change, close the meter with a version end date and create a new version.

AREA TYPE drives which floor area field the meter links to — and affects scope emissions allocation. Whole building and Shared services map to GFA; Common area maps to GFA — Common Area; Tenant space maps to GFA — Tenant Area.

COVERED AREA cannot exceed the linked floor area. If left blank, it automatically stays in sync with the relevant floor area field from the Floor Areas sheet.

Water meters have an additional PERCENTAGE INDOOR field. When AREA TYPE is set to Mixed indoor/outdoor, you must enter a percentage (0–100) indicating how much of the consumption belongs to the indoor area. You must also set INDOOR AREA TYPE and OUTDOOR AREA TYPE to specify operational control for each portion.

INCLUDE IN CALCULATIONS defaults to TRUE when blank. Set it explicitly to FALSE for source meters feeding a calculated meter, or for tenant meters you're not yet reporting on.

To create a new meter version: add a METER VERSION END DATE to the existing row, copy the row, clear the METER VERSION field on the new row, set METER VERSION START DATE to the day after the previous version's end date, and update the field that changed.

This sheet follows the same structure as Energy Consumption. The same date rules, format rules, and ID rules apply.

Key rules for this sheet

When meter details change, never update Water Consumption in the same session. Export only the Water Meters sheet, make the change, upload it, then export a fresh Water Consumption sheet. The updated meter details propagate into the export automatically. If you edit both sheets in parallel, consumption rows can end up carrying outdated meter details — which corrupts the import.

METER VERSION is auto-generated — leave it blank on new rows. Scaler assigns the correct version based on which meter version was active during the consumption period.

SUBCATEGORY and AREA TYPE are pre-filled on export — do not edit them. These come directly from the meter configuration. If they look wrong, fix them in the Water Meters sheet and re-export.

CONSUMPTION FORMAT is set on the meter, not here — and it determines which fields are required. Consumption recording: enter a start date, end date, and consumption quantity. Meter reading: enter a reading date and cumulative meter reading value; Scaler calculates consumption from consecutive readings. You cannot mix formats within a single meter.

UNIT OF CONSUMPTION must be consistent across all rows for the same meter. If historical rows use m³ and you add a new row in litres, intensity calculations will be wrong. Check existing rows before adding new ones.

TYPE OF CONSUMPTION indicates whether this is a standard consumption value or an adjustment to a previously recorded value (e.g. a utility provider correction).

CURRENCY is required whenever COST is populated. Both are optional, but if you enter a cost figure you must select the currency from the dropdown.

CONSUMPTION ID is auto-generated by Scaler. Do not edit or copy it to another entry. Leave it blank on new rows.

If you've already set up energy or water meters, the versioning model, area type rules, and covered area constraints are identical. The differences are waste-specific: subcategory, source (disposal route), and waste type.

Key rules for this sheet

Each row is one meter version. A single waste meter can have multiple rows if its configuration has changed. Scaler links versions together via the Meter ID.

METER TYPE, METER VERSION, AUTOMATED, and ASSET UNIT SYSTEM are all auto-generated or pre-filled. Do not populate these on new rows.

SUBCATEGORY indicates whether the waste is Hazardous or Non-hazardous. Must be selected from the dropdown — never typed or pasted. Don't edit when METER TYPE is a calculated meter.

SOURCE is the disposal route of the waste (e.g. Landfill, Recycling, Incineration). Must be selected from the dropdown.

WASTE TYPE is an optional but recommended field specifying the material category (e.g. paper, glass, organic). Scaler uses EPA ESPM–aligned conversion factors for each waste type. When no waste type is provided, a default average conversion factor is used, which may skew reported weight figures.

CONSUMPTION FORMAT must not be changed on an existing meter. If the format genuinely needs to change, close the meter with a version end date and create a new version.

AREA TYPE drives which floor area field the meter links to. Same rules as Energy and Water meters.

COVERED AREA cannot exceed the linked floor area. If left blank, it stays in sync with the relevant floor area field automatically.

INCLUDE IN CALCULATIONS defaults to TRUE when blank. Set to FALSE for source meters feeding a calculated meter.

To create a new meter version: same process as Energy — add METER VERSION END DATE to the existing row, copy the row, clear METER VERSION, set the new METER VERSION START DATE to the day after, and update the changed field.

This sheet follows the same structure as Energy and Water Consumption. The same date rules, format rules, and ID rules apply — with additional fields for bin-based estimation.

Key rules for this sheet

When meter details change, never update Waste Consumption in the same session. Export only the Waste Meters sheet, make the change, upload it, then export a fresh Waste Consumption sheet. The updated meter details propagate into the export automatically. If you edit both sheets in parallel, consumption rows can end up carrying outdated meter details — which corrupts the import.

METER VERSION is auto-generated — leave it blank on new rows.

SUBCATEGORY and AREA TYPE are pre-filled on export — do not edit them.

CONSUMPTION FORMAT is set on the meter, not here. Consumption recording: enter start date, end date, and consumption quantity. Meter reading: enter a reading date and cumulative reading; Scaler calculates consumption.

Waste has additional bin estimation fields. When MONITORING METHOD on the meter is set to Estimation (number of bins), three additional fields become required: NUMBER OF WASTE BINS (integer — how many bins allocated), VOLUME OF WASTE BINS (capacity of each bin in the unit of consumption), and FILLING LEVEL OF WASTE BINS (average percentage full, entered as 0–100, e.g. 75 for 75%). Scaler uses these three values to calculate the consumption quantity.

UNIT OF CONSUMPTION must be consistent across all rows for the same meter.

CURRENCY is required whenever COST is populated.

CONSUMPTION ID is auto-generated by Scaler. Do not edit or copy it. Leave blank on new rows.

Key rules for this sheet

This sheet does not use the Relevant Since pattern. Each row is a standalone record — one measure per asset per year.

YEAR OF MEASURE is the year in which the measure was implemented. Enter the four-digit year as an integer.

GROUP OF TENANTS & COMMUNITY and TYPE OF TENANTS & COMMUNITY are both required dropdown fields. They cascade: the group determines which type options are relevant. Always select from the dropdown — never type or paste.

GROUP OF TENANTS & COMMUNITY categorises the measure by target demographic — for example, families, students, elderly, or local businesses.

TYPE OF TENANTS & COMMUNITY specifies the program type within the selected group — for example, tenant engagement programs or ESG training.

DESCRIPTION OF MEASURE is an optional free-text field for additional context on the initiative.

Key rules for this sheet

Each column represents one risk assessment category. The 19 categories are: Biodiversity and Habitat, Building Safety and Materials, Climate Change Adaptation, Contaminated Land, Energy Efficiency, Energy Supply, Flooding, GHG Emissions, Health and Well-being, Indoor Environmental Quality, Natural Hazards, Regulatory, Resilience, Socio-economic, Transportation, Waste Management Risk, Water Efficiency, Water Supply, and Risk Assessments — Other.

Enter the most recent reporting year in which the assessment was conducted. All fields accept a four-digit year value (e.g. 2025). Row 8 confirms: most recent reporting year. For fiscal year reporters, enter the year in which the majority of your FY period falls — for example, FY Jun 2025–May 2026 → enter 2025; FY Jul 2025–Jun 2026 → enter 2026.

All assessment fields are optional. Only fill in the assessments that have actually been conducted for that asset.

These fields support GRESB aggregation at portfolio level for indicator RA1. They are not reported via the GRESB Asset Spreadsheet directly, but Scaler uses them to aggregate portfolio-level data.

Key rules for this sheet

Measures are grouped into three categories across the columns:

Enter the most recent reporting year in which the measure was implemented. All fields accept a four-digit year value. Row 8 confirms: most recent reporting year. Same fiscal year rule as Risk Assessments — enter the year in which the majority of your FY period falls.

All measure fields are optional. Only fill in the measures that have actually been implemented.

These fields relate to GRESB indicators RA2–RA5 and enable portfolio-level aggregation for GRESB reporting.

Key rules for this sheet

Each row is one building unit. There is no versioning or Relevant Since pattern — one row per unit per asset.

CLIENT UNIT ID is required and is how you identify the unit across all four Building Units sheets. It must match exactly across Building Units — Details, Reporting Data, Certifications, and Linking Meters. Always copy-paste; never type manually.

PROPERTY TYPE and PROPERTY SUBTYPE are required dropdown fields. These define the unit's category independently of the asset's main property type — a mixed-use building may have retail and residential units.

OWNED SINCE is required. It records when the unit became part of the portfolio. OWNED UNTIL is optional and records disposal or end of ownership.

LEASED AREA is the floor area leased to a specific tenant, in m² or ft² per the asset's unit system.

TENANT NAME, MOVE-IN DATE, BREAK DATE, and NOTICE PERIOD are all optional lease management fields. NOTICE PERIOD is entered in number of days.

Address fields (UNIT STREET NAME, UNIT STREET NUMBER, UNIT POSTAL CODE, CITY) are optional and only needed when the unit's address differs from the asset's main address.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when floor areas or vacancy status genuinely change. Scaler looks back to the most recent Relevant Since date on or before the reporting period.

CLIENT UNIT ID must match exactly with the corresponding entry in Building Units — Details.

ASSET UNIT SYSTEM is pre-filled on export — do not edit it.

UNIT FLOOR AREA is required — the total constructed internal floor area of the unit to external walls, in m² or ft².

UNIT USABLE AREA is the directly usable portion of the unit, excluding structural elements and shared service areas. Typically around 80% of floor area. This field is optional.

VACANT is a boolean field flagging whether the unit is currently vacant. When set, Scaler auto-generates VACANCY PERIOD — START DATE and VACANCY PERIOD — END DATE — these are system fields marked auto-generated by Scaler — do not edit.

Key rules for this sheet

This sheet follows the same rules as the asset-level Certifications sheet. Each row is a standalone certification record — one row per certification per unit. There is no Relevant Since pattern.

CLIENT UNIT ID must match exactly with the entry in Building Units — Details.

GROUP → TYPE → LEVEL must be filled in that order — always use the dropdown. These three fields cascade. Never type or paste values. Clear and re-select from the dropdown each time.

LEVEL is always required, even for pass/fail certifications.

DATE OBTAINED is required when OBTAINMENT STATUS equals Obtained or is blank (blank is treated as Obtained).

For in-progress certifications: set OBTAINMENT STATUS to Planning to obtain and leave DATE OBTAINED blank.

COVERED AREA — only enter a value if the certification covers a sub-area. If left blank, it links to the unit's floor area.

EU Taxonomy fields (PRIMARY ENERGY DEMAND, PED MEETS NZEB CRITERIA, PERCENTAGE LOWER THAN NZEB, TOP PERCENTAGE OF NATIONAL STOCK) — leave blank if not applicable. These are specialist fields for EU Taxonomy alignment and SFDR reporting.

Key rules for this sheet

This is a simple linking sheet — all fields are required. Each row maps a CLIENT UNIT ID to a METER ID, telling Scaler which meters serve which units.

CLIENT UNIT ID must match exactly with the entry in Building Units — Details.

METER ID must match an existing meter in the Energy Meters, Water Meters, or Waste Meters sheet.

One row per unit–meter link. A single unit can be linked to multiple meters (one row each), and a single meter can be linked to multiple units.

All identity fields (SCALER ASSET ID, CLIENT ASSET ID, ASSET NAME) must match exactly across sheets — same capitalisation, same spacing. Copy-paste from an existing row.

Key rules for this sheet

Each row is one measure per asset. This sheet does not use the Relevant Since pattern — each row is a standalone record describing a specific improvement measure.

SCALER MEASURE ID is auto-generated by Scaler. Leave it blank for new measures — do not populate or copy from another row.

YEAR OF MEASURE is the year the measure has or will have the given status. Required.

STATUS must be selected from the dropdown: Completed, In progress, Planned, or Cancelled. Required.

GROUP OF MEASURE and TYPE OF MEASURE are required dropdowns that categorise the measure. The group determines which types are available.

SOURCE indicates whether the measure is User-created, AI-Assisted, or Third-party. Required and must be selected from the dropdown.

Energy reduction tracking offers two methods via REDUCTION METHOD: Either Total energy savings (enter the absolute value in kWh in ABSOLUTE ENERGY SAVINGS) or EUI reduction (enter the expected kWh/m² reduction in EUI REDUCTION and select the UNIT — EUI REDUCTION). The method is conditionally required when TYPE OF MEASURE is not Sell.

Water and waste savings are optional: WATER SAVINGS in m³, WASTE SAVINGS in kg. WATER USE INTENSITY REDUCTION requires UNIT — WATER USE INTENSITY REDUCTION when populated.

Cost fields are informational. TOTAL COST, COST — LANDLORD, COST — TENANT, COST — CO-OWNER, and SERVICE CHARGE are all optional. TOTAL COST is used in roadmap analytics. When any monetary field is populated, the COMMERCIAL BENEFIT dropdown becomes conditionally required.

PERCENTAGE COMPLETED is entered as 0–100 (e.g. 75 for 75%). Optional.

Key rules for this sheet

Each row is one installation per asset. There is no Relevant Since pattern — each row is a standalone record for a specific piece of equipment.

TYPE OF INSTALLATION is a required dropdown describing the equipment category.

INSTALLATION ID is a user-defined identifier — required and must be unique per asset.

AREA TYPE is required and drives which floor area the installation links to, same as meters.

F-GAS CAPACITY is the weight of the refrigerant in kg — not kgCO2e. This is the charge weight, typically available from the manufacturer or service documentation. Required.

F-GAS TYPE must be selected from the dropdown. Each gas type has its own Global Warming Potential (GWP). Scaler uses this to convert kg to emissions. Required.

LEAK FACTOR is the estimated annual leakage rate as a percentage (0–100, e.g. 10 for 10%). Typical rates: refrigeration 10–15%, air conditioning 5–10%. Required. Scaler uses this with the GWP to calculate annual emissions.

ASSEMBLY LEAKAGE and DECOMMISSION LEAKAGE capture actual refrigerant losses in kg discovered during service events. These are optional fields that support the actual leakage recording workaround — the refrigerant added during a refill equals the leakage since the last service visit.

INSTALLATION DATE is required — the date the equipment was installed or commissioned.

COOLING OUTPUT and HEATING OUTPUT are optional, entered in kW.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when the climate risk assessment is genuinely updated. Scaler looks back to the most recent Relevant Since date.

All climate risk fields are dropdown selections. There are 28 risk categories across four groups — all optional, but the dropdown must be used when populated:

Each field represents a specific Climatic Impact-driver (CID) with varying degrees of detrimental impact or risk to the asset. Select the assessed risk level from the dropdown.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when the adaptation assessment is updated.

All fields are boolean (yes/no) except EXPECTED LIFESPAN OF THE BUILDING (number, in years). They track compliance with EU Taxonomy DNSH criteria for Climate Adaptation, including:

These are specialist EU Taxonomy fields. Leave them all blank if EU Taxonomy Climate Adaptation alignment is not relevant to your reporting.

Key rules for this sheet

Each row covers one reporting period per asset. Defined by REPORTING PERIOD — START DATE and REPORTING PERIOD — END DATE, both required.

TURNOVER, CAPEX, OPEX, and MARKET VALUE are entered in millions in your portfolio currency. EUR 13,000,000 = enter 13. EUR 2,500,000 = enter 2.5. Getting the unit wrong makes assets appear thousands of times their actual value.

PERCENTAGE OF NOI INVESTED IN SUSTAINABLE ACTIVITIES is entered as 0–100 (e.g. 3 for 3%).

Investment return metrics are all optional: DPI (Distributed to Paid-in), UNDERWRITTEN GROSS IRR, UNDERWRITTEN GROSS EQUITY MULTIPLE, CURRENT GROSS IRR, CURRENT GROSS EQUITY MULTIPLE, PROJECTED GROSS IRR, PROJECTED GROSS EQUITY MULTIPLE. IRR fields are percentages (0–100). Equity multiples are numbers. All exclude vehicle-level fees.

Underwritten metrics reflect original projections based on anticipated cashflows. Current metrics use actual cashflows to date plus book value. Projected metrics combine actual to-date data with anticipated future cashflows through liquidation.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when loan terms genuinely change.

LOAN START DATE is the actual date the loan commenced.

ORIGINAL LOAN AMOUNT (PRINCIPAL) is the starting loan amount. Entered as a number — check whether it should be in millions or absolute figures based on your portfolio's convention.

LOAN DENOMINATED CURRENCY must be selected from the dropdown.

Interest rate fields: INTEREST RATE — TYPE is a text field indicating fixed, floating, or capped floating. ANNUAL INTEREST RATE, BASE RATE, SWAP MARGIN, and REFERENCE RATE provide the breakdown. All percentage fields are entered as 0–100.

AMORTIZATION is a dropdown (yes/no). When yes, YEARLY AMORTIZATION RATE is expected (0–100).

Key ratios: LOAN TO COST and LOAN TO VALUE are percentages (0–100). DSCR (Debt Service Coverage Ratio) and ICR (Interest Coverage Ratio) are numbers.

Covenant tracking — the sheet includes extensive fields for LTV, DSCR, and ICR covenants: breach thresholds, cure procedures, cure periods, test dates, and test frequency. There is also an additional covenant section for other performance undertakings (e.g. occupancy, NOI growth). All covenant fields are optional.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when the values genuinely change.

ASSET UNIT SYSTEM is pre-filled on export — do not edit it. All area values must be entered in the unit shown (m² for Metric, ft² for Imperial).

Housing floor area fields: FLOOR AREA — AFFORDABLE HOUSING, FLOOR AREA — SOCIAL HOUSING, FLOOR AREA — ALTERNATIVE HOUSING, FLOOR AREA — FREE-MARKET HOUSING, and FLOOR AREA — PUBLIC FACILITIES. All are optional and entered in m² or ft².

Rental unit counts: RENTAL UNITS — AFFORDABLE HOUSING, RENTAL UNITS — SOCIAL HOUSING, RENTAL UNITS — ALTERNATIVE HOUSING, RENTAL UNITS — FREE-MARKET HOUSING, and RENTAL UNITS — GREEN LEASE SIGNED. All integers, all optional.

Tenant counts: TENANTS — TOTAL and breakdowns by housing type. BEDS — TOTAL is particularly relevant for student housing, senior living, and care facilities.

Community spaces: COMMUNITY SPACE — TOTAL FLOOR AREA, COMMUNITY SPACE — FLOOR AREA TENANTS (tenant-only access), and COMMUNITY SPACE — FLOOR AREA WIDER COMMUNITY (public access).

GREEN SPACE — AREA and GREEN SPACE — DESCRIPTION track green installations by area with a description of purpose and sustainability contribution.

WATER STORAGE — VOLUME is entered in m³. WATER STORAGE — DESCRIPTION captures the purpose.

Key rules for this sheet

Each row is one initiative per asset. This sheet uses the Relevant Since pattern.

GROUP OF INITIATIVES and TYPE OF INITIATIVE are both required dropdown fields. The group determines which types are available. Always select from the dropdown.

GROUP OF INITIATIVES categorises the initiative into broader categories — such as ecology programs, community programs, or public facilities.

TYPE OF INITIATIVE specifies the initiative type within the group.

DESCRIPTION OF INITIATIVE is an optional free-text field for objectives, scope, and expected or achieved outcomes.

Conditional fields depend on the group:

NUMBER OF INDIVIDUALS SERVICED BY INITIATIVE is an optional integer measuring direct impact.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when custom field values genuinely change.

The columns in this sheet are defined by your organisation's custom field configuration in the Scaler Platform. The base template includes only SCALER ASSET ID, CLIENT ASSET ID, ASSET NAME, RELEVANT SINCE, and COMMENTS. Additional columns appear when your portfolio has custom fields configured.

Custom fields are managed in the platform, not in the spreadsheet. To add, rename, or remove a custom field, use the platform settings. The spreadsheet reflects whatever custom fields exist at the time of download.

Key rules for this sheet

This sheet uses the Relevant Since pattern. Only add a new row when the development assessment is updated.

All fields except identity columns and RELEVANT SINCE are optional boolean fields — each records whether a specific design feature or sustainability strategy has been implemented.

Key categories: