top of page
Search
Survey builder screen with the canal block type field beside the headline Is the canal block still holding

Peatland REDD+ monitoring: a five-survey package for canal blocks

Writer: Nick
Nick
Nov 11
9 min read

Peatland REDD+ monitoring has to answer two questions at once: is the peat staying wet, and are the people and species around it better off? Satellites help with the first, but someone still has to stand at each canal block and look. This post walks through the five-survey peatland package on our Central Kalimantan use-case page: what each survey records, how the record is stored, and what a verifier could trace from it.


A note on status first. The page documents a survey configuration designed for a REDD+ peatland project in Central Kalimantan, set to run from September to December 2025. It reports no monitoring results, and nothing below should be read as one.


Why peatland REDD+ monitoring starts with water

Drained peat dries out, and dry peat burns. The 2015 fire season in Indonesia showed the cost: Kiely et al. (2021) in Nature Communications estimate that the 2015 fires "resulted in economic losses totalling US$28 billion", against a World Bank estimate of US$16.1 billion. The authors put the gap largely down to long-term health impacts, which the World Bank figure leaves out.

Stat card: Indonesia's 2015 fires, estimated losses of US$28 billion (Kiely et al.) and US$16.1 billion (World Bank)
Two estimates of the economic losses from Indonesia's 2015 fires. Source: Kiely et al., Nature Communications 12:7044 (2021).

So rewetting work in drained tropical peat centres on blocking the drainage canals, letting the water table rise again. A UN-REDD article published on 2 June 2026 puts it plainly: "monitoring peatlands requires more than tracking tree cover", and "field data remains essential" alongside satellite tools.


Field research in Central Kalimantan shows why the blocks themselves need watching. Ritzema et al. (2014) tested dams built from local materials in the former Mega Rice Project area. Water tables rose behind them, but the higher water did not fully offset faster subsidence near the canals, and erosion along the canals increased the risk of water overtopping the dams in heavy rain. A dam built in year one is not proof of rewetting in year three.


What VM0007 and the CCB Standards ask a project to show

Under Verra's VCS Program, the main reference for peatland REDD+ is VM0007, the REDD+ Methodology Framework, v1.8, which has been active since 4 June 2024. Verra's page says it applies to "forest lands, forested wetlands, forested peatlands and tidal wetlands" and lists peat modules for "peatland rewetting and conservation project activities", BL-PEAT for the baseline and M-PEAT (VMD0046) for monitoring.


The peat rules are changing. Verra is developing a separate Methodology for Tropical Peatland Conservation and Restoration, led by a consortium Verra calls TroPeat. Its page lists the status as "Concept Note" and the stage as "Under Development", with no dates. Once finished, it will "replace the peat modules currently included under VM0007".


Projects can also seek validation under the Climate, Community & Biodiversity Standards, which ask projects to show benefits for local communities and biodiversity as well as for the climate. That is where the community and species surveys come in.


CitizenClimate's data is structured to align with the monitoring requirements of Verra VCS, Gold Standard, Plan Vivo, Puro.earth and Carbon Standards International. CitizenClimate is not certified, accredited or endorsed by any standard body, and it does not issue credits. We are not affiliated with Verra. Our Verra alignment page lists the methodologies it covers; whether a project's monitoring meets its methodology is for the standard and the verifier to judge.


The five-survey package at a glance

The package splits the work by question. One survey watches the canal blocks, one gathers community species knowledge and threat reports, and three score social and environmental change against UN SDG indicators.


Survey

What a monitor records

Verifier question it speaks to

Settings on the page

Peat Swamp Rewetting

Block type, leakage, water level, water quality, peat moisture, new plants, wildlife, photos, bird audio

Are the canal blocks holding water?

GPS on, continuous, 15 points, currency reward of 5 units

Biodiversity

Native plants and animals people can name, threatened species sightings, threats seen

What lives here, and what threatens it?

GPS on, continuous, 15 points, currency reward of 5 units

SDG 15: Life on Land

Weighted questions on forests, land and biodiversity

Is the land better protected?

GPS on, 30 points, no currency reward

SDG 5: Gender Equality

Weighted questions, including indicators 5.1.1 and 5.3.1

