Skip to main content

Data change log events

Understand how the Data changelog gives you a version history of your sustainability data, and how to use it to track what changed and why.

Written by Jamie
Updated over a month ago

The Data changelog gives you a version history of your sustainability data. Every time someone in your organisation takes an action that affects your footprint calculations or your Supply Chain Engagement Programme, a new version is recorded. This lets you see exactly what changed, who made the change, and when it happened.


Why the Data changelog matters

Your sustainability data evolves constantly -- files are uploaded, facilities are updated, supplier engagement requests are sent. The Data changelog captures each of these moments as a discrete version, so you always have a clear trail of how your data got to its current state.

This is especially useful when:

- You need to explain to auditors or stakeholders why your footprint numbers changed between two dates

- You spot unexpected changes in your emissions data and want to trace the cause

- You want to confirm that a colleague's data upload or configuration change was captured correctly

- You need to review recent supplier engagement activity across your supply chain


How versions work

Each event in the Data changelog represents a version of your sustainability data. Events are grouped by daily snapshot, so you can see at a glance how many changes happened on a given day and drill into the details of each one.

Every version records:

  • Event code and name -- what happened (e.g. `ORG_009` -- Toggled Corporate Footprint year completion & lock status)

  • Event category -- which area of the platform the event belongs to (e.g. Organization Settings, Suppliers & Supply Chain)

  • Data impact status -- whether the event impacts emissions data, supplier engagement programme data, or both

  • User details -- who performed the action and their role

  • Entity details -- which business units, facilities, suppliers, franchises, data sources, or files were affected

  • Action context -- the specific detail of what changed, including the outcome (e.g. "[xxx]@[yyy].com marked 2022 as complete")


What's in the Data changelog

The Data changelog includes two categories of events:

  • Impacts Footprint Calculations -- events that may trigger recalculation of your emissions footprint data, such as uploading files, updating facilities details, merging two suppliers details, or changing calculation and reporting settings

  • Impacts Supplier Engagement Programme -- events related to your supply chain, including changes to the underlying purchases you connect your supplier data to, and the requests and responses you gather with your supply chain


Filtering and searching

By default we provide a number of filters on our Changelog experiences to help you narrow down your exploration. You can also use the **Search Change Log** bar to find specific events by keyword.


What events can create a new version?

For a complete list of every event that Altruistiq records -- including which ones impact footprint data and which impact supplier engagement programme data -- see the Audit events reference.

Did this answer your question?