How can we help? 👋

Audit features in Scaler

An overview of Scaler’s audit-support features, including validation rules, emissions factor transparency, audit trails, and controlled access for auditors.

Purpose

This article explains how Scaler supports assurance, verification, and audit processes across the full data lifecycle — from initial data capture, through calculation, to submission and change tracking. It's both a reference for how Scaler works and a guide your auditor can follow to navigate the platform.


Auditor quickstart

If you're an auditor arriving in Scaler for the first time, this is the shortest path to verifying a client's reported numbers:

  1. Get access — ask the client to invite you as a user in Scaler. They can assign the Auditor role to your profile so you're clearly identified in the user list. Access is granted at no additional cost.
  1. Start at Saved Reports — open the final submission under Data Collection Portal → Portfolio → Saved Reports. Each saved report is a timestamped, frozen copy of what was submitted, including the raw data and emission factors used.
  1. Open the audit trail — generated reports include a built-in audit trail with per-column calculation explanations, unit conversion factors, emission factors, and a full asset-level data export.
  1. Cross-check raw data — the Data Collection Portal gives full access to meter-level and asset-level data. Use the Meter List or the Scaler Spreadsheet export for line-by-line reconciliation.
  1. Review change history — the Audit Log shows every create, update, delete, and rollback event with timestamp, user, and reason.

Each surface is covered in more detail below. For a fuller onboarding guide covering typical auditor workflows, see Getting started in Scaler: Auditor.


Data capture controls

Before data reaches the report, Scaler enforces several controls that support integrity and provenance.

Validated input fields

Scaler enforces data integrity through built-in validation:

  • Field types — numeric, date, dropdown, and boolean fields are constrained to appropriate formats.
  • Consumption logic — every consumption record must include Start date, End date, and one of Consumption, Production, or Meter reading. Date ranges cannot overlap.
  • Mandatory classifications — consumption data must be categorised by Energy type, Subcategory, Area type, and Operational control, ensuring consistent Scope 1, 2, and 3 assignment.

Blocking issues surface directly in the Reports Portal as alerts and prevent final report generation until resolved.

Notion image

Warning dismissals with audit trail

Not every warning indicates a data problem. Some warnings flag legitimate situations (a kept-on-file expired certification, an intentional zero consumption, pre-ownership data retained for like-for-like benchmarking) and should be suppressed rather than corrected. To preserve the audit trail, Scaler tracks every dismissal:

  • A warning can be dismissed at the asset level or across the entire portfolio.
  • A reason can be recorded with each dismissal as the defensible explanation.
  • The dismissing user and timestamp are stored with every dismissal.
  • Dismissed warnings remain visible on a Dismissed tab and can be reversed at any time.
  • Every dismiss and undismiss event is logged in the Audit Log alongside other data changes.

Errors, blocking issues, and missing data cannot be dismissed and must be resolved at source.

Notion image

Data request workflow

Scaler's Data Request feature supports controlled data collection by:

  • Assigning specific fields to internal or external contributors
  • Tracking who submitted each value
  • Requiring review or approval before finalisation

Requested fields follow the same validation rules as standard data entry, and submissions are captured in the Audit Log like any other data entry.

Period Lock

Once reporting data has been reviewed and submitted, an Admin can lock the reporting period via Data Collection Portal → Portfolio → Settings. Locked data cannot be edited by other users, preserving the integrity of reported numbers after submission.

Admins can lift the lock if corrections are needed; any override is recorded in the Audit Log with the reason message attached.

Notion image

Calculation transparency

Once the data is in, Scaler makes every calculation step inspectable.

Emission factor transparency

Scaler provides default emission factors sourced from recognised databases:

  • CRREM
  • Australia NGA
  • US EPA eGRID
  • Canada National Inventory Report

Users can override default factors where permitted and provide a Reference on each override, supporting traceability back to the source used.

Notion image

Framework reports with full metadata and audit trail

In the Generate Report modal, tick Include audit trail to bundle a full audit trail with the Excel output. This is available for most framework reports — the GRESB Spreadsheet and SASB report follow framework-specific structures and don't include this toggle. The audit trail adds the following sheets to the Excel output:

  • Meta-data — date and time of generation, client and portfolio name, emission factor selection method (manual / default), data completion status, and unit system used.
  • Conversion factors — every unit conversion factor applied (e.g. kWh ↔ GJ, m² ↔ ft²), with source where relevant.
  • Location-based factors — the full country-by-country location-based emission factor table used for the submission.
  • Market-based factors — the full market-based emission factor table used.
  • Asset-level data export — one row per asset covering every raw input field behind the submission — floor area, construction year, country, consumption values, and all other asset fields.
  • Report-specific explanations — per-column explanations tying every field in the submission to its variable name, the conversion factor applied, and methodology or limitation notes (e.g. "Not covered in Scaler platform" for fields that must be entered manually in the framework portal).

Together these sheets enable step-by-step verification from raw input to reported result.

Notion image
Notion image
Notion image

Roadmap audit trail download

For portfolios using the Roadmap Tool, Scaler provides a separate Excel download showing how portfolio-level roadmap values are aggregated from asset-level data — including any filters applied, excluded assets with exclusion reasons, and year-by-year data coverage percentages.

For full guidance, see Roadmap audit trail download.


Change tracking

Audit Log

Scaler maintains a timestamped audit log of every data change made in your portfolio. Each entry records who made the change, which entity was affected, the event type (Create / Update / Delete / Rollback), and where the change originated (platform UI or Scaler Spreadsheet upload). The log is available at portfolio and asset level in both the Data Collection Portal and the Analytics Portal.

Notion image

For full guidance, see Using the Audit Log.


The record of submission

Saved Reports

Saved Reports are the record of what was actually submitted. Each saved report is a timestamped, frozen copy that preserves the full output — including the raw data, emission factors, and conversion factors used at the moment of generation. If emission factors or inputs change later in the season, the saved report stays unchanged, providing a defensible reference point for auditors and reviewers.

Saved reports live under Data Collection Portal → Portfolio → Saved Reports. Every generation event (draft or final) is also logged in Report History for full audit traceability.

Notion image

For full guidance, see Using the Reports Portal.

Raw data exports

Users with access to the Data Collection Portal can export raw, meter-level data, including:

  • Meter type
  • Energy, water, and waste Subcategories and Sources
  • Area type
  • Monitoring method
  • Consumption format
  • Consumption, Production, or Meter reading values

This supports line-by-line auditing and reconciliation outside the platform.


Access for auditors

Auditors can be granted access to Scaler at no additional cost. An Admin in your organisation invites the auditor through user management, grants access to the relevant portfolios, and can assign the Auditor role to clearly identify them in the user list.

Once invited, auditors can:

  • Review and export raw data via the Data Collection Portal
  • Access Saved Reports and Report History
  • View the Audit Log to see every change made during the audit period
  • Download generated reports including the full audit trail

All user activity across the platform is recorded in the Audit Log, supporting full traceability during the audit period.

Notion image

Together, these features make data traceable, calculations inspectable, and changes recorded — supporting both internal assurance and external verification.


Additional resources

  • Using the Audit Log — read, filter, and interpret the Audit Log in the Data Collection Portal
Did this answer your question?
😞
😐
🤩