For project developers
Forest monitoring for project developers
Know what is happening across your sites and what evidence your next project decision needs. Mynzo supports forest and carbon monitoring with satellite analysis and field data, from an initial site review to monitoring an established project.
The approach
What monitoring support does a project developer need?
Forest project developers need observations they can connect to defined areas, dates and methods. Mynzo helps teams assess forest condition, change and carbon estimates within an agreed scope. Monitoring supports project decisions and reporting; project design, land rights, financing, validation and credit issuance involve additional responsibilities.
Start with the decision in front of you
For a new project, the immediate question may be whether the available land records and observations are enough to plan further work. For an established project, it may be where conditions have changed or which measurements need updating before a report.
Agree the intended use before commissioning analysis. A site screening, an operational update and evidence for a crediting programme have different requirements. Ask Mynzo to confirm which questions the available data can answer, which need fieldwork and which sit outside the engagement.
One developer in Assam asked, do we need to get some sort of verification first?
in a public project-development discussion. In the VCS process, validation assesses the project design; verification assesses monitored outcomes. They are distinct assessments, although a project may combine them in one review.
Separate the mapped area from the carbon baseline
A boundary says where the analysis applies. Record its version, excluded areas and the dates when sites entered or left the project. Otherwise, a changed project footprint can distort a comparison between reporting periods.
A carbon baseline describes the scenario against which project outcomes are assessed under the selected method. Historical imagery can provide relevant observations, but it does not establish that scenario on its own. Verra’s project-description guidance also requires the proponent to address additionality and define monitored parameters.
Keep these questions separate in your brief: what area should be measured, what happened there, and what method will be used to assess the project’s contribution?
Make the evidence useful to the next person
A map is more useful when the field team, analyst and reporting lead can identify the records behind it. Use this checklist to discuss the required handover with Mynzo. Confirm the available formats and outputs in the proposal.
| Evidence | What to agree |
|---|---|
| Site register | Stable site identifiers, boundary versions, area units and an owner for corrections. |
| Observation record | Image dates, field dates, data sources and gaps that affect comparison. |
| Analysis | Definitions, calculation methods, validation evidence and uncertainty. |
| Change review | Which changes need investigation and how field findings will be recorded. |
| Reporting handover | Reporting period, reviewer needs, delivery format and responsibility for resolving questions. |
The digital MRV guide explains how observations, calculations and review fit together. This checklist helps specify what your project team needs from that work.
Test the difficult sites before expanding coverage
Include different site conditions in a pilot: a small parcel, an older planting, a recently disturbed area and a site with incomplete records, where these occur in your project. Define what a useful result must show and compare it with appropriate reference observations.
For biomass work, field locations and dates matter. GEDI’s calibration guidance, for example, pairs forest inventory with lidar observations and records plot geometry and geolocation accuracy. It illustrates why a reference dataset needs more than a total tree count; its specifications are not a universal project protocol.
Ask which estimates can be supported now and what additional measurements would change the assessment. Read about satellite forest monitoring before deciding the coverage and revisit schedule.
Give restoration and biodiversity their own measures
If your project reports habitat recovery as well as carbon, define both sets of questions at the start. A growing canopy does not, by itself, demonstrate recovery of native species or habitat quality. Agree which habitat observations can inform the assessment and which species questions require ecological surveys.
Use the restoration metrics guide to prepare a discussion with your ecological team, then explore biodiversity monitoring with Mynzo. Confirm the indicators, field responsibilities and geographic suitability before committing to a reporting claim.
Gold Standard’s Nature Activities Hub lists methodology, safeguarding and stakeholder requirements separately. A monitoring contract should identify the evidence it supplies and the wider project obligations that remain with the developer.
Plan around the sites you actually manage
India: distributed farm and plantation sites
For a programme across separate holdings, ask how parcels, planting dates and field records will be matched. Identify who can resolve a boundary discrepancy and revisit a plot. Plan measurements around local access and seasonal conditions. These are scoping considerations, not evidence that every planting qualifies for carbon credits.
Global portfolios: comparable, local evidence
Use common units and reporting definitions across countries while retaining each site’s method, season and limitations. Check whether reference data represents the local vegetation. Start with representative sites and confirm monitoring coverage before expanding a portfolio engagement.
Prepare a brief the technical team can assess
For a first discussion, outline the project in a few points:
- Sites: country, approximate area, number of parcels and whether mapped boundaries exist.
- Stage: early assessment, active planting, restoration or ongoing monitoring.
- Decision: what the next report or site review needs to establish, and by when.
- Records: available field measurements, previous assessments and major data gaps.
- Method: selected programme or methodology, if any, and the people responsible for reporting and review.
Request a scope covering assumptions, fieldwork, deliverables, costs and exclusions. Confirm how unresolved data issues will be handled before relying on a result in a project report.
Questions and answers
What is a carbon project developer?
A carbon project developer organizes a project intended to reduce emissions or remove carbon and manages the work needed under its chosen crediting programme. That can include project design, implementation, documentation and monitoring. The developer may commission specialist analysis and independent assessment rather than perform every task internally.
Can Mynzo finance or certify my project?
This engagement concerns forest analysis and monitoring evidence. It does not promise project finance, certification, credit buyers or credit issuance. Specify any wider support you need in the enquiry so that responsibilities can be confirmed before work is agreed.
Is it worth discussing a project before all field data is available?
Yes. Describe the records you have and the decision you need to make. An initial discussion can identify what needs checking before analysis is scoped. Estimates may remain limited until suitable field observations are available; incomplete records should be disclosed rather than treated as measured evidence.
Can an existing monitoring programme use Mynzo?
Bring its monitoring plan, data definitions, reporting timetable and known gaps to the discussion. Confirm whether the proposed analysis fits those requirements and who must approve any method change. Using a new provider does not automatically make old and new measurements comparable.
Discuss your project’s monitoring needs
Tell us where your sites are, what records you have and the decision or report you are preparing for.