Dashboard
Completeness
0%
Net GHG benefit
0
tCO₂e for monitoring-period rows
Indicative eligible quantity
0
tCO₂e potentially eligible; not issued VCUs
Open findings
0
CAR + CL + FAR not closed
Verification-readiness checks
Period calculation
Baseline, project, leakage and net values from the GHG Calculation tab.
0. Verra Version 5 Alignment
Project request & template decision
Current VCS rules snapshot
Configured against the current published Version 5 framework as of the rules snapshot date. The app does not replace Verra Project Hub or the official template files.
Program Guide: V5.0
VCS Standard: V5.0
Program Definitions: V5.0
Methodology Requirements: V5.0
Registration & Issuance Process: V5.0
AFOLU NPRT Procedure: V5.0
Geolocation File Requirements: V5.0
Corrections & Clarifications: 9 June 2026
Important use rule
The app selects the applicable VCS template family (legacy / 5.0A / 5.0B) from the project start date, submission date, request type and baseline-reassessment status. Methodology-specific requirements still control eligibility and quantification. Before final export, confirm the current Verra rules, current Corrections & Clarifications, active methodology and the exact official Verra template then in force. The app blocks the “Submission-Ready” export when critical readiness checks fail.
1. Project & Program Setup
Project summary
2. Rights, Claims & Double Counting
Right to operate and right to reductions/removals
Other programs, claims and labels
3. Boundary, GIS & Stratification
Project boundary
VCS v5 geolocation quick check
Verra submission format: VCS Geolocation File Requirements v5.0 require KML or KMZ unless the applied methodology specifies otherwise. KML is parsed and checked here. KMZ is accepted as a reference but should be extracted to KML for this offline validator. GeoJSON/SHP/CSV/GPX/GPKG remain useful working formats but are flagged for conversion where required.
No GIS file loaded.
For VCS v5 AFOLU submissions: use WGS 84 (EPSG:4326), decimal degrees, valid geometry, required instance/project-geodata structure, attributes and naming conventions. VVB validation/verification of the geolocation file remains required.
Strata / project instances
| Stratum / instance | Management unit | Activity / planting year | Area (ha) | Eligible ha | Basis of stratification |
|---|
4. Baseline & Additionality
Baseline scenario
Additionality
Project scenario & counterfactual integrity
5. Methodology Applicability, Deviations & Method Engine
Applied methodology control
Deviation controls
The selected active Verra methodology, its modules and tools control eligibility, baseline, quantification, leakage, uncertainty and monitoring. Generic IPCC/ISO calculations are supporting calculations only.
Built-in methodology calculation pack
Methodology applicability-condition register
Enter every applicable condition from the active methodology. The built-in VM0047 pack supplies a working checklist, but the project must provide its own response and evidence. Any applicable condition not marked Pass blocks submission-ready export.
| Condition / reference | Applicable? | Project response | Evidence | Status |
|---|
6. Carbon Pools & Sources
Pool/source inclusion register
Document inclusion/exclusion consistently with the applied methodology.
| Pool / source | Type | Included? | Baseline relevance | Project relevance | Justification / methodology reference |
|---|
7. Monitoring Plan & Data Parameters
Audit-ready monitoring parameter register
Each parameter can now be traced to source, procedure, responsible person, calibration, uncertainty, methodology/equation reference, evidence and archive requirement.
| Parameter | Unit | Kind | Data type | Description | Source | Method / procedure | Frequency | Responsible | Equipment | Calibration | QA/QC | Uncertainty | Equation ref | Methodology ref | Evidence ID | Archive / retention | Purpose |
|---|
8. Field Inventory & Methodology Uncertainty
Plot / measurement records
Import one row per plot here, including zero-tree plots. Plot area, coordinates, stratum and QA/QC status remain independent field metadata; mean DBH/height and carbon density are synchronized from the individual-tree inventory when matching Plot IDs exist.
No Plot CSV imported yet.
| Plot ID | Stratum | Plot area (m²) | Area basis | Lat | Lon | Mean DBH (cm) | Mean Height (m) | Carbon density (tCO₂e/ha) | Tree records / status | Checked? |
|---|
Generic sampling QA/QC
Generic sample statistics
N
0
Mean tCO₂e/ha
0
Relative CI half-width
—
QA/QC checked
0%
VM0047 v1.1 uncertainty engine
For the area-based pathway this implements the working form of VM0047 Eq. 28: paired/permanent-plot covariance may be represented by ρ; use ρ=0 for independent samples. For the census pathway it implements the working form of Eqs. 29–31, including mortality uncertainty. Confirm every entered term against the active methodology/calculation workbook.
9. Forest / Plantation Carbon Estimation
International protocol & calculation basis
Calculation framework: IPCC 2006 AFOLU + 2019 Refinement for Forest Land carbon-stock logic; ISO 14064-2:2019 for project-level quantification/MRV principles; optional Chave et al. (2014) pantropical tree allometry. The applicable Verra methodology and VCS rules remain controlling for crediting. GHG Protocol LSR v1.1 does not presently provide comprehensive forestry accounting requirements.
Resolved automatically from the integrated species database. It is not a field-data input and is no longer included in tree CSV templates.
Select a suitable IPCC/local value for ecological zone, forest origin and biomass class. The prefilled value is only a working placeholder.
Assam / India Allometric Equation Library & Automatic Verra Hierarchy Selector
How AUTO works: VM0047 v1.1 requires published allometric equations to be selected by a hierarchy. For facilitated natural regeneration or stands with more than two species, the app first looks for a forest-type equation from the same ecoregion/Holdridge life-zone, then a suitably validated global forest-type equation. For other stands (for example monocultures), it looks first for species/genus/family equations from the same ecoregion/life-zone, then global species/genus/family equations. If the library cannot support the required level, the app flags the tree instead of silently substituting an ineligible equation.
Wood density is resolved automatically tree-by-tree from the integrated species database after tree import. No wood-density column is required in the tree CSV.
Nath et al. (2019) unit-control note: the publication describes δ as wood density/specific gravity and its methods text labels kg m⁻³, while practical applications commonly use the specific-gravity / g cm⁻³ numerical scale. This app uses the tree-table ρ value in g/cm³ for the Nath arithmetic equation and deliberately requires the project/VVB to mark the unit convention as reviewed before submission-ready export.
Built-in biomass equation candidates
| ID | Scope | Equation | Applicable context | Source / status |
|---|
Integrated species wood-density database
Lookup priority is exact scientific-name match, then registered alias/vernacular match. Assam Forest Department/FSI-linked records are preferred where available; additional exact species records are sourced from GWDD v2.2. Unmatched or ambiguous species remain unresolved rather than receiving a generic default.
| Species | Local / aliases | ρ g/cm³ | Source |
|---|
Tree-level biomass inventory
DBH in cm and height in m are field inputs. Wood density is looked up automatically from the integrated species database using the Species value. With Model=AUTO, the app selects the highest-priority eligible equation from the Verra hierarchy and shows the selection basis. On CSV import, unique Plot IDs are now automatically reconciled to the Field Inventory plot register.
No tree inventory diagnostic available yet.
| Tree ID | Plot ID | Stratum | Species | DBH cm | Height m | ρ g/cm³ (auto) | WD Source / Match | Direct AGB kg | Model | Eq. / Source | VCS Hier. | Stem V m³ (ref.) | AGB kg | BGB kg | Carbon kg C | CO₂e kg |
|---|
Plot / stratum carbon summary
Tree results are aggregated by plot, converted to tCO₂e/ha and area-weighted to project strata where names match the Boundary & GIS strata register.
| Plot ID | Stratum | Plot area m² | Area basis | Trees | AGB kg | BGB kg | Carbon kg C | CO₂e kg | tCO₂e/ha |
|---|
IPCC stand-volume / BCEF method
Alternative inventory pathway using merchantable growing-stock volume and biomass conversion & expansion factor (BCEF). Do not combine with tree-allometry biomass for the same area.
| Stratum | Area ha | Growing stock V m³/ha | BCEF tDM/m³ | R | CF | AGB tDM/ha | Total biomass tDM/ha | Carbon tC/ha | CO₂e t/ha | Total tCO₂e |
|---|
Additional carbon pools — sample-plot field data
Enter one row per sample plot. Plot-level dead wood, litter and SOC densities are calculated first, then aggregated by stratum. Stratum totals use the matching Boundary & GIS eligible/stratum area—not the sampled plot area.
Raw field-data self-calculation: enter measurements actually taken in the sample/sub-plots. The app derives dead wood and litter tDM/ha, soil-core volume (V), bulk density, Soil C%, coarse-fragment %, and SOC. Plot ID links to Field Inventory so Stratum and Plot Area can be prefilled.
Dead wood raw measurements → tDM/ha
Mass method: dry kg = direct dry mass, or fresh mass × (subsample dry ÷ subsample fresh). tDM/ha = dry kg × 10 ÷ sampled area m². Volume method: dry kg = V × dry density.
Litter raw measurements → tDM/ha
Soil core, carbon and coarse-fragment measurements
Soil C% cannot be inferred reliably from plot geometry alone; use a laboratory organic-carbon result, or a laboratory organic-matter result with the documented conversion factor. SOC override is enabled only for an externally verified SOC stock.
No auxiliary-pool plot CSV imported yet.
| Plot ID | Stratum | Plot area m² | Dead wood tDM/ha | Litter tDM/ha | BD g/cm³ | Depth cm | Soil C % | Coarse % | SOC override tC/ha | SOC tC/ha | Aux tCO₂e/ha | Basis |
|---|
Stratum-wise auxiliary-pool summary
Plot densities are aggregated within each stratum. Where plot areas are recorded, the stratum mean is weighted by plot area; otherwise equal plot weights are used. The project total is mean tCO₂e/ha × matching Boundary & GIS stratum area.
| Stratum | Plots | Stratum area ha | Area source | Mean dead wood tDM/ha | Mean litter tDM/ha | Mean SOC tC/ha | Mean Aux tCO₂e/ha | Total Aux tCO₂e |
|---|
Carbon stock & stock-change summary
Trees measured
0
Tree-method biomass stock
0
tCO₂e scaled to matched strata
Volume/BCEF biomass stock
0
tCO₂e
Additional pools
0
tCO₂e
Selected current stock
0
biomass method + auxiliary pools
Stock difference
—
tCO₂e vs previous stock
Annual stock change
—
tCO₂e/yr
Mean plot density
0
tCO₂e/ha
10. Methodology-Controlled GHG Quantification & VCU Readiness
Probable project-emission source screening
Screen every probable source even when its final value is zero or excluded. Record applicability, inclusion decision, calculation pathway and evidence/rationale for VVB review.
| Probable GHG component | Typical project source | Applicable? | Accounting treatment | Calculation pathway | Evidence / rationale |
|---|
Detailed GHG activity data entry & auto-calculation
Enter raw activity data and source-specific emission factors. The app calculates tCO₂e automatically. Emission factors remain editable and must be supported by the applicable methodology, IPCC/national source, supplier data or other VVB-accepted evidence.
New Activity mode. Enter a new GHG source/activity below and click Save Activity.
Choose an EF library and record. Values remain editable after application and should be confirmed against the applicable methodology and monitoring period.
Activity-based GHG emission register
Calculated emissions remain traceable to the source activity, factor and evidence. Use Manual Register Entry for quick activity × EF or verified-total rows, or use the detailed form above for method-specific calculations.
| Scenario | Period | Stratum/activity | GHG component | Method | Activity basis | EF / source | Calculated tCO₂e | Evidence |
|---|
GHG activity summary
Project current
0
tCO₂e
Project prior
0
tCO₂e
Baseline current
0
tCO₂e
Rows needing data
0
| Scenario | GHG component | Rows | tCO₂e |
|---|
VM0047 v1.1 monitoring-period removal engine
When VM0047 v1.1 is selected and the method engine is enabled, the app uses the methodology-engine result for submission readiness. The generic row table below remains a reconciliation/supporting table and is not allowed to override the methodology result.
Supporting / reconciliation rows
Use for transparent reconciliation to workbooks, strata or years. In methodology-engine mode, these rows do not replace the VM0047 equation output.
| Year / stratum | Baseline (tCO₂e) | Project (tCO₂e) | Leakage (tCO₂e) | Net benefit (tCO₂e) | Evidence / calc ref |
|---|
Post-methodology adjustments
The official NPRT buffer is recorded from Verra Project Hub. The app now provides an indicative component-level NPRT pre-assessment for preparation and VVB review, but it does not replace the official digital NPRT.
Readiness calculation summary
Methodology / gross result
0
After methodology uncertainty
0
Buffer withheld
0
Indicative eligible quantity
0
11. Leakage & AFOLU Non-Permanence Risk
Quantified leakage register
Enter each methodology-applicable leakage component. The app calculates displaced activity, gross leakage, mitigation and net leakage; current/prior totals can auto-sync to the Method Engine.
| Include | Scenario | Period | Stratum/activity | Leakage component | Baseline activity | Project / retained activity | Unit | Shift / displacement % | Displaced activity | EF tCO₂e/unit | Gross leakage | Mitigation reduction tCO₂e | Direct override tCO₂e | Net leakage tCO₂e | Method / source | Evidence | Status |
|---|
Leakage is methodology-specific. This register is a calculation and evidence layer; use the leakage equation/module required by the applied methodology. For VM0047 projects where applicable, VMD0054 v1.1 provides a standardized approach for displacement of agricultural activities/fuelwood production.
Leakage narrative
Official AFOLU NPRT result
The official digital AFOLU NPRT in Verra Project Hub controls the final non-permanence risk report and buffer result. The quantified module below is an internal pre-assessment / VVB preparation aid.
AFOLU NPRT v5.0 quantified pre-assessment
Scores Internal, External and Natural risk components using the published v5.0 risk structure. Use the official digital Project Hub NPRT for the submission result.
Internal risk
0
External risk
0
Natural risk
0
Indicative buffer
12%
NPRT narrative outputs
12. Grouped Project Instances & Loss Events
Grouped-project activity instances / batches
Use when the project is grouped. Record eligibility area, batch, instance, inclusion date and evidence.
| Instance ID | Eligibility area | Batch | Location / activity | Area ha | Implementation date | Eligibility conclusion | Evidence |
|---|
AFOLU loss / reversal event register
Record fire, cyclone, pest, harvesting, drought or other unplanned carbon-stock loss. Use the official Loss Event Report where required.
| Date | Event | Affected area ha | Estimated loss tCO₂e | Evidence | Corrective / reporting action | Status |
|---|
13. Stakeholder Engagement, ESG & Sustainable Development
Stakeholder engagement
Environmental & social safeguards
Stakeholder engagement register
Structured support for the VCS Stakeholder Engagement Plan / monitoring evidence.
| Stakeholder / group | Category / rights | Engagement & date | FPIC? | Issue / feedback | Project response | Evidence | Status |
|---|
ESG risk assessment & monitoring register
Use alongside the official VCS ESG Risk Assessment / ESG Risk Monitoring Report templates where applicable.
| Category | Risk / impact | Affected party / receptor | Likelihood | Severity | Mitigation | Residual risk | Indicator / evidence | Status |
|---|
14. Evidence, Source Locator & Traceability
Evidence / document register
Record not only the file, but the exact page, sheet/cell, GIS layer/feature or record locator and how it supports the calculation/report.
| ID | Document / evidence | Type | Date | Version | Owner | Location / filename | Source locator (page/sheet/cell/layer/feature) | Parameter/equation/report linkage | Review status | Hash / control note |
|---|
Claim-to-evidence traceability matrix
This is the audit chain: report claim/output → evidence → exact source locator → parameter/equation → calculation record → report section. Mark critical links and review them before final export.
| Trace ID | Report claim / output | Critical? | Evidence ID | Source locator | Data parameter | Equation / method | Calculation record | Report section | Reviewed? |
|---|
15. VVB Findings & Closure Audit Trail
CAR / CL / FAR register
Track the exact requirement, evidence requested, iterative project responses, VVB assessment, auditor, due date, closure date, reviewer and closure evidence.
| No. | Type | Date raised | VCS/methodology reference | Finding | Evidence requested | PP response 1 | PP response 2 | PP response 3 | VVB assessment | Auditor | Due date | Status | Closure date | Reviewer | Closure evidence |
|---|
16. VCS Version 5 Compliance Crosswalk
Submission readiness
Applicable complete
0
Open gaps
0
How to use
This crosswalk is organized around the VCS Standard v5.0 project requirements. “Complete” means the app contains the expected information; it does not mean Verra or a VVB has accepted it. For methodology-specific items, the methodology register and supporting evidence remain controlling.
| VCS reference | Requirement area | Applicable | Status | App evidence / gap |
|---|
17. Official-Template-Mapped Report Builder
Generate VCS-aligned document
“Official-template mapped” means the report maps app content to the selected current Verra template family and inserts a template-control sheet. It does not claim to reproduce the official Verra DOCX byte-for-byte. Before submission, transfer/check the content against the exact official template then in force.
Report preview
Complete project data and click Generate / Refresh.