Skip to main content
Removals contain all CO₂e fluxes incurred in project operation, as specified by the schema in the project’s LCA builder, as well as an allocated portion of the project establishment and end-of-life emissions. Removals are verified once submitted in a GHG Statement.

​
Removal definition

There are no fixed requirements for how you define the boundaries of a removal, however all project flux data (sequestrations, losses, counterfactuals, activities and reductions), must be allocated to a removal to be accounted for.
Examples:
  • A CDR process with a product injection stage might report data per injection
  • A continuous process might report daily or weekly totals as individual removals
  • A project with multiple sequestration sites might separate removals geographically and temporally
A GHG statement can contain multiple removals: data across all removals will be provided to a verifier once the statement is submitted.

​
Create a removal

Draft removals are shown in the Removals section of Certify. If a removal has been allocated to a draft GHG statement it will also be visible there. Removals that are part of verified GHG Statements are not shown in the Removals section and should be accessed via the relevant verified GHG statement. To create a new removal:
1

Add a removal

In an existing GHG Statement, or in the Removals section of your project on Certify, click the Add removal button.
Removals can be created before or after GHG Statements. We recommend that non-API users create GHG Statements first as this ensures that Project emissions are calculated and shown on any included removals.
2

Load template

Select a template to pre-populate the removal with the components, fixed inputs (such as emission factors) and component descriptions required for calculations.
3

Set reporting period

Provide a start and end date for your removal.
4

Edit components

If your specific removal doesn’t match your regular template schema, you can add, delete or update components as needed to match your reporting requirements.
If a component is accounted for over multiple removals, an attribution factor can be assigned accordingly. For example, if a single transport leg transported feedstock for two production batches, an attribution factor of 0.5 can be assigned to the component on each removal.
5

Enter input values

For each datapoint input, add measurements relevant to your current reporting period.If multiple units (e.g. kg and tonnes) are supported for the given input, you can select your preferred unit from the dropdown.
6

Define measurement uncertainty

Where there is material uncertainty for the value of a given input, the standard deviation for the measurement should be entered in the +/- column. This could be due to:
  • Known uncertainty for a measurement device
  • Use of values from a probability distribution with a known variance
7

Upload sources

Measurements should be evidenced with source files. These may include:
  • Documentation such as bills of landing
  • Spreadsheets containing data behind aggregate calculations
  • Scientific citations for use of given approaches or emission factors
Net CO₂e removed is recalculated and the removal is saved automatically each time an input is updated.

​
API users

Removals can also be automated via API integration. See the Post Removal endpoint reference and Creating Your First Removal tutorial for documentation on how to enable this functionality.
If creating removals via an API integration, the removal template schema can be set in the API request, allowing you to define your LCA structure in your local stack or via an MRV partner platform.