VCS PROJECT DESCRIPTION TEMPLATE

This template is for the design of projects using the VCS Program.

Instructions for completing the project description

FILE NAME: Use the following format for the file name of the completed document:

 For projects requesting pipeline listing: VCS PD DRAFT ProjectID DDMMMYYYY

 For projects requesting registration approval: VCS PD ProjectID DDMMMYYYY
‘DDMMMYYYY’ should be the original date of issue as reported on the title page. If revised documents are
submitted, add ‘track’ to the end of the file name and update DDMMMYYYY to the most recent date of
issue.

FILE TYPE: Submit the document as a non-editable PDF.

TITLE PAGE FORMATTING: This document may feature the project title and project proponent’s or
preparers’ logo using size 24, regular (non-italic) Century Gothic font. Fill in and complete each row of the
table using size 10.5, black, regular (non-italic) Arial or Franklin Gothic Book font.

GENERAL FORMATTING: Complete all sections using size 10.5, black, regular (non-italic) Arial or
Franklin Gothic Book font.

GENERAL INSTRUCTIONS: Specific instructions for completing each section of the project description
template are located under the section headings in this template. Instructions relate back to the rules and
requirements set out in the VCS Standard and accompanying VCS Program documents. The preparer will
need to refer to these documents to complete the template.

Note: The instructions in this template are to serve as a guide and do not necessarily represent an exhaustive
list of the information the preparer must provide under each section of the template.

Where a section is not applicable, explain why the section is not applicable (i.e., do not delete the section
from the final document and do not only write “not applicable”).

Delete all instructions, including this introductory text, from the final document.
 PROJECT TITLE
Logo (optional)

Project title Name of the project

Project ID Verra Project ID

Crediting period DD-Month-YYYY to DD-Month-YYYY

Original date of issue For pipeline listing, DD-Month-YYYY is the date of submission

For registration, DD-Month-YYYY is the date the project description was completed
following the completion of the audit

Most recent date of

DD-Month-YYYY is the date on which the document was most recently submitted
issue

Version Version number of this document

VCS Standard Version Version number of the VCS Standard used by the project

Prepared by Individual and organization that prepared this document

CONTENTS
1 PROJECT DETAILS........................................................................................................5
1.1 Summary Description of the Project..................................................................................................5
1.2 Audit History.....................................................................................................................................5
1.3 Sectoral Scope and Project Type........................................................................................................5
1.4 Project Eligibility...............................................................................................................................6
1.5 Project Design....................................................................................................................................6
1.6 Project Proponent...............................................................................................................................7
1.7 Other Entities Involved in the Project................................................................................................7
1.8 Ownership..........................................................................................................................................7
1.9 Project Start Date...............................................................................................................................8
1.10 Project Crediting Period.....................................................................................................................8
1.11 Project Scale and Estimated GHG Emission Reductions or Removals..............................................8
1.12 Description of the Project Activity.....................................................................................................9
1.13 Project Location.................................................................................................................................9
1.14 Conditions Prior to Project Initiation.................................................................................................9
1.15 Compliance with Laws, Statutes and Other Regulatory Frameworks..............................................10
1.16 Double Counting and Participation under Other GHG Programs....................................................10
1.17 Double Claiming, Other Forms of Credit, and Scope 3 Emissions..................................................11
1.18 Sustainable Development Contributions..........................................................................................12
1.19 Additional Information Relevant to the Project...............................................................................12

2 SAFEGUARDS AND STAKEHOLDER ENGAGEMENT.........................................13

2.1 Stakeholder Engagement and Consultation......................................................................................13
2.2 Risks to Stakeholders and the Environment.....................................................................................15
2.3 Respect for Human Rights and Equity.............................................................................................16
2.4 Ecosystem Health.............................................................................................................................17

3 APPLICATION OF METHODOLOGY.......................................................................19
3.1 Title and Reference of Methodology................................................................................................19
3.2 Applicability of Methodology..........................................................................................................19
3.3 Project Boundary.............................................................................................................................19
3.4 Baseline Scenario.............................................................................................................................20
3.5 Additionality....................................................................................................................................21
 3.6 Methodology Deviations..................................................................................................................22

4 QUANTIFICATION OF ESTIMATED GHG EMISSION REDUCTIONS AND

REMOVALS.....................................................................................................................22
4.1 Baseline Emissions..........................................................................................................................22
4.2 Project Emissions.............................................................................................................................22
4.3 Leakage Emissions...........................................................................................................................22
4.4 Estimated GHG Emission Reductions and Carbon Dioxide Removals...........................................23

