Skip to main content

April 2026 — Freeze your disclosure, not your inventory

Lock down inventory and emission factor data for assurance with scenarios, define disclosure scope, and keep your live inventory moving at the same time.

Written by Ria Noche
Updated today

Kinesis for Organisations

Pin your disclosure data for assurance, without slowing down inventory work

When you're going through an assurance process, the last thing you want is for the underlying numbers to shift while your auditors are reviewing them. At the same time, you shouldn't have to freeze your whole inventory just to keep disclosures stable.

Scenarios give you that separation. You can now pin a scenario to the current version of your inventory data and to a specific version of your emission factor libraries, creating a stable snapshot that reflects exactly what you disclosed — while your live inventory continues to be updated with new sources and data.

Control which emission factor libraries apply

Within a scenario, you can select which emission factor libraries are applied to your calculations. Once you've landed on the right configuration, you can pin the library to its current version so that EF updates don't flow through to a disclosure that's already under review.

Define what's in scope for disclosure

Not everything you track needs to be in what you disclose. Scenarios let you define the inventory scope by excluding specific business entities, activities, or individual streams. This means you can keep tracking everything in your inventory — nothing gets hidden or deleted — while your disclosure scenario only includes what's actually in scope for that report.

Did this answer your question?