akar.earth
Standards & methodologies · Standards

Carbon Project Monitoring Reports: What Verifiers Check

Updated · 4 min read · By the akar.earth specialist team

Carbon monitoring report explained: what goes into a monitoring report, how verification works, and the data issues verifiers flag in Indonesian projects.

A carbon project monitoring report documents what a project actually delivered during a monitoring period: the data collected, the methods used and the resulting emission reductions or removals. A validation and verification body (VVB) audits it, and only a verified monitoring report leads to credit issuance.

If the project design document is the promise, the monitoring report is the proof. Verifiers check whether every reported tonne can be traced back to field and satellite data, measured the way the registered project said it would be.

What a monitoring report contains

Templates differ by standard, but the structure is similar:

SectionContent
Project and monitoring periodDates, area, status of implementation, changes since last report
Implementation statusActivities carried out, planting, protection, community programmes
Data and parametersFixed parameters from validation and monitored parameters with values, sources and methods
QuantificationBaseline, project emissions or removals, leakage, uncertainty, net result
Non-permanence riskUpdated risk assessment and buffer contribution for AFOLU
Safeguards and stakeholdersGrievances, consultation, benefit sharing
DeviationsAny departure from the registered monitoring plan
AnnexesSpatial files, plot data, calculation files, evidence

CCB projects also report community and biodiversity monitoring. Gold Standard projects report SDG indicators.

How verification of a monitoring report works step by step

  1. Close the monitoring period. Fix the start and end dates and finish data collection.
  2. Process data. Clean field data, run remote sensing analysis, apply QA/QC.
  3. Calculate results. Use the registered methodology and parameters.
  4. Draft the report. Use the current template.
  5. Internal review. Check every number against the calculation files.
  6. VVB desk review. Auditors review the report and data.
  7. Site visit. Auditors re-measure sample plots, inspect boundaries and interview staff and communities.
  8. Findings and responses. Corrective actions and clarifications are closed.
  9. Verification report. The VVB issues its opinion.
  10. Issuance request. Submit to the registry, which reviews and issues credits after buffer deductions.

What verifiers check

  • Traceability. Can a reported figure be traced to raw plot sheets, GPS points, photos and imagery?
  • Consistency with the registered design. Same methods, equations, strata and parameters as the project description, or a properly documented deviation.
  • Plot re-measurement. Auditors re-measure a sample of plots. Large differences trigger findings.
  • Remote sensing. Classification accuracy, imagery dates and change detection methods.
  • Uncertainty. Correct calculation and deductions. Read uncertainty deductions.
  • Leakage. Monitoring of displaced activities. Read leakage accounting.
  • Reversals. Any losses reported, and the risk assessment updated.
  • Safeguards. Grievances recorded and resolved.

Indonesia and Southeast Asia application

Common challenges in Indonesian forest and land projects:

  • Cloud cover. Optical imagery gaps over Sumatra, Kalimantan and Papua. Radar or multi-date composites help. Read Sentinel-2 for forest monitoring.
  • Plot relocation. Dense forest and weak GPS signals make it hard to find plots again. RTK-surveyed plot centres and markers solve this.
  • Smallholder data. Thousands of parcels, each needing current boundaries, survival data and consent records.
  • Fire events. Fires between verifications must be detected, mapped and reported.
  • Regulatory reporting. Units traded domestically must be recorded in SRUK, which may require additional reporting.

A structured dMRV data pipeline cuts preparation time and makes audits faster. See the dMRV hub.

Building an audit trail

An audit trail links each reported value back to its source. For tree plots that means plot ID, coordinates, date, crew, raw measurements, photos and the equation used. For remote sensing it means scene IDs, dates, processing steps and accuracy assessment. Store raw data in a read-only archive and keep processing scripts under version control. When an auditor asks where a number came from, the answer should take minutes, not days. Record every correction made during data cleaning with a reason, so that changes to raw values are transparent.

Timing of monitoring periods

Choose monitoring periods that match field seasons and data availability. In much of Indonesia, plot campaigns run best in the drier months, and cloud-free imagery is easier to find then too. Aligning the period end with the field season avoids gaps. Leave enough time between data collection and the audit for processing and internal review.

Pitfalls verifiers flag

  • Data sheets missing for some plots.
  • Values in the report that differ from the calculation file.
  • Undocumented changes in plot design or equations.
  • Satellite analysis without accuracy assessment.
  • Non-permanence risk report not updated.
  • Monitoring period overlapping a previous period.

Our validation and verification support prepares monitoring reports and audit evidence, and akar dMRV keeps field data audit-ready. More on the standards hub.

Frequently asked questions

What is a carbon project monitoring report?

A monitoring report documents what a carbon project actually achieved over a monitoring period. It reports measured data, calculates emission reductions or removals, and is the document a VVB verifies before credits are issued.

How often must a monitoring report be prepared?

Each time a project seeks verification and issuance. Frequency is set by the project, within the standard's rules. Long gaps between verifications can carry consequences under some programmes, so check current rules.

What do verifiers check most?

That reported numbers trace back to raw data, that methods match the registered project description and methodology, that uncertainty and leakage are handled correctly, and that any changes are properly documented.

Does the monitoring report include the buffer calculation?

For VCS AFOLU projects, yes. The non-permanence risk report is updated with each verification and determines the buffer contribution for that issuance.

Sources

  1. Verra – VCS Program details
  2. Verra
Ask a specialist