5 MONITORING................................................................................................................25
5.1 Data and Parameters Available at Validation....................................................................................25
5.2 Data and Parameters Monitored.......................................................................................................25
5.3 Monitoring Plan...............................................................................................................................26

APPENDIX 1: COMMERCIALLY SENSITIVE INFORMATION......................................28

APPENDIX X: <TITLE OF APPENDIX>................................................................................29

 VCS Project Description Template, v4.3

1 PROJECT DETAILS
1.1 Summary Description of the Project

Provide a summary description of the project to enable an understanding of the nature of the
project and its implementation, including the following (no more than one page):

 A summary description of the technologies/measures to be implemented by the project.

 The location of the project.
 An explanation of how the project is expected to generate GHG emission reductions or carbon
dioxide removals.
 A brief description of the scenario existing prior to the implementation of the project.
 An estimate of annual average and total reductions and removals.

1.2 Audit History

For projects undergoing crediting period renewal, include the audit history of the project using the
table below. For the project validation, state the validation date in the Period column. This table
should include all monitoring periods, including the period of this report.

Audit type Period Program Validation/verification Number

body name of years

Validation/ (DD-Month- VCS Validation/verification One year

verification YYYY-- DD- body name
Month-YYYY)

1.3 Sectoral Scope and Project Type

Complete the table below with information relevant for non-AFOLU projects:
Sectoral scope1
Project activity type

Complete the table below with information relevant for AFOLU projects:
Sectoral scope
AFOLU project category2
Project activity type

1
Projects, activities, or methodologies may be developed under any of the 16 VCS sectoral scopes:
https://verra.org/programs/verified-carbon-standard/vcs-program-details/#sectoral-scopes
2
See Appendix 1 of the VCS Standard

5
 VCS Project Description Template, v4.3

1.4 Project Eligibility

1.4.1 General eligibility

For all projects, describe and justify how the project is eligible to participate in the VCS Program.
The response should:

 Justify that the project activity is included under the scope of the VCS Program and not
excluded under Table 2.1 of the VCS Standard.

 Provide information to demonstrate that the project meets requirements related to the pipeline
listing deadline, the opening meeting with the validation/verification body, and the validation
deadline.

 Demonstrate that the applied methodology is eligible under the VCS Program. Where applying
a methodology with scale and/or capacity limits, demonstrate that the project is not a
fragmented part of a larger project or activity that would otherwise exceed such limits. If
applicable, demonstrate that no single cluster of project activity instances exceeds the
capacity limit.

 Include any other relevant eligibility information.

1.4.2 AFOLU project eligibility

For AFOLU projects, describe and justify how the project is eligible to participate in the VCS
Program. The response should:

 Justify and demonstrate that all selected AFOLU project categories are appropriate and that
all related category requirements are met.

 Provide evidence that native ecosystems have not been converted, cleared, drained, or
degraded to generate GHG credits in Section 2.4.3 below.

 For ARR, ALM, WRC, or ACoGS project areas, provide evidence that clearing or conversion
did not take place within 10 years of the project start date in Section 2.4.3 below.

1.4.3 Transfer project eligibility

For transfer projects and CPAs seeking registration, justify how eligibility conditions have been
met. The response should justify how the criteria in Appendix 2 and Section 3.22 (Participation
under other GHG Programs) of the VCS Standard have been met.

1.5 Project Design

Indicate if the project has been designed as:

Single location or installation

6
 VCS Project Description Template, v4.3

Multiple locations or project activity instances (but not a grouped project)

Grouped project

1.5.1 Grouped project design

For grouped projects, provide additional information relevant to the design of the grouped project,
including any eligibility criteria that new project instances must meet upon their inclusion,
subsequent to the initial validation of the project.

1.6 Project Proponent

Provide contact information for the project proponent(s). Copy and paste the table as needed.

Organization name

Contact person

Title

Address

Telephone

Email The email address domain must match that of the organization.

1.7 Other Entities Involved in the Project

Provide contact information and roles/responsibilities for any other entities involved in the
development of the project. Copy and paste the table as needed.

Organization
name

Role in the project

Contact person

Title

Address

Telephone

Email The email address domain must match that of the organization.

1.8 Ownership

7
 VCS Project Description Template, v4.3

Provide evidence of project ownership, in conformance with the VCS Program requirements on
project ownership.

1.9 Project Start Date

Project start date DD-Month-YYYY

Justification Justify how the project start date conforms with the VCS
Program requirements

1.10 Project Crediting Period

Crediting period Seven years, twice renewable

Ten years, fixed

Other (state the selected crediting period and justify how it

conforms with the VCS Program requirements)

Start and end date of DD-Month-YYYY to DD-Month-YYYY

first or fixed crediting
period

1.11 Project Scale and Estimated GHG Emission Reductions or Removals