Are women and girls better off?

GPS on, 30 points, no currency reward

SDG 10: Reduced Inequalities

Weighted questions, including indicator 10.1.1

Are the poorest households gaining?

GPS on, 30 points, no currency reward


Survey 1: peat swamp rewetting at each canal block

The Peat Swamp Rewetting survey is answered at a canal block. It is set as a continuous survey, so monitors can return to the same block on each visit and the project builds a history per block rather than a single snapshot.

Peat Swamp Rewetting survey settings: GPS on, Sept to Dec 2025 timeframe, 15 points, currency reward of 5
Survey settings for the Peat Swamp Rewetting survey, as configured on the use-case page. Real app screen.

The nine fields on the page cover:


  1. Type of canal block constructed: earth/soil dam, wooden planks, concrete barrier, stone/rock fill or combination materials, with custom input allowed.

  2. Signs of water leakage around the block: a required yes or no.

  3. Current water level behind the block: five plain-language levels, from "Very high (overflowing)" to "No standing water".

  4. Water quality behind the block: clear, slightly murky, brown/muddy, very dark or stagnant/smelly. The page notes that very dark water is typical of a healthy peat swamp, so this field describes the water body rather than grading it.

  5. Peat moisture near the block: from "Very wet/saturated" to "Very dry/cracking".

  6. New plant growth since rewetting: an optional yes or no, since regrowth may not be visible early on.

  7. Wildlife activity in the rewetted area: increased, same as before, decreased or none observed.

  8. Photos, set to low quality for slow connections.

  9. An audio recording of bird calls, also at low quality.

Required survey field for water quality behind a canal block, five options from Clear to Stagnant/smelly
Field 4 of the Peat Swamp Rewetting survey in the survey builder. Real app screen.

The record matters as much as the questions. The Data Integrity and Methodology Protocol says an offline record keeps the time it was made, with "the sync date recorded separately", and that GPS accuracy is stored with each reading. Surveys that require a location "won't start without a GPS fix". Submissions can never be deleted; a faulty one is archived with a reason from a fixed list. Editing a survey later never changes data already collected.


What a visual record cannot do

A water level of "halfway up block" is an observation, not a measurement of water table depth. Research networks use instruments for that: the UN-REDD article describes about 70 km of transects and more than 370 dipwells in one Central Kalimantan peat dome. A community survey complements instruments like these. It does not replace them.


The survey builder supports number questions as well as multiple choice, so a project that has dipwells or staff gauges at its blocks could add a field for the reading, taken on the same visit and stored with the same timestamp and GPS point. How water table depth enters the carbon calculation is set by the methodology and the project's monitoring plan, not by the app. The platform also does not enforce a sampling protocol: it records what monitors submit.


Survey 2: species sightings and threats

The Biodiversity survey starts with what people already know. Two optional text questions ask monitors to name three native plants and three native animals in their area. Over time, the answers show whether taking part is building local knowledge.


A required question asks whether the monitor has seen any listed threatened species, with "None" as an option and custom input for anything missing. A second required question asks about threats: illegal logging, forest fires, land clearing, river pollution, hunting of protected species and littering. A fire report with a GPS point gives the project a place to send someone.


Two cautions. The species list on the page mixes flagship species from across Indonesia, so a project would edit the options to the species its monitors could actually meet in their own landscape. And a report is a record, not an enforcement action: what happens next depends on the project and the authorities.


Bird recordings are identified by BirdNET, developed by the Cornell Lab of Ornithology and Chemnitz University of Technology, once the phone is back online. AI identification does not run offline; recordings are saved and identified on reconnection. Results come back with a confidence score and IUCN status. The biodiversity monitoring module does not treat AI output as ground truth: an ecologist can inspect and override any identification.


Community observers are good at this kind of local detection. In a study in Central Vietnam, Pratihast et al. (2012) found community members collected forest data with "accuracy comparable to expert measurements (index of agreement greater than 0.88)". In that study, local reports picked up small-scale degradation that the SPOT imagery largely missed, though they underestimated the area of one large deforestation event compared with the satellite-based estimate.


Surveys 3 to 5: weighted SDG scores for CCB co-benefits

