Aggregating Smallholders into One ARR Project

Updated 2026-11-02 · 4 min read · By the akar.earth specialist team

Smallholder carbon aggregation in Indonesia: grouping farmers into one ARR or agroforestry project, contracts, benefit-sharing, data and verification needs.

Smallholder carbon aggregation bundles many small farms into one project, so that shared costs for design, validation, monitoring and verification are spread across enough hectares and trees to be viable. It works when an aggregator has clear agreements with each farmer, a fair and transparent benefit-sharing model, and a data system that tracks every farm, plot and tree over the crediting period.

Why aggregation is necessary

A single farm of one or two hectares cannot carry the fixed costs of a carbon project. Aggregation creates scale, and grouped project rules let new farms join over time. In Indonesia this matches reality: much tree cover outside the forest estate sits on smallholder land in agroforestry systems, with coffee, cocoa, rubber, spices and fruit trees.

Indonesian policy also points this way. Permenhut 6/2026 names social forestry, customary forests and communities as legitimate, equal participants in forestry carbon trading. See social forestry carbon.

Aggregation models

Step by step

1. Define eligibility criteria for farms: location, land status, prior land cover, minimum tree commitments. These become the grouped project’s criteria. See grouped projects.
2. Engage communities before signing anyone up. Explain carbon, obligations, risks and revenue in local languages. See community engagement.
3. Register farmers and plots with identity, tenure evidence, polygons and consent. See farmer registration and consent.
4. Sign agreements covering carbon rights transfer or assignment, obligations (keep trees, allow monitoring), duration, payments, exit and dispute resolution.
5. Agree benefit-sharing. Who gets what share, when, and in what form (cash, inputs, services). Publish it. See benefit-sharing.
6. Plant and support. Seedlings, training, extension visits.
7. Monitor tree by tree or plot by plot, often with farmer participation using mobile measurement.
8. Manage the group. Add new farms at verification, handle drop-outs, update the buffer and risk assessments.

Benefit-sharing that holds

• Pay something early. Carbon revenue arrives years after planting; farmers need a reason to protect trees in year one. Advance payments, input support or prepayment-funded stipends help.
• Link payments to verified results, but keep a predictable base.
• Make deductions transparent: aggregator costs, buffer, verification, reserves.
• Provide a working grievance mechanism.
• Consider Indonesia’s benefit-sharing rules for state forest and social forestry areas.

Governance and decision-making

Aggregated projects run for decades, so governance matters as much as contracts. Set up a farmer representative body or use the cooperative board to review benefit-sharing, hear grievances and approve changes to project rules. Publish annual summaries of credits issued, revenue received, costs deducted and payments made. Rotate representatives and include women and younger farmers. Transparent governance reduces drop-outs and makes the project stronger in buyer due diligence.

Handling churn

Farms change hands, farmers migrate, and some leave. Agreements should say what happens to trees and carbon obligations when land is sold or inherited, how a farmer exits, and how reversals from exits are reported. Budget for re-enrolment and keep a waiting list of eligible farms to replace leavers in the next verification period.

Common mistakes

• Signing farmers before explaining long-term obligations.
• Contracts only in a language farmers do not read.
• No tenure check, so parcels overlap or are disputed.
• Treating drop-outs as rare. Plan for churn.
• One-size benefit-sharing that ignores women, tenants or landless labourers who do the work.
• Separate data systems for carbon, certification and EUDR, so farmers are surveyed three times.

What good evidence looks like

A VVB and buyer due diligence team will want: the eligibility criteria and evidence each farm meets them; signed agreements and consent records; the farmer and plot register with polygons; benefit-sharing policy and payment records; grievance logs; and monitoring data linked to farm IDs. For Plan Vivo-style projects, governance and participation records carry extra weight.

Linking to EUDR

Many aggregated farmers grow EUDR commodities. Plot polygons, deforestation-free checks and farmer records collected for carbon can serve EUDR due diligence too, and vice versa. See one dataset for carbon and EUDR.

akar mapper supports farmer and plot registration at scale. For standards suited to community projects, see Plan Vivo. More on the ARR hub.