Indicate the estimated annual GHG emission reductions/removals (ERRs) of the project:

< 300,000 tCO2e/year (project)

≥ 300,000 tCO2e/year (large project)
Complete the table below for the first (if renewable) or fixed crediting period:

Calendar year of crediting Estimated GHG emission reductions or removals

period (tCO2e)

DD-Month-YYYY to 31-December-
YYYY

01-January-YYYY to 31-December-
YYYY

01-January-YYYY to DD-Month-YYYY

Total estimated ERRs during the

first or fixed crediting period

8
 VCS Project Description Template, v4.3

Total number of years

Average annual ERRs

1.12 Description of the Project Activity

Describe the project activity or activities (including the technologies or measures employed) and
how it/they will achieve the GHG emission reductions or carbon dioxide removals. Describe the
implementation schedule of project activity or activities.

For non-AFOLU projects:

 Include a list and the arrangement of the main manufacturing/production technologies,
systems and equipment involved. Include in the description information about the age and
average lifetime of the equipment based on manufacturer’s specifications and industry
standards, and existing and forecast installed capacities, load factors and efficiencies.
 Include the types and levels of services (normally in terms of mass or energy flows)
provided by the systems and equipment that are being modified and/or installed and their
relation, if any, to other manufacturing/production equipment and systems outside the
project boundary. Clearly explain how the same types and levels of services provided by the
project would have been provided in the baseline scenario.
 Where appropriate, provide a list of facilities, systems, and equipment in operation under
the existing scenario prior to the implementation of the project.

For AFOLU projects:

 For all measures listed, include information on any conservation, management or planting
activities, including a description of how the various organizations, communities and other
entities are involved.
 In the description of the project activity, state if the project is located within a jurisdiction
covered by a jurisdictional REDD+ program.

1.13 Project Location

Indicate the project location and geographic boundaries (if applicable) including a set of geodetic
coordinates.

For AFOLU projects, GCS projects, grouped projects, or projects with multiple project activity
instances, a separate KML file is required.

1.14 Conditions Prior to Project Initiation

Describe the conditions existing prior to project initiation and demonstrate that the project has not
been implemented to generate GHG emissions for the purpose of their subsequent reduction,
removal, or destruction.

9
 VCS Project Description Template, v4.3

Where the baseline scenario is the same as the conditions existing prior to the project initiation,
there is no need to repeat the description of the scenarios; state that this is the case and refer the
reader to Section 3.4 (Baseline Scenario).

AFOLU projects must also provide the following information:

 Ecosystem type: Provide a brief (1–2 sentence) description of the ecosystem type.

 Current and historical land-use: Provide a brief (2–4 sentence) description of the current and
historical land use of the project area.

 Present and prior environmental conditions of the project area: Provide information on the
climate, hydrology, topography, relevant historic conditions, soils, vegetation, and ecosystems
of the project area.

1.15 Compliance with Laws, Statutes and Other Regulatory Frameworks

Identify and demonstrate compliance of the project with all and any relevant local, regional and
national laws, statutes and regulatory frameworks.

1.16 Double Counting and Participation under Other GHG Programs

1.16.1 No Double Issuance

Is the project receiving or seeking credit for reductions and removals from a project activity under
another GHG program?
Yes No

If yes, provide required evidence of no double issuance as outlined by the VCS Standard.

1.16.2 Registration in Other GHG Programs

Is the project registered or seeking registration under any other GHG programs?
Yes No

If yes, provide the registration number and all relevant details.

1.16.3 Projects Rejected by Other GHG Programs

Has the project been rejected by any other GHG programs?

Yes No

If yes, provide the program name(s), reason(s) and date for the rejection, justification of eligibility
under the VCS Program, and any other relevant information.

10
 VCS Project Description Template, v4.3

1.17 Double Claiming, Other Forms of Credit, and Scope 3 Emissions

1.17.1 No Double Claiming with Emissions Trading Programs or Binding Emission Limits

Are project reductions and removals or project activities also included in an emissions trading
program or binding emission limit? See the VCS Program Definitions for definitions of emissions
trading program and binding emission limit.

Yes No

If yes, provide all required evidence of no double claiming as outlined by the VCS Standard.

1.17.2 No Double Claiming with Other Forms of Environmental Credit

Has the project activity sought, received, or is planning to receive credit from another GHG-related
environmental credit system? See the VCS Program Definitions for definition of GHG-related
environmental credit system.

Yes No

If yes, provide all required evidence of no double claiming as outlined by the VCS Standard.

1.17.3 Supply Chain (Scope 3) Emissions

Do the project activities specified in Section 1.12 affect the emissions footprint of any product(s)
(goods or services) that are part of a supply chain?

