Data requirements

Used to measure the impact of regenerative practice changes for verification by carbon standards.

Overview

Regrow’s Intervention module quantifies the impact of regenerative agricultural practice changes by calculating greenhouse gas emissions and removals. It is powered by DNDC, Regrow’s scientifically-rigorous soil model. DNDC measures nutrient cycling and changes in soil carbon to model GHG outcomes resulting from adoption of agricultural practice changes. The GHG quantification data provided by the API can be used for reporting and verification to carbon standards for carbon asset generation.

The Intervention module processes farm management (e.g., crop, tilling, fertilizer) and field conditions (e.g., weather, soil) to generate greenhouse gas emissions data for quantifying carbon assets. It incorporates historical events and specific regenerative practices, producing results that reflect the quantified credits from these practices. Outcomes are determined based on a designated carbon protocol, yielding scope-specific assets with associated uncertainty.

Data requirements for any intervention project

Protocol

Each project requires a protocol. A protocol is a defined methodology for quantifying carbon credits, including baseline logic, uncertainty application rules, and carbon asset calculations. Regrow supports credit quantification with leading Scope 1 protocols such as Verra VM0042 and CAR's Soil Enrichment Protocol. Additionally, Regrow supports general protocol logic for Scope 3 projects.

Select the protocol option for that aligns with the Protocol your project is following or your project verifier. The protocol selected for the project sets the Scope of the project. For Scope 1 choose the vm0042 protocol or the SEP protocol. For Scope 3 projects, choose the General Scope 3 protocol. If you select the General Scope 3 protocol there is an additional parameter to set.

Reporting Percentile

A reporting percentile defines the uncertainty adjustment for the project. This is the percentile of the uncertainty distribution that final credit value will be taken from. In Scope 1 projects, the protocol defines the required reporting percentile to use. For Scope 3 projects, there is more flexibility for project developers to choose and defend the reporting percentile. The default value for the reporting percentile with Scope 3 projects is 33, but you can override that value by setting this parameter.

Baseline Method

The baseline method determines the logic used to generate a counterfactual baseline from a history of field management practices. Depending on the protocol selected for the project, you may need to select the baseline method.

Baselines are an important concept. You can read more here:  https://help.regrow.ag/baseline-method-descriptions 

Field management events

The DNDC model powering the API is calibrated for specific farm management practices (also referred to as “events”), field metadata and conditions. Intervention module takes in your field location and field management data (crop info, tilling events, fertilizer data, etc.). The API combines your data with field-level weather, soil info, etc. Field management data includes a recent history of events, we recommend a minimum of 3 years history but more ideally 5 years of history, as well as the reporting period for which your the measurement is taken.

The table below outlines the relevant information used by the model. Not all data in the table is required, and some field management events listed below will not be applicable for every field.