Rebranding the entire platform to EQS branding
- Updated Daato’s colors and fonts to match EQS branding, as Daato is now part of EQS Group
- Updated email templates to use EQS colors and fonts for a consistent experience.
Gap Analysis – Correct Activation/Deactivation of Standards & Disclosure Requirement
- Ensured that Disclosure Requirements remain activated if any associated data points are still active.
- Disclosure Requirements are now deactivated only when all related data points are deactivated.
- Applied the same logic to Standards, preventing unintended deactivation.
More Focused Supplier Import Error Log
What's Improved?
- Now, only failed suppliers will appear in the error log when an issue occurs during supplier import.
What’s Changed?
- Previously, the error log included all suppliers, making it difficult to pinpoint which supplier and specific cell caused the issue. With this update, the log will only display suppliers that failed to import, allowing users to quickly identify and resolve errors.
Scope 2 emissions update in CO2 to avoid double counting of emissions
Background
Previously, the calculation of Scope 2 emissions resulted in double counting when reporting on both market-based and location-based emissions. This issue stemmed from users needing to input both emissions sources, causing duplication in total emissions calculations.
A common case is electricity consumption:
- Location-based emissions are derived from the grid.
- Market-based emissions occur when a company contracts a greener energy supplier.
- Both values were included in emissions totals, even though only one should be counted.
Example:
Customer X receives electricity from the grid but has a contract with Supplier Y for greener energy.
- Market-based emissions: 1,000 kg CO₂
- Location-based emissions: 2,000 kg CO₂
- → Previously, both values were included in total emissions calculations, leading to over-reporting.
With this new feature, users can now choose whether an activity’s emissions should be included in the total emissions calculation. The selection applies to custom activities, smart activities, and imported activities.
Feature Updates & Expected Behavior
1. New Scope 2 Emissions Selection Toggle
- Applicable to activities categorized under Scope 2.1, 2.2, 2.3, or 2.4.
- Users must select a category: Market-based or Location-based.
- A toggle appears in the activity creation modal (for Scope 2 activities only).
- If toggle is ON (default): Emissions are included in the total calculation.
- If toggle is OFF: Emissions are excluded from the total calculation.
- Tooltip on hover: “Select this activity if you want to avoid double counting.”
- Toggle is displayed in:
- Activity creation modal
- Activity overview table
2. Scope 2 Imported Activities Behavior
- Imported activities default to Location-based emissions with the toggle ON.
- If user turns the toggle OFF, a confirmation modal appears.
- Confirmation copy is provided in both English & German.
3. Updates to Market-Based / Location-Based Selection Rules
- Selection of Market-based or Location-based is now mandatory.
- Default selection: Location-based.
- Field cannot be left empty.
Where This Change Applies
The toggle selection affects total emissions displayed in the following sections:
- Dashboard (Entity Level) → Shows emissions included in total calculation.
- Analytics Tab → Reflects emissions included in total calculations.
- Launchpad → Updated emissions calculation based on selection.
- Data Summary Overview:
- Column “Total Emissions” → Displays included emissions only.
- “See Details” View → Lists both included and excluded activities.
Impact & Benefits
✅ Prevents double counting of Scope 2 emissions in reports and dashboards.
✅ Gives users control over Scope 2 emissions calculations via a toggle.
✅ Ensures compliance with reporting requirements by mandating Market/Location-based selection.
✅ Enhances clarity in emissions data across all analytics and reporting views.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article