☐ Yes No

If yes:

Is the project proponent(s) or authorized representative a buyer or seller of the product(s) (goods or
services) that are part of a supply chain?

Yes No

If yes:

Has the project proponent(s) or authorized representative posted a public statement on their
website saying, “Carbon credits may be issued through Verified Carbon Standard project [project
ID] for the greenhouse gas emission reductions or removals associated with [project proponent or
authorized representative organization name(s)] [name of product(s) whose emissions footprint is
changed by the project activities].”

Yes No

If yes to all:

11
 VCS Project Description Template, v4.3

Provide evidence of the public statement. Evidence must be provided in this section or in an
appendix.

1.18 Sustainable Development Contributions

Provide a brief description that includes the following (no more than 500 words):

 A summary description of project activities that result in sustainable development (SD)

contributions (i.e., technologies/measures implemented, activity location).

 An explanation of how project activities will result in expected SD contributions.

 A description of how the project contributes to achieving any nationally stated sustainable
development priorities, including any provisions for monitoring and reporting these.

1.19 Additional Information Relevant to the Project

1.19.1 Leakage Management

Where applicable, describe the leakage management plan and implementation of leakage and risk
mitigation measures.

1.19.2 Commercially Sensitive Information

Indicate whether any commercially sensitive information has been excluded from the public version
of the project description using Appendix 1, and briefly describe the items to which such
information pertains. Provide justification for why the information is commercially sensitive and
confirm that it is not otherwise publicly available.

Note - Information related to the determination of the baseline scenario, demonstration of

additionality, and estimation and monitoring of GHG emission reductions and removals (including
operational and capital expenditures) cannot be considered to be commercially sensitive and must
be provided in the public versions of the project documents.

1.19.3 Further Information

Include any additional relevant legislative, technical, economic, sectoral, social, environmental,
geographic, site-specific and/or temporal information that may have a bearing on the eligibility of
the project, the GHG emission reductions or carbon dioxide removals, or the quantification of the
project’s reductions or removals.

2 SAFEGUARDS AND STAKEHOLDER

ENGAGEMENT

12
 VCS Project Description Template, v4.3

2.1 Stakeholder Engagement and Consultation

2.1.1 Stakeholder Identification

Use the table below to describe the stakeholder identification process. Where the rows do not apply,
provide justification in the cell in the table below.

Stakeholder Describe the process(es) used to identify stakeholders likely impacted

Identification by the project. List the stakeholders identified.

Legal or customary Describe any legal or customary tenure/access rights to territories

tenure/access rights and resources, including collective and conflicting rights, held by
stakeholders, indigenous people (IPs), local communities (LCs), and
customary rights holders.

Stakeholder diversity Describe the social, economic, and cultural diversity within
and changes over time stakeholder groups, the differences and interactions between the
stakeholder groups, and any changes in the make-up of each group
over time.

Expected changes in Describe the expected changes in well-being and other stakeholder
well-being characteristics relative to the baseline scenario, including changes to
ecosystem services identified as important to stakeholders;

Location of Describe the location of stakeholders, IPs, LCs, and customary rights
stakeholders holders, and areas outside the project area that are predicted to be
impacted by the project.

Location of resources Describe the location of territories and resources which stakeholders
own or to which they have customary access.

2.1.2 Stakeholder Consultation and Ongoing Communication

Use the table below to describe the process for and the outcomes from the stakeholder consultation
conducted prior to project initiation.

Date of stakeholder DD-Month-YYYY

consultation

Stakeholder Describe the process to engage stakeholders in a culturally

engagement process appropriate manner (e.g., dates of announcements or meetings,
language and gender sensitivity). Describe the process or methods

13
 VCS Project Description Template, v4.3

used to document the outcomes.

Consultation outcome Summarize the discussion around consent to project design and
implementation, risks, costs and benefits of the project, all relevant
laws and regulations covering workers’ rights in the host country, the
discussion of FPIC and the VCS validation and verification process.

Ongoing Describe the mechanisms for ongoing communication with

communication stakeholders.

Stakeholder input Describe how due account was taken of all input received during the
consultation. Include details on any updates to the project design or
justify why updates were not necessary or appropriate.

2.1.3 Free Prior and Informed Consent

Use the table below to describe the outcome of the FPIC process as part of the stakeholder
consultation process.

Obtaining consent Describe and demonstrate how consent to implement the project
activities was obtained from those concerned, including IPs, LCs, and
customary rights holders, and a transparent agreement was reached.
Describe any ongoing or unresolved conflicts and demonstrate that
the project does not exacerbate nor influence the outcomes of
unresolved conflicts.

