You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the GFANZ august report (https://assets.bbhub.io/company/sites/63/2022/07/GFANZ-Portfolio-Alignment-Measurement-August2022.pdf) Figure 27 (page 61 and footnote 80) shows Scope 3 emissions percentage by 15 categories in high impact sectors. This is a request for that data, so that we can input S3 categorization according to GHG Protocol guidelines. The GHG Protocol guidelines for Scope 3 say: when Scope 3 data is properly categorized, use that, else if Scope 3 data is reported but incomplete, estimate unreported data using sectoral averages, else if Scope 3 data is not reported at all, estimate all Scope 3 data using sectoral averages.
When we have this data (with permissive usage license), we can use it for estimation of unreported Scope 3 data.
@kmarinushkin when we have the data delivered, would you like to implement the estimation logic?
The text was updated successfully, but these errors were encountered:
In the GFANZ august report (https://assets.bbhub.io/company/sites/63/2022/07/GFANZ-Portfolio-Alignment-Measurement-August2022.pdf) Figure 27 (page 61 and footnote 80) shows Scope 3 emissions percentage by 15 categories in high impact sectors. This is a request for that data, so that we can input S3 categorization according to GHG Protocol guidelines. The GHG Protocol guidelines for Scope 3 say: when Scope 3 data is properly categorized, use that, else if Scope 3 data is reported but incomplete, estimate unreported data using sectoral averages, else if Scope 3 data is not reported at all, estimate all Scope 3 data using sectoral averages.
When we have this data (with permissive usage license), we can use it for estimation of unreported Scope 3 data.
@kmarinushkin when we have the data delivered, would you like to implement the estimation logic?
The text was updated successfully, but these errors were encountered: