Report scope 3 category 7 employee commuting
Important
This content is archived and is not being updated. For the latest documentation, go to the Microsoft Dynamics 365 documentation. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Dec 31, 2022 |
Mar 31, 2023 |
Business value
Many organizations try to track employee commute to their primary offices as a form of emissions in their value chain. Employee commute can cause a significant amount of carbon and other greenhouse gases (GHGs) to be released, as employees need to make their way to offices and factories. Like other indirect sources of emissions, in the Greenhouse Gas Protocol this is accounted for in scope 3. To calculate scope 3 category 7: Employee commuting, organizations need a way to collect data on employee commutes. They need to turn that data into activity data, which might mean using proxy methods such as averages or standard factors for vehicles. To do this, we need to store employee commute data, ingest it, align it to our schema, calculate, and report on the emissions. Providing an out-of-the-box standard for this mechanism of data alignment and calculation enables reporting on this category, giving an organization a complete view of its carbon footprint.
Feature details
This feature provides a data model schema, ingestion of activity data, default calculation model, and reporting for scope 3 category 7: Employee commuting in Microsoft Sustainability Manager. Employee commute data can come from surveys or actual data. We only take and store generalized data to create calculations based on the GHG Protocol method for scope 3 category 7.
See also
Categories 6 and 7: Business travel and employee commuting (docs)