Outcome of FPIC Describe the outcome of the FPIC process, the transparent agreement,
and the information disclosed prior to establishing a transparent
agreement with those concerned, IPs, LCs, and customary rights
holders. Provide assurance that the project has not encroached on
land, relocated people without consent, and forced physical or
economic displacement.

2.1.4 Grievance Redress Procedure

Use the table below to describe the grievance redress procedures developed to resolve any conflicts
which may arise between the project proponent and stakeholders.

Development process Describe the process used to develop the grievance redress procedure
including processes for receiving, hearing, responding and
attempting to resolve grievances within a reasonable time period,
taking into account culturally appropriate conflict resolution
methods.

14
 VCS Project Description Template, v4.3

Grievance redress Describe the grievance redress procedures developed with

procedure stakeholders.

2.1.5 Public Comments

Summarize any public comments submitted during the public comment period and any comments
received after the public comment period. Demonstrate how due account was taken of all comments
received. Include details on when the comments were received, and any updates to the project
design or demonstrate the insignificance or irrelevance of comments.

Comments received Actions taken

Summary of comment received Provide a summary of actions taken and any

project design updates or justify why updates were
not necessary or appropriate.

… ….

2.2 Risks to Stakeholders and the Environment

Use the table below describe the risk assessment and outcome of the potential risks to stakeholders
and the environment. Describe the mitigation or preventative measure in place to prevent or
mitigate the risk. Where no risk is identified, write “No risk identified” in the first column, and
provide justification in the second column.

Risks identified Mitigation or preventative

measure taken
Risks to stakeholder
participation
Working conditions
Safety of women and
girls
Safety of minority
and marginalized
groups, including
children
Pollutants (air,
noise, discharges to
water, generation of
waste, release of

15
 VCS Project Description Template, v4.3

hazardous
materials)

2.3 Respect for Human Rights and Equity

2.3.1 Labor and Work

Use the table below to demonstrate the project’s respect for rights related to work and labor.

Discrimination and
Demonstrate that no discrimination or sexual harassment has occurred or
sexual harassment
will occur.
Management
Demonstrate that management teams have expertise or experience in
experience
implementing similar project activities and engaging communities. Where
relevant experience is lacking, demonstrate how the project proponent has
partnered with other organizations to support the project or have a
recruitment strategy to fill the identified gaps.
Gender equity in Demonstrate that equal opportunities have been or will be provided in the
labor and work context of gender equity and pay for labor and work.
Human trafficking, Demonstrate that the project does not and will not use victims of human
forced labor, and trafficking, forced labor, and child labor.
child labor

2.3.2 Human Rights

Demonstrate how the project recognizes, respects, and promotes the protection of the rights of IPs,
LCs, and customary rights holders in line with applicable international human rights law, and the
United Nations Declaration on the Rights of Indigenous Peoples and ILO Convention 169 on
Indigenous and Tribal Peoples.

2.3.3 Indigenous Peoples and Cultural Heritage

Demonstrate that the project preserves and protects cultural heritage as part of project activities.

2.3.4 Property Rights

Using the table below, describe the property rights of IPs, LCs, and customary rights holders and
demonstrate respect of such rights.

Rights to Describe any legal or customary tenure/access rights to territories,

territories and property, and resources, including collective and/or conflicting rights,
resources held by stakeholders.

Respect for Describe the measures implemented to protect and preserve the property

16
 VCS Project Description Template, v4.3

property rights rights of IPs, LCs, and customary rights holders.

2.3.5 Benefit Sharing

Where the project impacts property rights as described in Section 2.4.4 above, use the table below
to describe the project’s benefit sharing agreement.

Process used to Describe the process used to develop the benefit-sharing agreement with
design the benefit the affected stakeholder groups.
sharing plan

Summary of the Describe the benefit-sharing agreement. Where affected stakeholder

benefit sharing groups wish to keep elements of the plan private, provide the full
plan arrangement as a commercially sensitive document. The project proponent
shall demonstrate that the community wishes to keep this information
private.

Approval and Demonstrate that the benefit- sharing agreement was agreed up on by the
dissemination of affected stakeholder groups, and that the agreement was shared in a
benefit sharing culturally appropriate manner. Demonstrate that the agreement is readily
plan accessible should stakeholders wish to review the agreement.

2.4 Ecosystem Health

Identify and summarize any risks to the environment and the steps taken to mitigate them. Where no
risk is identified, write "No risk identified” in the first column, and provide justification in the second
column.

Risks identified Mitigation or preventative

measure taken
Impacts on biodiversity
and ecosystems
Soil degradation and soil
erosion
Water consumption and
stress
Usage of fertilizers

2.4.1 Rare, Threatened, and Endangered species

