Projects must explain why they are eligible under the selected protocol.
Work with us as a Biochar supplier
We've combined requirements from our modular protocol framework outlining everything you need to be validated as a Biochar supplier.
We provide further support to compile a compliant validation package on our platform, Isometric Certify.
Overview
Where do requirements come from?
List of Biochar requirements
Search
Table of contents
Project setup
Project setup
Essential project details including who's involved, the location of your project, and how much carbon will be removed.
Projects must provide reasoning and evidence for legal ownership over the rights to all removals that will be claimed.
A single project proponent must be specified as the sole owner of the removals.
Ownership of removals must be defined in contracts between the Project Proponent and other project participants, for example with storage site owners and operators.
Contracts must relinquish ownership of all removals to the Project Proponent.
Contracts must clearly indicate that other companies or operators participating in the Project cannot claim credits, emissions reductions or offsets as a result of participation in the Project.
Contracts must provide mechanisms for the Project Proponent to obtain required information to fully calculate the removals from aspects of the Project relevant to the company.
Contracts must stipulate that unless these third parties are the end owners of the generated credits that they will not advertise that they are producing a “low emission product or practice,” in connection with the removals carried out by the Project.
Protocol & monitoring data
Protocol & monitoring data
How will you be measuring, monitoring and maintaining carbon removal, including data models and risk assessments.
Projects must define their temporal and geographic boundary.
Projects must define their system boundary and outline all GHGs considered across all sources, sinks and reservoirs (SSRs).
System boundaries must include the construction/manufacturing of each physical site and associated equipment.
System boundaries must include the operation of each process.
System boundaries must include the closure and disposal of each site and associated equipment.
Projects must reason and evidence the baseline scenario of their activities having not taken place.
Counterfactuals must be calculated using conservative assumptions and must be assessed for every removal.
Project baselines must account for any existing government policies or legal requirements that lower GHG emissions.
Projects must provide a robust assessment of the potential increases in GHG emissions outside the system boundary that occurs as a result of the Project activity.
Projects must quantify and deduct leakage from the CO₂ Removals in accordance with the relevant Protocol.
Projects must demonstrate removals are the main purpose and only source of revenue; OR Project must demonstrate that economic barriers would prevent Project implementation in the absence of Carbon Finance.
In order to demonstrate economic barriers would prevent Project implementation in the absence of Carbon Finance, projects must provide full Project financials, calculate return on investment via Internal Rate of Return (IRR) and a scenario analysis to demonstrate the ability to meet Additionality criteria for cases where values in the analysis change.
Projects must briefly describe any public funding it has received.
Projects must demonstrate Environmental Additionality.
Environmental Additionality is demonstrated if the climate impact of the Project is net negative after subtracting the Counterfactual CO₂ removal and all project GHG emissions.
Projects must demonstrate Regulatory Additionality.
Projects must demonstrate it is not required by existing laws, regulations, policies, or other binding obligations; OR Projects can consider anything in excess of the legal requirements as additional.
Projects must assert the method(s) for compliance with regulations for all jurisdictions to which the Project is beholden.
Projects must select from the durability threshold(s) defined in the protocol or module to be the project durability threshold.
Projects must demonstrate a durability in excess of the designated project durability threshold.
Projects can justify durability by providing information and justification; presenting scientifically falsifiable hypotheses; conducting ongoing monitoring.
Projects must undertake a full risk assessment to identify possible reversals mechanisms and subsequent decreases in durability.
Projects must specify whether they will follow the default monitoring plan or submit and justify a monitoring plan which may contain additional or modified monitored parameters.
Monitoring plans must adhere to the Protocol, define frequency of measurement and reporting, consider baselines, identify emissions and be made public on the Registry.
Projects must conduct a sensitivity analysis that demonstrates the impact of each input parameter’s uncertainty on the final net CO₂e uncertainty.
Projects must provide details of the sensitivity analysis method so that the results can be re-created.
Parameters may be omitted from a full uncertainty analysis if a Sensitivity Analysis can demonstrate that the parameter contributes to <1% change in Removal.
Projects must provide the source for information relevant to Uncertainty calculation and/or justification for each input parameter.
Projects must specify whether they used conservative estimates of input parameters, variance propagation and/or Monte Carlo simulations in consideration of uncertainty (one or multiple options).
Projects must describe and justify any models used for quantification, monitoring, and meeting specified protocol requirements.
Models and Proxy measurements must apply Conservative Uncertainty factors and make Conservative assumptions.
Assumptions and estimations must be disclosed and justified.
Uncertainty must be assessed and clearly outlined in the Protocol.
Proxies must be shown to be well-correlated with the variable of interest
Projects must provide Proxy data, empirical fits, correlation data, and sources
Models must be from a Reputable Source and/or shown to be reliable via peer-review, testing or correlation with empirical data
Projects must outline the source of models, any modifications, input parameters, data used and validation results
Environmental & social impacts
Environmental & social impacts
How will your project affect people and nature, and how will you manage any risks that arise.
Projects must outline and detail compliance with applicable national and local laws and regulations.
Projects must provide an assessment of the material environmental and social impacts.
Projects must demonstrate how risks have been assessed and, if applicable, what mitigation plan is in place to prevent them.
Projects must report risks that are not applicable to the Project and justify within the PDD.
A full Environmental and/or Social Impact Assessment (EIA and/or SIA) conducted by a third party is suggested for all Projects but is only required if impacts are considered significant and/or if required by the host jurisdiction.
Projects must demonstrate that it creates no net environmental harm.
Projects must consider biodiversity conservation and sustainable management of living natural resources
Projects must demonstrate that it creates no net social harm.
Projects must consider labor rights and working conditions.
Projects must consider land acquisition and involuntary resettlement.
Projects must consider the impacts on Indigenous People (IP), Local Communities (LC) and cultural heritage.
Project must consider respect for human rights and stakeholder engagement.
Project must demonstrate how their carbon removal activities are consistent with relevant SDGs.
Projects must describe the conditions under which the Project will be considered closed, and describe the Project closure plan – outlining any post-cessation actions that will be undertaken upon Closure of the Project.
Stakeholder input process
Stakeholder input process
How will your project work with and respond to the community while staying compliant and adaptable.
Projects must provide a description and documentation of how comments by local stakeholders have been invited and compiled, a summary of comments received, and report on how due account was taken of comments received.
Project must inform relevant stakeholders of proposed and current activities.
All stakeholders should be equitably represented, involved and able to contribute freely.
Consultations must be iterative, accessible, transparent, independent, equal and documented.
Projects must outline the mechanism for stakeholders to voice, process and resolve grievances.
Projects must make contact information available to all stakeholders.
Projects must acknowledge grievances no later than 14 days after receipt.
Projects must resolve or escalate grievances no later than 60 days after receipt.