How to Build Restoration Monitoring That Funders and Carbon Investors Trust
Bernat Fortet ·
A restoration monitoring system earns a funder's trust when any number in a report can be traced back to the records behind it: which site, which visit, which photos, which person. For a carbon project, that same record is what a verifier reviews. Build it in this order:
- Agree on indicators and definitions with funders, or take them from your carbon methodology, before the first season.
- Tie every record to a place with a boundary and a stable ID.
- Capture evidence in the field with the observation, not in a separate folder.
- Use remote sensing for context and cross-checks across large areas.
- Review data while the season is running, not when the report is due.
- Report from the same records your team uses to run the work.
Each step is ordinary. Trust comes from keeping them connected, so a report is a view of the work and not a separate document assembled at the end.
What funders and investors ask
Most funder questions come down to a few:
- Where did the work happen, and can I see it on a map?
- What was done: how many trees, which species, how many hectares?
- When did it happen, and what has happened since?
- How is it doing now? Survival, growth, cover, species observed.
- How do you know? What evidence sits behind each number?
- Will it hold up? For carbon investors: can the baseline, measured plots and project activities be shown to a verifier?
The last two questions are the ones that separate a monitoring system from a reporting template. Our five-question planting data audit is a quick way to test whether your current data can answer them.
Build each part of the monitoring system
1. Define restoration monitoring indicators
Pick indicators that match the decisions your team and funders need to make, and write down exactly how each is calculated. "Trees planted" needs a rule for replanting. "Survival" needs a monitoring unit and a time after planting. "Hectares restored" needs a definition of restored.
Use a framework where you can. The UN Decade's Framework for Ecosystem Restoration Monitoring (FERM), the WRI Restoration Monitoring Tools Guide
and funder or methodology requirements give shared language, which makes reports comparable across projects. Our comparison of restoration monitoring tools covers where each fits. Agreeing on this up front is cheaper than reconciling definitions after a season of data.
2. Tie every record to a place
Every observation should point to a site, planting area, plot or tree with a boundary or location. Projects and partners can sit above it in a hierarchy, so you can move from a programme view to a single plot. Without the place, numbers can be added up but not checked.
3. Capture field evidence with the observation
Photos, GPS and structured answers belong on the record they support, captured at the same time. A photo in a shared drive named IMG_2041.jpg is evidence nobody can find later. A geotagged photo attached to "Plot 14, second visit" is evidence a funder can open.
Field teams often work without signal, so the capture tool needs to work offline and sync later. Our guide to field-data apps compares the main options.
4. Cross-check with satellite and drone imagery
Satellite and drone imagery show change across areas too large to visit, and give an independent view of the field records. Use them alongside field data, not instead of it. Satellite imagery shows canopy and cover change, but rarely young seedlings or species. High-resolution drone surveys can help in suitable conditions, with field checks. Who did the work still comes from your records.
5. Review monitoring data during the season
Set up checks that flag missing fields, overlapping boundaries, records outside their site and numbers that do not add up. Run them as data arrives, early enough to send someone back to the field. Found at report time, the same issues are harder to fix, and an observation that was never collected cannot be collected again. We explain why in reporting vs. operations.
6. Report to funders from the same records
When reports, dashboards and donor portals read from the records your team works with, you stop rebuilding the numbers for each report. Keep the review, approval and reporting-period snapshots a funder requires. Each audience gets a selected view: a funder sees their projects, the public sees what you choose to share, and internal records stay private.
Ask, too, how you would get your data out. A full export with IDs, geometry, photos and relationships protects the record if you change tools.
Where monitoring systems usually break
| What you notice | Usual cause | What fixes it |
|---|---|---|
| Report numbers change each time someone rebuilds them | Definitions live in people's heads, not in the system | Written indicator definitions, calculated the same way every time |
| Survival cannot be calculated for some sites | Monitoring visits do not link to planting records | Stable IDs and a monitoring unit decided before planting |
| Photos exist but cannot be matched to plots | Evidence stored apart from the records | Photos captured on the record, with GPS |
| Errors found only at report time | No review step during the season | Checks that run on every sync |
| Partners report in different formats | No shared structure across the programme | Agreed shared records, with local detail kept per partner |
Monitoring ARR carbon projects for verification
Afforestation, reforestation and revegetation (ARR) carbon projects add a methodology and third-party verification. The methodology sets much of the monitoring design. Verra's VM0047 v1.1, for example, has two approaches, and eligibility decides which applies. The area-based approach, for projects that create or grow forest, combines field sample plots with a performance benchmark from remote sensing that compares the project to matched control plots. The census-based approach, for dispersed planting such as agroforestry that does not change land use, counts every planting unit and measures a sample of them (methodology document
). Our guide to VM0047 field data covers what the field team records, and carbon standards for nature projects compares the other standards.
Whichever applies, the monitoring record has to carry the project from the start:
- Land and eligibility. Property boundaries, land cover and eligibility checks, linked to landowner records and contracts.
- Baseline and plots. Baseline imagery and field data, and the sample plots or trees the methodology measures, with stable IDs.
- Activities. Planting, maintenance and replanting, each tied to its planting area and date.
- Monitoring events. Repeat measurements of the plots or planting units the methodology samples, with photos, GPS and who collected them.
- History. What changed in each record, and when, so a verifier can follow it.
Software does not certify credits; the standard and its verifiers do. The goal is a record good enough that verification is not a reconstruction. For the tools involved, see ARR carbon monitoring software and Restoration Scope for carbon projects.
Biodiversity monitoring
Biodiversity monitoring adds survey protocols, sampling events and species identification. Keep each observation linked to where, when and how it was collected, with its photos or recordings, and make expert review part of the workflow. Restoration Scope is early here, with one engagement so far; see Restoration Scope for biodiversity for what we can and cannot say yet.
Where Restoration Scope fits
We build digital infrastructure for nature projects: we connect a team's field data, maps and workflows so they can see their operations, make better decisions and show funders credible evidence. For carbon project teams, that means land acquisition, field operations and monitoring in one place. It also suits restoration organizations whose monitoring spans many sites, partners or seasons, and whose reports take too long to assemble or are hard to trace back. We configure the records, workflow stages, maps, permissions and data connections around your operating process.
- Keep your tools. The data platform connects spreadsheets, survey forms such as Kobo, GIS files and photos into one project, with quality checks we set up with you.
- Capture in the field. The field app records observations, photos and GPS offline and syncs when a connection returns.
- Run your methods on the map. Geospatial workflows run your team's analysis on the same boundaries.
- Report from the work. The app platform and donor portals give each audience its own view of the same records.
For a multi-partner example, read how Acción Andina brought its partners' field data into one vetted system it can share with funders and the public, or see Restoration Scope for multi-partner programmes.
It is not the right fit if a funder's own platform already covers your reporting and your operations are simple, or if you want to configure everything yourselves without a scoped setup.
Start with one funder question
- Pick one question a funder or verifier asks every year, such as survival by site or measurements for each plot.
- Trace one recent answer back to its records. Note every manual step.
- Write down the definition and the monitoring unit behind it.
- Make the next season's field form capture that evidence on the record.
- Set up one check that would have caught last season's most common error.
If that one answer becomes traceable, the rest of the system can be built the same way.