Is the project located in or adjacent to habitats for rare, threatened, or endangered species?

17
 VCS Project Description Template, v4.3

Yes No

If yes, list such species and habitats in the table below and provide evidence that the project will not
adversely impact these areas.

Species and habitat Demonstrate that the project will not adversely impact
habitats for rare, threatened, or endangered species.

… …

2.4.2 Introduction of species

Demonstrate, using the table below, that no invasive species will be used as part of project
activities. Categorize each species as native, non-native, and indicate if the species is a mono-
culture. Where the species is non-native include an explanation of possible adverse effects of its
usage, and a description of how the project will mitigate such risks. This table is not required for
projects with no planting or species introduction; this section may be indicated as N/A.

Species introduced Classification Justification for use Adverse effects and

mitigation

Where invasive species exist in the project area, list such species in the table below and
demonstrate that the project activity will not allow the species to thrive.

Existing invasive species Mitigation measures to prevent spread or continued

existence of invasive species

2.4.3 Ecosystem conversion

ARR, ALM, WRC or ACoGS projects shall provide evidence that the project area was not cleared or
drained of existing natural ecosystems, unless such clearing took place at least 10 years prior, or
the dominant land cover was invasive.

3 APPLICATION OF METHODOLOGY
3.1 Title and Reference of Methodology

18
 VCS Project Description Template, v4.3

Provide the title, reference and version number of the following information for the methodology(s),
tools, and modules applied to the project (where applicable).

Type Reference ID, if Title Version

(methodology, applicable
tool or module).

Example: Example: Example: Example:

Methodology VM0007 VM0007 REDD+ Methodology Framework 6.0

(REDD+MF),

... ... ... ...

3.2 Applicability of Methodology

Demonstrate and justify how the project activity(s) meets each of the applicability conditions of the
methodology(s), tools, and modules applied by the project (where applicable). Address each
applicability condition separately.

Methodology ID Applicability condition Justification of compliance

Example: VM0007 First applicability condition Justification that the project

for given methodology, tool, complies with this
or module applicability condition

... ... ...

3.3 Project Boundary

Define the project boundary and identify the relevant GHG sources, sinks and reservoirs for the
project and baseline scenarios (including leakage if applicable). Add rows as needed.

Source Gas Included? Justification/Explanation

CO2

CH4
Source 1
Baseline

N2O

Other

Source 2 CO2

CH4

19
 VCS Project Description Template, v4.3

Source Gas Included? Justification/Explanation

N2O

Other

CO2

CH4
Source 1
N2O
Project

Other

CO2

CH4
Source 2
N2O

Other

Provide a diagram or map of the project boundary, showing clearly the physical locations of the
various installations or management activities taking place as part of the project activity based on
the description provided in Section 1.12 (Description of the Project Activity) above.

For non-AFOLU projects, include in the diagram the equipment, systems and flows of mass and
energy. Include the GHG emission sources identified in the project boundary.

For AFOLU projects, include in the diagram or map the locations of where the various measures
are taking place, any reference areas and leakage belts.

3.4 Baseline Scenario

Identify and justify the baseline scenario, in accordance with the procedure set out in the applied
methodology and any relevant tools. Where the procedure in the applied methodology involves
several steps, describe how each step is applied and clearly document the outcome of each step.

Explain and justify key assumptions, rationale, and methodological choices. Provide all relevant
references.

3.5 Additionality
Demonstrate and assess the additionality of the project, in accordance with the applied
methodology and any relevant tools, taking into account the following additionality methods:

3.5.1 Regulatory Surplus

Is the project located in an UNFCCC Annex 1 or Non-Annex 1 country?
Annex 1 country Non-Annex 1 country

20
 VCS Project Description Template, v4.3

Are the project activities mandated by any law, statute, or other regulatory framework?

Yes No

If the project is located inside a Non-Annex 1 country and the project activities are mandated by a
law, statute, or other regulatory framework, are such laws, statutes, or regulatory frameworks
systematically enforced?

Yes No

If no, describe which mandated laws, statutes, or other regulatory frameworks require project
activities and provide evidence of systematic non-enforcement to demonstrate regulatory surplus.

3.5.2 Additionality Methods

 Where a project method is applied to demonstrate additionality and the procedure in the
applied methodology or tool involves several steps, describe how each step is applied and
clearly document the outcome of each step. Indicate clearly the method selected to demonstrate
additionality (e.g., investment analysis or barrier analysis in the case of the CDM Tool for the
demonstration and assessment of additionality). Where barrier analysis, or equivalent, is used
to demonstrate additionality, only include the most relevant barriers. Justify the credibility of
the barriers with key facts and/or assumptions and the rationale. Provide all relevant
references.
 Where a performance method is applied to demonstrate additionality, demonstrate that
