How to collect data (in the new CO2 workflow) : Daato Support Center

Once you have assigned scopes and selected relevant activities, the main procedure of collecting data can begin. Here, the admin or the module manager initiates the process by setting a deadline for data entry completion and notifying all entity managers directly from the module interface.

Once data collection is initiated, all entity managers will be promptly notified via email, informing them that they can begin entering data for their respective entities. They will be able to enter activity and emissions data for Scope 1, 2, and 3 categories assigned to them. If specific activities have been pre-assigned, they can input values for those activities and select appropriate emission factors from the database to match.

Each data point submitted will include a data confidence score, reflecting the quality and reliability of the information provided. Data rated as very accurate is based on primary sources such as invoices, meter readings, or direct measurements. Moderately accurate data typically relies on a combination of actual data and accepted estimation methods, such as using industry averages or partially complete datasets. Low-confidence data is generally based on assumptions, generic emission factors, or unverifiable sources, and carries a higher degree of uncertainty.

This structured and transparent approach helps ensure the integrity of emissions reporting and enhances the credibility of the data, particularly for audits and sustainability certifications.

Users can add comments, upload supporting attachments, or request data. These actions can be performed at two levels:

Scope level – request data for all activities within the scope at once. To do this, select the Request Data button next to the Scope heading.

Activity level – request or comment on a specific data point. In this case, the data provider will only see the selected activity.

Entity managers have the flexibility to choose and edit relevant emission factors directly from our database. This process is explained in detail in the following helpdesk article. Additionally, the module manager or admin can review the collected data at any point to quickly identify and resolve any inconsistencies or inaccuracies, ensuring the highest quality data for final reporting.