GHG quantification
General GHG quantification rules can be found in the Riverse Standard Rules.
Calculations of GHG emissions for the baseline and project scenarios shall follow a robust, recognized method and good practice guidance. The overall methodological approach is a comparative life cycle assessment (LCA) at the project-scale, based on .
Mineral carbonation projects may be eligible for removal and avoidance Riverse Carbon Credits.
Avoidance RCCs from fossil or calcination CO2 storage are calculated using the same approach as for removals biogenic and atmospheric CO2, and are simply assigned a different credit label (avoidance instead of removal).
Avoidance RCCs from reduced cement use are calculated and issued according to a separate accounting mechanism, described below. This conservative approach results in double counting the project's induced emissions, and avoids the need for allocation of emissions/removals.
GHG quantification shall be completed for each reporting period. The duration of the reporting period is chosen by the Project Developer and may be either each carbonation batch, each calendar year, another duration shorter than 1 year, or a maximum of 18 months.
Functional unit
Two different functional units are used:
1 tonne of carbonated material sold (e.g. 1 tonne of carbonated concrete, 1 tonne of carbonated aggregate...)
1 tonne of captured CO2
Credits are issued on the basis of carbonated material sale, so this may be considered the main functional unit. Captured CO2 is used as a secondary functional unit for comparability across CDR technologies.
System boundary
The project system boundary shall include only the activities that are additional to the business as usual (BAU) scenario.
The baseline scenario system boundary shall include the processes that would have occurred in the absence of the project.
A summary of the calculation approach is presented below, and detailed descriptions and equations for calculating GHGs are in the respective Project and Baseline scenario sections.
For removals and avoidance from carbonation,
The project system boundary shall include at least the following elements where relevant and additional (i.e. beyond BAU):
production of any non-waste inputs and additives
transport of inputs to the project site (e.g. CO2, recycled concrete, alkaline feedstock...)
onsite energy use (electricity, fuels, heat...) related to e.g. preparation of feedstock, and the carbonation process
fugitive CO2 leaks during CO2 transport
carbon storage
The baseline system boundary shall include:
any removals that would have occurred naturally from carbonation of the alkaline feedstock, and/or
any use-phase carbonation benefits that would have naturally occurred at greater rates had the project not altered the material or process.
Removals and avoidance from carbonation are calculated using the following high-level equations, detailed in their respective sections below.
Allocation
Allocation of captured carbon: removals vs. avoidance
Credits can be issued from carbonation processes that result in both
/removals, from using biogenic and atmospheric (e.g. DAC) CO2, and
/avoidance, from using fossil and calcination CO2.
The same calculation method applies to all CO2 sources, they are simply assigned different credit types upon issuance (i.e. removal vs avoidance, see Eq. 2 and 3).
If the CO2 stream used in the carbonation batch is 100% biogenic/atmospheric or 100% fossil/calcination, no allocation is needed. All carbon storage and project induced emissions are fully attributed to removal or avoidance, respectively.
If the CO2 stream is mixed, Project Developers must determine the proportion of biogenic/atmospheric vs. fossil/calcination carbon, according to Article 39 of the (even for non-EU based projects), summarized here for informative purposes only:
conservatively assume all CO2 is fossil/calcination CO2, or
use mass balance of material inputs by type, or
use measurement method, e.g. C14 testing, or
use other standards and analytical methods, subject to approval by Riverse and the VVB.
The proportion of CO2 types shall be used to allocate the following:
Carbon storage accounting: CO2 flows shall assume a proportional repartition of the two CO2 types in the different CO2 fates (e.g. successfully carbonated CO2, inflow and outflow CO2, unsuccessfully carbonated CO2 left in pore space...).
Project induced emissions: project emissions shall be proportionally assigned to removal or avoidance based on the share of CO2 input from each source.
Allocation between existing activities and baseline activities
When a process is shared between the project scope and BAU activities (e.g. total electricity use at a site performing both cement manufacturing and carbonation), only the portion attributable to the project and additional to the baseline should be included. This allocation should follow one of the approaches below:
Subdivide the system and isolate measurements to collect only input/output data for the project scope (e.g. install electricity meters at the entry point of the carbonation process).
If subdivision is not feasible, allocate shared processes based on a relevant underlying characteristic of the shared systems (e.g. by mass for jointly transported materials, by economic value for co-products with distinct markets...).
This allocation shall be applied at the data collection stage. Project Developers shall do this allocation outside of the GHG quantification equations, and submit allocated data into the removal and avoidance calculations (with justification/proof of work for allocation).
Assumptions
By default, future uses (beyond the product's first life) or end-of-life treatment of the carbonated material will not lead to reversals. This assumes no significant changes in environmental conditions (e.g. pH or fire exposure) that would cause CO2 release.
Carbonation during the use phase of concrete is considered to be the same in both the project and baseline scenarios.
A standard transport distance of 50 km is assumed for concrete and/or carbonated solid materials delivery. Transport emissions for distances below this threshold are considered equivalent between the baseline and project scenarios and are excluded. Transport emissions for distances above this threshold shall be included.
Baseline carbonation of the alkaline feedstock for carbonation of solid materials is conservatively assumed by default to offset 2% of the CO2 removals achieved by the project.
For directly carbonated cement (e.g. during curing or hydration/mixing), it is assumed that either no significant amount of unreacted CO2 remains trapped in the pore space, or that any trapped CO2 will eventually react fully with the cement matrix.
All carbonated material from the same carbonation batch has similar characteristics.
Baseline scenario
The baseline scenario is twofold, and is detailed in following sections:
Removals from carbonation that would have occurred anyway, from alternative feedstock use (for carbonation of solid materials such as SCMs and aggregates) and in use-stage concrete carbonation (for all technology types).
Avoidance from reduced cement shall be considered for projects issuing avoidance credits from reduced cement use, thanks to improved binder strength.
The baseline scenario structure remains valid for the entire crediting period but may be significantly revised earlier if:
The Project Developer notifies Riverse of a substantial change in project operations or baseline conditions, and/or
The methodology is revised, affecting the baseline scenario.
The specific values within the baseline scenario will be updated annually, using project data to accurately reflect the equivalent of the project’s annual operations.
Baseline CO2 stored
BAU carbon removal from natural carbonation of alkaline feedstock and from concrete carbonation during the use-phase shall be considered in the baseline scenario, as detailed below.
Note that this section does not apply to carbonation curing or carbonation during mixing/hydration project.
The alkaline feedstock used by carbonation projects may naturally undergo carbonation upon exposure to atmospheric CO2. The extent of carbonation depends on the
alternative fate of alkaline feedstock
exposure to CO2
mineralogy
particle size
Project Developers shall either
estimate baseline removals in alkaline feedstock over 1000 years using justification and description of common practices for managing the alkaline material, carbonation models, scientific literature, or , or
opt for a default assumed carbon removal rate of of alkaline feedstock in the baseline scenario.
If a first screening assessment based on conservative estimates demonstrates combined baseline removals (sum of alkaline feedstock and concrete use phase) are <1% of the net project removals, then baseline removals may be set to 1%, and the Project Developer does not need to collect more precise baseline removal information. Otherwise, the Project Developer may choose to collect/model baseline removals in detail in order to prove and apply a lower baseline removal rate.
Baseline induced emissions
Baseline induced emissions are only considered for avoidance credits from avoided cement production. In this case, baseline induced emissions shall include the emissions from producing an equivalent amount of cement to serve the same purpose (compressive strength, lifetime...) as the cement produced in the project scenario.
Emissions are calculated based on the quantity and emission intensity of cement used in the project scenario compared to the baseline. While the emission factor of cement production remains the same- since carbonation projects typically do not alter upstream or downstream cement/concrete production- the total amount of cement needed in the concrete design mix may differ. This is because the project may create a stronger binder, requiring less cement than conventional practices.
To determine the quantity of cement avoided, Project Developers shall provide the cement usage ratio between the project and baseline scenarios for each end use of the carbonated material.
This shall be proven using the stated concrete mix designs used by the client, demonstrating a lower cement use than otherwise used, or similar project-specific estimates (i.e. not default global replacement rates).
Calculations from this life cycle stage are presented in Eq. 4-7.
Project scenario
An example of a typical project design and system boundary is shown in Figure 1. Each life cycle stage is detailed in the following sections.

Project CO2 capture
This stage includes process emissions from the CO2 capture facility, CO2 transport emissions, and CO2 leakage during transport.
Induced emissions from the CO2 capture process shall only include emissions/activities that would not have occurred in the baseline.
Typically, CO2 capture is done on industrial sites that are already operating and emitting CO2. In this case, emissions from the industrial site operations and embodied emissions shall not be counted towards the CO2 capture. Furthermore, the CO2 itself is considered a waste product, and according to the waste cutoff LCA principle, is modeled as entering the project system boundary with no environmental burden/emissions.
Processes that may be considered in this stage may include but are not limited to:
additional infrastructure/machinery/instruments that are required for carbon capture (note that only substantial pieces that contribute to at least 1% of the total project life cycle emissions need to be included. This can be assessed with a screening LCA using estimates, and if deemed substantial, more precise material data shall be provided).
additional energy use required for carbon capture: Project Developers shall isolate the amount of energy used at the site that is only for carbon capture, that is not related to the site's BAU activities.
energy or material use from purification and processing of CO2 streams, for example through chemical (e.g. amine-based absorption) or physical treatment (cryogenic separation or membrane separation)
For infrastructure calculations and emission factors, see the Infrastructure and machinery module of the BiCRS methodology. For energy use calculations and emission factors, see the Processing and energy use module of the BiCRS methodology.
Project feedstock provisioning
If the feedstock is a waste, it is considered to enter the project system boundary with no emissions. The waste material enters the system boundary upon the transport step where it is diverted from its BAU use and sent to the project site, or the first non-BAU treatment step, whichever comes first.
If a feedstock is produced for the sole purpose of carbonation, then its entire production emissions shall be counted towards project induced emissions. This includes, for example, mining of olivine rocks.
If a feedstock is a valuable co-product of a process with a different main product, but where the co-product is typically sold and used, then a share of the production emissions shall be allocated to the co-product, preferably based on economic allocation. This includes, for example, steel slag.
Processes that may be considered in this stage may include but are not limited to:
production of non-waste feedstocks
feedstock preparation/processing to increase mineral purity (e.g. magnetic separation of iron), to increase carbonation rates
feedstock preparation/processing to increase surface area (e.g. grinding), to increase carbonation rates
heating, drying, wetting, to obtain optimal feedstock moisture content and diffusivity
For calculations and emission factors used in this stage, see the Processing and energy use module and the Transport module of the BiCRS methodology.
Project carbonation
This stage includes induced emissions from carbonation energy use, input and machinery use, and transport/delivery of the carbonated material. All induced emissions from the carbonation process shall be included and counted towards the project GHG quantification, because they are all by definition part of the carbonation project and additional to baseline conditions.
This shall include: energy use (electricity, heat and fuel) for heating, maintaining temperature, and compression/maintaining pressure. To be measured directly for each reported period using e.g. energy meters, measured for the whole site and allocated to the project, or calculated using machinery power requirements and operation hours.
Depending on the project-specific technology, this may also include but is not limited to:
additives to increase dissolution rates (where dissolution of metal ions is the precursor to carbonation)
water
For energy use calculations and emission factors, see the Processing and energy use module of the BiCRS methodology.
Project CO2 stored
Carbon storage shall be determined using project-specific measurements and CO2 mass balance calculations, using either:
Solid sample: High-accuracy, periodic, solid-sample measurements of carbon in the carbonated material compared to a baseline material using or , with a cross-check measurement, or
Gas inflow-outflow: continuous measurements of CO2 gas inflow minus outflow measurements.
Solid sample measurements are preferred and should be used when possible, because they are the most direct measurement of carbonation. All measurements shall follow an internationally recognized norm or standard (e.g. EN, ISO, ASTM). Cross verification of carbon storage measurements with another is encouraged but not required.
Solid sample
All solid sample TGA or TCA measurements shall be conducted on:
A carbonated sample from the project, and
A non-carbonated control sample of the same material.
The difference in CO2 content between the two shall be used to quantify the amount of CO2 removed by the project activity.
To ensure consistency:
Project and control samples must be collected at the same time interval after exiting the reactor (e.g. 24 hours, 1 week, 1 month).
Both samples must be stored under identical conditions between carbonation and measurement to avoid variations due to natural ambient carbonation.
All measurements shall be performed on . Refer to the Sampling section for detailed procedures on sampling approach, frequency, and traceability.
Gas inflow outflow
Gas inflow-outflow measurements shall be taken continuously (at least 1x per minute) and summarized and reported daily.
Gas measurements shall use a calibrated flow metering with ±1.0% accuracy or better. The Project Developers shall provide equipment calibration certificates and QA/QC procedures.
Any projects using:
Technology type: carbonated solid materials to add to e.g. concrete or asphalt, and
Measurement type: gas inflow-outflow,
shall account for unreacted CO2 trapped in pore space of the carbonated material. This shall be calculated using conversions and subtracted from carbon storage measurements, according to Eq. X.
Data sources
The required primary data for GHG reduction calculations from projects are presented in Table 2, 3 and 4. These data shall be provided for each reporting period and made publicly available.
Table 2 Summary of primary data needed from all projects and their source. Asterisks (*) indicate which data are only required for initial project certification and validation, and do not need to be monitored and updated during verification. Two asterisks (**) indicate which data are only necessary if the project is eligible for avoidance credits from reduced cement use.
Amount of CO2 leaving CO2 capture facility
t CO2 per reporting period
Operations records, sales contracts, invoices
Repartition of CO2 types purchased, entering carbonation facility
fraction
Operations records, sales contracts, invoices
Transport distance or amount of fuel, and transport mode, for CO2 delivery
tonne*km, or kg fuel, or L fuel
Operations records
Amount and type of alkaline feedstock used
tonne/reporting period
Operations records
Amount and type of infrastructure/machinery used for CO2 capture*
kg, tonne, or m3; and material type
Technical design documents
Amount and type of infrastructure/machinery used for carbonation*
kg, tonne, or m3; and material type
Technical design documents
Transport distance or amount of fuel, and transport mode, for alkaline feedstock delivery
tonne*km, or kg fuel, or L fuel
Operations records
Baseline removal calculations from alkaline feedstock carbonation
kgCO2eq/tonne feedstock
Models, calculations
Baseline and project concrete use phase carbonation calculations
kgCO2eq/tonne concrete
Models, calculations
Amount cement needed in project scenario**
kg cement produced /reporting period
Operations records
Amount cement needed in baseline scenario**
kg cement equivalent calculated/ reporting period
Cement mix designs, statements from clients, mandatory concrete mixes
Energy and/or material use from CO2 capture
kg, liter, kWh, MWh, GWh, m3; and material type
Operations records
Energy and/or material use from CO2 purification
kg, liter, kWh, MWh, GWh, m3; and material type
Operations records
Energy and/or material use from alkaline feedstock processing
kg, liter, kWh, MWh, GWh, m3; and material type
Operations records
Energy and/or material use from carbonation
kg, liter, kWh, MWh, GWh, m3; and material type
Operations records
Transport distance or amount of fuel, and transport mode, for carbonated material delivery (if distance >50 km)
tonne*km, or kg fuel, or L fuel
Operations records
Amount of carbonated material produced
tonne
Operations records
Table 3 Summary of primary data needed from projects using solid-sample CO2 storage measurements, and their source. Project Developers shall provide only one of the two data sources listed.
TGA: Carbon storage in project and control materials
mass loss percentage of CO2
Laboratory measurements
TCA: Carbon storage in project and control materials
% mass of carbon or t C/100 t dry material
Laboratory measurements
Table 4 Summary of primary data needed from projects using gas inflow-outflow CO2 storage measurements, and their source.
Volumetric flow of CO2 inflow and outflow
m3 of gas/day
Primary measurements, sensors
Concentration of CO2 inflow and outflow
t CO2/m3 gas
Primary measurements, sensors
gas void fraction of the material (if carbonating solid materials)
fraction of volume per m3
measured or estimated using secondary sources
molar fraction of CO2 in the pore gas (if carbonating solid materials)
unitless
gas analysis or conservatively assumed to equal 1
bulk density of the dry carbonated material (if carbonating solid materials)
kg/m3
measured or estimated using secondary sources
The ecoinvent database version 3.11 (hereafter referred to as ecoinvent) shall be the main source of emission factors unless otherwise specified. Ecoinvent is preferred because it is traceable, reliable, and well-recognized. The ecoinvent processes selected are detailed in Appendix 1. No other secondary data sources are used in this module.
Uncertainty assessment
See general instructions for uncertainty assessment in the Riverse Standard Rules. The outcome of the assessment shall be used to determine the percent of RCCs to eliminate with the .
The following assumptions have low uncertainty:
Use phase concrete carbonation is the same in the project and baseline.
Baseline delivery of concrete or aggregates is 50 km.
Directly carbonated cement will have no CO2 trapped in pore space.
The following assumptions have moderate uncertainty:
Future uses or end-of-life treatment of the carbonated material will not lead to reversals.
All carbonated material from the same carbonation batch has similar characteristics.
The baseline scenario selection at the methodology level has low uncertainty, because it requires a project-specific assessment of the specific amount and type. The specific circumstances, amount and type of baseline material must be proven by the Project Developer, and their uncertainty shall be assessed at the project level. There is low uncertainty that the baseline scenario includes baseline removals and cement.
The equations have low uncertainty, because they consist of straightforward conversions. No models are used in this methodology. Secondary data used in the model include a default baseline carbonation rate of solid feedstocks of 10 kgCO2eq/m3 of feedstock, which comes with low uncertainty due to its very small contribution and the low sensitivity of final results to changes in this value.
The uncertainty at the module level is estimated to be low. This translates to an expected discount factor of at least 3% for projects using this module.
Last updated