performance can be achieved to a level at least equivalent to the performance benchmark
metric.
 Where the methodology applies an activity method for the demonstration of additionality,
include a statement that notes that conformance with the positive list is demonstrated in the
Applicability of Methodology section above.

 Provide sufficient information (including all relevant data and parameters, with sources) so
that a reader can reproduce the additionality analysis and obtain the same results.

3.6 Methodology Deviations

Describe and justify any methodology deviations applied, including any previous deviations.
Include evidence to demonstrate the following:

 The deviation will not negatively impact the conservativeness of the quantification of GHG
emission reductions or removals.

 The deviation relates only to the criteria and procedures for monitoring or measurement
and does not relate to any other part of the methodology.

21
 VCS Project Description Template, v4.3

4 QUANTIFICATION OF ESTIMATED
GHG EMISSION REDUCTIONS AND
REMOVALS
4.1 Baseline Emissions
Describe the procedure for quantification of baseline emissions and/or carbon stock changes in
accordance with the applied methodology. Baseline emissions may be negative where carbon stock
increases (sinks) exceed baseline emissions. Specify the reductions and removals separately where
the applied methodology provides procedures and equations to do so. Include all relevant
equations here and provide sufficient information to allow the reader to reproduce the calculations.
Explain and justify all relevant methodological choices (e.g., with respect to selection of emission
factors and default values). Include all calculations in the emission reduction and removal
calculation spreadsheet.

4.2 Project Emissions

Describe the procedure for quantification of project emissions and/or carbon stock changes in
accordance with the applied methodology. Project emissions may be negative where carbon stock
increases (sinks) exceed project emissions. Specify the reductions and removals separately where
the applied methodology provides procedures and equations to do so. Include all relevant
equations here and provide sufficient information to allow the reader to reproduce the calculations.
Explain and justify all relevant methodological choices (e.g., with respect to selection of emission
factors and default values). Include all calculations in the emission reduction and removal
calculation spreadsheet.

4.3 Leakage Emissions

Describe the procedure for quantification of leakage emissions in accordance with the applied
methodology. Specify the reductions and removals separately where the applied methodology
provides procedures and equations to do so. Include all relevant equations here and provide
sufficient information to allow the reader to reproduce the calculations. Explain and justify all
relevant methodological choices (e.g., with respect to selection of emission factors and default
values). Include all calculations in the emission reduction and removal calculation spreadsheet.

4.4 Estimated GHG Emission Reductions and Carbon Dioxide Removals

Describe the procedure for the quantification of estimated GHG emission reductions (reductions)
and carbon dioxide removals (removals). Include all relevant equations.

22
 VCS Project Description Template, v4.3

For data and parameters monitored, use the estimated data/parameter values provided in Section
5.2 below. Document how each equation is applied in a manner that enables the reader to
reproduce the calculations. Provide calculations for all key equations to allow the reader to
reproduce the annual calculations for estimated reductions or removals. Specify the reductions and
removals separately where the applied methodology provides procedures and equations to do so.
Include all of the above in the emission reduction and removal calculation spreadsheet.

Complete the tables below by vintage period (calendar year). Note that the baseline or project
emissions subtotals may be negative where sinks exceed emissions. Only specify the estimated
VCUs for reductions and removals separately where the applied methodology provides procedures
and equations to do so.

For projects that are not required to assess permanence risk, complete the table below for the
project crediting period:
Vintage Estimated Estimated Estimated Estimated Estimated Estimated
period baseline project leakage reduction removal total VCUs
emissions emissions emissions VCUs VCUs (tCO2e)
(tCO2e) (tCO2e) (tCO2e) (tCO2e) (tCO2e)

DD-MMM- Example: Example: Example: Example: Example: Example:

YYYY to
50,000 20,000 10,000 10,000 10,000 20,000
31-Dec-
YYYY

01-Jan-
YYYY to
31-Dec-
YYYY

01-Jan-
YYYY to
DD-MMM-
YYYY

Total

For projects required to assess permanence risk:

i) Provide the requested information using the table below:

State the non-permanence risk rating (%) Example: 20%

Has the non-permanence risk report been Yes No

attached as either an appendix or a separate
document?
For ARR and IFM projects with harvesting,
state, in tCO2e, the Long-term Average (LTA).
Has the LTA been updated based on Yes No
monitored data, if applicable? If no, provide justification.

23
 VCS Project Description Template, v4.3

State, in tCO2e, the expected total GHG

benefit to date.
Is the number of GHG credits issued below the Yes No
LTA? If no, provide justification.

