> For the complete documentation index, see [llms.txt](https://docs.carboncentral.app/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carboncentral.app/knowledge-base/demos/carbon-reporting/ghg-protocol-corporate-standard.md).
# GHG Protocol Corporate Standard
This use case demonstrates the use of Carbon Central to track and manage the carbon emissions from a corporate entity. In this example, we will look at examples of Scope 1, 2 and 3 emissions from NoviqTech - demonstrating how we track our company emissions using the GHG Protocol - Greenhouse Gas Accounting Standard.
### Digital Twin
Leveraging Carbon Central's library of digital twin templates crafted by our environmental specialists, users can kickstart their baseline GHG Corporate Standard digital twin. When calculating total emissions using the GHG accounting standard, it is key to understand each source of emissions across all scopes. To achieve this, our digital twins come fitted with emissions calculators which help users to enter the important information to calculate emissions.
Leveraging this template provides examples of all device data sources, as well as manual reporting and documentation elements essential for generating evidence tokens according to the Standard and Methodology guidelines.
This demo shows three emissions calculators across each scope, and one area to manage and track any purchased offsets.
### Using the scope emissions calculator
When a user selects 'Upload' on one of these blocks, they are presented with the option to upload evidence and input the necessary data required for token minting. This streamlined process ensures that users can easily provide the documentation and information needed to generate tokens accurately and efficiently.
**Supported emissions sources**
All emissions sources can be accounted for in Carbon Central. We offer native support for common sources, and can easily add support for unique sources on request.
Common examples include:
* mobile combustion for petrol or diesel company vehicles (scope 1),
* purchased energy for head office (scope 2); or
* purchased goods and services such as cloud services (scope 3).
**Example - Scope 1**
Here we can see the details required for an example scope 1 emissions calculation. A user has selected an emissions source and category, and proceeded to enter relevant metrics and emissions factors, along with the total calculated emission.
In this scenario, we see that the emissions for a company car using mobile combustion (gasoline/petrol) is being calculated.
The user has entered the appropriate unit (L), usage (1000 L), and emissions factor (2.312) used in their calculation. Finally they entered the appropriate emissions for the year for a total of 2313 kg CO2e.
This value is now tracked and accounted for in the company's total emissions for the calculated period.
### Offsets
After total emissions are calculated, users can enter appropriate sources of purchased offsets. Offsets can be sourced from an appropriate location and entered into Carbon Central to be factored into the total emissions calculation.
In this example, we can see that Australian Carbon Credit Units were purchased, offsetting 10 t CO2e (10 credits were applied).
### Total company emissions
After entering appropriate sources of scope 1, 2 and 3 emissions for the selected period, along with any purchased offsets, carbon emission tokens are minted aligned with the GHG Corporate Standard. For example, tokens can be minted aligned with the InterWork Alliance (IWA) Carbon Emission Token Protocol.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.carboncentral.app/knowledge-base/demos/carbon-reporting/ghg-protocol-corporate-standard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.