How to assign scopes (in the new CO2 workflow)

The redesigned CO₂-Footprinting module guides you through four clear stages, and the first is Assign scopes. This is an optional step.

Scopes are the boundaries that classify where greenhouse-gas emissions originate in relation to your organisation’s activities and they help you understand how directly each source is tied to your operations. 

Inside the EQS Sustainability Cockpit you can allocate every scope and sub-scope to the individual entities in your reporting structure. By default, all scopes are assigned to all entities, which means that when data collection begins, every entity will be able to report on all scopes and their categories.

If you want to exclude certain data, you can unassign an entire scope across all entities. For example, you might decide not to include Scope 3 emissions in a report. In that case, unassigning Scope 3 ensures it will not appear in data collection or reporting results. You can reassign the scope later if needed.

This can be done for every single scope and scope category. You can do so by following these steps:

Open the report you want to work on and click "Assign" scope, for example Scope 1.

All entity toggles are switched on by default to prevent accidental omissions. If you already know that certain entities do not report under this scope, turn their toggles off and click Confirm. You can do this for a single entity of a group of entities at once.  

When you exclude an entity, the system asks for an optional justification. Enter a short note explaining why the entity is not included, for example, “No combustion sources on site.” If you prefer, you can close the popup without entering a justification.

Once a scope is switched off for an entity the corresponding entity managers will no longer be able to add activities under that scope, ensuring the data remains consistent with the boundaries you have defined. 

The next step in the data collection setup is about assigning activites to entities. You can also find an article on this 2nd step on the helpdesk.