ii) Complete the table below for the project crediting period. Note that the buffer pool allocation is
split proportionally between the estimated reductions and removals. (For example, if a project is
estimated to achieve 20,000 tCO 2e removals and 80,000 tCO2e reductions and has a buffer
contribution of 20%, or 20,000, the estimated removal VCUs would be 16,000 and reduction VCUs
would be 64,000).

Vintage Estimated Estimated Estimated Estimated Estimated Estimated Estimated

period baseline project leakage buffer pool reduction removal total VCU
emissions emissions emissions allocation VCUs VCUs issuance
(tCO2e) (tCO2e) (tCO2e) (tCO2e) (tCO2e) (tCO2e) (tCO2e)
DD-
Example: Example: Example: Example: Example: Example: Example:
MMM-
YYYY to 50,000 20,000 10,000 4,000 8,000 8,000 16,000
31-Dec-
YYYY

01-Jan-
YYYY to
31-Dec-
YYYY

01-Jan-
YYYY to
DD-
MMM-
YYYY

Total

5 MONITORING
5.1 Data and Parameters Available at Validation
Complete the table below for all data and parameters that are determined or available at validation
and remain fixed throughout the project crediting period (copy the table as necessary for each
data/parameter). The values provided are used to quantify the estimated reductions and removals
for the project crediting period in Section 4 above. Data and parameters to be monitored during the
operation of the project are included in Section 5.2 (Data and Parameters Monitored) below.

24
 VCS Project Description Template, v4.3

Data / Parameter

Data unit Indicate the unit of measure

Description Provide a brief description of the data/parameter

Source of data Indicate the source(s) of data

Value applied Provide the value applied

Justification of choice of Justify the choice of data source, providing references where applicable.
data or description of Where values are based on measurement, include a description of the
measurement methods measurement methods and procedures applied (e.g., what standards or
and procedures applied protocols have been followed), indicate the responsible person/entity that
undertook the measurement, the date of the measurement and the
measurement results. More detailed information may be provided in an
appendix.

Purpose of data Indicate one of the following:

 Determination of baseline scenario (AFOLU projects only)
 Calculation of baseline emissions
 Calculation of project emissions
 Calculation of leakage

Comments Provide any additional comments

5.2 Data and Parameters Monitored

Complete the table below for all data and parameters that will be monitored during the project
crediting period (copy the table as necessary for each data/parameter). The values provided are
used to quantify the estimated reductions and removals for the project crediting period in Section 4
above.

Data / Parameter

Data unit Indicate the unit of measure

Description Provide a brief description of the data/parameter

Source of data Indicate the source(s) of data

Description of Specify the measurement methods and procedures, any standards or

measurement methods protocols to be followed, and the person/entity responsible for the
and procedures to be measurement. Include any relevant information regarding the accuracy of
applied the measurements (e.g., accuracy associated with meter equipment or
laboratory tests).

25
 VCS Project Description Template, v4.3

Frequency of Specify measurement and recording frequency

monitoring/recording

Value applied Provide an estimated value for the data/parameter

Monitoring equipment Identify equipment used to monitor the data/parameter including type,
accuracy class, and serial number of equipment, as appropriate.

QA/QC procedures to be Describe the quality assurance and quality control (QA/QC) procedures to
applied be applied, including the calibration procedures where applicable.

Purpose of data Indicate one of the following:

 Calculation of baseline emissions
 Calculation of project emissions
 Calculation of leakage

Calculation method Where relevant, provide the calculation method, including any equations,
used to establish the data/parameter.

Comments Provide any additional comments

5.3 Monitoring Plan

Describe the process and schedule for obtaining, recording, compiling and analyzing the monitored
data and parameters set out in Section 5.2 (Data and Parameters Monitored) above.

Include details on the following:

 The methods for measuring, recording, storing, aggregating, collating and reporting on
monitored data and parameters. Where relevant, include the procedures for calibrating
monitoring equipment.
 The organizational structure, responsibilities and competencies of the personnel that will be
carrying out monitoring activities.
 The procedures for internal auditing and QA/QC.
 The procedures for handling non-conformances with the validated monitoring plan.
 Any sampling approaches used, including target precision levels, sample sizes, sample site
locations, stratification, frequency of measurement and QA/QC procedures.

Where appropriate, include line diagrams to display the GHG data collection and management
system.

26
APPENDIX 1: COMMERCIALLY
SENSITIVE INFORMATION
Use the table below to describe the commercially sensitive information included in the project description to
be excluded in the public version.

Section Information Justification

 VCS Project Description Template, v4.3

APPENDIX X: <TITLE OF APPENDIX>

Use appendices for supporting information. Delete this appendix (title and instructions) where no appendix
is required.

28