The three SDG surveys turn community answers into scores. Under the Protocol, each answer option carries a score from 0 to 100, each question carries a weight, and "the final submission score is the weighted average of all field scores". Questions can be tagged to official UN indicator codes, as our guide to measuring SDG impact explains.


The page shows three of those weights in the Kalimantan configuration:


  • SDG 5, indicator 5.1.1, weight 1.6: whether customary law and tradition in the community support gender equality.

  • SDG 5, indicator 5.3.1, weight 1.9: whether the respondent knows of a girl aged 15 to 18 who has been married.

  • SDG 10, indicator 10.1.1, weight 3.2: "Thinking about the poorest 40% of people in our community, has the conservation project helped increase their income or economic opportunities?"


The SDG 10 question asks directly whether the project is helping the poorest households, and its weight is the highest of the three. The SDG dashboard compares communities side by side, which could help keep a fall in one village from disappearing into a project average.


The early-marriage question is sensitive. It needs trained facilitation, and a project can use the app's consent tick box so each respondent confirms they agree to take part. The SDG surveys earn 30 points and carry no currency reward.


Where a project does offer a currency reward, as on the first two surveys, it is set per project and per survey. Points and any reward are credited on submission, and the Protocol describes a daily check that reverses them if a submission is rejected.


What a verifier could trace

A validation and verification body (VVB) can be given a read-only role. The App Guide describes it as "a read-only role for independent auditors", and the Protocol says VVBs "do not rely on PD-generated reports". Exports in CSV and JSON contain raw records, not only summaries.

Diagram: four steps from a canal block visit to sync, review with archiving, and a read-only verifier
How one canal block record reaches a verifier. Source: citizenclimate.net/protocol and /app-guide, October 2026.

For each canal block, a verifier could check:


  • every visit, with its original timestamp and GPS point, including those made offline;

  • the photos taken at the block, which cannot be deleted in the app;

  • any archived record and the reason it was archived;

  • the community's grievances, which members file without their name being shown to the project developer.


What a verifier concludes from that evidence is their call.

Illustration of two men in rubber boots building a canal block in a drained peat canal
Illustration (AI-generated): building a canal block. Not a real project, place or community.

Adapting the package to another peatland project

The page shows a configuration, and most of it is editable. A project in another peat landscape would typically:


  1. Upload its site boundary as a KML, KMZ or GeoJSON file, or draw it on the map.

  2. Rewrite the threatened species options for its own landscape.

  3. Add number fields for any dipwell or gauge readings it takes.

  4. Set points and any currency reward per survey.

  5. Run the surveys in the monitors' language. The app is available in 11 languages, including Indonesian.


Frequently asked questions

What is peatland REDD+ monitoring?

Peatland REDD+ monitoring tracks whether a project is keeping peat wet and forest standing, and what that means for the people living nearby. It combines remote sensing with field data, from water table readings and canal block checks to household surveys. Under Verra's VM0007, peat projects use dedicated modules (BL-PEAT and M-PEAT), and projects can also seek validation under the CCB Standards for community and biodiversity benefits.


Can community monitors check canal blocks?

Yes, for what can be seen at the block: its type, any leakage, where the water sits against it and how wet the peat is nearby, with photos and a GPS point. Visual categories are not water table measurements, so projects with dipwells or gauges should record those readings too. Research in Central Kalimantan (Ritzema et al., 2014) found erosion near canals can raise the risk of dams overtopping. Regular visits at least give a record of how the canal edges are changing.


Does the CitizenClimate app work without a signal?

Yes. Surveys, lessons and recent submissions stay on the phone, and offline submissions queue with the time and place they were recorded, then send automatically. Some features need a connection: the leaderboard, the forum, the dashboards and finishing an AI species identification. Bird recordings made offline are identified once the phone reconnects.


Is this five-survey package a finished pilot?

No. The use-case page documents a survey configuration for a REDD+ peatland project in Central Kalimantan, set for September to December 2025, and reports no monitoring results. Read it as a worked example of how the surveys could be set up for a peatland project, not as evidence of outcomes.


Start with the surveys

The Central Kalimantan use-case page shows every field in the package. To build your own, download the free app, or read the App Guide first.

Comments


bottom of page